Status: blocked
Required mode continues to disable model-backed compaction. This issue tracks only a separately reviewed upstream/dependency seam; it does not authorize an OpenClaw upgrade, a prompt/Skill workaround, or a second Tiangong model runtime.
References: M9 design §16.1/§20.1; M9-A0 result and pinned patch evidence in smoke-testing/runs/2026-08-22-m9-a0-trusted-native-boundaries/; merged PR #117.
Exact unblock conditions — all four required
- Reviewed source seam: the pinned OpenClaw/pi-coding-agent integration exposes an awaited payload seam from every model-backed compaction path (
generateSummary/completeSimple, including context-engine-owned paths) through the same final trusted model boundary and before every selected provider transport. No supported transport or compaction branch may bypass it.
- Pinned public provenance: the proposed upstream/dependency tag, commit, source patch, SHA-256, license, and changed-file scope are reviewed and recorded; dependencies are public and immutable-pinned. No silent OpenClaw upgrade, private artifact, or unreviewed patch is accepted.
- Deterministic contract evidence: source/type/contract,
--network none container fake-provider, and deterministic integration tests prove native transforms then trusted allow on success; missing/duplicate registration, malformed result, throw, timeout, abort, and transport bypass all fail closed with zero provider requests. Activation-absent stock behavior remains covered as an adjacent regression.
- Fresh A0 re-acceptance: on the same pinned Tiangong base and candidate image, Layers 1–4 are rerun serially, including corrected Basic Matrix only after Layers 1–3 pass; direct provider-boundary and final-handler evidence, sanitized artifact hashes, cleanup proof, independent design review, and explicit authorization are all accepted.
Until all four conditions are directly evidenced and reviewed, semantic/manual model compaction remains unsupported and disabled in required mode. Session rollover is tracked separately and must not be implemented here.
Status: blocked
Required mode continues to disable model-backed compaction. This issue tracks only a separately reviewed upstream/dependency seam; it does not authorize an OpenClaw upgrade, a prompt/Skill workaround, or a second Tiangong model runtime.
References: M9 design §16.1/§20.1; M9-A0 result and pinned patch evidence in
smoke-testing/runs/2026-08-22-m9-a0-trusted-native-boundaries/; merged PR #117.Exact unblock conditions — all four required
generateSummary/completeSimple, including context-engine-owned paths) through the same final trusted model boundary and before every selected provider transport. No supported transport or compaction branch may bypass it.--network nonecontainer fake-provider, and deterministic integration tests prove native transforms then trusted allow on success; missing/duplicate registration, malformed result, throw, timeout, abort, and transport bypass all fail closed with zero provider requests. Activation-absent stock behavior remains covered as an adjacent regression.Until all four conditions are directly evidenced and reviewed, semantic/manual model compaction remains unsupported and disabled in required mode. Session rollover is tracked separately and must not be implemented here.