# Consensus Center

## Docs

- [Engine schema](https://whitepaper.consensus.center/architecture/engine-schema.md): 67 tables organized into clinical, safety, runtime, and governance layers.
- [Runtime facts and decision traceability](https://whitepaper.consensus.center/architecture/runtime-traceability.md): How every interpretation becomes auditable, from input facts to resulting state.
- [System overview](https://whitepaper.consensus.center/architecture/system-overview.md): How the Consensus Engine converts patient facts into traceable clinical states.
- [Technology stack and dependencies](https://whitepaper.consensus.center/architecture/technology-stack.md): System layers, external services, open-source inventory, and continuity controls.
- [The clinical problem](https://whitepaper.consensus.center/clinical-problem.md): Preventive interpretation without over-diagnosis, bias, or unsafe automation.
- [Ancestry, genotype, phenotype, and context inputs](https://whitepaper.consensus.center/clinical/ancestry-genotype-inputs.md): How sensitive calibration signals are handled safely.
- [Calibration methodology](https://whitepaper.consensus.center/clinical/calibration-methodology.md): How evidence becomes a reviewed, versioned clinical rule.
- [Clinical guardrails](https://whitepaper.consensus.center/clinical/clinical-guardrails.md): How the engine escalates uncertainty instead of over-asserting.
- [Evidence management and scientific defensibility](https://whitepaper.consensus.center/clinical/evidence-management.md): How sources, evidence grades, rule provenance, and updates are governed.
- [AI agent architecture](https://whitepaper.consensus.center/governance/ai-agent-architecture.md): What agents do, what they cannot do, and how they stay grounded in the deterministic engine.
- [Operating model](https://whitepaper.consensus.center/governance/operating-model.md): How clinical, engineering, product, and compliance teams maintain the engine over time.
- [Physician-in-the-loop governance](https://whitepaper.consensus.center/governance/physician-governance.md): Medical Director review, lifecycle controls, and release gates.
- [Release, deployment, and rollback](https://whitepaper.consensus.center/governance/release-deployment.md): How schema versions move from review to production without exposing patients to unsafe logic.
- [Security, privacy, and data governance](https://whitepaper.consensus.center/governance/security-privacy.md): Protecting clinical data, consent, audit logs, and de-identified learning loops.
- [Treatment and protocol governance beyond GLP-1](https://whitepaper.consensus.center/governance/treatment-governance.md): How the engine supports clinical pathways without becoming an automated prescriber.
- [Validation strategy](https://whitepaper.consensus.center/governance/validation-strategy.md): Golden test cases, boot validators, clinical review, and outcomes monitoring.
- [Consensus Center technical whitepaper](https://whitepaper.consensus.center/index.md): A deterministic, traceable, physician-governed engine for preventive precision health.
- [Due diligence readiness](https://whitepaper.consensus.center/stakeholders/due-diligence.md): What investors, clinical partners, and regulators should be able to verify.
- [Final synthesis](https://whitepaper.consensus.center/stakeholders/final-synthesis.md): The Consensus technical thesis and why this architecture can support scalable preventive medicine.