Repo-local governance and memory
Proteus emits a `.proteus/` surface with rules, context, decision history, and reusable workflow scaffolds that multiple AI tools can share.
It gives repositories a durable shared brain through files: governance, memory, contract scaffolds, and thin tool entrypoints. The current framework core is strong enough for external beta evaluation, but it is still honest about what is not product-ready yet.
Proteus keeps the durable parts of AI-assisted engineering inside the repository instead of inside hidden prompts, transient sessions, or external memory layers.
Proteus emits a `.proteus/` surface with rules, context, decision history, and reusable workflow scaffolds that multiple AI tools can share.
Proteus does not claim to be a worker pool, credentials backend, orchestration daemon, or product-specific control plane.
The framework prefers plain files over hidden state so maintainers and agents can inspect the same source of truth.
The site organizes and explains the framework, but canonical contract and assessment artifacts remain in `docs/`.