A task becomes a plan; each step runs through the proven
P1–P6 governed loop — retrieve → quarantine untrusted →
tool-call → deny-by-default policy gate → Λ kernel check (advisory) → emit —
behind a durable HumanApprovalGate, emitting a signed, hash-chained DSSE receipt you can
re-verify in the browser. This is the real engine (a11oy_code_engine), not a redirect.
engine: probing…signature: probing…HumanApprovalGate: probing…behavior profiles: probing…plan: MODELEDexecution: LIVE-when-engine-upΛ = Conjecture 1 (advisory, never a gate)Doctrine v11 LOCKED 749/14/163
1 · Describe the task
Nothing is fabricated. If the engine can't be reached, every panel says so honestly — no fake orchestration.
A behavior profile attaches a governed persona to each step: its system layer is Λ-gated, sha256-provenanced and folded into the step's signed receipt;
the swap is logged to /llm/forum. Behavior transfer is MODELED (disposition only — capability ceiling unchanged). Λ = Conjecture 1 (advisory).