FR-040 follow-up: complete artifact-axis edge vocabulary for the corpus#2
Merged
Conversation
…rpus The FR-040 allowed_links widening covered US but left NFR/FR/StR/master- requirements missing the traceability verbs the real corpus uses, so a local sweep of the ecosystem master specs surfaced ~70 disallowed-edge-type warnings. Close the gap so the authored links validate: - edge_types: register `contained_by` (structural, inverse contains) and `peer` (traceability) — used at the master-requirements bundle level. - allowed_links: FR +extends; NFR +traces_to; US +depends_on; StR +supersedes; master-requirements +supersedes/+peer/+contained_by. Verified locally against the quire-rs fr040 engine: the 8-repo sweep now reports zero disallowed-edge-type/-target findings. iso `make test` green. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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.
Context
Follow-up to the merged FR-040 typed-edge-vocabulary work (#1), found by running the FR-040 engine against the real ecosystem master-spec corpus. A local sweep (quire-rs main engine + quire-cli, both built locally) surfaced ~60
disallowed-edge-typewarnings. Root cause: the FR-040allowed_linkswidening coveredUSbut leftNFR/FR/StR/master-requirementsmissing the traceability verbs the corpus already uses. The authored links are correct — the vocabulary was incomplete.Changes —
spec_artifacts_iso/manifest.yaml(9 lines)contained_by(structural, inversecontains) andpeer(traceability) — used at the master-requirements bundle level (e.g. filament-core-service spec.md).FR+extends;NFR+traces_to;US+depends_on;StR+supersedes;master-requirements+supersedes/peer/contained_by.Verification (local, against current main)
validate+ Tier-2validate --okf) goes from ~60disallowed-edge-typewarnings to 0 with this PR + the paired quire-rs corpus-verb PR.disallowed-edge-target) was already 0; warn-tier invariant confirmed (every FR-040 diagnostic is a warning, zero new errors).make testgreen (59 passed; quire-wheel-gated skips unchanged).Pairs with quire-rs
fr040-corpus-link-fixes(relationship-verb rewrites to better-fitting registered verbs).🤖 Generated with Claude Code