EON AI Ventures · handover §5 · build spec

Where Compound IQ sits vs the agreed spec.

Conductor job compound-iq.nightly-batch, cadence nightly at 07:00 UTC. The engine is done. Live plugs wait on a password manager.

Done

· Nightly engine: ingest → cluster → classify → propose
· Auditable safe/unsafe policy with published thresholds
· Verdict gate: nothing writes Genesis without a pass
· Versioned twin write-back and rollback (Compound IQ is the only writer)
· Unsafe field patterns → Brainy lesson + supervisor alert
· Safe refinements write real SOP text, then push the new recipe to Brainy
· Data contracts: discrepancy, proposal, verdict, write-back, Distillery capsule
· xAPI pack/unpack for the customer Learning Record Store
· Conductor job clock (nightly batch, 07:00 UTC)
· Distillery public-accident classroom (teaching only, never a twin write)
· Per-site twin isolation (Houston cannot write Aberdeen)
· Live HTTP clients for LRS, Verdict, Genesis, Brainy — mock fallback kept
· CI workflow: typecheck + tests on every push
· Practice site on Vercel, Why / What / How guide, go-live board, audit export

· Practice product is complete. Waiting on live door URLs and a named steward in the host secret store — never in chat.