Codex/v0.9.6 layer runtime workflow

docs/cli-reference.md

@@ -23,8 +23,11 @@ invart run --target . --agent codex --goal "..." -- <command>
 ```bash
 invart runtime analyze-event --event '{"type":"shell","command":"rm -rf ."}'
 invart runtime shell --session demo --ledger .invart/demo.jsonl -- <command>
+invart runtime layers --ledger .invart/demo.jsonl --out-dir .invart/layers
 ```
 
+`runtime layers` exports a L1-L5 operation workflow for an existing ledger. It writes JSON and HTML that link proof, replay, path graph, coverage, audit, and evidence manifest artifacts.
+
 ### Proof and gate
 
 ```bash
@@ -44,11 +47,14 @@ invart audit report --ledger ledger.jsonl --out-dir .invart/audit
 
 ```bash
 invart adapter profile --kind claude-code
+invart adapter profiles
+invart adapter profiles --track managed_wrapper
 invart real-agent check --agent claude-code --out-dir .invart/real-agent
 invart real-agent report --run-dir .invart/real-agent --out .invart/real-agent/report.html
 ```
 
 Use `--require-live` when you want missing local agent binaries to fail the run instead of being recorded as blocked evidence. Fixture-backed runs validate the Invart adapter contract; live runs validate the installed product surface.
+The plural `adapter profiles` command lists priority agent tracks: reference full adapter, managed wrapper, native bridge, vendor/cloud evidence import, and framework trace import. Vendor import tracks are audit evidence, not Invart mediation.
 
 ### Claude Code reference adapter
 
@@ -70,5 +76,7 @@ invart eval list
 invart eval benchmark --suite full-product-readiness
 invart eval benchmark --suite v0.9.3-agent-adapter-contract
 invart eval benchmark --suite v0.9.4-claude-reference-adapter
+invart eval benchmark --suite v0.9.5-priority-agent-tracks
+invart eval benchmark --suite v0.9.6-layer-runtime-workflow
 invart roadmap status --require-full
 ```

docs/html/cli-reference.html

@@ -9,15 +9,18 @@
       <div class="card"><h3>Managed session</h3><pre>invart session start --target . --agent codex --goal "..."
 invart run --target . --agent codex --goal "..." -- &lt;command&gt;</pre></div>
       <div class="card"><h3>Runtime event</h3><pre>invart runtime analyze-event --event '{"type":"shell","command":"rm -rf ."}'
-invart runtime shell --session demo --ledger .invart/demo.jsonl -- &lt;command&gt;</pre></div>
+invart runtime shell --session demo --ledger .invart/demo.jsonl -- &lt;command&gt;
+invart runtime layers --ledger .invart/demo.jsonl --out-dir .invart/layers</pre><p><code>runtime layers</code> exports a L1-L5 operation workflow with proof, replay, path graph, coverage, audit, and evidence manifest links.</p></div>
       <div class="card"><h3>Proof and gate</h3><pre>invart proof export --ledger ledger.jsonl --out proof.json
 invart proof verify --proof proof.json --ledger ledger.jsonl
 invart gate verify --proof proof.json --ledger ledger.jsonl --mode ci</pre></div>
       <div class="card"><h3>Replay and audit</h3><pre>invart replay export --ledger ledger.jsonl --out replay.html
 invart audit report --ledger ledger.jsonl --out-dir .invart/audit</pre></div>
       <div class="card"><h3>Real agent conformance</h3><pre>invart adapter profile --kind claude-code
+invart adapter profiles
+invart adapter profiles --track managed_wrapper
 invart real-agent check --agent claude-code --out-dir .invart/real-agent
-invart real-agent report --run-dir .invart/real-agent --out .invart/real-agent/report.html</pre><p>Use <code>--require-live</code> when missing local binaries should fail instead of being recorded as blocked evidence.</p></div>
+invart real-agent report --run-dir .invart/real-agent --out .invart/real-agent/report.html</pre><p>Use <code>--require-live</code> when missing local binaries should fail instead of being recorded as blocked evidence. <code>adapter profiles</code> lists priority tracks and keeps vendor/cloud import separate from Invart-mediated control.</p></div>
       <div class="card"><h3>Claude Code reference adapter</h3><pre>invart adapter claude-code \
   --target . \
   --out-dir .invart/claude-reference \
