Governance Law
Prose is not enough. Important claims need source tracking, version history, review gates, and the ability to say no when evidence is missing. Status words follow one ladder: BUILT means the code or document exists, WIRED means it is connected to a live path, and PROVEN means it was shown working with a retained receipt. Merged is not the same as accepted or enforced, and no item below has independent installation acceptance. The source repositories are private; see Evidence & Source Access.
Adopted on 2026-10-03, by Principal instruction, as the starting point for estate governance. The contract itself says v1.3 has not been red-teamed. A rule may be called enforced only after its tests pass on a bound implementation.
A signed, read-only boot service on Supabase Edge. Each session checks its Ed25519 receipts, nonce, epoch and the pinned governance hashes. It exposes five boot and status tools, and none of them can take an action, give an approval or trade.
Session boot: the session verifies the signed receipts, matches every governance root and pointer to its live bytes, checks every connector against the registry, and reads the Phoenix carry-forward. A pass is a session check. It is not installation acceptance.
A claim gate and test harness. It was merged on 2026-10-04 as an unbound candidate (a2e-platform PR #32). It is not bound to any live path, so it enforces nothing in production yet.
Session close and resume through carry-forward files archived on GitHub. The protocol file itself says it is not enough, alone, to prove current estate state.
METATRON Prime Directive v10.9 and IRONCLAD v3.3 carry historical-provenance banners. VERITAS v4.1 and Definition of Done v1.0 name retired seats as owners. They state rules, but enforcement at runtime is not established.
Under the access registry, no session may place, modify or cancel a brokerage order. Where the console reads holdings, the server route is read-only and its guard refuses order paths.
Workflow layer: n8n, default-off, one-at-a-time reactivation.
Portfolio surfaces
The surfaces below are worth preserving as concepts and demonstrations. Their public status is intentionally conservative: useful design patterns, private evidence, and rebuild candidates until current behavior is revalidated.
Work-control board concept for AI-assisted execution: lanes, dependency views, roll-call, closure criteria, review status, and evidence-first task tracking.
Collective Intelligence Layer rebuild target: candidate qualification and portfolio-fit assessment with explicit no-execution authority. Model routes are inputs to be checked, not authority by themselves; contradicted or unsupported claims must remain non-actionable.
Market research view for sector rotation, relative volume and source timestamps. It is now built as a members-only console view (October 2026). It is research only, with no order path and no advice.
Intelligence Tools
Inquiry-to-evidence-card evaluator rebuild: questions, sources, policy scoring, output contracts and fail-closed behavior before any claim is treated as proven. Its server evaluation backend is not bound.
Why it exists: decades of program, SOW and contract reviews (see the résumé). The design is program, project, contract and subcontract management in which every figure links back to what, where, when and how. A members-only build exists in the console. It is under a first-pass standards review, not a certification.
Three papers are in progress: refusing rails, session continuity (Phoenix), and conversational AI as cognitive rehabilitation. Only the titles are public until each paper is complete, with its receipts.