11# OntoLoop Sovereign OS (Engineering Runtime)
2-
3- OntoLoop 鏄竴涓潰鍚戔€滄不鐞?+ 鎵ц + 瀛︿範 + 鍥炴斁鈥濈殑 AI 涓绘潈杩愯鏃躲€傚綋鍓嶇増鏈凡缁忚繘鍏ュ彲楠屾敹宸ョ▼鎬侊紝鍏峰娌荤悊闂幆銆佹墽琛岄棴鐜€佽瘉鎹棴鐜拰瀛︿範闂幆銆?
4- ## 鎴戜滑鐜板湪鏈夊摢浜涜兘鍔?
5- - 娌荤悊涓婚摼锛歅olicy / Tenant / Approval / Risk / Budget / Rollout
6- - 鎵ц涓婚摼锛欳apability Admission -> Trust Admission Kernel -> Runtime Guard -> Layered Tool Stack -> Execution Fabric
7- - 璇佹嵁涓婚摼锛欵vidence Tagger -> Flow State Engine -> Trust Evidence Ledger锛坔ash-chain锛?- 瀛︿範涓婚摼锛歀earning Proposal -> Promotion Gate -> Private Memory / Org Knowledge
8- - 鍙娴嬩富閾撅細Telemetry Collector -> Policy Signal Aggregator -> Query/Replay/Explanation Plane
9- - TrustKernel锛圢oumenonCore锛夎瀺鍚堬細韬唤璇佹槑銆乤ttestation銆佷緵搴旈摼楠岃瘉銆佸己鍒堕棬绂併€佸彲鍥炴斁瀹¤
10-
11- ## 鏋舵瀯涓婚摼锛堢畝鐗堬級
12-
2+ OntoLoop is an AI sovereign runtime oriented to ** Governance + Execution + Learning + Replay** .
3+ The current version has entered a production-ready engineering phase, featuring closed-loop capabilities for governance, execution, trust verification and continuous learning.
4+
5+ ## Core Capability Modules
6+ - Governance Pipeline:Policy / Tenant / Approval / Risk / Budget / Rollout
7+ - Execution Pipeline:Capability Admission → Trust Admission Kernel → Runtime Guard → Layered Tool Stack → Execution Fabric
8+ - Trust Pipeline:Evidence Tagger → Flow State Engine → Trust Evidence Ledger (Hash-chain)
9+ - Learning Pipeline:Learning Proposal → Promotion Gate → Private Memory / Org Knowledge
10+ - Observability Pipeline:Telemetry Collector → Policy Signal Aggregator → Query/Replay/Explanation Plane
11+ - TrustKernel (NoumenonCore) Integration:Identity Authentication, Attestation, Supply Chain Validation, Strong Isolation, Replayable Audit
12+
13+ ## Architecture Pipeline (Compact Version)
1314``` text
1415[User/Trigger]
1516 -> [Structured Transport + Session Bridge]
@@ -33,27 +34,24 @@ OntoLoop 鏄竴涓潰鍚戔€滄不鐞?+ 鎵ц + 瀛︿範 + 鍥炴斁
3334 -> [Next Iteration]
3435```
3536
36- ## 蹇€熷紑濮?
37- ### 1) 鐜瑕佹眰
38-
37+ ## Quick Start
38+ ### 1) Environment Requirements
3939- Rust toolchain
40- - 鍙€夛細StateStore CLI
41- - 鍙€夛細Docker / Docker Compose
42-
43- ### 2) 鏈湴杩愯
40+ - Optional: StateStore CLI
41+ - Optional: Docker / Docker Compose
4442
43+ ### 2) Local Execution
4544``` powershell
4645cargo run --manifest-path .\Cargo.toml -- --message "Build a governed autonomous loop" --swarm
4746```
4847
49- ### 3) 鏈湴妫€鏌?
48+ ### 3) Local Validation
5049``` powershell
5150cargo check --workspace --manifest-path .\Cargo.toml
5251cargo test --workspace --manifest-path .\Cargo.toml
5352```
5453
55- ## 甯哥敤鍛戒护
56-
54+ ## Common CLI Commands
5755``` powershell
5856cargo run --manifest-path .\Cargo.toml -- system health
5957cargo run --manifest-path .\Cargo.toml -- --session demo system replay-report
@@ -62,69 +60,67 @@ cargo run --manifest-path .\Cargo.toml -- --session demo focus board
6260cargo run --manifest-path .\Cargo.toml -- --session demo org context
6361cargo run --manifest-path .\Cargo.toml -- bridge status
6462cargo run --manifest-path .\Cargo.toml -- knowledge batch-export --anchor-list .\deploy\anchors.txt --type graph
65- cargo run --manifest-path .\Cargo.toml -- trigger webhook --anchor-id cli:focus --topic order.created --payload "{"" order_id"": "" A-1001" "}" --run-now
63+ cargo run --manifest-path .\Cargo.toml -- trigger webhook --anchor-id cli:focus --topic order.created --payload "{\" order_id\": \" A-1001\ "}" --run-now
6664cargo run --manifest-path .\Cargo.toml -- --session cli:focus system export
6765cargo run --manifest-path .\Cargo.toml -- --session cli:focus frontend status
6866cargo run --manifest-path .\Cargo.toml -- --session cli:focus frontend events --format pretty --limit 20
6967```
7068
71- CLI frontend is additive. Existing app frontend directories such as ` dashboard-ui/ ` are preserved for later application surfaces.
72-
73- ## 楠屾敹鑴氭湰
69+ The CLI frontend is designed additively. Existing frontend directories such as ` dashboard-ui/ ` are fully reserved for subsequent application interface expansion.
7470
71+ ## Acceptance Scripts
7572``` powershell
7673powershell -ExecutionPolicy Bypass -File .\deploy\scripts\p95_acceptance.ps1
7774powershell -ExecutionPolicy Bypass -File .\deploy\scripts\pq9_acceptance.ps1
7875powershell -ExecutionPolicy Bypass -File .\deploy\scripts\week6_acceptance.ps1
7976powershell -ExecutionPolicy Bypass -File .\deploy\scripts\trigger_supermemory_acceptance.ps1
8077```
81- Linux: ` bash ./deploy/scripts/week6_acceptance.sh `
8278
83- 杈撳嚭璇佹嵁锛?
79+ Linux Environment:
80+ ``` bash
81+ bash ./deploy/scripts/week6_acceptance.sh
82+ ```
83+
84+ Output Artifacts:
8485- ` deploy/runtime/p95-acceptance.log `
8586- ` deploy/runtime/p95-acceptance.json `
8687
87- ## 鐩綍缁撴瀯
88-
89- - ` src/ ` 锛氭牳蹇冭繍琛屾椂涓庢不鐞嗛€昏緫
90- - ` src/query_engine/ ` 锛歵urn state / continuation / compactor / loop
91- - ` src/runtime/ ` 锛歡uard / admission / execution / evidence / flow
92- - ` src/security/ ` 锛歱olicy / permission mode / capability admission
93- - ` src/session/ ` 锛歝heckpoint / resume / runtime
94- - ` src/memory/ ` 锛歮emory + supermemory pipeline
95- - ` src/observability/ ` 锛歝ollector / query plane / replay explanation
96- - ` src/transport/ ` 锛歴tructured transport + bridge
97- - ` src/plugins/ ` 锛歱lugin lifecycle
98- - ` src/skills/ ` 锛歴kill registry / builder pipeline
99- - ` src/services/ ` 锛歴ervice mediation spine
100- - ` tests/ ` 锛欵2E + 鍥炲綊娴嬭瘯
101- - ` deploy/scripts/ ` 锛氶獙鏀朵笌婕旂粌鑴氭湰
102- - ` docs/ ` 锛氬崗璁€佹灦鏋勩€侀獙鏀舵枃妗?
103- ## 褰撳墠鐘舵€?
104- 褰撳墠鐗堟湰澶勪簬鈥滀富閾惧彲璺戙€佽瘉鎹彲杩芥函銆佸洖鏀惧彲瑙i噴鈥濈殑楂樺彲鐢ㄥ伐绋嬮樁娈碉紱寤鸿鎸佺画鎸? ` deploy/scripts/ ` 鍥炲綊鍚庡啀閫愭鏀惧ぇ鐢熶骇娴侀噺銆?
105-
106-
107- CLI 瑙勮寖鏂囨。锛?
88+ ## Directory Structure
89+ - ` src/ ` : Core runtime & governance logic
90+ - ` src/query_engine/ ` : Turn state / Continuation / Context Compactor / Loop Scheduler
91+ - ` src/runtime/ ` : Runtime Guard / Admission Control / Execution / Evidence Collection / Flow Engine
92+ - ` src/security/ ` : Policy Control / Permission Mode / Capability Admission System
93+ - ` src/session/ ` : Checkpoint / Resume / Runtime Session Management
94+ - ` src/memory/ ` : Private Memory + SuperMemory Pipeline
95+ - ` src/observability/ ` : Telemetry Collector / Query Plane / Replay & Trace Explanation
96+ - ` src/transport/ ` : Structured Transport / Cross-environment Session Bridge
97+ - ` src/plugins/ ` : Plugin Lifecycle Management
98+ - ` src/skills/ ` : Skill Registry / Capability Build Pipeline
99+ - ` src/services/ ` : Service Mediation & Orchestration Spine
100+ - ` tests/ ` : E2E Testing & Regression Test Suite
101+ - ` deploy/scripts/ ` : Automated Acceptance & Operational Scripts
102+ - ` docs/ ` : Protocol Specifications / Architecture Design / Acceptance Standards
103+
104+ ## Current Status
105+ The current release is in a high-maturity engineering stage: ** core pipeline runnable, data traceable, audit log explainable ** .
106+ It is recommended to complete full regression verification via ` deploy/scripts/ ` first, then gradually scale production workloads.
107+
108+ CLI Specification Document:
108109- docs/CLI_SPECIFICATION.md
109110
110111## Signal Whitebox Commands (D9/D10/D11)
111-
112- The signal pipeline is now exposed through whitebox CLI commands:
113-
112+ The internal signal pipeline is exposed via white-box CLI commands for debugging and inspection:
114113``` powershell
115114cargo run --manifest-path .\Cargo.toml -- system signal status
116115cargo run --manifest-path .\Cargo.toml -- system signal explain --trace-id <trace-id>
117116cargo run --manifest-path .\Cargo.toml -- system signal drain
118117```
119118
120- Implementation policy :
121- - Business -side signal writes must go through ` SignalFacade ` .
122- - Direct bypass writes are blocked by static scan tests.
123- - Signal acceptance is included in ` deploy/scripts/ week6_acceptance.ps1 ` and ` deploy/ scripts/week6_acceptance.sh ` .
119+ Implementation Governance Rules :
120+ - All business -side signal writes must pass through the unified ` SignalFacade ` layer .
121+ - Direct bypass write operations are blocked by static scan tests.
122+ - Signal pipeline acceptance is integrated into ` week6_acceptance ` full regression scripts.
124123
125124## Rule Reference Policy
126-
127- ` rule/ ` 下的第三方材料如需引入,仅用于设计对照与第一性抽取,不进入构建与运行时依赖。
128-
129-
130-
125+ Third-party reference materials under the ` rule/ ` directory are only used for architecture benchmarking and theoretical abstraction.
126+ These files are excluded from build dependencies and runtime execution.
0 commit comments