-
Notifications
You must be signed in to change notification settings - Fork 0
Community GA Release Packet Validation
Huzefaaa2 edited this page Jun 28, 2026
·
1 revision
CAVRA validates public Community GA release packet JSON artifacts before merge and before Community release publication.
scripts/validate-release-packets.py validates:
- packet JSON syntax;
- conformance to
docs/release-packets/community-ga-release-packet.schema.json; - the complete Community GA gate set;
- public-boundary flags when boundary validation passes;
- no accepted risks on
ready_for_community_gapackets.
The validator covers packet JSON files in:
docs/release-packets/community-ga-*.jsonexamples/release-packets/community-ga-*.json
It excludes the packet schema file itself.
The validator runs in:
- Community CI;
- Community security scan;
-
cavra-required-check; - Community release workflow.
python scripts/validate-release-packets.pyUse --root for a checkout or generated packet directory:
python scripts/validate-release-packets.py --root /path/to/cavraContinue with a final tagged Community GA release packet when the maintainer is ready to publish an official Community GA release.
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