@@ -28,6 +31,8 @@
 invart eval benchmark --suite full-product-readiness
 invart eval benchmark --suite v0.9.3-agent-adapter-contract
 invart eval benchmark --suite v0.9.4-claude-reference-adapter
+invart eval benchmark --suite v0.9.5-priority-agent-tracks
+invart eval benchmark --suite v0.9.6-layer-runtime-workflow
 invart roadmap status --require-full</pre></div>
     </section>
   </main>

docs/html/release-history.html

@@ -32,6 +32,8 @@ <h2>0.9 Patch Track</h2>
         <tr><th>Version</th><th>Status</th><th>Focus</th></tr>
         <tr><td>v0.9.3</td><td>Implemented</td><td>Agent adapter contract registry and fixture-backed real-agent conformance foundation. The live mode can be strict, but missing local agent binaries are not reported as successful live validation.</td></tr>
         <tr><td>v0.9.4</td><td>Implemented</td><td>Claude Code reference full adapter: hook events and child command mediation, managed risk pause/block before launch, full L5 evidence package, and truthful degraded process-tree coverage when only portable subprocess supervision is active.</td></tr>
+        <tr><td>v0.9.5</td><td>Implemented</td><td>Priority agent tracks for Claude Code, Codex, Gemini CLI, Cursor, OpenCode, OpenClaw, Hermes, cloud agents, and frameworks, with profile-derived product matrix rows and explicit vendor/import versus Invart-mediated control positions.</td></tr>
+        <tr><td>v0.9.6</td><td>Implemented</td><td>Ledger-derived L1-L5 runtime operation workflow via <code>runtime layers</code>, exporting a stage x layer matrix, layer timeline, operator command guide, and linked proof/replay/path graph/coverage/audit/evidence artifacts.</td></tr>
       </table>
     </section>
     <section>

docs/html/runtime-effect-demo.html

@@ -25,6 +25,11 @@ <h2>Run</h2>
   --out-dir .invart/pre-1-demo-check
 
 scripts/container-demo.sh all .invart/container-risk-demo</pre>
+      <p>For any existing Invart ledger, generate a layer operation report:</p>
+      <pre>PYTHONPATH=src python -m invart.cli runtime layers \
+  --ledger .invart/session.jsonl \
+  --out-dir .invart/layer-workflow</pre>
+      <p>Open <code>.invart/layer-workflow/layer-runtime-workflow.html</code>. The report is derived from the ledger and links proof, replay, path graph, coverage, audit, and evidence manifest artifacts.</p>
     </section>
     <section>
       <h2>Runtime Effect Matrix</h2>
@@ -58,6 +63,18 @@ <h2>Artifact Map</h2>
         <tr><td><code>path-graph.html</code></td><td>L3 causal chain</td><td>Tracing risky paths such as secret read to network sink.</td></tr>
         <tr><td><code>coverage.html</code></td><td>L4/L5 truthfulness</td><td>Checking observed, mediated, enforced, and fail-open claims.</td></tr>
         <tr><td><code>audit-report.html</code></td><td>L5 reviewer report</td><td>Presenting the enterprise security review view.</td></tr>
+        <tr><td><code>layer-runtime-workflow.html</code></td><td>L1-L5 operation workflow</td><td>Operating a single ledger through before/during/after runtime questions.</td></tr>
+      </table>
+    </section>
+    <section>
+      <h2>Layer Operation Flow</h2>
+      <table>
+        <tr><th>Layer</th><th>Practical command</th><th>What the user gets</th></tr>
+        <tr><td>L1 Execution Surface</td><td><code>invart pre-runtime --target . --save</code></td><td>Surface inventory and unmanaged coverage gaps.</td></tr>
+        <tr><td>L2 Runtime Fact Model</td><td><code>invart runtime record-event --ledger ledger.jsonl --event '{...}'</code></td><td>Normalized invocation, resource, taint, identity, and outcome facts.</td></tr>
+        <tr><td>L3 Decision Plane</td><td><code>invart policy check-path --ledger ledger.jsonl --out path-policy.json</code></td><td>Deterministic and path-aware reasons for allow, approval, or deny.</td></tr>
+        <tr><td>L4 Mediation Plane</td><td><code>invart mediation inspect --ledger ledger.jsonl</code></td><td>Pause, block, fail-open, approval, and mediation outcome state.</td></tr>
+        <tr><td>L5 Evidence Plane</td><td><code>invart runtime layers --ledger ledger.jsonl --out-dir .invart/layers</code></td><td>A reviewable stage x layer matrix with proof/replay/graph/coverage/audit links.</td></tr>
       </table>
     </section>
     <section>

