Janus Documentation
Getting Started
Start with the glossary (canonical meanings), then the architecture overview, then the governance pipeline.
- Read full document → docs/glossary.md (GitHub rendered)
- Read full document → docs/architecture/janus-stack.md (GitHub rendered)
- Read full document → docs/governance/governance-pipeline.md (GitHub rendered)
Concepts
Janus is a governance core for systems where humans, software, and AI participate in decision processes. It governs how system evolution is evaluated, recorded, and reconstructed (not business logic execution).
- Read full document → docs/janus-explained.md (GitHub rendered)
- Read full document → docs/runtime-model.md (GitHub rendered)
Architecture
Janus is structured as a layered architecture: Core defines canonical terms, log types, and event identifiers; runtimes execute governance evaluation without redefining Core meanings.
- Read full document → docs/architecture/janus-stack.md (GitHub rendered)
- Read full document → docs/architecture/rebuild-model.md (GitHub rendered)
- Read full document → docs/architecture/governance-event-structure.md (GitHub rendered)
Governance Model
Janus Core Lite defines a deterministic pipeline separating domain activity from governance evaluation and accountable audit writing. The scope model ensures evaluation remains deterministic, traceable, and reproducible.
- Read full document → docs/governance/governance-pipeline.md (GitHub rendered)
- Read full document → docs/governance/governance-scope.md (GitHub rendered)
- Read full document → docs/omission-principle.md (GitHub rendered)