feat(notations): TERM element type + generated glossary report view - #479
Merged
Conversation
Adds TERM (business-layer vocabulary, ArchiMate Meaning) as the 31st live element TYPE, folded into the ELEM-ALIAS-001 cross-catalogue uniqueness gate so a TERM restating an existing element's name fails admission. The new glossary report view (32-glossary.md) projects name/aliases/ description from TERM and every other TYPE into one flat, alphabetised lookup surface. Closes transitrix-hq#118. Signed-off-by: transitrix <279946036+transitrix@users.noreply.github.com>
The new glossary notation needs a family-selection row, a summary paragraph, and a starter template so the onboarding Skill offers it like every other report view — required by CI's cheat-sheet conformance check. Signed-off-by: transitrix <279946036+transitrix@users.noreply.github.com>
github-actions
Bot
added
the
needs:human-merge
4 tasks
…glossary # Conflicts: # .github/workflows/ingest-skill-test.yml
transitrix
added a commit
that referenced
this pull request
Aug 16, 2026
Categorised the 8 PRs landed since #475's 3.4.0 bump per RELEASING.md's bump table; highest is #479/#477/#478/#480/#481/#484 (new TERM element type, catalogue-integration spec surface, blocks render contract section) -> MINOR. Bumped notations/CURRENT_VERSION.yaml to 3.5.0 and every methodology_version pin the V1 check flagged (41 files), plus the remaining illustrative-example occurrences in the same files the check doesn't scan past the first match, for doc consistency (11 files). No v3.4.0 tag was ever cut after #475 -- this release folds that gap in rather than shipping an intermediate untagged version. Signed-off-by: transitrix <automation@transitrix.com> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
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
2 participants
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.
Summary
TERM(business-layer vocabulary, ArchiMate Meaning) as a new standalone element TYPE — name + definition only, no modelled behaviour.ELEM-ALIAS-001cross-catalogue uniqueness gate so aTERM's ownnamealso participates in collision detection — restating an existing element's definition under a newTERMfails admission.notations/views/reports/32-glossary.md) — projectsname/aliases[]/descriptionfromTERMand every other TYPE into one flat, alphabetised lookup surface.TERM/GLOSSARYin the vocabulary, ID grammar, and rule-codes tables; adds unit tests for the collision-gate extension; wires the new test into CI.Test plan
node --test packages/ingest-cli/src/canon.test.mjs— 6/6 passnode scripts/check-notations.mjs— doc-lint cleancloses THQ-118