{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T23:47:34.928Z",
  "record_id": "VXI-EXT-PROCUREMENT-SENSORTHINGS-SERVER-ASSIGNED-PHENOMENON-TIME-01-v1",
  "record_kind": "external_reference",
  "title": "SensorThings server-assigned observation times",
  "system": "OGC SensorThings Sensing 1.1",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does SensorThings phenomenonTime always come from the sensing device clock?",
  "near_questions": [
    "Can SensorThings fill in a missing observation timestamp?",
    "Is SensorThings phenomenonTime always measured at the device?",
    "What time is assigned when a SensorThings client has no clock?",
    "How can an agent distinguish SensorThings server time from sample time?"
  ],
  "supported_claims": [
    {
      "claim": "SensorThings Sensing 1.1 permits a client to omit phenomenonTime when creating an observation. The service must then assign its current server time. A populated phenomenonTime can therefore be a server fallback rather than a device timestamp. A freshness decision needs the submitted observation and timestamp-origin policy, not just the stored field.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Actual observation time and clock accuracy were not inspected.",
    "No independently verified physical outcome, calibration, industrial safety, deletion or complete capture.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "SensorThings Sensing 1.1 permits a client to omit phenomenonTime when creating an observation. The service must then assign its current server time. A populated phenomenonTime can therefore be a server fallback rather than a device timestamp. A freshness decision needs the submitted observation and timestamp-origin policy, not just the stored field.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html",
    "source_url": "https://docs.ogc.org/is/18-088/18-088.html",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SENSORTHINGS-SERVER-ASSIGNED-PHENOMENON-TIME-01-v1",
    "candidate_record_sha256": "03f51b17aa287be56949163ca8f074645d565a287f6227c6ff5a5ec6a3e97be7",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "SensorThings Sensing 1.1 permits a client to omit phenomenonTime when creating an observation. The service must then assign its current server time. A populated phenomenonTime can therefore be a server fallback rather than a device timestamp. A freshness decision needs the submitted observation and timestamp-origin policy, not just the stored field.",
    "required_buyer_context": "Original observation submission; Timestamp assignment policy; Device clock and collection evidence. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-24",
    "claim_to_check": "Does SensorThings phenomenonTime always come from the sensing device clock?",
    "documented_statement": {
      "status": "documented",
      "statement": "SensorThings Sensing 1.1 permits a client to omit phenomenonTime when creating an observation. The service must then assign its current server time. A populated phenomenonTime can therefore be a server fallback rather than a device timestamp. A freshness decision needs the submitted observation and timestamp-origin policy, not just the stored field.",
      "source_ids": [
        "sensorthings-sensing"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Identify server fallback before assessing sample age. This is a review judgment, not a measured deployment result.",
      "source_ids": [
        "sensorthings-sensing"
      ]
    },
    "buyer_evidence_required": [
      "Original observation submission",
      "Timestamp assignment policy",
      "Device clock and collection evidence"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse device-time attribution without evidence that the client supplied it."
    },
    "unknowns": "Actual observation time and clock accuracy were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual observation time and clock accuracy were not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "sensorthings-sensing",
        "url": "https://docs.ogc.org/is/18-088/18-088.html",
        "final_url": "https://docs.ogc.org/is/18-088/18-088.html",
        "status": 200,
        "captured_at_utc": "2026-10-24T23:24:18.177Z",
        "sha256": "76d3bb035eabd6a690b93532ca94cc610dd868abe54d9988b07d24ec4cac25ae",
        "bytes": 1730821,
        "title": "OGC SensorThings Part1 Sensing 1.1, published 2021-08-04 — 18-088.html",
        "hash_basis": "SHA-256 of unmodified HTTP response body bytes",
        "rights_review": "Original bounded paraphrase; source bodies are captured privately and not redistributed. OGC published-document copyright and licence reviewed; no modified standard or endorsement is represented.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "8.2.6 Observation properties; phenomenonTime",
          "8.2.6 Observation properties; resultTime",
          "8.2.2 Location; 8.2.6 Observation relations",
          "8.2.4 Datastream properties and relations",
          "10.4 entity deletion; Table 25 integrity constraints",
          "13.2.2 dataArray creation response",
          "12 MultiDatastream; requirement 42",
          "9.3.3.2 top; response pagination",
          "11 batch requests; 11.3 example batch response",
          "14 MQTT extension and serverSettings",
          "14.1 observation creation over MQTT",
          "7.7 security"
        ],
        "version_context": "OGC SensorThings Part1 Sensing 1.1, published 2021-08-04; fixed published document 18-088; linked Sensing 1.1 errata URL returned 404, so absence of errata is not established. Documentation is not evidence of buyer deployment behaviour."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Identify server fallback before assessing sample age.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the specification version, errata availability, deployed profile, clock policy and retained operation results before relying on a current outcome."
    },
    "buyer_relevance": "Identify server fallback before assessing sample age.",
    "refusal_conditions": [
      "Refuse device-time attribution without evidence that the client supplied it."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Identify server fallback before assessing sample age.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#sensorthings-server-assigned-phenomenon-time",
  "machine_readable_record": "/varexis-index/records/sensorthings-server-assigned-phenomenon-time.json"
}