-
Notifications
You must be signed in to change notification settings - Fork 0
Final Closeout Trial Guide
Huzefaaa2 edited this page Jun 28, 2026
·
1 revision
This guide explains how a customer trial should evaluate CAVRA final closeout workflows without exposing Enterprise source code or private license-server logic.
The trial proves that CAVRA can create a public-safe final closeout evidence chain and show where Enterprise or SaaS features add private enforcement.
- Start the Community API and Evidence Console.
- Generate final readiness evidence.
- Create a signed archive manifest using external signature metadata.
- Generate and deliver a final closeout summary.
- Request and approve closeout retention.
- Build the closeout artifact bundle.
- Run closeout retention health.
- Send a retention health alert through a non-production connector.
- Create a retry plan for a simulated failed closeout delivery.
- Run the retry worker in dry-run mode.
- Review release criteria and decide whether the trial passes.
- Public-safe evidence metadata
- Evidence Console visibility
- Redacted connector delivery records
- Retention approval and health metadata
- Retry planning and dry-run worker evidence
- Open-core boundaries
- License validation
- Tenant management
- Organization dashboards
- SSO and RBAC
- Authenticated live connector execution
- Private archive mutation and retention enforcement
- Compliance evidence exports
- Paid policy packs
Use non-production connectors and synthetic evidence. Do not use production customer tickets, archive paths, private policy packs, license keys, or secrets in Community trial walkthroughs.
- Final Closeout Trial Walkthrough:
Final-Closeout-Trial-Walkthrough.md - Final Closeout Trial Sample Evidence:
Final-Closeout-Trial-Sample-Evidence.md - Final Closeout Sales Engineering Demo:
Final-Closeout-Sales-Engineering-Demo.md - Final Closeout Production Pilot Intake:
Final-Closeout-Production-Pilot-Intake.md - Final Closeout Pilot Intake API:
Final-Closeout-Pilot-Intake-API.md - Final Closeout Pilot Readiness Checklists:
Final-Closeout-Pilot-Readiness-Checklists.md - Final Closeout Enterprise And SaaS Handoff:
Final-Closeout-Enterprise-And-SaaS-Handoff.md - Synthetic sample evidence package:
examples/demos/final-closeout-trial/sample-evidence-package.json - Synthetic pilot intake template:
examples/demos/final-closeout-trial/pilot-intake-template.json
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