docs(adr): mark ADR-019 implemented, record merge and close-out evidence#204
Merged
Conversation
Status was still "proposed" in both the frontmatter and body despite MIF#203, ontologies#25, and .github#44 all having merged and been verified end to end. Updated status to implemented, and appended a close-out audit entry recording: the merge triggered deploy.yml's normal push trigger and redeployed successfully without needing repository_dispatch to fire first; the live mif-spec.dev/ontologies/index.json was re-verified against ontologies' current main with zero mismatches; ontologies#6 closed on that evidence; the CI regression the --path fix caused (and its fix) in validate.yml; and the new ontologies#26 issue the --path fix surfaced.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates ADR-019 to reflect that deploy-time, attestation-verified ontology vendoring has been completed and verified, and records the post-merge audit trail/evidence for closing the ADR.
Changes:
- Marked ADR-019 status as implemented (frontmatter + Status section) and updated the
updated:date. - Appended a 2026-07-02 close-out entry documenting merge/deploy triggers, live-site verification evidence, and follow-up findings.
status: implemented is not a valid Structured MADR status (schema enum is proposed/accepted/deprecated/superseded; all 18 other ADRs in this repo use accepted for decided/in-effect work). Changed to accepted in both the frontmatter and the body Status section. adr/README.md's index table still listed ADR-019 as Proposed with present-tense "Proposes amending..." wording, and ADR-018's row still said the propagation amendment was merely "proposed via ADR-019" -- both now stale. Updated both rows. ADR-018's own Amendment section still asserted ADR-019 was "proposed, not yet accepted" and that the old propagation mechanism "remains this ADR's decision until ADR-019 is accepted." Appended a dated update noting ADR-019 is now accepted and implemented, preserving the original entry per this file's append-only audit convention. The new audit entry was missing the bold "Status:" line every other entry in this file opens with. Added it. Reworded a phrase in the audit entry that used a banned word.
Backticked cross-repo/issue references (`MIF`#203, `ontologies`#25, `.github`#44, `ontologies`#6, `ontologies`#26) don't auto-link on GitHub; code-formatting suppresses the reference parser. Switched to plain modeled-information-format/<repo>#<number> so these are clickable from the rendered ADR, and rewrote the sentence listing the four matched index fields to avoid the awkward possessive-plus-slash-separator line break.
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.
ADR-019 still said status: proposed despite MIF#203/ontologies#25/.github#44 all merging and being verified end to end. Updates status to implemented and appends a close-out audit entry with the merge/deploy/live-verification evidence, the CI regression the --path fix caused and its fix, and the new ontologies#26 issue it surfaced.