Repository navigation
docs: x-FuSa spec v1.13.0 — evidence-artifact schemas + content-quality baseline - #82
Merged
Merged
Conversation
…ty baseline Formalizes HARA/FMEA/TARA/safety-case/SAS/SCI from tool-defined sketches into real field-level MUST/SHOULD schemas grounded in ISO 26262-3, IEC 60812/AIAG-VDA, ISO/SAE 21434, the GSN Community Standard, and DO-178C, following a cross-tool content audit that found traceability/coverage strong but several artifacts schema-shaped without being information-bearing (templated FMEA boilerplate, an untouched HARA template, an artifact with invalid JSON). Adds a new cross-cutting §1.6 content-quality baseline (bans placeholder text, requires JSON validity, bans a single hardcoded qualitative fallback, requires real referents) that a schema alone can't enforce, and a §1.5.2 requirement-text quality rule grounded in ISO/IEC/IEEE 29148 and EARS. Bumps SpecVersion 1.12.0 -> 1.13.0. Signed-off-by: SoundMatt <SoundMatt@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
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.
Summary
Follows a cross-tool content audit (all six x-FuSa tools) run against real live output: traceability and unit-test coverage were uniformly strong, but several evidence artifacts were schema-shaped without being information-bearing — hundreds of near-identical FMEA rows, an untouched HARA template, an artifact with invalid JSON. A schema alone can't catch fabricated-looking content, so this PR does two things:
1. Formalizes real schemas for the previously tool-defined evidence artifacts, each grounded in the actual governing standard instead of an invented shape:
.fusa-hara.json(MUST read/validate) — ISO 26262-3 Clause 6, using theoperationalSituations[]/hazards[]/safetyGoals[]cross-referenced shape already independently converged on across the family and matching FuSaOps' ownharapackage.hara/fmea/tara/safety-case(mirrors howcompwas formalized) —fmeaper IEC 60812/AIAG-VDA Handbook with anactionPriorityfield superseding raw RPN;taraper ISO/SAE 21434 Clause 15 using SFOP impact categories;safety-caseper the GSN Community Standard v3 with all six real node types.sas/sci— DO-178C §11.20/§11.16.2. Adds §1.6, a cross-cutting content-quality baseline (MUST unless noted) applying to every free-text evidence artifact: no placeholder/template text, structural JSON validity required, no single hardcoded qualitative fallback applied regardless of the item's actual signature, real (non-keyword) file/function referents only, plus SHOULD-level provenance (
"analysis": "heuristic"|"reviewed") and freshness recommendations.Also adds a §1.5.2 SHOULD rule for requirement-text quality, grounded in ISO/IEC/IEEE 29148:2018 and EARS sentence patterns.
SpecVersionbumped1.12.0→1.13.0.Scope note: this is the spec-design step only — none of these six schemas is yet implemented by any tool against the new shape, and none is consumed by FuSaOps (that remains a future MINOR bump, tracked separately per-tool as needed).
Test plan
go build ./.../go vet ./...— cleango test ./...— all packages passhara/hara.goimplementation (no code changes needed, doc-only change)