GovOPlaN/govoplan
2
0
Fork 0
Code Issues 18 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

[Task] Integrate coordinated backup evidence and restore drills into deployment flow #35

New Issue
Closed
opened 2026-08-01 01:49:31 +02:00 by zemion · 2 comments
zemion commented 2026-08-01 01:49:31 +02:00
Owner
Copy Link
Copy Source

Objective

Turn the deployment journal's explicit migration boundary into an operator-verifiable production backup gate. Parent: #13.

Acceptance criteria

  • Define a provider-neutral backup-evidence contract for PostgreSQL, object storage, and encryption-key references at one recovery point; never copy key material into evidence.
  • Record artifact identity, scope, timestamp, encryption/protection, expiry, provider, database LSN/snapshot identity where available, object-store version/manifest identity, and restore-test evidence.
  • Require fresh verified evidence before a forward-only or destructive migration; annotations alone are not sufficient.
  • Exercise restore into an isolated target, apply the matching immutable release, verify migration heads and representative object hashes, and retain the drill result.
  • Make failures, stale evidence, partial backup sets, and key mismatch fail closed with an explicit forward-recovery/manual-intervention state.
  • Support Compose and exported orchestrator profiles without giving the application API host or orchestrator control-plane access.
  • Document RPO/RTO ownership, retention, disposal, and provider-specific runbooks.

Current baseline

govoplan-deploy records a checksum-verified applied bundle and hash-chained operation journal. It permits bounded pre-migration configuration restore and switches permanently to forward recovery after migration starts. Core can reference a verified backup in a snapshot_restore recovery plan, but no production backup provider currently creates or validates that evidence.

## Objective Turn the deployment journal's explicit migration boundary into an operator-verifiable production backup gate. Parent: #13. ## Acceptance criteria - [ ] Define a provider-neutral backup-evidence contract for PostgreSQL, object storage, and encryption-key references at one recovery point; never copy key material into evidence. - [ ] Record artifact identity, scope, timestamp, encryption/protection, expiry, provider, database LSN/snapshot identity where available, object-store version/manifest identity, and restore-test evidence. - [ ] Require fresh verified evidence before a forward-only or destructive migration; annotations alone are not sufficient. - [ ] Exercise restore into an isolated target, apply the matching immutable release, verify migration heads and representative object hashes, and retain the drill result. - [ ] Make failures, stale evidence, partial backup sets, and key mismatch fail closed with an explicit forward-recovery/manual-intervention state. - [ ] Support Compose and exported orchestrator profiles without giving the application API host or orchestrator control-plane access. - [ ] Document RPO/RTO ownership, retention, disposal, and provider-specific runbooks. ## Current baseline `govoplan-deploy` records a checksum-verified applied bundle and hash-chained operation journal. It permits bounded pre-migration configuration restore and switches permanently to forward recovery after migration starts. Core can reference a verified backup in a `snapshot_restore` recovery plan, but no production backup provider currently creates or validates that evidence.
zemion commented 2026-08-01 12:38:57 +02:00
Author
Owner
Copy Link
Copy Source

Codex State: progress

Summary

  • Reference-readiness validation now requires a signed, expiring recovery claim bound to the exact release, deployment profile, controls, and evidence artifact hashes.

Verification

  • python -m unittest tests.test_capability_fit_evidence: 40 passed; tools/checks/check-focused.sh: passed.

Next / Blocked

  • Keep this issue open until deployment tooling actually executes coordinated backup/restore drills and supplies the resulting signed evidence.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Reference-readiness validation now requires a signed, expiring recovery claim bound to the exact release, deployment profile, controls, and evidence artifact hashes. ### Verification - `python -m unittest tests.test_capability_fit_evidence: 40 passed; tools/checks/check-focused.sh: passed.` ### Next / Blocked - Keep this issue open until deployment tooling actually executes coordinated backup/restore drills and supplies the resulting signed evidence. Suggested status label: `status/in-progress`
zemion commented 2026-08-03 02:03:52 +02:00
Author
Owner
Copy Link
Copy Source

Implemented and pushed.

