Support supplementary specification documents in trifecta audit#50
Merged
Alan-Jowett merged 2 commits intomicrosoft:mainfrom Mar 20, 2026
Merged
Conversation
Add optional additional_specs parameter to audit-traceability template. The protocol's Phase 1 now: - Inventories supplementary specs for cross-reference verification - Scans core documents for references to external specifications not provided, reporting them in the coverage summary This catches the case where a component's full spec surface is larger than its requirements/design/validation trifecta (e.g., Sonde's safe-bpf-interpreter.md was outside all component trifectas, causing 4 ad-hoc audit issues with ~50+ gaps to be invisible to the audit). Closes microsoft#47 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds support for supplementary specification documents to improve traceability audits when core trifecta docs reference external specs that may be missing.
Changes:
- Adds an
additional_specsparameter and template section for supplementary specifications. - Updates Phase 1 to inventory supplementary specs and detect references to unprovided external documents.
- Extends the coverage summary to report missing external references.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| templates/audit-traceability.md | Adds additional_specs parameter, input section, and instructions for handling supplementary specs and missing external references. |
| protocols/reasoning/traceability-audit.md | Adds Phase 1 steps for supplementary spec inventory + external reference scanning and reports missing references in Phase 6 summary. |
- additional_specs param: 'omit or leave empty' instead of 'none' - Input section: 'ignore if empty' hint for LLM - External ref scan: 'provided documents' instead of hardcoding 'requirements and design' Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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
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.
Closes #47
Adds an optional
additional_specsparameter so users can provide supplementary specifications that requirements reference but aren't part of the core trifecta.Changes:
additional_specsparam and input section, plus instruction for handling external referencesMotivation: The Sonde case study found 4 ad-hoc audit issues from
safe-bpf-interpreter.md— a spec outside all component trifectas. The audit had no way to know it was missing relevant context. Now it will either use the supplementary spec (if provided) or flag that the core documents reference external specs not included in the audit.