-
Notifications
You must be signed in to change notification settings - Fork 0
Diagrams
Huzefaaa2 edited this page May 17, 2026
·
72 revisions
See docs/diagrams/c4-context.md.
See docs/diagrams/c4-container.md. The current container diagram marks the Approval Router as an implemented JSON/SQLite-backed lifecycle service with repository routing, claims-aware authorization, console actions, provider request specs, and live provider delivery evidence. It keeps the Go enforcement plane plus Agent/MCP registry as planned containers.
See docs/diagrams/c4-component-runtime.md.
See docs/diagrams/runtime-decision-flow.md.
See docs/diagrams/evidence-lifecycle.md.
Repository diagram images:
docs/diagrams/architecture-context.svgdocs/diagrams/c4-container.svgdocs/diagrams/runtime-flow.svgdocs/diagrams/evidence-hub.svgdocs/diagrams/policy-lifecycle.svgdocs/diagrams/developer-journey.svgdocs/diagrams/agent-orchestration.svg
CAVRA Field Compass
Before the agent acts, CAVRA asks: who is acting, what will change, what policy applies, and what evidence will prove it?
Before the agent acts, CAVRA asks: who is acting, what will change, what policy applies, and what evidence will prove it?
| Start | Build | Operate | Assure |
|---|---|---|---|
| Quick Start | CLI | Enterprise Guide | AISPM |
| Reader Paths | Policy Syntax | Deployments | Evidence |
| Community | GUI | Troubleshooting | Conclusion |
Textbook home: Before the Agent Acts |
Development archive: development and testing artifacts |
Source repository: github.com/Huzefaaa2/cavra
- Foreword And Reader Paths
- Why CAVRA Exists
- Runtime Authority Model
- Architecture
- Editions
- Install And Deploy
- Community Guide
- Enterprise Guide
- CLI Reference
- GUI And Sandbox
- AISPM Guide
- Policy And Evidence
- Operations And Integrations
- Labs And Use Cases
- Appendices And FAQ
- Policy Language Reference
- Troubleshooting Playbook
- Conclusion