Evidence:

  • cbbe08d defines strict signed provider-neutral schemas for coordinated PostgreSQL, object, protected-configuration, and key-custody recovery points, with no key material.
  • The evidence is bound to the installation/profile and exact immutable release, enforces component coordination, write-fence identity, expiry/revocation, isolated restore chronology, migration-head/object-manifest hashes, semantic checks, and measured RPO/RTO.
  • govoplan-deploy verify-backup --adopt requires an independently supplied SHA-256 and an explicit Ed25519 trust keyring; stored bytes are canonicalized, rehashed, and reverified without a second-open swap window.
  • Compose blocks release-changing migrations and re-verifies after runtime quiescing immediately before the migration boundary. Rejections are hash-chained in the deployment journal.
  • Kubernetes export fails closed for a release-changing migration and annotates the Job with only sanitized evidence identifiers/digest.
  • 0105fd4 projects expiry-aware sanitized status through Ops without exposing artifact, provider, credential, or key-custody references.
  • Provider signing utility, operator/provider runbooks, retention/disposal and RPO/RTO ownership are documented in docs/BACKUP_AND_RESTORE_EVIDENCE.md.

Validation:

  • Full meta suite: 373 tests passed.
  • Ops: 10 tests passed plus Ruff.
  • Zipapp build/help and both JSON schemas validated.
  • Tamper, stale, partial, wrong release, wrong key purpose, component skew, dishonest RTO, canonical signing, adoption, and next-release gate paths are covered.

A real production restore and signed target receipt cannot be manufactured from source tests; that target-environment acceptance remains explicitly tracked by #37.

Implemented and pushed. Evidence: - `cbbe08d` defines strict signed provider-neutral schemas for coordinated PostgreSQL, object, protected-configuration, and key-custody recovery points, with no key material. - The evidence is bound to the installation/profile and exact immutable release, enforces component coordination, write-fence identity, expiry/revocation, isolated restore chronology, migration-head/object-manifest hashes, semantic checks, and measured RPO/RTO. - `govoplan-deploy verify-backup --adopt` requires an independently supplied SHA-256 and an explicit Ed25519 trust keyring; stored bytes are canonicalized, rehashed, and reverified without a second-open swap window. - Compose blocks release-changing migrations and re-verifies after runtime quiescing immediately before the migration boundary. Rejections are hash-chained in the deployment journal. - Kubernetes export fails closed for a release-changing migration and annotates the Job with only sanitized evidence identifiers/digest. - `0105fd4` projects expiry-aware sanitized status through Ops without exposing artifact, provider, credential, or key-custody references. - Provider signing utility, operator/provider runbooks, retention/disposal and RPO/RTO ownership are documented in `docs/BACKUP_AND_RESTORE_EVIDENCE.md`. Validation: - Full meta suite: 373 tests passed. - Ops: 10 tests passed plus Ruff. - Zipapp build/help and both JSON schemas validated. - Tamper, stale, partial, wrong release, wrong key purpose, component skew, dishonest RTO, canonical signing, adoption, and next-release gate paths are covered. A real production restore and signed target receipt cannot be manufactured from source tests; that target-environment acceptance remains explicitly tracked by #37.
zemion removed the codex/ready
status
ready
 labels 2026-08-03 02:04:57 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
 area/auth
Authentication, sessions, access bootstrap, or login behavior.
 area/db
Database sessions, models, transactions, or persistence primitives.
 area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
 area/docs
Durable documentation and project guidance.
 area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
 area/marketing
Public website, product messaging, publication copy, or legal page content.
 area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
 area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
 area/rbac
Permissions, roles, delegation, or authorization policy.
 area/release
Versioning, release locks, tags, packaging, or dependency pins.
 area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
 area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
 area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
 audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
 audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
 audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
 audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
 audit/quick-fix
Audit finding that appears narrow and directly fixable.
 audit/structural
Audit finding that needs design, refactoring, or behavior review.
 codex/needs-human
Needs an explicit human decision before Codex should implement.
 codex/ready
Suitable for Codex to pick up with the existing issue context.
 module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
 module/addresses
