-
Notifications
You must be signed in to change notification settings - Fork 0
Provider Interfaces
Huzefaaa2 edited this page Jul 1, 2026
·
1 revision
CAVRA separates product capability from provider readiness. Community operators can self-host with their own providers; CAVRA Managed operates providers as a service; Enterprise Subscription can add certified packages and implementation help.
- Identity provider for SSO/RBAC.
- Approval provider and reviewer mapping.
- Audit and evidence store.
- Object storage.
- Database.
- Report delivery provider.
- Policy registry.
- Secret store.
- Connector credentials.
- Monitoring and alerting.
The public repository can contain provider contracts, schemas, and reference implementations. It must not contain customer secrets, production credentials, private signing material, customer-specific templates, billing records, or internal-only runbooks.
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