# Date Authority Functions as a Dependency Layer for Adjudication Legitimacy

- **Artifact ID:** CHQ-ASC-2026-006
- **Version:** v1.1
- **Status:** Canonical
- **Public record:** https://record.cybersecurityhq.com/constraints/chq-asc-2026-006
- **Machine-record SHA-256:** `6fc1ad2f886a47be7ab055f59409261ce5e06eab1571cb9457668cda7a4a249c`

## Complete structured record

```json
{
  "id": "CHQ-ASC-2026-006",
  "legacy_ids": [
    "CHQ-ACJ-2026-006"
  ],
  "title": "Date Authority Functions as a Dependency Layer for Adjudication Legitimacy",
  "version": "v1.1",
  "issued": "2026-05-02",
  "status": "Canonical",
  "doctrine_class": "Anticipatory Structural Constraint",
  "precedent": [
    "CHQ-ASC-2026-002",
    "CHQ-ASC-2026-003"
  ],
  "purpose": "This Anticipatory Structural Constraint establishes the governing principle that temporal authority — the system’s ability to correctly anchor reasoning, attribution, and governance state to the date and time at which they occur — functions as a dependency layer for adjudication legitimacy in any structured intelligence system.\n\nGovernance frameworks that treat chronology as metadata hygiene rather than as adjudication infrastructure are operating under an assumption that the available evidence does not consistently support, particularly in systems where reasoning is composed across signals, assumptions, and positions that span time. This constraint defines the interpretive boundary for all CHQ governance artifacts that depend on temporal coherence: assumption applicability, position lineage, exhibit temporal scope, evidence docket freeze timestamps, and any structured output whose conclusions depend on the temporal precedence of its constituent inputs.",
  "core_judgment": "Temporal coherence is not a property that can be added to outputs after the fact. It is a property that constrains every step of reasoning that produces those outputs. Chronology establishes precedence. Precedence affects doctrine applicability. Doctrine applicability affects adjudication. Adjudication affects publication legitimacy. A failure at any layer in this chain does not produce an obvious error. It produces outputs whose individual components are correct and whose aggregate inference about current state is wrong because the temporal frame is wrong.\n\nThe dangerous failure mode is not overt date corruption — a wrong date in a run header is detectable. The dangerous failure mode is subtle temporal bleed: old assumptions silently treated as active, dormant governance states implicitly revived, publication cadence interpreted as evidentiary freshness, AI-generated synthesis collapsing historical separation boundaries.\n\nWhen a system produces a claim about current state by reasoning across signals from different time windows without explicit temporal anchoring, the error is invisible in the output and undetectable by normal review. The individual signal entries remain accurate. The aggregate inference about current state is wrong because the temporal frame is wrong.\n\nThis constraint requires that systems producing structured intelligence outputs treat any confirmed temporal-context drift as a structural integrity event, not a metadata error.",
  "derivation_intro": "This constraint derives from prior canonical constraints and observed structural conditions:",
  "derivation": [
    "From CHQ-ASC-2026-002: Contemporaneous evidence is the basis of knowledge. Evidence whose temporal context has been corrupted is no longer contemporaneous in any operationally meaningful sense, even if the underlying source material remains accurate.",
    "From CHQ-ASC-2026-003: Institutional trust state cannot be represented by Boolean signals. The same principle applies to temporal state: chronology is not a binary “current/not-current” property but a continuous boundary condition affecting which assumptions, patterns, and positions remain in force.",
    "From an observed CHQ system condition: a confirmed temporal-context date-drift event on April 27, 2026, established that temporal-context failures occur in practice within structured intelligence systems and produce reasoning errors that propagate through downstream artifacts before detection."
  ],
  "scope_governs": [
    "Assumption applicability assessments where the temporal validity of an assumption has been claimed",
    "Position lineage and version-effective dates",
    "Exhibit temporal scope declarations",
    "Evidence docket freeze timestamps and the contemporaneous validity claims they encode",
    "Run authority continuity across the production of structured intelligence outputs",
    "Pattern reinforcement counts and their interpretation as current strength",
    "Publication cadence interpretation as a proxy for evidentiary freshness",
    "Any CHQ governance artifact whose conclusions depend on temporal precedence between signals, assumptions, or positions"
  ],
  "scope_does_not_govern": [
    "Operational scheduling, calendaring, or reminder systems",
    "Incidental references to dates within artifact prose where the date is not load-bearing for the artifact’s conclusions",
    "Human-authored annotations whose temporal claims are descriptive rather than authoritative",
    "Dating practices for external sources cited within CHQ artifacts (those follow source-citation discipline)"
  ],
  "relationship_to_derived": "CHQ governance procedures applying this constraint inherit its authority but operationalize it through specific detection and escalation mechanisms. The first such mechanism is the date-authority gate established in May 2026: any confirmed temporal-context date-drift occurrence triggers mandatory structured review before the next operational run closes; any second confirmed occurrence within a rolling ninety-day window triggers mandatory adjudication of all temporally-dependent outputs produced in the affected window.\n\nCHQ Positions, Memoranda, Exhibits, and Evidence Dockets that rely on temporal precedence for their conclusions inherit this constraint’s scope. They do not inherit its permanence; their specific conclusions remain subject to revision as evidence evolves. This constraint does not.",
  "irreversibility_statement": "This constraint contains no retirement triggers.\n\nIt may be superseded only by a successor Anticipatory Structural Constraint demonstrating that structured intelligence systems can produce coherent adjudication outputs without temporal anchoring of their constituent reasoning steps. No such demonstration exists or is anticipated. Improvements in temporal-context detection, automation of date validation, or reductions in the frequency of confirmed temporal-context date-drift incidents are not grounds for supersession; they are grounds for sustained operational compliance with this constraint.",
  "boundary_of_application": [
    "Prescribe specific date-validation tooling, automation systems, or audit cadences",
    "Assign liability for temporal-context failures in any specific organization or system",
    "Replace operational scheduling or reminder controls",
    "Establish that any specific output has been temporally compromised in any specific instance",
    "Address the accuracy of any external source’s own date claims"
  ],
  "attestation": "This constraint reflects CHQ’s position that structured intelligence systems cannot produce defensible adjudication outputs without treating chronology integrity as governance infrastructure rather than metadata. Single confirmed manifestation of temporal-context drift is sufficient grounds for structural governance of the failure mode because governance-layer temporal failures are asymmetrically dangerous: the cost of under-governing date authority exceeds the operational cost of the review mechanisms this constraint requires.",
  "pdf_hash": "3f6a471c465557f76c2d692e30ede9224e04b5a6a25ed31c14aa4d4f29b40a4c",
  "classification_scope": "INTERNAL_ADJUDICATION",
  "classification_resolution": "ASC-006 remains an Anticipatory Structural Constraint because it binds the legitimacy of adjudication across artifact classes. It governs an internal structural dependency, not a discretionary implementation method, tool, or operating procedure.",
  "lifecycle_governance": {
    "error_correction": "A clerical, citation, date, identifier, or transcription error may be corrected only by a dated erratum that identifies the prior text, corrected text, evidence for the correction, affected hash, and whether meaning changed. Meaning-changing corrections are amendments, not errata.",
    "amendment": "A constraint may be amended only by a ratified, versioned amendment that preserves the prior version, states the changed proposition and rationale, recomputes the canonical hash, and notifies registered reliance. An amendment may clarify or narrow a constraint but may not silently replace its core judgment.",
    "successor": "A constraint may be superseded only by a separately identified successor that cites the predecessor, satisfies the predecessor's stated supersession test, states the exact proposition displaced, and records the effective transition. Prior versions remain historical and ineligible for new reliance after supersession.",
    "permanence": "Permanent means no automatic expiry or retirement trigger. It does not mean immune from demonstrated error, transparent amendment, or a successor that satisfies the canonical supersession test."
  },
  "governance_amendments": [
    {
      "date": "2026-09-22",
      "effective_version": "v1.1",
      "amendment_id": "CHQ-ASC-TEMPLATE-2026-001",
      "description": "Successor and reassessment language normalized as explicit artifact-governance metadata; individual canonical supersession tests remain controlling.",
      "canonical_hash_effect": "RECOMPUTED"
    },
    {
      "date": "2026-09-22",
      "effective_version": "v1.1",
      "amendment_id": "CHQ-PRS-2026-001-AMD-003",
      "description": "Class-wide error-correction, amendment, successor, and permanence semantics ratified as non-canonical governance metadata. ASC-006's internal-adjudication classification is formally resolved without changing its canonical constraint text.",
      "canonical_hash_effect": "UNCHANGED"
    }
  ]
}
```