-
Notifications
You must be signed in to change notification settings - Fork 0
Evidence Metadata Migrations
Huzefaaa2 edited this page May 17, 2026
·
3 revisions
CAVRA supports SQLite-backed evidence metadata search for self-hosted pilots.
Migration:
migrations/sqlite/001_evidence_metadata.sql
migrations/sqlite/002_approval_router.sql
Apply:
cavra evidence migrate --sqlite .cavra/evidence/metadata.dbThe CLI records applied migration filenames in schema_migrations, so deployment automation can run the command repeatedly.
Run API:
CAVRA_EVIDENCE_METADATA_DB=.cavra/evidence/metadata.db uvicorn cavra.api:app --reloadSearch filters: session_id, signer, min_blocked, has_approvals, limit, and offset.
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