Contract
A stable emitted surface
`docs/versions/current.md` defines the active scaffold and the behavior of `proteus init` and `proteus doctor`.
docs/versions/current.md
Framework
The current contract is intentionally narrow.
Proteus is strongest when it stays abstract. The framework emits a stable scaffold, keeps entrypoints thin, and governs its own knowledge with explicit lifecycle rules. Runtime orchestration and organization-specific topology stay outside the default contract.
Knowledge model
Records, lifecycle, views
`docs/knowledge/registry.yaml` governs record identity and lifecycle. Canonical prose lives in core and current-contract views, not in arbitrary secondary docs.
docs/knowledge/lifecycle.md
Scope control
Framework truth stays separate from workspace truth
Proteus treats organization-specific repo maps, environments, hosts, and role rosters as downstream instantiation details unless abstracted first.
docs/core/invariants.md
Operational shape
Thin entrypoints, shared brain
Root entrypoints point into `.proteus/`. Durable behavior belongs in the shared brain and canonical docs, not in thick tool-specific wrappers.
README.md