# CHQ POSITION RECORD STANDARD (PRS) v1.0

- **Artifact ID:** CHQ-PRS-2026-001
- **Version:** v1.0
- **Status:** IN FORCE
- **Public record:** https://record.cybersecurityhq.com/doctrine/chq-prs-2026-001
- **Machine-record SHA-256:** `ba820f6483aa674ab1f239f963f31661ce353b0bcc1cdf541f209f942c979f81`

## Complete structured record

```json
{
  "id": "CHQ-PRS-2026-001",
  "title": "CHQ POSITION RECORD STANDARD (PRS) v1.0",
  "version": "v1.0",
  "issued": "2026-09-22",
  "status": "IN FORCE",
  "doctrine_class": "MAINTENANCE_STANDARD",
  "doctrine_scope": "POSITIONS",
  "governed_artifacts": [
    "all artifacts in the CHQ Position Record, published and forthcoming"
  ],
  "related_doctrine": [
    "CHQ-RAT-2026-001",
    "CHQ-D-2026-ESG",
    "CHQ-R-2026-001"
  ],
  "purpose": "Exact ratified instrument text. Ratified under CHQ-RAT-2026-001 on 2026-09-22.",
  "sections": [
    {
      "heading": "CHQ POSITION RECORD STANDARD (PRS) v1.0",
      "content": "# CHQ POSITION RECORD STANDARD (PRS) v1.0\n\n**Instrument ID:** CHQ-PRS-2026-001\n**Version:** v1.0\n**Ratified under:** CHQ-RAT-2026-001, 2026-09-22\n**Status:** IN FORCE\n**Applies to:** all artifacts in the CHQ Position Record, published and forthcoming\n\n---\n\n## PRS-01. AUTHORITY AND SCOPE\n\nPRS-01.1 This Standard is the governing layer above the Position Record. It defines fields, sections, counts, states, transitions, integrity and publication gates.\n\nPRS-01.2 Positions do not define, explain or vary these rules inside their own text. A position that needs a rule this Standard does not provide is blocked pending a PRS amendment.\n\nPRS-01.3 This Standard does not govern the Criteria Governance Standard, the Intelligence System, the signal registry or the weekly report series. Where a term appears in both, PRS governs its use inside the Position Record only.\n\nPRS-01.4 Amendment of this Standard requires DM ratification and a version increment. Provision IDs are stable across versions.\n\n---\n\n## PRS-02. ARTIFACT PRECEDENCE\n\nPRS-02.1 The exported PDF is the canonical artifact. The rendered page at record.cybersecurityhq.com is a derived rendering of it.\n\nPRS-02.2 Canonical text may not be changed by editing the rendering. A change originating in the site is an unrecorded edit and must be either adopted by amendment or reverted to the canonical text.\n\nPRS-02.3 Where the two diverge, the PDF prevails, except where an amendment has adopted the site text under PRS-10.\n\nPRS-02.4 Site rebuilds are executed from the canonical PDFs, not from the site's prior state.\n\n---\n\n## PRS-03. CANONICAL TEXT BOUNDARY\n\nPRS-03.1 Canonical text is the Position Metadata block, the Amendment Note where present, and all body sections through Reference Conditions inclusive.\n\nPRS-03.2 Canonical text excludes: navigation, the header and footer bars, the export control, the Reliance Notice, the issuance line, page furniture, and all styling.\n\nPRS-03.3 Section headings are inside canonical text. Renaming a heading is an amendment.\n\nPRS-03.4 The published SHA-256 covers PRS-03.1 exactly, normalized to UTF-8, with trailing whitespace stripped and line endings set to LF.\n\n---\n\n## PRS-04. SECTION SCHEMA\n\nPRS-04.1 Sections appear in this order. Canonical names are binding; the rendering uses the same names.\n\n| # | Section | Required |\n|---|---|---|\n| 1 | Position Metadata | yes |\n| 2 | Amendment Note | where amendments exist |\n| 3 | Evidence Basis | yes |\n| 4 | Authority Derivation | yes |\n| 5 | Governing Constraint | yes |\n| 6 | Scope of Application | yes |\n| 7 | Position Statement | yes |\n| 8 | Structural Observation | optional |\n| 9 | Architectural Implication | optional |\n| 10 | Evidential Record | yes |\n| 11 | Structural Consequence | yes |\n| 12 | Boundary of Application | yes |\n| 13 | Suggested Citation | yes |\n| 14 | Position Status | yes |\n| 15 | Record Integrity | yes |\n| 16 | Doctrinal Alignment | yes |\n| 17 | Reference Conditions | yes |\n\nPRS-04.2 The Reference Boundary and Reference blocks are retired. Their content moves to the Reliance Notice, which sits outside canonical text.\n\nPRS-04.3 A required section may not be omitted. Where it has no content, it states the absence explicitly.\n\nPRS-04.4 Boundary of Application bullets are noun phrases completing the stem \"This Position does not address\". Verb phrases are non-conforming.\n\n---\n\n## PRS-05. METADATA FIELDS\n\nPRS-05.1 Closed vocabularies. A value outside the list is non-conforming.\n\n**Doctrine Family:** BOUNDARY_ILLUSION, REPRESENTATION_FAILURE, MARKET_STRUCTURE, EXECUTION_GOVERNANCE, SYSTEM_COMPLEXITY_LIMITS, CONTROL_VERIFICATION, ENFORCEMENT_GOVERNANCE, SUPPLY_CHAIN_INTEGRITY\n\n**Pressure Class:** GOVERNANCE, STRUCTURAL, MARKET, INFRASTRUCTURE, EXECUTION\n\n**Position Type:** CONTROL_INVALIDATION, STRUCTURAL_CONDITION, STRUCTURAL_OBSERVATION, MARKET_ABSORPTION, GOVERNANCE_FAILURE, ARCHITECTURAL_LIMIT\n\n**Durability Class:** ARCHITECTURAL, STRUCTURAL, MARKET, TRANSITIONAL\n\n**Evidence State:** EMERGING, BUILDING, REINFORCING, CONFIRMED\n\nPRS-05.2 Values are never truncated to fit a render width. The template accommodates the value.\n\nPRS-05.3 Pattern Register ID uses the form CHQ-PR-NNN. The CHQ-PB form is retired.\n\nPRS-05.4 The evidence sufficiency gate reference is CHQ-D-2026-ESG V1.0. No other gate identifier is valid in the Position Record.\n\nPRS-05.5 Lens carries an assigned LENS-NNN value. PENDING is not a publishable value. See PRS-16.\n\nPRS-05.6 Evidence Docket carries a CHQ-ED-NNNN-NNN value. NULL and empty are not publishable values.\n\nPRS-05.7 Source Signals are listed in ascending chronological order by signal date, then by sequence.\n\nPRS-05.8 Anticipatory Structural Constraints are cited as CHQ-ASC-NNNN-NNN. The forms ACJ, ACHQ-SC and bare SC are invalid as constraint prefixes. The bare form SC-NNNN-NNN is reserved for structural conditions and is not a constraint.\n\n---\n\n## PRS-06. INHERITANCE FIELDS\n\nPRS-06.1 The three fields answer three different questions and are not interchangeable.\n\n**Authority Derivation** answers: does this position inherit authority from another instrument? It names the instrument, or states \"No constraint derivation applies. This is a standalone Position.\"\n\n**Governing Constraint** answers: which constraints bound interpretation of this position? Every position carries this, derived or standalone. Listing a constraint here is not inheritance.\n\n**Doctrinal Alignment** mirrors Authority Derivation exactly. Where Authority Derivation states standalone, Doctrinal Alignment reads \"Standalone Position\". Where it names instruments, Doctrinal Alignment reads \"Extends:\" followed by the same instruments in the same order.\n\nPRS-06.2 A position may not declare standalone in Authority Derivation and list Extends targets in Doctrinal Alignment. This is the single most common non-conformance in the record as of ratification.\n\nPRS-06.3 Constraints listed under Governing Constraint appear in ascending numeric order.\n\nPRS-06.4 Where the Extends target is a position rather than a constraint, the position is derived, not standalone.\n\n---\n\n## PRS-07. COUNTS\n\nPRS-07.1 **Signal Count** is the number of distinct source signals admitted to the evidence basis. It equals the number of identifiers listed under Source Signals.\n\nPRS-07.2 **Vector Count** is the number of independent confirmation paths supporting the position. A vector is independent when it does not share a technical failure class, an actor, an ecosystem or a source root with another vector.\n\nPRS-07.3 Vector Count may not exceed Signal Count unless each excess vector is enumerated in the Evidence Basis with its basis stated. CHQ-P-2026-005 demonstrates the conforming pattern, naming condition ratification as its second vector.\n\nPRS-07.4 Where sources are not proven independent, they default to SHARED_ROOT and contribute one vector, not several.\n\n---\n\n## PRS-08. EVIDENCE STATE AND CERTAINTY PARITY\n\nPRS-08.1 Evidence state definitions.\n\n**EMERGING:** one confirmation path. The condition is observed but not independently corroborated.\n**BUILDING:** two or more independent paths, insufficient for structural generalization.\n**REINFORCING:** an established position receiving new independent confirmation.\n**CONFIRMED:** independent confirmation across distinct mechanisms, actors or ecosystems, sufficient that the condition is treated as structural.\n\nPRS-08.2 **Certainty parity.** Published prose may not assert more confidence than the registry state holds. This is checkable, not a matter of editorial judgment.\n\nPRS-08.3 At EMERGING, prose may not contain:\n- universal quantifiers applied to the condition (every, all, any, no organization, regardless of)\n- irreversibility claims (permanent, irreversible, cannot be reopened, closed for good)\n- future-tense outcome claims outside a Forecast Condition block\n\nPRS-08.4 At BUILDING and REINFORCING, PRS-08.3 applies to the position statement. Body prose may generalize where the generalization is attributed to a named source.\n\nPRS-08.5 At CONFIRMED, universal claims are permitted where the evidence basis enumerates the paths supporting them.\n\nPRS-08.6 A position asserting a dated outcome carries a Forecast Condition block with a measurable indicator and a horizon, and a Kill Condition block stating what retires it. Silent withdrawal is prohibited.\n\nPRS-08.7 Vendor and third-party claims are attributed, not adopted. \"Demonstrated\" and \"confirmed in production\" are distinct and not interchangeable.\n\n---\n\n## PRS-09. STATUS AND TRANSITIONS\n\nPRS-09.1 Status values: DRAFT, ACTIVE, REINFORCED, WITHDRAWN, SUPERSEDED, RETIRED.\n\nPRS-09.2 Permitted transitions:\n\n- DRAFT to ACTIVE, on issuance\n- ACTIVE to REINFORCED, on recorded reinforcement\n- ACTIVE or REINFORCED to WITHDRAWN, under PRS-12\n- ACTIVE or REINFORCED to SUPERSEDED, on issuance of a superseding version\n- ACTIVE or REINFORCED to RETIRED, on a met Kill Condition\n- WITHDRAWN to DRAFT, for repair\n\nPRS-09.3 **No status change occurs without a recorded amendment.** The amendment names the transition, the date and the instrument or evidence that caused it. A status that moved without an instrument is corrected by returning the status, not by backfilling the instrument.\n\nPRS-09.4 Position Status and Amendment Note are mutually consistent. A rendered amendment note with \"Amendments: None\" is non-conforming, and so is the reverse.\n\n---\n\n## PRS-10. AMENDMENT, VERSIONING AND INTEGRITY\n\nPRS-10.1 Revision policy across the Position Record is amendment only. There are no silent edits, including corrections of corrupted text.\n\nPRS-10.2 Any change to canonical text under PRS-03.1 is an amendment. It carries a version increment, an amendment entry and a recomputed hash.\n\nPRS-10.3 Changes outside PRS-03.1 are rendering changes. They carry no version increment and no hash change.\n\nPRS-10.4 Amendments are numbered AMD-NNN per position and dated. Multiple positions amended under one instrument share the instrument reference and the date.\n\nPRS-10.5 Minor version increments cover amendment within a position's claim. Major version increments cover reissue after withdrawal or a changed claim, and carry Supersedes.\n\nPRS-10.6 The Record Integrity block publishes the hash, the scope note and the version. The same value publishes in the canonical PDF and the rendering.\n\n---\n\n## PRS-11. HASH RECONCILIATION\n\nPRS-11.1 A holder of a previously exported PDF verifies its hash against the value printed in that PDF. After an amendment, that value no longer matches the current artifact.\n\nPRS-11.2 Every amendment wave publishes a reconciliation note listing, per affected position: prior version, prior hash, new version, new hash, and the instrument that superseded it.\n\nPRS-11.3 The reconciliation note is a permanent record artifact. It is not superseded by later waves; later waves append.\n\nPRS-11.4 Absent PRS-11.2, a hash mismatch is indistinguishable from tampering, which defeats the purpose of publishing the hash.\n\n---\n\n## PRS-12. WITHDRAWAL AND SUPERSESSION\n\nPRS-12.1 A position is withdrawn when its canonical text cannot be brought into conformance by amendment. The test is whether an amendment note could describe the correction without itself documenting text that should never have been published.\n\nPRS-12.2 Withdrawal is executed by DM instrument. It records the position ID, version withdrawn, date, and the ground under PRS-12.1.\n\nPRS-12.3 A withdrawn position renders at its URL with status WITHDRAWN, the withdrawal instrument reference, and its metadata block. Canonical text of the withdrawn version is not rendered.\n\nPRS-12.4 Position IDs are never reused. A withdrawn position returns at the same ID with a major version increment and Supersedes naming the withdrawn version.\n\nPRS-12.5 Registered reliance on a withdrawn version is notified under CHQ-R-2026-001. Where no reliance is registered, withdrawal carries no external obligation.\n\nPRS-12.6 Withdrawal cost rises with inbound citation. A position cited by others cannot be withdrawn without amending every citing position in the same instrument.\n\n---\n\n## PRS-13. CROSS-REFERENCE AND CITATION\n\nPRS-13.1 A cross-reference names the position ID and its full registered title. Shortened titles, paraphrased titles and symbols in place of words are non-conforming.\n\nPRS-13.2 The ID and the title must match. A mismatched pair is a citation error regardless of which element is correct.\n\nPRS-13.3 Position numbering is issuance order, not dependency order. A later-numbered position may be doctrinally upstream of an earlier one.\n\nPRS-13.4 Where a position is upstream of an earlier-issued position, both carry the linkage. The earlier position is amended to record the inbound reference.\n\nPRS-13.5 **A claim that more than one position depends on is an instrument, not a paragraph.** Joint claims may not live in a Structural Observation or Architectural Implication section. They are promoted to their own instrument or removed.\n\nPRS-13.6 Internal identifiers permitted in published prose: position IDs, ASC IDs, assumption IDs (A-NNN), condition IDs (SC-NNNN-NNN), signal IDs, exhibit IDs, docket IDs, pattern register IDs, lens IDs. Permitted only where the referenced register is itself published.\n\nPRS-13.7 Internal identifiers prohibited in published prose: PAT, TSEM, SGR, RUN identifiers, and any workbook, sheet or run-log reference.\n\n---\n\n## PRS-14. EVIDENCE ATTRIBUTION\n\nPRS-14.1 Every signal in an Evidence Basis carries a named source. CHQ-P-2026-016 demonstrates the conforming pattern.\n\nPRS-14.2 Quantitative claims carry their source inline: counts, percentages, download figures, exposure figures, time windows.\n\nPRS-14.3 Named-actor attribution is not stated as fact until PRIMARY read. Secondary attribution is rendered as reported, with the reporting party named.\n\nPRS-14.4 Compound claims are decomposed before CONFIRMED. Confidence is the minimum across layers. A load-bearing layer below PROVISIONAL splits the claim.\n\nPRS-14.5 Where a position's state depends on N independent mechanisms, each mechanism is individually assessed against the position's claim. A mechanism that does not instantiate the claim is removed and the counts adjusted.\n\n---\n\n## PRS-15. EDITORIAL STANDARD\n\nPRS-15.1 No em dashes in canonical text, in prose or as a field separator. Constraint listings use a colon.\n\nPRS-15.2 No formulaic parallel structures, no directional forecasting language outside a Forecast Condition block, no AI-pattern constructions.\n\nPRS-15.3 The position statement appears once. Restating it verbatim later in the same document is non-conforming.\n\nPRS-15.4 Independence wording, uniform across the record:\n\n- Authored independently of any subscribing organization\n- Not tailored to a specific contractual, commercial, or advocacy interest\n- Subsequent analysis based only on new evidence\n\nThe wording \"Not tailored to a specific environment, incident, or vendor\" is retired. It is contradicted on its own page wherever evidence names vendors, which the record requires.\n\nPRS-15.5 Naming vendors, products and incidents in an Evidence Basis is required by PRS-14 and is not a breach of independence.\n\n---\n\n## PRS-16. PUBLICATION GATE\n\nPRS-16.1 A position does not publish until every item passes:\n\n1. Lens assigned, not PENDING\n2. Evidence Docket assigned, not NULL\n3. Exhibits populated or explicitly stated as none\n4. Every signal carries a named source\n5. Signal Count equals the listed identifiers\n6. Vector Count conforms to PRS-07.3\n7. Authority Derivation and Doctrinal Alignment agree\n8. Every cross-reference ID and title pair verified\n9. Prose conforms to the certainty parity rule for its evidence state\n10. No em dashes in canonical text\n11. Closed-vocabulary fields carry valid values\n12. Hash computed over PRS-03.1 and published in both artifacts\n\nPRS-16.2 The gate is run before issuance and again before any rendering rebuild.\n\nPRS-16.3 A position failing any item is held, not published with a caveat.\n\n---\n\n## PRS-17. TRANSITION\n\nPRS-17.1 The sixteen positions published before this Standard are brought into conformance by the corrective wave ratified under CHQ-RAT-2026-001.\n\nPRS-17.2 Wave execution order:\n\n- **WAVE-1.** Map each of the 85 change-order items to a PRS provision.\n- **WAVE-2.** Completeness pass. Any item not decided by a provision is a gap in this Standard and is resolved by PRS amendment before the wave proceeds. Any provision decided against by an item is a conflict and is escalated to DM.\n- **WAVE-3.** Execute amendments. One date, one instrument reference, one version increment and one recomputed hash per affected position. Publish the PRS-11 reconciliation note.\n- **WAVE-4.** Rebuild the rendering from canonical PDFs.\n\nPRS-17.3 CHQ-P-2026-007 is withdrawn under PRS-12 rather than amended, on the PRS-12.1 ground, and returns as v2.0.\n\nPRS-17.4 The Assumption Register publishes as reference only, outside reliance eligibility under CHQ-R-2026-001, until its states have held for one full cycle. DM may lift this at any time.\n\nPRS-17.5 CHQ-P-2026-014 publishes, or CHQ-P-2026-015 is amended to remove the 014 pairing and the A-032 reference, before WAVE-3.\n\nPRS-17.6 Until WAVE-3 completes, the record is in active correction. No new position issues during this period.",
      "type": "paragraph"
    }
  ]
}
```