-
Notifications
You must be signed in to change notification settings - Fork 0
Go Backend Rollback Drill Auditor Export Retry Archive Health
Huzefaaa2 edited this page Jun 28, 2026
·
1 revision
CAVRA now plans retries for failed final auditor export delivery and checks archive custody health for verified rollback drill auditor exports.
- Added final auditor export delivery retry plans.
- Added archive reference health reports for verified auditor exports.
- Added Evidence Console Plan Auditor Retry and Archive Health controls.
- Added dashboard metrics for retry plan count, retryable auditor deliveries, archive health report count, and archive health alert count.
- Kept private connector redelivery and archive write operations outside Community Edition.
POST /runtime/go-pilot/rollback-drill-notifications/acknowledgements/audit-delivery/final-reporting-auditor-export/delivery-retry-plan
GET /runtime/go-pilot/rollback-drill-notifications/acknowledgements/audit-delivery/final-reporting-archive-reference-healthgo-backend-rollback-drill-acknowledgement-audit-delivery-final-reporting-auditor-export-delivery-retry-plango-backend-rollback-drill-acknowledgement-audit-delivery-final-reporting-archive-reference-health
- As a release manager, I can see which failed final auditor export deliveries are safe to retry.
- As an auditor, I can verify that final auditor exports are represented in immutable archive references.
- As a platform operator, I can identify archive custody gaps without exposing storage credentials or private endpoints.
This phase makes delivery retry posture and archive completeness measurable in Community Edition while keeping private connector execution and storage writes in Enterprise or operator-owned systems.
See docs/diagrams/go-backend-rollback-drill-auditor-export-retry-archive-health.svg.
Completed in the next slice: final auditor export retry worker execution records and archive health alert delivery acknowledgements. See Go-Backend-Rollback-Drill-Auditor-Export-Retry-Worker-Archive-Alert-Acks.md.
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