docs: drop the permission-layer node from the architecture diagram
The diagram used to start with a permission-layer diamond naming an upstream package. Removed that node and its edges: the request now flows straight into L1, which is the accurate picture - this package does not own the permission layer at all. - README.md / README.en.md: mermaid source updated (no P node, no P edges) - 00-architecture.png re-rendered: 1042x1588, five sections + two tool exits
This commit is contained in:
parent
dc7477e088
commit
033c3d158f
@ -57,8 +57,7 @@ So the right structure is by **layer**, where each layer owns a different stage:
|
|||||||
|
|
||||||
```mermaid
|
```mermaid
|
||||||
graph TD
|
graph TD
|
||||||
U[User request] --> P{Permission layer<br/>host patches}
|
U[User request] --> L1
|
||||||
P -->|tools runnable| L1
|
|
||||||
|
|
||||||
subgraph "moyun-ultimate five sections"
|
subgraph "moyun-ultimate five sections"
|
||||||
L1["L1 persona core · order 100<br/>6003 B"]
|
L1["L1 persona core · order 100<br/>6003 B"]
|
||||||
|
|||||||
@ -60,8 +60,7 @@ config 覆盖类 改官方 cordis config(system-prompt / approval / permissio
|
|||||||
|
|
||||||
```mermaid
|
```mermaid
|
||||||
graph TD
|
graph TD
|
||||||
U[用户请求] --> P{权限层<br/>宿主补丁}
|
U[用户请求] --> L1
|
||||||
P -->|工具可执行| L1
|
|
||||||
|
|
||||||
subgraph "moyun-ultimate 五段注入"
|
subgraph "moyun-ultimate 五段注入"
|
||||||
L1["L1 人格内核 · order 100<br/>双槽主核 6003 B"]
|
L1["L1 人格内核 · order 100<br/>双槽主核 6003 B"]
|
||||||
|
|||||||
Binary file not shown.
|
Before Width: | Height: | Size: 148 KiB After Width: | Height: | Size: 133 KiB |
Loading…
Reference in New Issue
Block a user