BACKEND RECOVERY CONTROL PLANE

Know what can recover
before you touch production.

Reprise reconstructs a mutually compatible backend state across code, schema, functions, contracts, configuration, and dependencies—then verifies it in isolation.

Watch the visual briefing Read the technical README ↗
STATE GRAPHCHANGE LEDGERRECOVERY GUARDPROOF RECEIPTS
SAMPLE INCIDENT · LOCAL ONLY

UNSAFE STATE · v1.8

Deployment v1.8
Migration M104
Function F18
RREPRISE

VERIFIED CANDIDATE · v1.7

Schema S12
Function F17
Contract C6
✓ COMPATIBLE
verification required

A 45-SECOND RECOVERY BRIEFING

Why a backup alone cannot explain a safe recovery.

Walk through the deterministic v1.7 → v1.8 incident fixture. Every frame maps to a concrete part of Reprise’s executable demo; no provider operation is performed.

01 / 04OBSERVED FAILURE

INCIDENT INPUT

The users API fails after v1.8.

A deployment, a schema revision, and a function revision changed together. Reprise records the relationship before it proposes a response.

deployment v1.8schema S13function F18
Sample data · incident-acquisition · no live provider calls

THE DIFFERENTIATOR

Reprise Signal

A portable recoverability passport. Not a confidence score: every dimension remains visible, traceable, and policy-enforceable.

CompatibilityCOMPATIBLECross-component evidence
VerificationVERIFIEDRecovery candidate receipt
FreshnessCURRENTRevision-bound guard
Unknowns0Never hidden as safe

EXECUTABLE LOCAL DEMO

Watch the evidence accumulate.

Run the same six-step recovery path as the CLI fixture. It is a timed visual rendering of deterministic sample output—not a live production console.

  • 01 Find the suspected change boundary
  • 02 Reconstruct the compatible checkpoint
  • 03 Verify evidence and block unsafe promotion
reprise demo acquisition --jsonDETERMINISTIC
Ready to reconstruct incident-acquisition.
No provider calls

PRODUCT-FIT VIEW · NOT A PARTNERSHIP CLAIM

A recovery-intelligence layer for branchable Postgres.

Neon’s documented branch lifecycle is a useful isolation primitive. Reprise adds the decision layer: the cross-component evidence for which historical state merits a branch, what must travel with it, and whether its result may be trusted.

PROVIDER PRIMITIVE

Isolated database branch

Documented branch discovery, creation, and explicit cleanup are implemented in the Neon adapter.

REPRISE CONTROL PLANE

Compatible recovery candidate

State graph, change boundary, verification evidence, stale-plan guard, and auditable receipt.

ENGINEER OUTCOME

Explainable, safer recovery

Unknowns remain visible. Production mutation remains explicitly authorized and outside this demo.

The live Neon adapter is contract-tested against documented branch endpoints. Snapshot/PITR and production promotion are not implemented in this release.

SAFE BY CONSTRUCTION

Recovery is a proof-bearing workflow.

Incident, boundary, candidate, verification, and recovery guard flow

Provider operations are capability-gated. Production promotion remains an explicit, separately authorized action. A stale state revision blocks a plan even when its candidate once verified.