{
  "schema_version": "1.3.0",
  "slug": "what-invariants-prevent-naive-iso8601-timestamps-from-shifting-the-event-instant",
  "title": "What invariants prevent naive ISO8601 timestamps from shifting the event instant?",
  "date_of_record": "2026 November 2",
  "scope": "Applies to timestamps serialized as ISO8601 without a trailing Z or ±HH:MM offset, at a boundary where producer and consumer may disagree on interpretation. Does not apply to timestamps carrying an explicit offset, or systems with a global TZ discipline enforced by schema.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-invariants-prevent-naive-iso8601-timestamps-from-shifting-the-event-instant.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-naive-iso8601-timestamps-from-shifting-the-event-instant.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-naive-iso8601-timestamps-from-shifting-the-event-instant.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 780,
    "python_slice_tokens": 97,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "An ISO8601 timestamp without a timezone is *local* by definition, but most consumers assume UTC. When producer and consumer disagree, the same string names two instants differing by the offset between producer locale and UTC. **Invariant.** The instant is unambiguous if and only if every timestamp on the path carries Z or ±HH:MM, or producer and consumer are...",
    "what_was_observed": "**Signature.** Events clustered at an offset boundary. Nightly batches whose window no longer matches expected traffic. Timestamps appearing off by hours only for records from a specific source. **Trace.** Producer in UTC-8, serialization omits offset, consumer in UTC. Timestamp `2026-11-02T09:00:00` becomes 2026-11-02T09:00:00Z, but the producer meant 2026-11-02T17:00:00Z. Every event from that source shifts by eigh...",
    "condition_of_validity": "The instance must ensure at least one holds before it treats a naive timestamp as a point in time: 1. **Must carry offset.** Every timestamp carries Z or ±HH:MM, and the schema enforces it. 2. **Must document naive-means-UTC.** Both producer and consumer are documented, enforced, and tested to interpret naive as the same zone, including during DST changes. 3...",
    "decision_boundary": "- Offset present on every timestamp: unambiguous. - Naive with global TZ discipline enforced by schema: safe. - Naive with no discipline: shift guaranteed for any producer whose locale differs from the consumer's assumed zone. - Mixed: worst case; some timestamps are correct, some shifted, and no filter distinguishes them.",
    "operational_effect": "The defect is proportional to the producer's timezone offset, which changes twice a year for DST, so it can shift by an hour without any code change. Remediation is offset-enforcement in the schema. The trap is to append `Z` in the parser. That assumes the producer already meant UTC, which is exactly the assumption in question."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "13a636f8daf53f45aa610110942124e4fad096c3adbf1f0ee93b3f82d8060013",
    "verified_classes": [
      "NaiveTimestampError",
      "TimestampGate"
    ],
    "verified_functions": [
      "dispatch_timestamp_parse",
      "verify"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "NaiveTimestampError"
    ],
    "sample_fail_closed_invariants": [
      "timestamp lacks timezone; producer and consumer may disagree on the instant"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "re"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}