Independent provider posture
The backup service is treated as a distinct provider function with evidence that the replica is not just an internal admin copy.
Backup provider typeAgreement lifecycleSame-provider guardrails
Backup of record service
Independent DPP continuity when the primary host is not enough.
Redy Backup of Record is the continuity service for independent replica ingest, durable proof, read-only serving posture, and no-lock-in export for Digital Product Passport records.
Backup service posture
ingest -> archive -> proof -> serve -> export
Service role
Independent
Backup replicas are modeled separately from normal authoring and publishing workflows.
Replica mode
Read-only
Backup of record rows are served as replicas, not edited like primary-hosted DPP drafts.
Continuity
Failover-aware
Serving behavior can distinguish public-only, delegated, and operator-ceased availability paths.
Portability
Exportable
A replica can be reconstructed as a re-ingestable envelope for no-lock-in portability.
Service model
Backup is a provider function, not an admin permission.
The product line has to prove independence, source provenance, replica state, and access posture. That is why the backup path is modeled separately from primary-host DPP authoring.
Replica provenance
Every backup record needs source operator, source provider, source DPP identifier, cursor, freshness, and integrity context.
Source identityLast replicated versionIntegrity state
Read-only serving
Backup replicas should never enter the normal author or publish mutation path; serving must label freshness and access posture.
Replica guardsStaleness policyAccess-mode labels
Replica flow
The backup record must be usable by another provider.
No-lock-in only matters if the replica can be exported in a shape another DPP provider can ingest without inheriting Redy-specific agreement state.
01
Ingest a source DPP replica
Bulk export, resolver crawl, or standards-aligned source connectors bring a DPP and attached evidence into a controlled backup envelope.
02
Store durable evidence
Archived bytes, manifests, source hashes, and proof records preserve what was received and what remains complete.
03
Track freshness and integrity
RPO, cursor, replicated version, proof status, stale-serving policy, and alerting make continuity measurable.
04
Serve only under the right mode
Temporary failover, delegated restricted access, and operator-ceased availability are different serving cases with different labels.
05
Export without lock-in
A backup replica can be emitted as a portable ingest envelope so another provider can re-ingest it under their own agreement.
Proof posture
Continuity claims need evidence, not slogans.
Replica provenance and source cursor are visible to operations and audit workflows.
Attached document completeness is explicit, not assumed.
Export envelopes omit Redy agreement internals and preserve only portable DPP evidence.
Restricted access remains public-only unless Redy can verify delegated or native entitlements.
A live service posture, not a certification claim
This page describes the service model and implementation posture. Formal certification and market claims must stay gated by the certification roadmap.
Not normal DPP authoring
Backup of record replicas are ingest, proof, serving, and export records. They are not edited through manufacturer draft workflows.
Access remains honest during failover
If delegated authorization is not available, external failover should be labeled public-only rather than implying access to restricted data.
Compare backup continuity with the live evidence workflow.
Backup protects published records. Supplier evidence workflow creates and reviews the claims before publication.