# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T20:57:02Z", "synthesisSha256": "71a37b8522457e5b69c344b9941253c9b4dbef60a9ca3b5e0a777c8d13c9084a", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-FLW-014", "registryId": "vr.wm-flw-014", "name": "Network Flow / Telemetry Stream", "version": "0.1.0", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.FLW.NET" ], "tags": [ "network", "flow", "telemetry", "stream", "phy.flw.net" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-flw-014-network-flow-telemetry-stream/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-014", "model": { "registry_id": "vr.wm-flw-014", "model_id": "WM-FLW-014", "name": "Network Flow / Telemetry Stream", "entry_kind": "entity", "purpose": "Describe a governed, time-varying telemetry stream about flow through a physical or logical network, preserving measurement meaning, provenance and use limits.", "scope_statement": "One persistent logical telemetry stream with versioned observation contracts and referenced or locally recorded observations. Physical measurements and packet-flow records are alternative explicit profiles. The stream is distinct from the transported material or energy, the network, the sensor, any one observation, and the delivery connection. Associated pressure or voltage can qualify flow context but does not automatically become a flow quantity.", "in_scope": [ "Stream identity, accountable custodian, profile and continuity across collection sessions", "Network observation scope, quantity and units, measurement method, selection, event time and delivery evidence", "Observation record identity, counter semantics, quality, derived-view lineage, controlled retention and projection" ], "out_of_scope": [ "Network topology and asset lifecycle masters, sensor design and calibration execution", "Physical conservation or hydraulic/electrical simulation, resource accounting, billing adjudication and logistics custody", "Packet payload inspection, collection deployment, routing changes, valve or setpoint control, and automated incident enforcement", "General application traces, arbitrary business event streams and protocol implementation certification" ], "boundary_notes": [ { "neighbor": "WM-BLT-003 Infrastructure Network", "distinction": "The registry parent is contextual organization, not inheritance of network structure. Reference a versioned node, link, interface or observation region; topology stays in the network master.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "neighbor": "Sensor, observation and collector masters", "distinction": "The stream has persistent identity and membership rules. Sensors, individual measurements and collection sessions retain their own identities and lifecycle; this model stores references and stream-specific qualifications.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "neighbor": "WM-FLW-008 Mass-balance / Material Flow and WM-FLW-015 Resource Consumption", "distinction": "Telemetry can supply observations to balances or consumption assessment; it does not assert conservation, loss, billable consumption or causal diagnosis. Quantity, sign, interval and uncertainty must be compatible before comparison.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "neighbor": "Actuation, incident and general event records", "distinction": "Telemetry observations and local quality assessments do not authorize intervention. Irregular and event-triggered observations are allowed; a generic operational event log is a different subject.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc7011", "version_or_date": "RFC 7011, September 2013", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:55:41Z", "relevance": "Sections 2-5, 8-11: scoped flow export, templates, timing, reliability and privacy. Packet profile only." }, { "id": "SRC-002", "title": "Information Model for IP Flow Information Export (IPFIX)", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc7012.html", "version_or_date": "RFC 7012, September 2013", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:55:41Z", "relevance": "Sections 2-4: field definitions, units, namespaces and counter semantics. Does not define a universal physical-flow schema." }, { "id": "SRC-003", "title": "Sampling and Filtering Techniques for IP Packet Selection", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc5475", "version_or_date": "RFC 5475, March 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:55:41Z", "relevance": "Sections 3-5: packet selection population and sampling/filtering distinctions; no universal expansion factor." }, { "id": "SRC-004", "title": "OGC SensorThings API Part 1: Sensing Version 1.1", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/18-088/18-088.html", "version_or_date": "Version 1.1, OGC 18-088", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:55:41Z", "relevance": "Sections 8.2.4-8.2.8: datastream, sensor, observed property, observation and feature relations; observation timing and quality." }, { "id": "SRC-005", "title": "Semantic Sensor Network Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/", "version_or_date": "Recommendation 2017-10-19", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:55:41Z", "relevance": "Sections 4.3, 4.6-4.9 and 5.1: sensor, procedure, feature, observation, conditions and system capabilities. Joint work with OGC." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/2013/REC-prov-o-20130430/", "version_or_date": "Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:55:41Z", "relevance": "Sections 3-4: entities, activities, attribution, derivation and revision; provenance is not a truth certificate." }, { "id": "SRC-007", "title": "Sensor Measurement Lists (SenML)", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc8428", "version_or_date": "RFC 8428, August 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:55:41Z", "relevance": "Sections 4 and 5.7: sensor names, base fields, units, time and integrated sums; reset and wrap limitations." }, { "id": "SRC-008", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:55:41Z", "relevance": "Sections 4-5: timestamp offsets and syntax. Does not prove clock synchronization or establish interval identity." } ], "structure": { "bundles": [ { "id": "bundle-scope", "name": "Stream definition and observation scope", "description": "Stream-specific context for stream definition and observation scope.", "rationale": "Authored grouping of source-supported concepts and explicit adoption questions; no cited standard mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-identity", "name": "Stream identity and profile", "description": "Assign a governed stream identity independently of endpoint, sensor and observation IDs. Declare a physical-measurement or packet-flow profile; multiple quantities require explicit channel definitions.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-identity", "name": "Persistent stream contract", "description": "Assign a governed stream identity independently of endpoint, sensor and observation IDs. Declare a physical-measurement or packet-flow profile; multiple quantities require explicit channel definitions.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-identity-1", "text": "Which master namespace and stable identifier distinguish this stream from a sensor, endpoint or individual record?", "kind": "identity", "answer_data": [ "identity: master namespace, stream ID, alias evidence, revision, reconciliation status", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-2", "text": "Which flow domain and observation profile define membership in this stream?", "kind": "classification", "answer_data": [ "profile: domain, medium or packet population, physical or packet profile, channels, membership predicate, profile version", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-3", "text": "Which accountable operator and custodian may approve this stream contract?", "kind": "ownership", "answer_data": [ "custody: operator role, steward reference, authority basis, purpose, approval evidence", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-identity-1", "name": "Identity", "description": "Candidate nested field group: identity: master namespace, stream ID, alias evidence, revision, reconciliation status. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "data-identity-2", "name": "Profile", "description": "Candidate nested field group: profile: domain, medium or packet population, physical or packet profile, channels, membership predicate, profile version. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "data-identity-3", "name": "Custody", "description": "Candidate nested field group: custody: operator role, steward reference, authority basis, purpose, approval evidence. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Stream identity and profile register", "description": "Versioned stream-local assertions and references for persistent stream contract. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-network", "name": "Observation scope and network links", "description": "Bind each record to its applicable network scope and direction. Location of a collector is not the observed feature. Keep overlapping scopes visible to avoid counting the same flow twice.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-network", "name": "Versioned observation boundary", "description": "Bind each record to its applicable network scope and direction. Location of a collector is not the observed feature. Keep overlapping scopes visible to avoid counting the same flow twice.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "questions": [ { "id": "q-network-1", "text": "Which network revision and node, link, interface or region was observed?", "kind": "spatial", "answer_data": [ "scope: network master reference, topology revision, point or region reference, location or geometry reference, validity interval", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-network-2", "text": "How are flow direction and overlapping or nested observation scopes represented?", "kind": "relationship", "answer_data": [ "direction: orientation basis, inlet or outlet designation, forward or reverse channel, overlap group, aggregation exclusion", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-network-3", "text": "Which scope binding applied when a sensor moved or the network changed?", "kind": "temporal", "answer_data": [ "binding: sensor or probe reference, effective interval, changed topology reference, unresolved interval, supporting evidence", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-network-1", "name": "Scope", "description": "Candidate nested field group: scope: network master reference, topology revision, point or region reference, location or geometry reference, validity interval. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "data-network-2", "name": "Direction", "description": "Candidate nested field group: direction: orientation basis, inlet or outlet designation, forward or reverse channel, overlap group, aggregation exclusion. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "data-network-3", "name": "Binding", "description": "Candidate nested field group: binding: sensor or probe reference, effective interval, changed topology reference, unresolved interval, supporting evidence. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-network", "name": "Observation scope and network links register", "description": "Versioned stream-local assertions and references for versioned observation boundary. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-meaning", "name": "Measurement meaning and method", "description": "Stream-specific context for measurement meaning and method.", "rationale": "Authored grouping of source-supported concepts and explicit adoption questions; no cited standard mandates this hierarchy.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-quantity", "name": "Quantity and counter meaning", "description": "Keep rate, interval amount, instantaneous value, total counter, delta counter and integrated sum distinct. SenML sum is a time integral, not a generic byte or event counter. Units and sign belong to each profile.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-quantity", "name": "Typed measurement values", "description": "Keep rate, interval amount, instantaneous value, total counter, delta counter and integrated sum distinct. SenML sum is a time integral, not a generic byte or event counter. Units and sign belong to each profile.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ], "questions": [ { "id": "q-quantity-1", "text": "What quantity, unit, scale and direction convention give each channel value its meaning?", "kind": "measurement", "answer_data": [ "quantity: property URI, medium, unit URI and symbol, scale, sign convention, result datatype, applicable conditions", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-quantity-2", "text": "Is this value a rate, interval amount, gauge, total counter, delta counter or time integral?", "kind": "classification", "answer_data": [ "semantics: value category, integration or count basis, temporal support, counter width, reset rule, profile definition", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-quantity-3", "text": "What evidence distinguishes counter wrap, reset, replacement and legitimate reverse flow?", "kind": "exception", "answer_data": [ "discontinuity: prior and next record references, device epoch, reset evidence, wrap hypothesis, ambiguity status, prohibited derivation", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-quantity-1", "name": "Quantity", "description": "Candidate nested field group: quantity: property URI, medium, unit URI and symbol, scale, sign convention, result datatype, applicable conditions. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "data-quantity-2", "name": "Semantics", "description": "Candidate nested field group: semantics: value category, integration or count basis, temporal support, counter width, reset rule, profile definition. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "data-quantity-3", "name": "Discontinuity", "description": "Candidate nested field group: discontinuity: prior and next record references, device epoch, reset evidence, wrap hypothesis, ambiguity status, prohibited derivation. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-quantity", "name": "Quantity and counter meaning register", "description": "Versioned stream-local assertions and references for typed measurement values. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-procedure", "name": "Procedure and measurement capability", "description": "Link the method and sensor capabilities under stated conditions. Calibration evidence, resolution and uncertainty are separate assertions; a calibration date alone cannot establish uncertainty for a result.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-procedure", "name": "Qualified observation method", "description": "Link the method and sensor capabilities under stated conditions. Calibration evidence, resolution and uncertainty are separate assertions; a calibration date alone cannot establish uncertainty for a result.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-procedure-1", "text": "Which sensor, probe, procedure and configuration revision produced the observation?", "kind": "provenance", "answer_data": [ "method: sensor master reference, procedure version, configuration digest, deployment reference, observation provenance", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-procedure-2", "text": "Which uncertainty, tolerance and operating conditions are supported for this measurement?", "kind": "quality", "answer_data": [ "capability: uncertainty value and unit, uncertainty definition, coverage qualifier, tolerance, resolution, conditions, evidence or unknown reason", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-procedure-3", "text": "Which calibration or method assessment was applicable at the observation time?", "kind": "evidence", "answer_data": [ "assessment: certificate or assessment reference, validity interval, limitations, reviewer, expiry or missing evidence, affected records", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-procedure-1", "name": "Method", "description": "Candidate nested field group: method: sensor master reference, procedure version, configuration digest, deployment reference, observation provenance. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-procedure-2", "name": "Capability", "description": "Candidate nested field group: capability: uncertainty value and unit, uncertainty definition, coverage qualifier, tolerance, resolution, conditions, evidence or unknown reason. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-procedure-3", "name": "Assessment", "description": "Candidate nested field group: assessment: certificate or assessment reference, validity interval, limitations, reviewer, expiry or missing evidence, affected records. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-procedure", "name": "Procedure and measurement capability register", "description": "Versioned stream-local assertions and references for qualified observation method. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-acquisition", "name": "Selection and temporal support", "description": "Stream-specific context for selection and temporal support.", "rationale": "Authored grouping of source-supported concepts and explicit adoption questions; no cited standard mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-selection", "name": "Sampling and selection", "description": "Describe physical acquisition cadence separately from packet selection. A packet sampling ratio is not a physical sampling interval. No observed sample is assumed to represent an entire population without an explicit method.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-selection", "name": "Observed population and exclusions", "description": "Describe physical acquisition cadence separately from packet selection. A packet sampling ratio is not a physical sampling interval. No observed sample is assumed to represent an entire population without an explicit method.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ], "questions": [ { "id": "q-selection-1", "text": "Which acquisition schedule or trigger determines when physical observations are produced?", "kind": "process", "answer_data": [ "acquisition: periodic or event trigger, nominal cadence, jitter allowance, duty cycle, missed trigger policy, profile applicability", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-selection-2", "text": "Which packet selection population, filter or sampling method applies to flow records?", "kind": "classification", "answer_data": [ "selection: population definition, selector type, parameters, selection order, probability if known, effective interval, not-applicable reason", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-selection-3", "text": "Under what documented assumptions may selected observations support a population estimate?", "kind": "constraint", "answer_data": [ "estimation: estimator reference, selection metadata, bias limitations, confidence method, eligible scope, refusal conditions", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-selection-1", "name": "Acquisition", "description": "Candidate nested field group: acquisition: periodic or event trigger, nominal cadence, jitter allowance, duty cycle, missed trigger policy, profile applicability. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "data-selection-2", "name": "Selection", "description": "Candidate nested field group: selection: population definition, selector type, parameters, selection order, probability if known, effective interval, not-applicable reason. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "data-selection-3", "name": "Estimation", "description": "Candidate nested field group: estimation: estimator reference, selection metadata, bias limitations, confidence method, eligible scope, refusal conditions. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-selection", "name": "Sampling and selection register", "description": "Versioned stream-local assertions and references for observed population and exclusions. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-time", "name": "Observation time and ordering", "description": "Separate phenomenon interval, result production, export and ingestion. Preserve source clock and precision; normalized wall time does not prove alignment. Server-assigned phenomenon time remains explicitly qualified.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "findings": [ { "id": "finding-time", "name": "Qualified time axes", "description": "Separate phenomenon interval, result production, export and ingestion. Preserve source clock and precision; normalized wall time does not prove alignment. Server-assigned phenomenon time remains explicitly qualified.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "q-time-1", "text": "Which phenomenon, result, export and ingestion times are known for this record?", "kind": "temporal", "answer_data": [ "times: start and end or instant, result time, export time, ingestion time, source versus assigned status, raw time representation", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-time-2", "text": "What clock evidence and uncertainty support ordering or alignment across observation points?", "kind": "quality", "answer_data": [ "clock: clock domain, synchronization evidence, uncertainty, precision, timezone or offset, leap handling, unresolved ordering", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-time-3", "text": "Which window boundaries and late-arrival rules govern this stream view?", "kind": "constraint", "answer_data": [ "window: interval convention, time basis, lateness allowance, watermark meaning, provisional or final state, reopening rule", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-time-1", "name": "Times", "description": "Candidate nested field group: times: start and end or instant, result time, export time, ingestion time, source versus assigned status, raw time representation. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "data-time-2", "name": "Clock", "description": "Candidate nested field group: clock: clock domain, synchronization evidence, uncertainty, precision, timezone or offset, leap handling, unresolved ordering. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "data-time-3", "name": "Window", "description": "Candidate nested field group: window: interval convention, time basis, lateness allowance, watermark meaning, provisional or final state, reopening rule. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-time", "name": "Observation time and ordering register", "description": "Versioned stream-local assertions and references for qualified time axes. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Records and delivery continuity", "description": "Stream-specific context for records and delivery continuity.", "rationale": "Authored grouping of source-supported concepts and explicit adoption questions; no cited standard mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ], "layers": [ { "id": "layer-records", "name": "Record identity and interpretation", "description": "Identify observations independently of timestamp. Packet templates need session and domain context; unresolved decoding remains quarantined. Flow-key equality does not establish a unique conversation or person.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "finding-records", "name": "Traceable observations and templates", "description": "Identify observations independently of timestamp. Packet templates need session and domain context; unresolved decoding remains quarantined. Flow-key equality does not establish a unique conversation or person.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "q-records-1", "text": "What stable record identifier and source context distinguish duplicates from simultaneous observations?", "kind": "identity", "answer_data": [ "record: master record ID or opaque local ID, stream revision, source namespace, source epoch, sequence and record ordinal, duplicate evidence", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-records-2", "text": "Which template and information-element definitions permit decoding this packet-flow record?", "kind": "interoperability", "answer_data": [ "decode: exporter reference, transport session, observation domain, template ID and revision, field IDs and enterprise namespace, registry pin, decode status", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-records-3", "text": "Which flow keys, direction and interval delimit the represented packet population?", "kind": "composition", "answer_data": [ "flow: key definition, key values under access policy, observation scope, direction, interval, timeout or split reason, unknown fields", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-records-1", "name": "Record", "description": "Candidate nested field group: record: master record ID or opaque local ID, stream revision, source namespace, source epoch, sequence and record ordinal, duplicate evidence. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-records-2", "name": "Decode", "description": "Candidate nested field group: decode: exporter reference, transport session, observation domain, template ID and revision, field IDs and enterprise namespace, registry pin, decode status. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-records-3", "name": "Flow", "description": "Candidate nested field group: flow: key definition, key values under access policy, observation scope, direction, interval, timeout or split reason, unknown fields. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-records", "name": "Record identity and interpretation register", "description": "Versioned stream-local assertions and references for traceable observations and templates. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-delivery", "name": "Delivery and stream continuity", "description": "A stream can persist across transport sessions, pauses and replacements when the contract permits. Distinguish record export loss from network traffic loss. A stopped collector does not prove zero physical flow.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-delivery", "name": "Delivery evidence and lifecycle", "description": "A stream can persist across transport sessions, pauses and replacements when the contract permits. Distinguish record export loss from network traffic loss. A stopped collector does not prove zero physical flow.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "q-delivery-1", "text": "What evidence supports the current active, delayed, paused or retired stream state?", "kind": "state", "answer_data": [ "state: asserted state, event evidence, effective time, custodian, last observation, freshness bound, uncertainty", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-delivery-2", "text": "Which delivery gaps, replay, duplicates or backpressure affect the received records?", "kind": "quality", "answer_data": [ "delivery: session epoch, sequence evidence, record counts, gap intervals, duplicate or replay status, backlog, measured versus inferred loss", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-delivery-3", "text": "Does a restart, sensor replacement or contract change continue this stream or create a successor?", "kind": "lifecycle", "answer_data": [ "continuity: prior revision, change reason, semantic compatibility decision, successor link, partition boundary, approval evidence", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-delivery-1", "name": "State", "description": "Candidate nested field group: state: asserted state, event evidence, effective time, custodian, last observation, freshness bound, uncertainty. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-delivery-2", "name": "Delivery", "description": "Candidate nested field group: delivery: session epoch, sequence evidence, record counts, gap intervals, duplicate or replay status, backlog, measured versus inferred loss. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-delivery-3", "name": "Continuity", "description": "Candidate nested field group: continuity: prior revision, change reason, semantic compatibility decision, successor link, partition boundary, approval evidence. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-delivery", "name": "Delivery and stream continuity register", "description": "Versioned stream-local assertions and references for delivery evidence and lifecycle. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-fitness", "name": "Quality and derivation", "description": "Stream-specific context for quality and derivation.", "rationale": "Authored grouping of source-supported concepts and explicit adoption questions; no cited standard mandates this hierarchy.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-quality", "name": "Validation and missing observations", "description": "Preserve measured, estimated, substituted, invalid, missing and unavailable states separately. Absence has meaning only against an expected coverage contract. An outlier is an assessment, not an automatic correction.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-quality", "name": "Result fitness and gap assessment", "description": "Preserve measured, estimated, substituted, invalid, missing and unavailable states separately. Absence has meaning only against an expected coverage contract. An outlier is an assessment, not an automatic correction.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-quality-1", "text": "Which versioned checks and acceptance thresholds were applied to this result?", "kind": "validation", "answer_data": [ "checks: check profile, units and range validation, reference checks, outcomes, reviewer, threshold rationale, applicability", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-quality-2", "text": "Which expected observations are missing and what evidence explains each gap?", "kind": "quality", "answer_data": [ "gaps: expectation schedule or population, coverage interval, missing record range, outage or access restriction evidence, unknown cause", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-quality-3", "text": "Which substituted or disputed values must remain separate from original observations?", "kind": "exception", "answer_data": [ "qualification: original reference, measured or estimated status, substitution method, dispute reason, supersession link, reviewer", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-quality-1", "name": "Checks", "description": "Candidate nested field group: checks: check profile, units and range validation, reference checks, outcomes, reviewer, threshold rationale, applicability. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-quality-2", "name": "Gaps", "description": "Candidate nested field group: gaps: expectation schedule or population, coverage interval, missing record range, outage or access restriction evidence, unknown cause. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-quality-3", "name": "Qualification", "description": "Candidate nested field group: qualification: original reference, measured or estimated status, substitution method, dispute reason, supersession link, reviewer. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-quality", "name": "Validation and missing observations register", "description": "Versioned stream-local assertions and references for result fitness and gap assessment. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-derivation", "name": "Aggregation and derived views", "description": "Derived views require lineage, compatible units and temporal support. A derived quantity or changed population gets a distinct stream identity; late input produces a new view revision. No causal leak or intrusion conclusion is implied.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-derivation", "name": "Reproducible transformations", "description": "Derived views require lineage, compatible units and temporal support. A derived quantity or changed population gets a distinct stream identity; late input produces a new view revision. No causal leak or intrusion conclusion is implied.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-derivation-1", "text": "Which inputs and algorithm revision reproduce this aggregate or derived stream?", "kind": "process", "answer_data": [ "derivation: input stream and record revisions, method version, parameters, execution evidence, output identity, attribution", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-derivation-2", "text": "What dimensional, coverage and overlap checks permit integration or comparison of these values?", "kind": "measurement", "answer_data": [ "compatibility: unit conversion, duration weighting, interval overlap, scope overlap, sampling treatment, missing-data rule, uncertainty propagation method", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-derivation-3", "text": "How are late inputs, corrections and failed assumptions reflected in dependent views?", "kind": "validation", "answer_data": [ "revision: provisional output, changed input, superseded output, invalidation reason, recomputation requirement, lineage status", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-derivation-1", "name": "Derivation", "description": "Candidate nested field group: derivation: input stream and record revisions, method version, parameters, execution evidence, output identity, attribution. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-derivation-2", "name": "Compatibility", "description": "Candidate nested field group: compatibility: unit conversion, duration weighting, interval overlap, scope overlap, sampling treatment, missing-data rule, uncertainty propagation method. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-derivation-3", "name": "Revision", "description": "Candidate nested field group: revision: provisional output, changed input, superseded output, invalidation reason, recomputation requirement, lineage status. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-derivation", "name": "Aggregation and derived views register", "description": "Versioned stream-local assertions and references for reproducible transformations. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-use", "name": "Governance and profile acceptance", "description": "Stream-specific context for governance and profile acceptance.", "rationale": "Authored grouping of source-supported concepts and explicit adoption questions; no cited standard mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-governance", "name": "Authorized use and disposition", "description": "Treat fine-grained telemetry as potentially sensitive. Local stewardship proposals require an adopting policy for access, retention and disposal; no universal lawful basis or retention period is supplied.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-governance", "name": "Purpose-bound telemetry stewardship", "description": "Treat fine-grained telemetry as potentially sensitive. Local stewardship proposals require an adopting policy for access, retention and disposal; no universal lawful basis or retention period is supplied.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-governance-1", "text": "Which recipient, purpose and resolution are authorized for this stream or derived view?", "kind": "access", "answer_data": [ "authorization: recipient role, purpose, field scope, time and spatial resolution, authorization expiry, policy reference", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-governance-2", "text": "Which identifiers or inferences require minimization before release?", "kind": "privacy", "answer_data": [ "disclosure: sensitive fields, inference assessment, aggregation or redaction method, residual risk review, approval, denied fields", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-governance-3", "text": "Which disposition rules govern raw, derived and replay copies of this telemetry?", "kind": "retention", "answer_data": [ "retention: data class, approved schedule, hold basis and expiry review, copies and recipients, disposal authority, minimal tombstone", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-governance-1", "name": "Authorization", "description": "Candidate nested field group: authorization: recipient role, purpose, field scope, time and spatial resolution, authorization expiry, policy reference. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-governance-2", "name": "Disclosure", "description": "Candidate nested field group: disclosure: sensitive fields, inference assessment, aggregation or redaction method, residual risk review, approval, denied fields. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-governance-3", "name": "Retention", "description": "Candidate nested field group: retention: data class, approved schedule, hold basis and expiry review, copies and recipients, disposal authority, minimal tombstone. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-governance", "name": "Authorized use and disposition register", "description": "Versioned stream-local assertions and references for purpose-bound telemetry stewardship. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-projection", "name": "Profile bindings and acceptance", "description": "Bindings are proposed alignments, not protocol implementations. Record profile-specific losses and refuse projections that erase required meaning. Telemetry supports monitoring; operational control and billing authority remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-projection", "name": "Qualified interoperability and use", "description": "Bindings are proposed alignments, not protocol implementations. Record profile-specific losses and refuse projections that erase required meaning. Telemetry supports monitoring; operational control and billing authority remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-projection-1", "text": "Which versioned mapping preserves the required meaning in the target profile?", "kind": "interoperability", "answer_data": [ "mapping: source profile, target version, field map, unit conversion, identifier map, omitted qualifiers, loss assessment", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-projection-2", "text": "Which adversarial fixtures and acceptance evidence support this binding?", "kind": "validation", "answer_data": [ "acceptance: fixture references, repeated timestamps, reset or wrap cases, missing templates, irregular observations, result report, unresolved failures", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-projection-3", "text": "Which intended uses remain prohibited or require separately evidenced operator approval?", "kind": "authority", "answer_data": [ "use: monitoring purpose, decision limitations, external control reference, billing or enforcement authority reference, refusal reason", "Record source, revision, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-projection-1", "name": "Mapping", "description": "Candidate nested field group: mapping: source profile, target version, field map, unit conversion, identifier map, omitted qualifiers, loss assessment. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "data-projection-2", "name": "Acceptance", "description": "Candidate nested field group: acceptance: fixture references, repeated timestamps, reset or wrap cases, missing templates, irregular observations, result report, unresolved failures. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "data-projection-3", "name": "Use", "description": "Candidate nested field group: use: monitoring purpose, decision limitations, external control reference, billing or enforcement authority reference, refusal reason. Requires a profile-specific schema before operational use.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-projection", "name": "Profile bindings and acceptance register", "description": "Versioned stream-local assertions and references for qualified interoperability and use. External master records remain external.", "media_or_form": [ "structured register", "authorized report" ], "serial": true, "identity_strategy": "Authoritative master-system ID plus namespace and revision first; otherwise a governed IRI or local opaque UUID. Stream key plus independent artifact sequence and revision; timestamp alone is never identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-stream", "name": "Resolve a stream reference", "description": "Proposed operation, not implemented. Resolve exact namespace and stream revision; ambiguous aliases return unresolved status.", "inputs": [ "namespace and stream ID", "requested revision", "purpose" ], "outputs": [ "qualified reference or ambiguity report" ], "preconditions": [ "Verified role, purpose and record-level access scope", "Pinned input evidence and applicable profile; missing authority causes refusal", "Mutation requires expected revision, idempotency and applicable retention controls" ], "effects": [ "Read-only local result; no identity merge" ], "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "register-observation", "name": "Register an evidenced observation", "description": "Proposed operation, not implemented. Validate the profile and append a local record reference or quarantined assertion. Never invent missing values, timestamps or templates.", "inputs": [ "stream revision", "source record and context", "idempotency key", "expected revision" ], "outputs": [ "registered record or quarantine report" ], "preconditions": [ "Verified role, purpose and record-level access scope", "Pinned input evidence and applicable profile; missing authority causes refusal", "Mutation requires expected revision, idempotency and applicable retention controls" ], "effects": [ "Append local membership and provenance; no source modification" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "assess-stream-quality", "name": "Assess stream quality", "description": "Proposed operation, not implemented. Evaluate declared coverage and check rules, preserving unknowns and counter discontinuities. Does not diagnose a physical leak or network attack.", "inputs": [ "record set and revisions", "expectation and quality profile", "clock and selection evidence" ], "outputs": [ "quality assessment with limitations or refusal" ], "preconditions": [ "Verified role, purpose and record-level access scope", "Pinned input evidence and applicable profile; missing authority causes refusal", "Mutation requires expected revision, idempotency and applicable retention controls" ], "effects": [ "Create local assessment; original records remain unchanged" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "derive-stream-view", "name": "Derive a local stream view", "description": "Proposed operation, not implemented. Apply an approved dimensionally compatible method to pinned inputs. Refuse unsupported scaling, unresolved reset or overlap assumptions.", "inputs": [ "input record revisions", "method and parameter version", "unit and temporal profile" ], "outputs": [ "derived view with lineage or refusal" ], "preconditions": [ "Verified role, purpose and record-level access scope", "Pinned input evidence and applicable profile; missing authority causes refusal", "Mutation requires expected revision, idempotency and applicable retention controls" ], "effects": [ "Create distinct derived stream or view revision; no operational intervention" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "record-continuity", "name": "Record a continuity decision", "description": "Proposed operation, not implemented. Append an evidenced pause, restart, contract revision or successor link. Does not reconfigure collectors or sensors.", "inputs": [ "stream identity", "change evidence and compatibility assessment", "expected revision", "idempotency key" ], "outputs": [ "continuity revision or refusal" ], "preconditions": [ "Verified role, purpose and record-level access scope", "Pinned input evidence and applicable profile; missing authority causes refusal", "Mutation requires expected revision, idempotency and applicable retention controls" ], "effects": [ "Update only local stream continuity assertions with supersession links" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "prepare-projection", "name": "Prepare an authorized local projection", "description": "Proposed operation, not implemented. Create a recipient-scoped local artifact with pinned mapping and loss report. Refuse a projection that drops mandatory uncertainty, time origin or confidentiality qualifiers.", "inputs": [ "recipient authorization", "stream and view revision", "target profile", "mapping version" ], "outputs": [ "projection and loss report or refusal" ], "preconditions": [ "Verified role, purpose and record-level access scope", "Pinned input evidence and applicable profile; missing authority causes refusal", "Mutation requires expected revision, idempotency and applicable retention controls" ], "effects": [ "Create local export artifact and access audit reference; no transmission" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007" ] } ], "composition": [ { "target": "WM-BLT-003", "relation": "REFERENCE", "purpose": "Candidate registry parent reconciled as network-context reference, not inheritance. Pin topology version and observation scope; network lifecycle stays external.", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "target": "WM-FLW-008", "relation": "REFERENCE", "purpose": "Optional downstream balance context. Referenced model owns conservation and material-balance reasoning, not this telemetry stream.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "target": "WM-FLW-015", "relation": "REFERENCE", "purpose": "Optional downstream consumption context. Telemetry does not itself establish consumed or billable quantity.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "target": "IPFIX RFC 7011 and RFC 7012", "relation": "ALIGN", "purpose": "Packet-flow profile only; exact templates and field registry versions require tested bindings.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "OGC SensorThings API Sensing 1.1", "relation": "ALIGN", "purpose": "Observation profile only. Sensor changes may require separate target Datastreams even when local logical continuity is retained.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "SOSA/SSN 2017", "relation": "ALIGN", "purpose": "Reference sensor, procedure, observed property and feature concepts without taking ownership of actuation.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "PROV-O 2013", "relation": "ALIGN", "purpose": "Lineage and attribution alignment, not certification of measurement truth.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "SenML RFC 8428", "relation": "ALIGN", "purpose": "Measurement serialization alignment; preserve base fields and distinguish integrated sums from event counters.", "required": false, "source_refs": [ "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable network operator role and stream custodian with evidenced authority", "Versioned physical or packet profile, quantity vocabulary and master namespaces", "Approved access, retention, quality and escalation policies for raw and derived telemetry" ], "namespace_guidance": "Use operator-qualified opaque stream IDs. Endpoint address, sensor ID, five-tuple and timestamp are not sufficient stream identity; retain source epochs and alias evidence.", "registry_links": [ "vr.wm-flw-014", "WM-BLT-003 contextual network binding must be pinned before use" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve raw source values and their decoded qualifiers; normalization never overwrites evidence.", "Do not conflate unknown with zero, loss with no flow, sequence with event time, or packet counters with physical quantities." ], "patch_rules": [ "Append corrections with expected revision, actor, reason and idempotency key; dependent views need explicit supersession.", "Semantic changes to quantity, population or method require a compatibility decision and new stream or partition where continuity is unsupported." ], "compatibility_rules": [ "Version all profile mappings and preserve loss reports; do not silently coerce incompatible units, time origins, intervals or template epochs.", "A local stable stream may map to multiple external Datastream identities across sensor changes; never rewrite old observations as produced by a new sensor." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with namespace and revision", "Governed global IRI with source version", "Local opaque UUID assigned by the adopting Dimension" ], "timestamp_rule": "Represent known absolute instants with RFC 3339, seconds and an explicit offset or Z; preserve fractional precision. Keep phenomenon/event time, result time, export time and ingestion time separate. Retain raw relative clocks, clock uncertainty and missing values; do not manufacture wall times or treat server-assigned time as measured phenomenon time.", "serial_naming_rule": "Use opaque stream key, artifact class and independent sequence or revision. Timestamps may label artifacts but never identify them alone; avoid sensitive addresses in filenames.", "integrity_rule": "Store digest algorithm, content digest and transformation lineage where available. A digest proves neither sensor authenticity nor measurement truth; access and provenance review remain necessary." }, "policies": [ "Reviewable draft under a single-provider waiver; external independent review is still required.", "Physical-flow and packet-flow profiles share a logical stream boundary but must not share unqualified quantity, sampling or counter semantics.", "Limit fine-grained telemetry and derivations to authorized purposes and recipient scopes; no payload inspection or household inference disclosure is authorized by this model.", "Only local record operations are proposed. Routing, valves, load control, sensor configuration, billing and enforcement require separate authority and systems." ], "crud": { "read": [ "Return authorized record fields and resolution with quality, time origin and source qualifiers; denied data remains unavailable, not zero." ], "create": [ "Require stable stream identity, custodian, membership profile and scope reference; unresolved evidence must be explicitly pending." ], "update": [ "Use revision and idempotency checks for append, qualification and supersession; never silently backfill invented observations." ], "delete": [ "Approved retention schedules and legal holds govern deletion of raw records, derived copies and replay buffers. The adopting records authority executes disposal; this model records its evidence and minimal non-identifying tombstones where lawful.", "History retention does not override lawful payload erasure. Stream retirement does not delete network or sensor masters or prove cessation of flow." ] }, "roles": [ { "name": "Stream custodian", "responsibilities": [ "Approve identity and membership continuity within delegated authority" ] }, { "name": "Measurement steward", "responsibilities": [ "Assess procedure, conditions, calibration evidence and uncertainty" ] }, { "name": "Collection operator", "responsibilities": [ "Supply authenticated export and delivery evidence without changing source meaning" ] }, { "name": "Data quality reviewer", "responsibilities": [ "Review gaps, estimates, derivations and unresolved defects" ] }, { "name": "Access and records officer", "responsibilities": [ "Approve disclosure, retention, holds and disposal" ] }, { "name": "Authorized consumer", "responsibilities": [ "Use only permitted views with their stated limitations" ] } ], "access": { "default_rule": "Deny telemetry access unless recipient, purpose, fields and resolution are authorized. Infrastructure ownership alone grants no unrestricted consumer access.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "A policy exception requires a named accountable role, documented basis, expiry and minimum necessary scope; no blanket emergency bypass." ], "audit_requirements": [ "Record authorized reads, changes, projections and disposal with actor, purpose, scope, revision and outcome; reference the external audit master and apply minimal-data retention." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and adopting Dimension authority policies", "spec.yaml and publication holds", "Pinned observation profile, master references and authorized source evidence" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one persistent telemetry stream with explicit physical-measurement and packet-flow profiles. Separate local no-tools self-audit completed. Independent review, source/version checks, adoption profiles and executable conformance remain holds; this is a noncanonical reviewable draft.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable stream and record identity are independent of sensor, endpoint and timestamp." }, { "dimension": "lifecycle", "status": "covered", "notes": "Pause, restart, semantic change, successor and retirement are evidenced local assertions." }, { "dimension": "relationships", "status": "covered", "notes": "Network, sensor, observation and consumption masters stay separate." }, { "dimension": "temporal", "status": "covered", "notes": "Phenomenon, result, export and ingestion axes with clock uncertainty and late data." }, { "dimension": "provenance", "status": "covered", "notes": "Procedure, source record, derivation and revision evidence are explicit." }, { "dimension": "ownership", "status": "covered", "notes": "Generic operator and custodian roles require evidenced authority." }, { "dimension": "validation", "status": "covered", "notes": "Quality questions distinguish original, estimated, missing and disputed values; runtime validation remains a gap." }, { "dimension": "access", "status": "covered", "notes": "Purpose, recipient, resolution and inference risk govern disclosure." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Adopting authority sets schedules for raw, derived and replay copies and lawful erasure." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual alignments exist; executable mappings and fixtures are pending." }, { "dimension": "direct properties", "status": "covered", "notes": "Quantity, unit, counter meaning, temporal support and uncertainty are stream content; the root itself has no physical mass or dimensions." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Membership, sensor, feature and profile distinguish telemetry from topology or an arbitrary event log." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Proposed local operations assess and project evidence; they do not actuate or decide billing." }, { "dimension": "physical domain completeness", "status": "gap", "notes": "Shared observation concepts do not supply domain-specific physical laws or metrology rules." }, { "dimension": "source verification", "status": "gap", "notes": "Browser sections reviewed; direct HTTP and comprehensive version or errata verification remain open." } ], "known_omissions": [ "Independent external review is absent; the separate local no-tools audit is a self-audit.", "Direct HTTP checks are unattempted under the owner-reported sandbox restriction; source status, errata and latest applicable versions remain to be verified outside the sandbox.", "Physical domain profiles for water, gas, power and transport require specialist metrology, sign, reference-condition and regulatory review; no conservation or billing engine is supplied.", "Nested instance schemas, IPFIX template/field registry pins, SensorThings and SenML mappings, throughput behavior and adversarial fixtures remain unimplemented.", "Current cryptographic transport recommendations, jurisdictional privacy rules and retention periods require adoption review; no legal or security certification is claimed." ], "conflicts": [], "regional_assumptions": [ "Technical standards provide selected interoperable concepts; no jurisdiction or industry profile is treated as universal.", "Access, metrology, safety and records rules must be selected by the adopting authority." ], "adversarial_checks": [ "Two valid records at one timestamp must survive deduplication unless independent identity evidence establishes replay.", "Counter decrease with uncertain epoch must block rate derivation; do not assume wrap or reset.", "Missing template must quarantine packet decoding; a matching template ID from another session is insufficient.", "A delivery gap cannot establish zero flow, a leak, intrusion or consumption.", "Sensor replacement may preserve local continuity only with a documented decision and correct external Datastream split.", "Late or substituted data creates explicit derived revisions and never becomes silently measured evidence." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The subject retains governed stream identity across observation and delivery sessions, with versioned membership and typed profiles. It is distinct from the network, sensor, single observation and transported flow. The registry standalone-mm label is not a subject-kind enum; the network parent is a contextual reference." }, "decisions": [ { "concept": "Stream root and alternative profiles", "disposition": "accepted", "rationale": "Persistent telemetry identity is coherent across explicit physical and packet profiles. The root is neither a physical network nor one exported record; standalone-mm is not a subject-kind enum." }, { "concept": "Network and downstream masters", "disposition": "qualified", "rationale": "The registry parent is reconciled as a contextual reference. Topology, sensor lifecycle, material balance and consumption assessments remain outside this model; candidate bindings require version pins." }, { "concept": "Supplement identity and continuity claims", "disposition": "rejected in part", "rationale": "Point plus quantity and a timestamp alone cannot distinguish stream profiles, simultaneous records or replay. Irregular and event-triggered observations are admitted, so continuity is not mandatory." }, { "concept": "Sensor replacement and profile identity", "disposition": "accepted with mapping qualification", "rationale": "Local continuity requires a compatibility decision. External SensorThings Datastream identity must still respect its sensor and property relations; old observations cannot be rewritten as produced by a replacement." }, { "concept": "Quantity and counter semantics", "disposition": "accepted", "rationale": "The draft separates rates, amounts, gauges, total counters, delta counters and time integrals. Reset or wrap uncertainty prevents unsupported derivation and SenML sum is not used as a generic packet counter." }, { "concept": "Sampling and selection scope", "disposition": "accepted", "rationale": "Physical acquisition cadence and packet selection are distinct questions. Population estimates require a declared method and limitations instead of an assumed universal expansion factor." }, { "concept": "Time and observation provenance", "disposition": "accepted", "rationale": "Phenomenon, result, export and ingestion time remain distinct. Server-assigned time stays qualified and wall-time syntax does not prove clock alignment or observation order." }, { "concept": "Record decoding and delivery", "disposition": "accepted", "rationale": "Template identity retains source session and domain context. Unknown templates cause quarantine and export loss does not prove network packet loss, zero flow or a physical fault." }, { "concept": "Uncertainty and derived views", "disposition": "accepted with evidence dependency", "rationale": "Calibration date does not supply result uncertainty. Quality assessments preserve original and substituted states, while changed inputs create explicit derived revisions with no causal or billing conclusion." }, { "concept": "Functions and operational authority", "disposition": "accepted as proposed only", "rationale": "All six functions are unimplemented local record operations with role and evidence preconditions. They cannot actuate equipment, configure collection, send telemetry or authorize enforcement." }, { "concept": "Access and record disposal", "disposition": "accepted with policy dependency", "rationale": "Purpose-bound access covers raw and derived views. Raw, aggregate and replay retention depends on approved schedules and holds; preservation of history does not defeat lawful payload erasure." }, { "concept": "Sources and single-provider assurance", "disposition": "limited", "rationale": "Eight primary documents support selected concepts but no direct HTTP request was attempted. Local self-audit is not external independent review; the source/version and waiver holds remain visible." }, { "concept": "Operational conformance and physical scope", "disposition": "deferred", "rationale": "Candidate nested groups and conceptual mappings are not executable schemas or certified profiles. Metrology, safety, security, legal applicability and adversarial fixtures require adoption work." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not an independent second-provider review.", "Source and version verification remains incomplete. Eight primary documents were available through browser retrieval for selected-section review, but direct HTTP checks were unattempted under the owner-reported sandbox block; no HTTP status was measured. Coordinator checks, errata and applicable registry/version review remain open.", "Physical metrology, domain quantities and reference conditions, uncertainty, legal applicability, privacy, retention, safety, current transport security and intended-use authority require qualified adoption-profile review. No billing, control, causality or regulatory certification is claimed.", "Nested instance schemas, pinned neighbor and field-registry bindings, IPFIX/SensorThings/SenML mappings, performance guarantees and executable adversarial fixtures remain incomplete. Structural research validation is not protocol or runtime conformance.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Run the prepared source checker outside the sandbox and review document errata, exact versions, field registries and source applicability; restore independent external review before canonical promotion.", "Develop physical-domain and packet-flow adoption profiles with competent metrology, access, records, security and operational authorities.", "Implement and test nested schemas and mappings using repeated timestamps, sensor replacement, clock uncertainty, missing templates, reset versus wrap, replay, overlapping scopes and late corrections." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }