{
  "schema_version": "1.3.0",
  "slug": "when-does-an-iso8601-timestamp-without-a-timezone-silently-shift-the-event-time",
  "title": "When does an ISO8601 timestamp without a timezone silently shift the event time?",
  "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 the consumer assumes UTC but the producer may have emitted local time. Excludes timestamps that carry an explicit offset and systems with a global TZ discipline enforced by schema.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-does-an-iso8601-timestamp-without-a-timezone-silently-shift-the-event-time.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-does-an-iso8601-timestamp-without-a-timezone-silently-shift-the-event-time.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-does-an-iso8601-timestamp-without-a-timezone-silently-shift-the-event-time.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 724,
    "python_slice_tokens": 97,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "**Predicate.** ISO8601 allows a timestamp to omit timezone. That form is *local* by definition, but most consumers assume UTC. If producer and consumer disagree on interpretation, the same string names two different instants differing by the offset between producer locale and UTC. **Failure.** A service running in UTC-8 emits `2026-11-02T09:00:00`. A consume...",
    "what_was_observed": "**Signature.** Events clustered at an offset boundary. Nightly batches whose window no longer matches expected traffic. Timestamps that appear \"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 is shifted...",
    "condition_of_validity": "Timestamps are unambiguous only while at least one holds: 1. **Explicit offset.** Every timestamp carries Z or ±HH:MM, and the schema enforces it. 2. **Naive = UTC by convention.** Both producer and consumer are documented, enforced, and tested to interpret naive as UTC, including during DST changes. 3. **Typed representation.** Timestamps are parsed into a ...",
    "decision_boundary": "- Offset present on every timestamp: unambiguous. - Naive with global TZ discipline enforced by schema: safe. - Naive with no discipline: shift is guaranteed for any producer whose locale differs from the consumer's assumed UTC. - Mixed: the worst case, because some timestamps are correct and some shifted, and no filter distinguishes them.",
    "operational_effect": "The defect is proportional to the timezone offset of the producer, 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": [
    "DST_SHIFT_OR_CLOCK_SKEW"
  ],
  "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
  }
}