docs/release-history.md

@@ -32,6 +32,8 @@ Invart has a long local implementation history. The public docs summarize capabi
 | --- | --- | --- |
 | v0.9.3 | Implemented | Agent adapter contract registry and fixture-backed real-agent conformance foundation. The live mode can be strict, but missing local agent binaries are not reported as successful live validation. |
 | v0.9.4 | Implemented | Claude Code reference full adapter: hook events and child command mediation, managed risk pause/block before launch, full L5 evidence package, and truthful degraded process-tree coverage when only portable subprocess supervision is active. |
+| v0.9.5 | Implemented | Priority agent tracks for Claude Code, Codex, Gemini CLI, Cursor, OpenCode, OpenClaw, Hermes, cloud agents, and frameworks, with profile-derived product matrix rows and explicit vendor/import versus Invart-mediated control positions. |
+| v0.9.6 | Implemented | Ledger-derived L1-L5 runtime operation workflow via `runtime layers`, exporting a stage x layer matrix, layer timeline, operator command guide, and linked proof/replay/path graph/coverage/audit/evidence artifacts. |
 
 ## Internal History
 

docs/runtime-effect-demo.md

@@ -19,6 +19,16 @@ For isolated per-risk-case runs:
 scripts/container-demo.sh all .invart/container-risk-demo
 ```
 
+For any existing Invart ledger:
+
+```bash
+PYTHONPATH=src python -m invart.cli runtime layers \
+  --ledger .invart/session.jsonl \
+  --out-dir .invart/layer-workflow
+```
+
+Open `.invart/layer-workflow/layer-runtime-workflow.html`. This report is derived from the ledger and links the proof, replay, path graph, coverage, audit, and evidence manifest produced for that run.
+
 ## What To Look For
 
 | View | What it proves | Main artifact |
@@ -28,6 +38,7 @@ scripts/container-demo.sh all .invart/container-risk-demo
 | Path Graph | Risk chains such as secret read to external network sink can be traced. | `path-graph.html` |
 | Coverage Report | Observed, mediated, and enforced are reported as different claims. | `coverage.html` |
 | Audit Report | A reviewer can answer who, what, why, policy, approval, outcome, and coverage. | `audit-report.html` |
+| Layer Runtime Workflow | A command-level way to operate L1-L5 for a single ledger. | `layer-runtime-workflow.html` |
 
 ## Three Runtime Stages
 
@@ -47,6 +58,16 @@ scripts/container-demo.sh all .invart/container-risk-demo
 | L4 Mediation Plane | Shows allow, audit, require approval, deny, enforced block, and fail-open alert semantics. |
 | L5 Evidence Plane | Shows proof, replay, graph, coverage, audit, evidence bundle, and release gate outputs. |
 
+## Layer Operation Flow
+
+| Layer | Practical command | What the user gets |
+| --- | --- | --- |
+| L1 Execution Surface | `invart pre-runtime --target . --save` | Surface inventory and unmanaged coverage gaps. |
+| L2 Runtime Fact Model | `invart runtime record-event --ledger ledger.jsonl --event '{...}'` | Normalized invocation, resource, taint, identity, and outcome facts. |
+| L3 Decision Plane | `invart policy check-path --ledger ledger.jsonl --out path-policy.json` | Deterministic and path-aware reasons for allow, approval, or deny. |
+| L4 Mediation Plane | `invart mediation inspect --ledger ledger.jsonl` | Pause, block, fail-open, approval, and mediation outcome state. |
+| L5 Evidence Plane | `invart runtime layers --ledger ledger.jsonl --out-dir .invart/layers` | A reviewable stage x layer matrix with proof/replay/graph/coverage/audit links. |
+
 ## Boundaries
 
 The container demo uses safe equivalent trajectories. It does not install hostile packages or replay private incidents.