pharaoh-req-review

You can audit a single requirement against ISO 26262 Part 8 §6 axes by running the review on a draft or existing need-id, which outputs a structured JSON document with per-axis findings and an overall verdict.

ISO 26262 requirement traceability audit includes per-axis scoring with binary and subjective scales, verifiability checks against needs.json, and actionable items for failures emitted as structured JSON.

To check if requirement verification links resolve in sphinx-needs, the audit validates :verification: links against needs.json to ensure references are correctly mapped and traceable.

Yes, you can audit an existing sphinx-needs requirement by providing its need-id to the review process, which then evaluates it against ISO 26262 axes and generates a findings JSON.

Yes, the audit output supports automated traceability checks by emitting a structured JSON document containing need_id, axes, action_items, and an overall verdict for downstream processing.

Binary axes in ISO 26262 audits use a 0/1 score, while subjective axes use a 0–3 scale, both generating specific action items when requirements fail the compliance check.