Changes to Published Documentation Policy
Defines how published documentation may be changed. Applies to TPP — Open Finance Standards and LFI — Integration Guide. Read alongside the Version Management Policy.
Why this policy exists
This policy defines how published documentation may be changed for TPP — Open Finance Standards and LFI — Integration Guide, ensuring that every post-publication change is traceable, auditable, and surfaced to readers.
Errata-only after publication
For any published documentation version, content may only be changed through a formally published Errata.
- This applies to all normative and implementation-impacting content in published versions
- Any correction or clarification made after publication must be traceable to a specific Errata identifier
- The affected page or section should clearly display that it has been modified by Errata
Errata example
Consent State Transitions
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Original content that now no longer applies as the Errata clearly says their is new content that supersedes this.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Updated freely until published
For non-published versions (for example v3.1-rc or v3.1-rc-final), content may be updated without issuing an Errata.
- These versions remain draft / pre-publication artifacts
- Normal review and approval controls still apply
- Once the version is published, post-publication changes must follow the Errata process
Who enforces this policy
Nebras is responsible for enforcing this policy across published documentation baselines for both TPP and LFI documentation sets.