{
  "readAt": "2026-09-21",
  "verificationScope": "Codex read the named sections through the web tool; no complete-standard conformance, engine execution, historical parent-source ratification or paywalled clause verification. Original design, no third-party schema copied. Provider source claims are separately preserved and not automatically adopted.",
  "sources": [
    {
      "id": "S01",
      "url": "https://www.w3.org/TR/2022/CRD-owl-time-20221115/",
      "edition": "2022-11-15 Candidate Recommendation Draft",
      "section": "Principles and vocabulary; temporal reference systems",
      "evidence": "observed-source-text",
      "claim": "Temporal topology and reference systems need explicit interpretation. Half-open storage and receipt history are our additional choices, not an OWL-Time conformance claim.",
      "decision": "accepted-as-comparison-not-conformance"
    },
    {
      "id": "S02",
      "url": "https://www.w3.org/TR/scxml/",
      "edition": "2015-09-01 Recommendation",
      "section": "3.10 History; 3.11 Legal state configurations",
      "evidence": "observed-source-text",
      "claim": "A history pseudostate restores a prior active configuration. It is not an archival audit ledger. Parallel configurations cannot always be represented by one status code.",
      "decision": "accepted-as-comparison-not-conformance"
    },
    {
      "id": "S03",
      "url": "https://docs.xtdb.com/about/time-in-xtdb.html",
      "edition": "Living documentation read 2026-09-21",
      "section": "System time; Valid time; Behind the scenes",
      "evidence": "observed-source-text",
      "claim": "Distinct system and valid axes support late corrections and earlier recorded views. The application contract chooses full snapshots, not XTDB SQL portion updates.",
      "decision": "accepted-as-comparison-not-conformance"
    },
    {
      "id": "S04",
      "url": "https://docs.xtdb.com/concepts/key-concepts.html",
      "edition": "Living documentation read 2026-09-21",
      "section": "Temporal columns and bitemporality; transaction processing",
      "evidence": "observed-source-text",
      "claim": "Database temporal columns and half-open periods inform the narrow reference. Engine imports can have different clock controls; no automatic adapter or SQL conformance is claimed.",
      "decision": "accepted-as-comparison-not-conformance"
    },
    {
      "id": "S05",
      "url": "https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal/overview?view=sql-server-ver17",
      "edition": "Living vendor documentation read 2026-09-21",
      "section": "How does temporal work?; How do I query temporal data?",
      "evidence": "observed-source-text",
      "claim": "Columns named ValidFrom/ValidTo in this system-time example use transaction begin time. Import must not mistake them for domain effective time. Equal transaction instants motivate a separate sequence.",
      "decision": "accepted-as-comparison-not-conformance"
    },
    {
      "id": "S06",
      "url": "https://learn.microsoft.com/en-us/azure/architecture/patterns/event-sourcing",
      "edition": "Living architecture guidance read 2026-09-21",
      "section": "Solution; Pattern advantages; concurrency example",
      "evidence": "observed-source-text",
      "claim": "Append-only domain-event replay is an alternative. Optimistic expected-version checks inform our guarded writes; this companion records assertion snapshots rather than pretending to execute domain events.",
      "decision": "accepted-as-comparison-not-conformance"
    },
    {
      "id": "S07",
      "url": "https://semver.org/spec/v2.0.0.html",
      "edition": "2.0.0",
      "section": "Items 1–3, 9–11",
      "evidence": "observed-source-text",
      "claim": "API compatibility promises require a defined surface. The companion uses only the normal numeric triplet as a binding grammar and infers no compatibility from a label.",
      "decision": "accepted-as-comparison-not-conformance"
    }
  ]
}