# AMENDMENT 003 — Governing Constraint Applicability and Constraint Lifecycle - **Artifact ID:** CHQ-PRS-2026-001-AMD-003 - **Version:** v1.0 - **Status:** RATIFIED / IN FORCE - **Public record:** https://record.cybersecurityhq.com/doctrine/chq-prs-2026-001-amd-003 - **Machine-record SHA-256:** `d12af8c476ac8eb0b71df8d3b0b39b2c381abab4cf711a27d03306c400ed7cf6` ## Complete structured record ```json { "id": "CHQ-PRS-2026-001-AMD-003", "title": "AMENDMENT 003 — Governing Constraint Applicability and Constraint Lifecycle", "version": "v1.0", "issued": "2026-09-22", "status": "RATIFIED / IN FORCE", "doctrine_class": "MAINTENANCE_STANDARD", "doctrine_scope": "POSITIONS", "governed_artifacts": [ "Positions", "Anticipatory Structural Constraints", "Constraint Registry" ], "related_doctrine": [ "CHQ-PRS-2026-001", "CHQ-RAT-2026-001", "CHQ-ASC-2026-001", "CHQ-ASC-2026-006" ], "purpose": "Ratified amendment defining material applicability for Governing Constraint entries, recording the complete Position audit, and establishing constraint lifecycle and classification semantics.", "sections": [ { "heading": "AMENDMENT AUTHORITY AND EFFECT", "content": [ "Instrument ID: CHQ-PRS-2026-001-AMD-003.", "Status: RATIFIED / IN FORCE.", "Ratified by CHQ editorial governance on September 22, 2026 as a versioned amendment to CHQ-PRS-2026-001.", "This amendment preserves the exact PRS v1.0 instrument. It supplements PRS-06 and governs the Position and constraint registry corrections recorded below." ], "type": "paragraph" }, { "heading": "PRS-06.5 MATERIAL-APPLICABILITY TEST", "content": [ "A constraint is listed under Governing Constraint only when its core rule materially bounds a load-bearing inference, classification, exclusion, or conclusion in the Position.", "Background relevance, shared vocabulary, evidentiary citation, chronological proximity, and a constraint's general applicability to CHQ artifacts are insufficient.", "For each listed constraint, removing that constraint must permit a materially different interpretation of the Position. If the Position's reasoning and conclusion remain unchanged, the constraint is not governing and must not be listed.", "A Position with no materially applicable canonical constraint records NONE. Governing Constraint is not a default baseline set, an evidence list, or an authority-derivation field.", "Applicability is assessed against the constraint version in force on the Position's effective date and must be reconsidered whenever either the Position or the constraint is substantively amended." ], "type": "paragraph" }, { "heading": "COMPLETE POSITION APPLICABILITY AUDIT", "content": "", "type": "table", "tableData": { "headers": [ "Position", "Materially Applicable Constraints" ], "rows": [ [ "CHQ-P-2026-001", "ASC-001" ], [ "CHQ-P-2026-002", "ASC-003" ], [ "CHQ-P-2026-003", "NONE" ], [ "CHQ-P-2026-004", "ASC-001" ], [ "CHQ-P-2026-005", "ASC-001, ASC-003, ASC-004" ], [ "CHQ-P-2026-006", "ASC-001, ASC-003" ], [ "CHQ-P-2026-007", "ASC-003 (historical withdrawn record)" ], [ "CHQ-P-2026-008", "NONE" ], [ "CHQ-P-2026-009", "ASC-001, ASC-003" ], [ "CHQ-P-2026-010", "NONE" ], [ "CHQ-P-2026-011", "ASC-003" ], [ "CHQ-P-2026-012", "ASC-003" ], [ "CHQ-P-2026-013", "ASC-001" ], [ "CHQ-P-2026-014", "ASC-001" ], [ "CHQ-P-2026-015", "ASC-001, ASC-004" ], [ "CHQ-P-2026-016", "ASC-001, ASC-003, ASC-004" ] ] } }, { "heading": "P-016 FORMAL APPLICABILITY DECISION", "content": [ "ASC-004 applies. P-016's conclusion depends on the distinction between inherited authorization and independently verified authority at the point where execution or publication authority is exercised; independent execution-boundary validation is therefore load-bearing.", "ASC-005 does not apply. P-016 cites exploitation and remediation evidence, but its conclusion does not use disclosure timing as a proxy for exploitation onset and would be unchanged if the disclosure timeline evidence were removed.", "ASC-001 and ASC-003 remain applicable because capability controls scope across registry and pipeline boundaries, and provenance signals cannot represent the correctness of institutional trust state. ASC-002 is removed because P-016 does not attribute knowledge or decision state at a relevant time." ], "type": "paragraph" }, { "heading": "CONSTRAINT ERROR, AMENDMENT, SUCCESSOR, AND PERMANENCE SEMANTICS", "content": [ "Error correction: a clerical, citation, date, identifier, or transcription error requires a dated erratum identifying prior text, corrected text, supporting evidence, hash effect, and whether meaning changed. A meaning-changing correction is an amendment.", "Amendment: a constraint may be amended only through a ratified version increment that preserves the prior version, states the proposition changed and rationale, recomputes the canonical hash, and notifies registered reliance. Core judgments may not be silently replaced.", "Successor: supersession requires a separately identified successor that cites its predecessor, satisfies the predecessor's canonical supersession test, states the displaced proposition, and records the effective transition. Superseded versions remain historical and are ineligible for new reliance.", "Permanence means no automatic expiry or retirement trigger. It does not mean immunity from demonstrated error, transparent amendment, or a qualifying successor. Each constraint's canonical supersession test remains controlling." ], "type": "paragraph" }, { "heading": "ASC-006 CLASSIFICATION RESOLUTION", "content": [ "ASC-006 is classified as an INTERNAL ADJUDICATION constraint; ASC-001 through ASC-005 are classified as EXTERNAL INTERPRETIVE constraints.", "ASC-006 remains in the Anticipatory Structural Constraint class because it binds the legitimacy of adjudication across Positions, assumptions, exhibits, dockets, and other artifact classes. It is not a discretionary internal method, implementation tool, or operating procedure.", "No current Position materially depends on ASC-006. Effective dates and chronology in the audited Positions are contextual metadata rather than load-bearing temporal-precedence conclusions." ], "type": "paragraph" } ] } ```