Business Continuity
CHIMERA / GOVERNANCE"What happens to Chimera if something happens to the founder?"
Continuity does not rest on one person's memory. It rests on a written architecture, an enforced test and CI gate, an internal knowledge base large enough to onboard a new engineer without a walkthrough, and a development process that already runs from those documents rather than from conversations.
244 pages across 25 categories cover every backend route group, core module, ML model, service, and integration. Every page carries a verification date and is flagged, not silently trusted, when it goes stale.
Every non-trivial architectural choice is a dated, reasoned, numbered decision-log entry. A successor engineer reconstructs why the system is shaped the way it is from that log, not from a handoff meeting.
14 CI/CD workflows cover lint, type-check, security scanning, and end-to-end tests. Enforcement varies by path -- backend PRs run under a 30% coverage floor, specialized ML tests deliberately skip coverage collection. Deploys run through CI on push -- there is no "only the founder knows the deploy steps."
Architecture overview, the full decision log, the security and non-custodial vault model, and the CI/test discipline in detail -- with source references, not just summaries.
Read the full governance guideStart with paper. Move to live when you're ready.
Sign up free — no card required. Connect your exchange in the desktop app.