pharaoh-standard-conformance

Artefact conformance is checked by analyzing a single sphinx-needs artefact against a named regulatory standard like ISO 26262 or ASPICE to produce objective and subjective scores. The evaluation applies regulatory indicator sets and emits a structured JSON report of findings.

Evaluating regulatory compliance for a single requirement artefact involves applying a deterministic rubric across mechanized and subjective indicators for standards like ISO 26262-8 §6 and ISO/SAE 21434. This process generates a per-indicator JSON findings document suitable for audit trails.

Traceability analysis works by resolving cross-links in needs.json to verify references within a sphinx-needs artefact. When needs.json is available, the analysis uses these resolved references to accurately score verifiability and traceability indicators against the selected regulatory standard.

You can evaluate artefact compliance by providing an inline RST block instead of an existing artefact identifier. While needs.json is used to resolve cross-links when available, the skill can still apply its deterministic rubric to score the provided artefact against the named standard.

ISO/SAE 21434 conformance analysis supports automation and audit trails by emitting a structured JSON document containing per-indicator findings. This output format allows automated pipelines to consume the mechanized and subjective scores directly after evaluating the sphinx-needs artefact.

Supported standards for sphinx-needs artefact conformance evaluation include ISO 26262-8 §6, ASPICE 4.0, and ISO/SAE 21434. The analysis applies the specific regulatory indicator sets from these standards to generate a JSON report of mechanized and subjective findings.