Controlled Update & Break-Glass
Controlled Update & Break-Glass
Controlled Update & Break-Glass
Once a passport is published, its content is captured as an immutable snapshot. However, real-world operations sometimes require corrections — a typo in a material declaration, an updated compliance certification, or a regulatory correction. tieback provides two governance mechanisms for amending published passport data without reissuing the passport.
The two amendment paths serve different operational purposes:
Both mechanisms apply changes as controlled overrides — a separate data layer that sits on top of the original snapshot values. The original snapshot is never modified, preserving the full audit trail.
Controlled Update is the standard path for correcting published passport data.
The update is applied immediately. The new value takes effect in the public passport rendering, while the original snapshot value is preserved in the audit record.
Only fields that are registered in the governance policy as eligible for controlled update can be amended. The available fields are determined by the DPP Field Catalogue and the brand’s governance configuration.
published statepassports.controlled_update permissionBreak-Glass is the exceptional amendment path, designed for situations that require an auditable justification — such as regulatory corrections, safety-related updates, or post-revocation amendments.
Each brand configures its own set of break-glass reason codes in Settings. Reason codes provide structured categorisation of why an exceptional amendment was needed.
Once a reason code has been used in a break-glass amendment, it cannot be deleted — only deactivated. This ensures the historical audit trail remains intact.
Every break-glass amendment is recorded in an append-only ledger that captures:
This ledger is visible in the passport’s Compliance View tab as part of the unified governance change log.
published or revoked statepassports.break_glass permissionBoth Controlled Update and Break-Glass store their changes as controlled overrides on the passport record. When the passport is rendered:
The Machine Readable (JSON-LD) output also reflects controlled overrides, ensuring that both human-readable and machine-readable representations are consistent.
All amendments — both Controlled Update and Break-Glass — are visible in the passport’s Compliance View tab. The governance change log presents a unified, chronological timeline showing:
It is important to understand the distinction:
Product edits and passport amendments are independent operations. Editing a product does not update existing passports, and amending a passport does not change the product master.