-
Notifications
You must be signed in to change notification settings - Fork 0
Phase 6 Ecosystem Expansion Rollup
Huzefaaa2 edited this page Jul 4, 2026
·
1 revision
The Phase 6 rollup is the public closeout gate for the R6 ecosystem expansion workstream. It summarizes:
- R6.1 benchmark and SLO regression gates;
- R6.2 generic agent adapter SDK and action taxonomy;
- R6.3 AI red-team and supply-chain gates;
- R6.4 zero-trust reference deployments.
| State | Meaning |
|---|---|
ready_for_phase6_public_contract_release |
The public repository contains validated contracts, examples, docs, workflows, and tests for all R6 gates. |
ready_for_customer_live_phase6_closeout |
A customer or managed deployment has supplied real live evidence for benchmark runs, adapters, red-team closeout, and zero-trust deployment smoke tests. |
The public repository can satisfy the public-contract state. Customer live closeout must come from a real managed or enterprise deployment.
python3 scripts/validate_phase6_rollup.py \
--packet examples/phase6-rollup/phase6-ecosystem-rollup.json \
--repo-root .CLI equivalent:
cavra release phase6-rollup --repo-root .Expected public result:
ready_for_phase6_public_contract_release: true
ready_for_customer_live_phase6_closeout: false
status: ready_with_customer_live_warnings
Customer live closeout requires:
| Gate | Required live evidence |
|---|---|
| R6.1 | Tenant benchmark run, production HA evidence, failure drill recording. |
| R6.2 | Provider adapter install, customer action fixture, tenant runtime evaluation. |
| R6.3 | Customer prompt suite, proprietary scanner plugin, red-team closeout. |
| R6.4 | Docker Compose smoke, Helm template, Terraform validate, Azure what-if, scanner operation. |
Run with --require-customer-live only when those references are present.
Related pages: Benchmark SLO Regression Gates, Generic Agent Adapter SDK And Action Taxonomy, AI Red-Team And Supply-Chain Gates, and Zero-Trust Reference Deployments.
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
- Technology Stack
- Unified Enterprise Roadmap
- Conclusion
- Development And Testing Archive
- Unified Enterprise Roadmap
- CLI
- API
- CAVRA Trial Field Guide
- AISPM Enterprise Live Ingestion
- Enterprise HA/DR Readiness
- Enterprise HA/DR Azure Map
- Enterprise KMS/HSM Evidence Custody
- Enterprise Immutable Audit Log
- Enterprise Compliance Mapping Packs
- Enterprise Reporting Exports
- Connector SDK And Certification
- Priority Certified Connectors
- Model Registry Connectors