Repository navigation
Conversation
Make the official main text assessable under the specification framework without changing what it requires. DRS-1 to DRS-37, the two elevated cross-functional requirements and the required behaviour in chapters 4, 7, 8 and 9 become DRAFT requirements with empty framework IDs. Source gaps and ambiguities are recorded, not resolved. The original spec/, api/, examples/ and test/ trees stay byte-identical; tools/validate_migration.py guards that and the requirement ledger. Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
The fixture copied .git as a file, which only holds in a linked worktree. Point the fixture at the real git directory instead, so CI and plain clones run it too. Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
…ation draft Replace the DRS-derived migration of the upstream specification with the revised alpha.2 draft, expressed in the Specification Framework format: Registry Core and six independently selectable Consultation options (Retrieve, Lookup, List, Search, Revision List, Revision Retrieve), selectable read features, caller capability discovery, and purpose binding. The upstream DRS-1 to DRS-37 dispositions are preserved in the 3.0 migration ledger, and the replaced numbered requirement blocks in the requirement archive and migration mapping. Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Reviewers can read the rendered draft without a local build. The site is rendered by the shared specification renderer pinned to a commit, carries a not-official banner and noindex, nofollow on every page, and the job never runs in the GovStackWorkingGroup repository. Drop this commit before merge. Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
jeremi
force-pushed
the
docs/digital-registries-3.0.0-alpha.2
branch
from
October 29, 2026 11:10
e74d889 to
e814f5e
Compare
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
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
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.
Change
This draft replaces generated CRUD and database-builder assumptions with a domain-neutral Registry specification in the proposed functionality-based Building Block template. Registry Core is combined with at least one of six Consultation options or four independently selected Write options.
Read and Write now share one canonical Registry API and one native API reference:
retrieveRecordis the single Record GET; the duplicategetWritableRecordoperation identifier is retired.RecordId; Change Request and Operation identifiers keep their separate constraints.api/openapi.yamlis canonical.api/write.openapi.yamlis a Git symlink; the publishedresources/api.ymlandresources/write-api.ymldownloads resolve to the same contract. The API catalog and Registry metadata advertise one service classified in both families. Clients using the retired operation identifier should useretrieveRecord.Submission, approval, background execution, and authoritative application remain distinct. A commit receipt grants no read permission and does not establish immediate visibility through another projection, a retained history revision, or permission to inspect hidden state.
The source retains 102 unnumbered DRAFT requirements. This consolidation expands the caller-discovery statement and retargets five Write contract references; the other 101 statements and all requirement keys, classifiers, options, selection rules, and applicability remain unchanged. Vendored domain schemas remain byte-identical.
The structure follows the proposed Building Block template. Resources contains the unified API reference, illustrative examples, verification procedures, and attribution. Working notes remain local and excluded from publication. Supersedes #57. The other six API families remain outside the current conformance target.
Review preview
Unofficial Digital Registries preview, with one normative API reference and four illustrative bindings.
The fork-only Pages workflow must be removed before upstream merge. This PR remains a draft.
Validation
These gates validate specifications, static contract exchanges, and documentation rendering. They do not exercise a deployed Registry or Adapter, or establish runtime authorization, atomicity, workflow, source currency, history, or conformance.