GovOPlaN Addresses module behavior or integration.
 module/admin
GovOPlaN Admin module behavior or integration.
 module/appointments
GovOPlaN Appointments module behavior or integration.
 module/approvals
GovOPlaN Approvals module behavior or integration.
 module/audit
GovOPlaN Audit module behavior or integration.
 module/calendar
GovOPlaN Calendar module behavior or integration.
 module/campaign
GovOPlaN campaign module behavior or integration.
 module/cases
GovOPlaN Cases module behavior or integration.
 module/committee
GovOPlaN Committee module behavior or integration.
 module/connectors
GovOPlaN Connectors module behavior or integration.
 module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
 module/dashboard
GovOPlaN Dashboard module behavior or integration.
 module/dataflow
GovOPlaN Dataflow module behavior or integration.
 module/datasources
GovOPlaN governed datasource contracts, catalogs, and integrations.
 module/decisions
GovOPlaN formal Decisions module behavior or integration.
 module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
 module/dms
GovOPlaN Dms module behavior or integration.
 module/docs
GovOPlaN Docs module behavior or integration.
 module/encryption
GovOPlaN Encryption key custody, cryptographic policy, and E2EE integration.
 module/erp
GovOPlaN Erp module behavior or integration.
 module/evaluation
GovOPlaN Evaluation module behavior or integration.
 module/files
GovOPlaN files module behavior or integration.
 module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
 module/forms
GovOPlaN Forms module behavior or integration.
 module/forms-runtime
GovOPlaN Forms Runtime module behavior or integration.
 module/helpdesk
GovOPlaN Helpdesk module behavior or integration.
 module/identity
GovOPlaN Identity module behavior or integration.
 module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
 module/idm
GovOPlaN Idm module behavior or integration.
 module/ledger
GovOPlaN Ledger module behavior or integration.
 module/mail
GovOPlaN mail module behavior or integration.
 module/mandates
GovOPlaN Mandates, jurisdiction, responsibility, and authority behavior or integration.
 module/notifications
GovOPlaN Notifications module behavior or integration.
 module/ops
GovOPlaN Ops module behavior or integration.
 module/organizations
GovOPlaN Organizations module behavior or integration.
 module/parties
GovOPlaN procedure Parties, representation, and delivery-authority behavior or integration.
 module/payments
GovOPlaN Payments module behavior or integration.
 module/permits
GovOPlaN Permits module behavior or integration.
 module/policy
GovOPlaN Policy module behavior or integration.
 module/poll
GovOPlaN Poll module behavior or integration.
 module/portal
GovOPlaN Portal module behavior or integration.
 module/postbox
GovOPlaN Postbox module behavior or integration.
 module/projects
GovOPlaN Projects module behavior or integration.
 module/quick-access
GovOPlaN configurable task-local Quick Access behavior and integrations.
 module/records
GovOPlaN Records and eAkte lifecycle behavior or integration.
 module/reporting
GovOPlaN Reporting module behavior or integration.
 module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
 module/scheduling
GovOPlaN Scheduling module behavior or integration.
 module/search
GovOPlaN Search module behavior or integration.
 module/services
GovOPlaN versioned institutional Services behavior or integration.
 module/tasks
GovOPlaN Tasks module behavior or integration.
 module/templates
GovOPlaN Templates module behavior or integration.
 module/tenancy
GovOPlaN Tenancy module behavior or integration.
 module/tickets
GovOPlaN Tickets module behavior or integration.
 module/views
GovOPlaN governed task views, interface projections, and workflow view integration.
 module/voting
GovOPlaN Voting module behavior or integration.
 module/wiki
GovOPlaN Wiki module behavior or integration.
 module/workflow
GovOPlaN Workflow module behavior or integration.
 module/workflow-engine
GovOPlaN Workflow Engine runtime, persistence, or integration.
 module/xoev
GovOPlaN Xoev module behavior or integration.
 module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
 module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
 source/security-audit
Created from a structured security or code-quality audit report.
 source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No labels area/db area/release area/security module/core module/ops
priority
p1
type
task
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
govoplan-package-publisher zemion (Albrecht Degering)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan#35