docs(engine): tell retirement and archiving apart - #21
Draft
LKSNDRTMLKV wants to merge 2 commits into
Draft
LKSNDRTMLKV wants to merge 2 commits into
LKSNDRTMLKV wants to merge 2 commits into
Conversation
Deploying odal-node-docs with
|
| Latest commit: |
0c5bbd0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e0e56852.odal-node-docs.pages.dev |
| Branch Preview URL: | https://docs-retire-not-archive.odal-node-docs.pages.dev |
Deploying odal-node-landing with
|
| Latest commit: |
0c5bbd0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4a225d0c.odal-node-landing.pages.dev |
| Branch Preview URL: | https://docs-retire-not-archive.odal-node-landing.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The docs half of a vocabulary change landing across dpp-core and dpp-engine.
archivedwas this system's terminal lifecycle status. EN 18221:2026 clause 4.2— one of the six standards cited by Commission Implementing Decision (EU)
2026/1736 — uses "archiving" for something else entirely: the retention of
historical versions of a passport that is still live. The status is now
retired; the word stays where the standard put it.What changed
engine/retention— "Archival is a state, not an ending" becomes"Retirement is a state, not an ending", and gains a new section saying what
archiving actually is here. That section is the point of the page now: a
reader could previously finish it believing the passport history requirement
was covered by the word archived, and it never was. The two are named apart
and both are described.
core/overview— the lifecycle list.regulatory/central-registry— the status-sync sentence.Not touched, deliberately
site/dpp-docs/public/openapi.yamlis vendored from the engine at its lastrelease (v0.13.0) and still says
archiveDpp. It is re-synced when the enginereleases, and syncing it early would describe a route no released engine serves.
That sync is the release-day step, not this branch's.
Sequencing
The status rename ships in dpp-core 0.21.0 and reaches the API in the engine
release that repins to it. This branch describes the state after that release —
hold it until the engine ships.