# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T20:07:23Z", "synthesisSha256": "4a358e00249facefe54bf47521309555a4a42c9139c7524a8f1876a2ac4cdab4", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-BLT-004", "registryId": "vr.wm-blt-004", "name": "Utility Service Point", "version": "0.1.0", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.BLT.UTL" ], "tags": [ "utility", "service", "point", "phy.blt.utl" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-blt-004-utility-service-point/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-004", "model": { "registry_id": "vr.wm-blt-004", "model_id": "WM-BLT-004", "name": "Utility Service Point", "entry_kind": "entity", "purpose": "Describe one persistent utility service interface and its evidence-backed point-specific bindings.", "scope_statement": "A proposed entity for one authority-qualified water, heat, electricity or sewage service interface between a network and served place, including planned or retired points. The root is neither a meter, asset, billing account, virtual aggregate nor executable utility controller.", "in_scope": [ "Identity, service class, location, recognition evidence and network demarcation", "Qualified properties, metering assignments, reading references and service-state evidence", "Time-bounded party and terms references, disclosure context and revision assurance" ], "out_of_scope": [ "Network topology computation, pipe and cable asset lifecycle, building and premises lifecycle", "Meter hardware maintenance, measurement master storage, billing, tariff calculation and settlement", "Physical actuation, switching, disconnection authorization, safety certification and operational work execution", "Virtual portfolio aggregates as root instances; gas and telecommunications extensions require separate evidence" ], "boundary_notes": [ { "neighbor": "WM-BLT-002", "distinction": "Served premises and occupancy remain externally mastered; carry only point-to-place bindings.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "WM-BLT-001", "distinction": "Building master and structural lifecycle stay external; legacy U1 is mapped specifically to Building / Structure, not every shared-alias row.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "WM-BLT-003", "distinction": "Network and asset masters own topology and maintenance; local references do not recalculate flow or control equipment.", "source_refs": [ "SRC-003" ] }, { "neighbor": "WM-PER-001", "distinction": "Person identity and lifecycle stay external; store purpose-limited party references.", "source_refs": [ "SRC-005" ] }, { "neighbor": "WM-ORG-001", "distinction": "Organization identity stays external; local operator and steward role bindings convey no corporate ownership claim.", "source_refs": [ "SRC-005" ] }, { "neighbor": "External meter, measurement, work-order, agreement and tariff masters", "distinction": "Profile must pin these bindings before runtime use. Local records carry references and applicability only.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007" ] }, { "neighbor": "ESPI UsagePoint", "distinction": "Partial alignment: virtual aggregates are not equivalent to physical interfaces; versioned mapping and tests required.", "source_refs": [ "SRC-006", "SRC-007" ] }, { "neighbor": "INSPIRE Utility Networks", "distinction": "Align external network link semantics without owning network nodes, pipes or cables.", "source_refs": [ "SRC-003" ] }, { "neighbor": "SOSA/SSN and PROV-O", "distinction": "Conceptual observation and assertion-lineage alignment; no RDF implementation or conformance claim.", "source_refs": [ "SRC-004", "SRC-005" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Metering procedures, guidelines and processes", "organization": "Australian Energy Market Operator", "url": "https://www.aemo.com.au/energy-systems/electricity/national-electricity-market-nem/market-operations/retail-and-metering/metering-procedures-guidelines-and-processes", "version_or_date": "Page reviewed 2026-10-06; lists NMI procedure v7.4 effective 2026-05-31 and future v7.5 effective 2026-11-01", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T20:06:18Z", "relevance": "NMI identifies connection and associated metering points in the Australian NEM. Index-level evidence only; linked procedure PDF fetch timed out." }, { "id": "SRC-002", "title": "Planning and Developing a Service Line Inventory", "organization": "United States Environmental Protection Agency", "url": "https://www.epa.gov/ground-water-and-drinking-water/planning-and-developing-service-line-inventory", "version_or_date": "Page updated 2026-03-11; guidance dated 2022-08-04", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:06:18Z", "relevance": "Water connection material, location and split ownership are distinct assertions. Historical inventory guidance is not a current legal compliance determination." }, { "id": "SRC-003", "title": "INSPIRE Data Specification on Utility and Government Services - Technical Guidelines", "organization": "INSPIRE Maintenance and Implementation Group", "url": "https://inspire-mif.github.io/technical-guidelines/data/us/dataspecification_us.html", "version_or_date": "D2.8.III.6_v3.2.0; 2024-01-31; selected sections 5.10 and 5.11 reviewed", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:06:18Z", "relevance": "Separate network schemas for electricity, sewer, thermal and water support typed external network links. Guidelines do not define this proposed service-point entity or certify conformance." }, { "id": "SRC-004", "title": "Semantic Sensor Network Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-ssn/", "version_or_date": "2017 Recommendation; selected observation, time, deployment and capability sections", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:06:18Z", "relevance": "Separate feature, observed property, sensor, procedure, result and phenomenon time. Selected conceptual alignment only." }, { "id": "SRC-005", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 2013-04-30; revision and attribution sections", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:06:18Z", "relevance": "Attribution and derivation distinguish assertion history from truth and physical events." }, { "id": "SRC-006", "title": "Aggregated Data with Green Button", "organization": "Green Button Alliance", "url": "https://www.greenbuttonalliance.org/aggregated-data", "version_or_date": "Undated developer page reviewed 2026-10-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T20:06:18Z", "relevance": "UsagePoint can represent a virtual logical aggregate; this is not automatically a physical utility service point. No role bit implementation adopted." }, { "id": "SRC-007", "title": "[FB_01] Usage Data Common", "organization": "Green Button Alliance", "url": "https://www.greenbuttonalliance.org/fb01", "version_or_date": "Undated test page reviewed 2026-10-06; references ESPI 3.3", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T20:06:18Z", "relevance": "Separate UsagePoint identifier, service category, MeterReading and local time links; stable UsagePoint UUID test. Conceptual mapping only, not certification." }, { "id": "SRC-008", "title": "RFC 3339: 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; section 5.6", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:06:18Z", "relevance": "Timestamp lexical profile with seconds and explicit UTC offset; does not by itself specify validity intervals or ordering policy." } ], "structure": { "bundles": [ { "id": "usp-identity", "name": "Identity and service classification", "description": "Proposed service-point context for identity and service classification.", "rationale": "Keep this concern explicit while referenced masters retain their own lifecycle and authority.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "layers": [ { "id": "usp-l-identity", "name": "Persistent point identity", "description": "A service point is a persistent, authority-qualified interface record for one utility service. Meter serials, customer accounts and street addresses are aliases or links, not substitute root identities.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "usp-f-identity", "name": "Persistent point identity", "description": "A service point is a persistent, authority-qualified interface record for one utility service. Meter serials, customer accounts and street addresses are aliases or links, not substitute root identities.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "usp-f-identity-q1", "kind": "identity", "text": "Which authority and namespace identify this service point independently of its current meter or account?", "answer_data": [ "master identifier", "issuing authority", "namespace", "aliases" ] }, { "id": "usp-f-identity-q2", "kind": "classification", "text": "Which utility service and physical or planned interface class does the point represent?", "answer_data": [ "service kind", "profile version", "physical or planned classification" ] }, { "id": "usp-f-identity-q3", "kind": "exception", "text": "What evidence distinguishes a duplicate record from a replacement or split service point?", "answer_data": [ "identity decision", "predecessor references", "evidence", "decision time" ] } ], "data_elements": [ { "id": "usp-f-identity-data1", "name": "master identifier", "description": "Candidate group: master identifier, issuing authority, namespace, aliases. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "usp-f-identity-data2", "name": "service kind", "description": "Candidate group: service kind, profile version, physical or planned classification. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "usp-f-identity-data3", "name": "identity decision", "description": "Candidate group: identity decision, predecessor references, evidence, decision time. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "usp-f-identity-artifact", "name": "Persistent point identity evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "usp-l-usage", "name": "Usage and aggregation boundary", "description": "A measurement usage point can be physical or virtual. Link virtual aggregates and settlement groupings explicitly; do not materialize a new physical connection from an exchange identifier alone.", "source_refs": [ "SRC-006", "SRC-007" ], "findings": [ { "id": "usp-f-usage", "name": "Usage and aggregation boundary", "description": "A measurement usage point can be physical or virtual. Link virtual aggregates and settlement groupings explicitly; do not materialize a new physical connection from an exchange identifier alone.", "source_refs": [ "SRC-006", "SRC-007" ], "questions": [ { "id": "usp-f-usage-q1", "kind": "definition", "text": "Does the mapped usage point denote this interface or a logical aggregation?", "answer_data": [ "usage point reference", "mapping type", "virtual flag" ] }, { "id": "usp-f-usage-q2", "kind": "composition", "text": "Which component points contribute to a grouped usage reference and during what interval?", "answer_data": [ "component references", "membership intervals", "aggregation rule reference" ] }, { "id": "usp-f-usage-q3", "kind": "interoperability", "text": "What mapping evidence prevents duplicate counting of root and submetered usage?", "answer_data": [ "mapping revision", "coverage exclusions", "loss report" ] } ], "data_elements": [ { "id": "usp-f-usage-data1", "name": "usage point reference", "description": "Candidate group: usage point reference, mapping type, virtual flag. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "usp-f-usage-data2", "name": "component references", "description": "Candidate group: component references, membership intervals, aggregation rule reference. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "usp-f-usage-data3", "name": "mapping revision", "description": "Candidate group: mapping revision, coverage exclusions, loss report. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "usp-f-usage-artifact", "name": "Usage and aggregation boundary evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "usp-connection", "name": "Location and connection boundary", "description": "Proposed service-point context for location and connection boundary.", "rationale": "Keep this concern explicit while referenced masters retain their own lifecycle and authority.", "source_refs": [ "SRC-002", "SRC-003" ], "layers": [ { "id": "usp-l-location", "name": "Served place and recognition", "description": "Keep the served place separate from the physical connection location and recognition evidence. An address match alone is insufficient to identify an interface. Geometry precision and restricted views are adopting-profile decisions.", "source_refs": [ "SRC-002", "SRC-003" ], "findings": [ { "id": "usp-f-location", "name": "Served place and recognition", "description": "Keep the served place separate from the physical connection location and recognition evidence. An address match alone is insufficient to identify an interface. Geometry precision and restricted views are adopting-profile decisions.", "source_refs": [ "SRC-002", "SRC-003" ], "questions": [ { "id": "usp-f-location-q1", "kind": "spatial", "text": "Where is the interface located relative to the served premises or building?", "answer_data": [ "premises references", "connection geometry", "coordinate reference system", "accuracy" ] }, { "id": "usp-f-location-q2", "kind": "evidence", "text": "Which survey, label or approved drawing supports recognition of the point?", "answer_data": [ "evidence reference", "method", "observation time", "recognition confidence" ] }, { "id": "usp-f-location-q3", "kind": "relationship", "text": "Which places are served by this point over each effective interval?", "answer_data": [ "served-place bindings", "effective interval", "allocation basis" ] } ], "data_elements": [ { "id": "usp-f-location-data1", "name": "premises references", "description": "Candidate group: premises references, connection geometry, coordinate reference system, accuracy. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "usp-f-location-data2", "name": "evidence reference", "description": "Candidate group: evidence reference, method, observation time, recognition confidence. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "usp-f-location-data3", "name": "served-place bindings", "description": "Candidate group: served-place bindings, effective interval, allocation basis. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "usp-f-location-artifact", "name": "Served place and recognition evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "usp-l-demarcation", "name": "Network and responsibility demarcation", "description": "Reference network nodes and connection assets with profile-qualified cardinality. Distinguish asset title, operation, maintenance and data stewardship at the boundary. Split ownership does not force a single responsible party.", "source_refs": [ "SRC-002", "SRC-003" ], "findings": [ { "id": "usp-f-demarcation", "name": "Network and responsibility demarcation", "description": "Reference network nodes and connection assets with profile-qualified cardinality. Distinguish asset title, operation, maintenance and data stewardship at the boundary. Split ownership does not force a single responsible party.", "source_refs": [ "SRC-002", "SRC-003" ], "questions": [ { "id": "usp-f-demarcation-q1", "kind": "relationship", "text": "Which external network node and connection assets establish the interface?", "answer_data": [ "network reference", "node reference", "asset references", "topology revision" ] }, { "id": "usp-f-demarcation-q2", "kind": "ownership", "text": "Where does each responsibility change and who is assigned to each side?", "answer_data": [ "boundary description", "role bindings", "responsibility evidence" ] }, { "id": "usp-f-demarcation-q3", "kind": "quality", "text": "Which connection material or arrangement remains unknown or disputed?", "answer_data": [ "assertion status", "material evidence", "unknown reason", "review reference" ] } ], "data_elements": [ { "id": "usp-f-demarcation-data1", "name": "network reference", "description": "Candidate group: network reference, node reference, asset references, topology revision. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "usp-f-demarcation-data2", "name": "boundary description", "description": "Candidate group: boundary description, role bindings, responsibility evidence. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "usp-f-demarcation-data3", "name": "assertion status", "description": "Candidate group: assertion status, material evidence, unknown reason, review reference. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "usp-f-demarcation-artifact", "name": "Network and responsibility demarcation evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "usp-properties", "name": "Service properties and capability", "description": "Proposed service-point context for service properties and capability.", "rationale": "Keep this concern explicit while referenced masters retain their own lifecycle and authority.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "layers": [ { "id": "usp-l-envelope", "name": "Declared interface envelope", "description": "Record service-specific design and allowed operating envelopes as qualified assertions. Electric import or export, water delivery, thermal supply and return, and sewer discharge require distinct units and direction semantics. This draft supplies no engineering limits.", "source_refs": [ "SRC-003", "SRC-004" ], "findings": [ { "id": "usp-f-envelope", "name": "Declared interface envelope", "description": "Record service-specific design and allowed operating envelopes as qualified assertions. Electric import or export, water delivery, thermal supply and return, and sewer discharge require distinct units and direction semantics. This draft supplies no engineering limits.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "usp-f-envelope-q1", "kind": "measurement", "text": "What rated capacity and interface properties apply under the selected utility profile?", "answer_data": [ "property code", "quantity", "unit", "rating basis", "conditions" ] }, { "id": "usp-f-envelope-q2", "kind": "constraint", "text": "Which permitted directions and operating limits constrain service at the interface?", "answer_data": [ "direction convention", "limit reference", "applicability interval" ] }, { "id": "usp-f-envelope-q3", "kind": "validation", "text": "What evidence distinguishes an approved envelope from an observed operating value?", "answer_data": [ "approval reference", "observation reference", "verification status" ] } ], "data_elements": [ { "id": "usp-f-envelope-data1", "name": "property code", "description": "Candidate group: property code, quantity, unit, rating basis, conditions. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "usp-f-envelope-data2", "name": "direction convention", "description": "Candidate group: direction convention, limit reference, applicability interval. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "usp-f-envelope-data3", "name": "approval reference", "description": "Candidate group: approval reference, observation reference, verification status. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "usp-f-envelope-artifact", "name": "Declared interface envelope evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "usp-l-observations", "name": "Condition and observation context", "description": "Point observations retain feature, property, procedure, time and evidence. A recent observation is not permanent proof of condition. Safety assessments and work execution remain external; only their references and resulting point assertions belong here.", "source_refs": [ "SRC-004", "SRC-005" ], "findings": [ { "id": "usp-f-observations", "name": "Condition and observation context", "description": "Point observations retain feature, property, procedure, time and evidence. A recent observation is not permanent proof of condition. Safety assessments and work execution remain external; only their references and resulting point assertions belong here.", "source_refs": [ "SRC-004", "SRC-005" ], "questions": [ { "id": "usp-f-observations-q1", "kind": "measurement", "text": "Which condition was observed at the point using which method and unit?", "answer_data": [ "observed property", "result", "unit", "method", "uncertainty" ] }, { "id": "usp-f-observations-q2", "kind": "temporal", "text": "When did the observed condition apply and when was the result recorded?", "answer_data": [ "phenomenon interval", "result time", "ingestion time", "clock quality" ] }, { "id": "usp-f-observations-q3", "kind": "quality", "text": "What limitation or contrary evidence qualifies the condition assessment?", "answer_data": [ "quality flags", "contrary evidence", "assessment reference" ] } ], "data_elements": [ { "id": "usp-f-observations-data1", "name": "observed property", "description": "Candidate group: observed property, result, unit, method, uncertainty. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] }, { "id": "usp-f-observations-data2", "name": "phenomenon interval", "description": "Candidate group: phenomenon interval, result time, ingestion time, clock quality. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] }, { "id": "usp-f-observations-data3", "name": "quality flags", "description": "Candidate group: quality flags, contrary evidence, assessment reference. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "usp-f-observations-artifact", "name": "Condition and observation context evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "usp-metering", "name": "Metering and usage evidence", "description": "Proposed service-point context for metering and usage evidence.", "rationale": "Keep this concern explicit while referenced masters retain their own lifecycle and authority.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "usp-l-assignments", "name": "Meter and channel assignments", "description": "Device and channel bindings have effective intervals and distinct masters. Allow unmetered or multiple-channel profiles without fabricating devices; exchange of a meter does not automatically create a new point. Device maintenance stays outside this model.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "findings": [ { "id": "usp-f-assignments", "name": "Meter and channel assignments", "description": "Device and channel bindings have effective intervals and distinct masters. Allow unmetered or multiple-channel profiles without fabricating devices; exchange of a meter does not automatically create a new point. Device maintenance stays outside this model.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "questions": [ { "id": "usp-f-assignments-q1", "kind": "composition", "text": "Which meters and channels are assigned to the point for the relevant interval?", "answer_data": [ "device references", "channel references", "assignment intervals", "channel roles" ] }, { "id": "usp-f-assignments-q2", "kind": "lifecycle", "text": "How is a meter exchange linked to prior and replacement assignments?", "answer_data": [ "exchange evidence", "closing assignment", "opening assignment", "continuity decision" ] }, { "id": "usp-f-assignments-q3", "kind": "exception", "text": "What approved basis describes an unmetered, shared-meter or temporarily missing-meter arrangement?", "answer_data": [ "metering mode", "allocation method reference", "exception authority" ] } ], "data_elements": [ { "id": "usp-f-assignments-data1", "name": "device references", "description": "Candidate group: device references, channel references, assignment intervals, channel roles. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "usp-f-assignments-data2", "name": "exchange evidence", "description": "Candidate group: exchange evidence, closing assignment, opening assignment, continuity decision. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "usp-f-assignments-data3", "name": "metering mode", "description": "Candidate group: metering mode, allocation method reference, exception authority. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "usp-f-assignments-artifact", "name": "Meter and channel assignments evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "usp-l-readings", "name": "Reading and correction references", "description": "Reference measurement records with interval, quantity semantics, quality and correction lineage. Preserve distinctions among cumulative registers, interval usage and derived estimates. The local index neither calculates bills nor certifies settlement quantities.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "findings": [ { "id": "usp-f-readings", "name": "Reading and correction references", "description": "Reference measurement records with interval, quantity semantics, quality and correction lineage. Preserve distinctions among cumulative registers, interval usage and derived estimates. The local index neither calculates bills nor certifies settlement quantities.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "questions": [ { "id": "usp-f-readings-q1", "kind": "measurement", "text": "What quantity, unit, scale and direction does each linked reading express?", "answer_data": [ "reading reference", "quantity kind", "unit", "scale", "direction" ] }, { "id": "usp-f-readings-q2", "kind": "temporal", "text": "Which interval and time convention bind the reading to the point assignment?", "answer_data": [ "interval start", "duration", "time convention", "assignment revision" ] }, { "id": "usp-f-readings-q3", "kind": "provenance", "text": "Which source, quality flag and supersession evidence qualify a corrected or estimated reading?", "answer_data": [ "source record", "quality code", "superseded reference", "derivation reference" ] } ], "data_elements": [ { "id": "usp-f-readings-data1", "name": "reading reference", "description": "Candidate group: reading reference, quantity kind, unit, scale, direction. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ] }, { "id": "usp-f-readings-data2", "name": "interval start", "description": "Candidate group: interval start, duration, time convention, assignment revision. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ] }, { "id": "usp-f-readings-data3", "name": "source record", "description": "Candidate group: source record, quality code, superseded reference, derivation reference. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "usp-f-readings-artifact", "name": "Reading and correction references evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "usp-continuity", "name": "Service continuity and external terms", "description": "Proposed service-point context for service continuity and external terms.", "rationale": "Keep this concern explicit while referenced masters retain their own lifecycle and authority.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "layers": [ { "id": "usp-l-state", "name": "Service state and transitions", "description": "Separate point registration, physical availability and contractual service state. Record authorized evidence of commissioning, interruption, restoration or retirement with time and reason. A local state update never operates a switch or valve.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "findings": [ { "id": "usp-f-state", "name": "Service state and transitions", "description": "Separate point registration, physical availability and contractual service state. Record authorized evidence of commissioning, interruption, restoration or retirement with time and reason. A local state update never operates a switch or valve.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "usp-f-state-q1", "kind": "state", "text": "What registration and physical availability states are currently asserted for the point?", "answer_data": [ "registration state", "availability state", "assertion time", "unknown flag" ] }, { "id": "usp-f-state-q2", "kind": "event", "text": "Which evidenced event changed a service state and when did it take effect?", "answer_data": [ "event reference", "prior state", "resulting state", "effective time", "reason" ] }, { "id": "usp-f-state-q3", "kind": "authority", "text": "Which role and external authorization support the recorded transition?", "answer_data": [ "responsible role", "authorization reference", "work completion evidence" ] } ], "data_elements": [ { "id": "usp-f-state-data1", "name": "registration state", "description": "Candidate group: registration state, availability state, assertion time, unknown flag. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "usp-f-state-data2", "name": "event reference", "description": "Candidate group: event reference, prior state, resulting state, effective time, reason. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "usp-f-state-data3", "name": "responsible role", "description": "Candidate group: responsible role, authorization reference, work completion evidence. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "usp-f-state-artifact", "name": "Service state and transitions evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "usp-l-terms", "name": "Party and commercial bindings", "description": "Attach time-qualified operator, served-party, contract and tariff references only where applicable. These are proposed record bindings, not claims of universal market rules. Account, tariff, supplier-switch and entitlement lifecycles remain externally mastered.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "usp-f-terms", "name": "Party and commercial bindings", "description": "Attach time-qualified operator, served-party, contract and tariff references only where applicable. These are proposed record bindings, not claims of universal market rules. Account, tariff, supplier-switch and entitlement lifecycles remain externally mastered.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "usp-f-terms-q1", "kind": "ownership", "text": "Which operator, customer or other responsible role is bound to this point during the stated interval?", "answer_data": [ "role", "party reference", "validity interval", "binding evidence" ] }, { "id": "usp-f-terms-q2", "kind": "relationship", "text": "Which external agreement or tariff revision applies to each service or usage component?", "answer_data": [ "agreement reference", "tariff revision", "component scope", "applicability interval" ] }, { "id": "usp-f-terms-q3", "kind": "constraint", "text": "What unresolved overlap or gap prevents treating a commercial binding as authoritative?", "answer_data": [ "conflict record", "unresolved interval", "resolution authority" ] } ], "data_elements": [ { "id": "usp-f-terms-data1", "name": "role", "description": "Candidate group: role, party reference, validity interval, binding evidence. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "usp-f-terms-data2", "name": "agreement reference", "description": "Candidate group: agreement reference, tariff revision, component scope, applicability interval. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "usp-f-terms-data3", "name": "conflict record", "description": "Candidate group: conflict record, unresolved interval, resolution authority. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "usp-f-terms-artifact", "name": "Party and commercial bindings evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "usp-assurance", "name": "Evidence and controlled exchange", "description": "Proposed service-point context for evidence and controlled exchange.", "rationale": "Keep this concern explicit while referenced masters retain their own lifecycle and authority.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "usp-l-access", "name": "Disclosure context and retention", "description": "Proposed local governance separates point topology, customer links and usage payloads. Disclosure requires a profile-defined purpose and authority; consent is one possible basis rather than a universal rule. Aggregation alone does not establish anonymity.", "source_refs": [ "SRC-005", "SRC-007" ], "findings": [ { "id": "usp-f-access", "name": "Disclosure context and retention", "description": "Proposed local governance separates point topology, customer links and usage payloads. Disclosure requires a profile-defined purpose and authority; consent is one possible basis rather than a universal rule. Aggregation alone does not establish anonymity.", "source_refs": [ "SRC-005", "SRC-007" ], "questions": [ { "id": "usp-f-access-q1", "kind": "access", "text": "Which recipient may access each point, customer-link or usage scope for which purpose?", "answer_data": [ "recipient role", "scope", "purpose", "authority reference", "expiry" ] }, { "id": "usp-f-access-q2", "kind": "privacy", "text": "What evidence permits release of a derived usage view without exposing restricted linked data?", "answer_data": [ "release assessment", "transformation reference", "linkage risk", "decision reference" ] }, { "id": "usp-f-access-q3", "kind": "retention", "text": "Which retention rule, hold or disposal decision governs each local record and payload?", "answer_data": [ "policy reference", "retention trigger", "hold reference", "disposal evidence" ] } ], "data_elements": [ { "id": "usp-f-access-data1", "name": "recipient role", "description": "Candidate group: recipient role, scope, purpose, authority reference, expiry. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "usp-f-access-data2", "name": "release assessment", "description": "Candidate group: release assessment, transformation reference, linkage risk, decision reference. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "usp-f-access-data3", "name": "policy reference", "description": "Candidate group: policy reference, retention trigger, hold reference, disposal evidence. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "usp-f-access-artifact", "name": "Disclosure context and retention evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "usp-l-mapping", "name": "Revision and exchange assurance", "description": "Bind every exchange to source identity, model revision, transformation and loss report. Preserve disputed assertions until authorized resolution, subject to retention policy. Conceptual alignment is not executable schema conformance.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "findings": [ { "id": "usp-f-mapping", "name": "Revision and exchange assurance", "description": "Bind every exchange to source identity, model revision, transformation and loss report. Preserve disputed assertions until authorized resolution, subject to retention policy. Conceptual alignment is not executable schema conformance.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "usp-f-mapping-q1", "kind": "provenance", "text": "Which source revision and responsible role support the current point assertions?", "answer_data": [ "source revision", "attribution", "derivation", "recorded time" ] }, { "id": "usp-f-mapping-q2", "kind": "validation", "text": "What checks and unresolved errors qualify this exported view?", "answer_data": [ "validation report", "profile revision", "reference resolution", "loss report" ] }, { "id": "usp-f-mapping-q3", "kind": "interoperability", "text": "How are local identifiers, virtual usage points and time values mapped without changing their meaning?", "answer_data": [ "mapping version", "identifier crosswalk", "virtual mapping rule", "time transformation" ] } ], "data_elements": [ { "id": "usp-f-mapping-data1", "name": "source revision", "description": "Candidate group: source revision, attribution, derivation, recorded time. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "usp-f-mapping-data2", "name": "validation report", "description": "Candidate group: validation report, profile revision, reference resolution, loss report. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] }, { "id": "usp-f-mapping-data3", "name": "mapping version", "description": "Candidate group: mapping version, identifier crosswalk, virtual mapping rule, time transformation. Required fields and nested types must be pinned by the adopting profile; unknowns are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "usp-f-mapping-artifact", "name": "Revision and exchange assurance evidence record", "description": "Versioned evidence or restricted reference supporting the point-specific assertions; external master payloads are not copied by default.", "media_or_form": [ "Structured record", "Evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier; governed IRI; otherwise adopting Dimension UUID. Preserve revision and digest separately from identity.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "usp-fn-register", "name": "Register point evidence", "description": "Proposed unimplemented local record operation: register point evidence.", "inputs": [ "proposed identifier", "service profile", "recognition evidence" ], "outputs": [ "point revision or duplicate conflict" ], "preconditions": [ "Authorized local role and purpose, pinned adopting profile and expected revision match.", "Required evidence and referenced masters resolve; unknown or disputed inputs produce a refusal or review report." ], "effects": [ "Create local identity record only; do not allocate an external NMI." ], "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "usp-fn-bind", "name": "Record interface bindings", "description": "Proposed unimplemented local record operation: record interface bindings.", "inputs": [ "point revision", "place/network references", "responsibility evidence", "effective interval" ], "outputs": [ "binding revision or unresolved-reference refusal" ], "preconditions": [ "Authorized local role and purpose, pinned adopting profile and expected revision match.", "Required evidence and referenced masters resolve; unknown or disputed inputs produce a refusal or review report." ], "effects": [ "Record qualified links without editing network or party masters." ], "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "usp-fn-meter", "name": "Record metering assignment change", "description": "Proposed unimplemented local record operation: record metering assignment change.", "inputs": [ "point revision", "device/channel references", "exchange or exception evidence" ], "outputs": [ "assignment revision or interval-conflict report" ], "preconditions": [ "Authorized local role and purpose, pinned adopting profile and expected revision match.", "Required evidence and referenced masters resolve; unknown or disputed inputs produce a refusal or review report." ], "effects": [ "Record local assignment history without provisioning or configuring devices." ], "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "usp-fn-observe", "name": "Index observation or reading", "description": "Proposed unimplemented local record operation: index observation or reading.", "inputs": [ "source record", "quantity semantics", "time", "quality", "assignment reference" ], "outputs": [ "evidence index entry or attribution failure" ], "preconditions": [ "Authorized local role and purpose, pinned adopting profile and expected revision match.", "Required evidence and referenced masters resolve; unknown or disputed inputs produce a refusal or review report." ], "effects": [ "Index external evidence with correction lineage; do not calculate charges." ], "source_refs": [ "SRC-004", "SRC-005", "SRC-008" ] }, { "id": "usp-fn-transition", "name": "Record evidenced service transition", "description": "Proposed unimplemented local record operation: record evidenced service transition.", "inputs": [ "current revision", "event reference", "authority reference", "effective time" ], "outputs": [ "new assertion revision or refusal" ], "preconditions": [ "Authorized local role and purpose, pinned adopting profile and expected revision match.", "Required evidence and referenced masters resolve; unknown or disputed inputs produce a refusal or review report." ], "effects": [ "Change local assertions only; issue no control commands and confer no right to disconnect." ], "source_refs": [ "SRC-003", "SRC-005" ] }, { "id": "usp-fn-project", "name": "Prepare scoped review projection", "description": "Proposed unimplemented local record operation: prepare scoped review projection.", "inputs": [ "point revision", "recipient scope", "authority and purpose", "mapping version" ], "outputs": [ "restricted draft view and validation/loss report or denial" ], "preconditions": [ "Authorized local role and purpose, pinned adopting profile and expected revision match.", "Required evidence and referenced masters resolve; unknown or disputed inputs produce a refusal or review report." ], "effects": [ "Prepare local review artifact only; no external disclosure, certification or automatic publication." ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "composition": [ { "target": "WM-BLT-002", "relation": "REFERENCE", "purpose": "Served premises and occupancy remain externally mastered; carry only point-to-place bindings.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "WM-BLT-001", "relation": "REFERENCE", "purpose": "Building master and structural lifecycle stay external; legacy U1 is mapped specifically to Building / Structure, not every shared-alias row.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "WM-BLT-003", "relation": "REFERENCE", "purpose": "Network and asset masters own topology and maintenance; local references do not recalculate flow or control equipment.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-PER-001", "relation": "REFERENCE", "purpose": "Person identity and lifecycle stay external; store purpose-limited party references.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Organization identity stays external; local operator and steward role bindings convey no corporate ownership claim.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "External meter, measurement, work-order, agreement and tariff masters", "relation": "REFERENCE", "purpose": "Profile must pin these bindings before runtime use. Local records carry references and applicability only.", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007" ] }, { "target": "ESPI UsagePoint", "relation": "ALIGN", "purpose": "Partial alignment: virtual aggregates are not equivalent to physical interfaces; versioned mapping and tests required.", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "target": "INSPIRE Utility Networks", "relation": "ALIGN", "purpose": "Align external network link semantics without owning network nodes, pipes or cables.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "SOSA/SSN and PROV-O", "relation": "ALIGN", "purpose": "Conceptual observation and assertion-lineage alignment; no RDF implementation or conformance claim.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Owner archetype: utility service-point steward; identify the accountable role and authority in the adopting Dimension.", "Declare service kind, jurisdiction, master identifiers, physical boundary and responsibility profile.", "Pin model version, referenced masters, retention policy and recipient scopes before operational adoption." ], "namespace_guidance": "Use a governed service-point namespace; aliases and revisions never silently replace the master identifier.", "registry_links": [ "vr.wm-blt-004", "WM-BLT-001", "WM-BLT-002", "WM-BLT-003" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve original service codes, units, direction, evidence and effective time; normalize only through a documented mapping.", "Do not infer a point from an address, account, meter or virtual aggregate alone." ], "patch_rules": [ "Use expected revision, authorized role, reason and evidence for each patch; retain supersession links subject to lawful retention.", "Separate effective time from recorded time; retain concurrent disputed assertions until a reasoned resolution." ], "compatibility_rules": [ "Identity, cardinality, quantity or direction changes require explicit migration and loss review.", "Legacy U5 and wildcard imports are untrusted migration inputs, not conformance evidence." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with issuing namespace", "Governed global identifier or IRI", "UUID or ULID assigned by adopting Dimension" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z. Distinguish event/effective time, observation time, result time and ingestion time. Preserve interval semantics and source precision; unknown times are not fabricated.", "serial_naming_rule": "Use stable point and artifact identifiers plus separate revision labels; dates may annotate a record but are never its identity.", "integrity_rule": "Record digest, source revision and transformation lineage; a digest proves byte integrity only, not condition, authorization or correctness." }, "policies": [ "This noncanonical research draft proposes local context design; every external alignment needs a pinned implementation profile.", "Safety, field work, physical disconnection and restoration remain external authorized processes; no control instructions are specified.", "Do not expose detailed topology, location, customer bindings or usage by default. Consent is not asserted to be the sole lawful basis.", "Independent external review and source/version checks remain open; neither a provider waiver nor local validation closes them." ], "crud": { "read": [ "Return the authorized historical or current view with quality, unresolved bindings and holds." ], "create": [ "Require steward authority, service profile and identity evidence; prevent account or device identifiers from becoming accidental point IDs." ], "update": [ "Append attributable revisions with optimistic concurrency and effective intervals; reference external work evidence rather than executing it." ], "delete": [ "Retire point identities without identifier reuse. Payload retention, holds, erasure and minimal tombstones follow the adopting Dimension policy; indefinite personal-data history is not required.", "Deletion of referenced meters, observations, agreements and party records is executed only by their masters; local link removal does not delete them or disconnect utility service." ] }, "roles": [ { "name": "Service-point steward", "responsibilities": [ "Govern identity, boundary and binding revisions." ] }, { "name": "Utility evidence contributor", "responsibilities": [ "Supply authorized observations and work evidence without expanding access." ] }, { "name": "Measurement data steward", "responsibilities": [ "Resolve channel attribution, quality and correction references." ] }, { "name": "Data access reviewer", "responsibilities": [ "Review recipient scope, purpose, release risks and retention decisions." ] }, { "name": "Model reviewer", "responsibilities": [ "Check mappings, omissions and draft holds before adoption." ] } ], "access": { "default_rule": "Deny by default; evaluate recipient, purpose, authority, field scope and time in the external adopting access service.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency access requires external policy authority, narrow scope, expiry and subsequent review; the local model grants no emergency powers." ], "audit_requirements": [ "Reference the external audit record for access decisions, revision authorship, exports and disposal; do not own an audit engine." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the owner Dimension policies and AGENTS.md.", "Read this specification, visible holds and pinned neighbor masters before interpreting or changing point records." ] } }, "coverage": { "claim": "Source-grounded proposed structure for one persistent water, heat, electricity or sewage service interface, reconciled with legacy U5 and checked by a separate local no-tools self-audit. Selected domain examples support a reviewable draft only; independent review, source/version verification, detailed utility profiles and executable conformance remain incomplete.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Authority-qualified root distinct from meter, account and virtual aggregate." }, { "dimension": "lifecycle", "status": "covered", "notes": "Planned, commissioned and retired point continuity; assignments and service assertions have their own intervals." }, { "dimension": "relationships", "status": "covered", "notes": "Place, network, device, party and term masters remain references; no strict ledger edges exist for this model." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, observed, result and recorded time differ; interval overlap requires review." }, { "dimension": "provenance", "status": "covered", "notes": "Evidence attribution, revision and contradiction remain explicit." }, { "dimension": "ownership", "status": "covered", "notes": "Asset ownership, maintenance, operation and record stewardship are distinct role bindings." }, { "dimension": "validation", "status": "gap", "notes": "Research structure passes repository gates; executable instance and mapping fixtures remain a gap." }, { "dimension": "access", "status": "covered", "notes": "Purpose-scoped views separate topology, usage and customer links; external policy decides authority." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Dimension policy controls payload retention and minimal tombstones; local retirement has no physical effect." }, { "dimension": "interoperability", "status": "gap", "notes": "ESPI, INSPIRE and observation/provenance vocabulary alignments are partial; legacy wildcard imports not accepted." }, { "dimension": "direct properties", "status": "covered", "notes": "Typed interface capacity and direction with units and conditions; no universal engineering thresholds." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Survey or label evidence, location precision and condition quality distinguish recognition from identity." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Local record functions separated from physical supply capability, behavior and external work." }, { "dimension": "utility profiles", "status": "gap", "notes": "Water, power, heat and sewage covered conceptually; detailed heat return and sewer discharge profiles remain incomplete." } ], "known_omissions": [ "Executable nested data schemas, pinned external master bindings and adversarial instance fixtures.", "Detailed thermal return, sewer discharge, unmetered allocation, multi-feed and embedded-network mappings require domain review.", "Current legal, engineering safety, licensing, privacy and operational applicability are not determined.", "IEC CIM and DLMS/COSEM wildcard imports from U5 are deferred until exact editions, licensing and mappings are reviewed." ], "conflicts": [ "Legacy one-connection-to-one-point and one-tariff-per-spell assumptions are not universal constraints; adopting profiles must define multiplicity.", "Legacy consent-only access and claimed conformance are not carried forward; authority and conformance require separate evidence." ], "regional_assumptions": [ "NMI procedure evidence is specific to the Australian NEM; the index marks v7.5 as future relative to this run.", "EPA inventory examples do not establish current universal material reporting duties.", "INSPIRE distinguishes utility network types; the proposed service-point root is a local design, not an INSPIRE class." ], "adversarial_checks": [ "Meter exchange must not silently create a new root point.", "Virtual usage aggregation must not fabricate a physical interface.", "One address can require distinct service-point records; matching addresses do not merge them.", "Zero usage does not prove disconnection; an approved service state does not prove physical availability.", "Unknown material or capacity is not a safe value; inferred estimates remain labelled.", "Party change does not grant historical usage access to a new occupant.", "Retirement and record deletion do not operate utility equipment." ] }, "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 root maintains authority-qualified service-interface identity across meter, customer and status changes. It is not a network asset, observation, commercial account or virtual aggregate. The registry standalone-mm value classifies the registry record rather than the subject-kind enum." }, "decisions": [ { "concept": "Persistent service interface", "disposition": "accepted", "rationale": "Identity survives qualified assignment changes; planned and retired points remain representable without a current meter or active supply." }, { "concept": "Virtual usage point equivalence", "disposition": "rejected", "rationale": "The admitted ESPI guidance permits logical aggregation. The result uses qualified mappings and does not infer a physical interface from an exchange identifier." }, { "concept": "Legacy connection and tariff cardinalities", "disposition": "qualified", "rationale": "U5 one-to-one connection and single tariff assumptions are not universal constraints. Local profiles must resolve multiple assets, channels and component-specific terms." }, { "concept": "Place and asset ownership", "disposition": "separated", "rationale": "Served premises, connection location, asset ownership, maintenance and stewardship are distinct bindings. Network and building masters retain their own lifecycle." }, { "concept": "Utility-specific physical properties", "disposition": "accepted with profile hold", "rationale": "Typed properties and direction conventions allow utility differences without inventing engineering limits. Thermal return and sewer discharge detail is explicitly deferred." }, { "concept": "Metering and observation lineage", "disposition": "accepted", "rationale": "Device assignments, observation times, quantity semantics and corrected readings are separate references. Meter exchange is not automatic point replacement or a billing calculation." }, { "concept": "Availability and operational action", "disposition": "separated", "rationale": "Registration, physical availability and contractual service state remain distinct. Proposed local functions neither actuate equipment nor grant a right to disconnect." }, { "concept": "Consent, disclosure and retention", "disposition": "qualified", "rationale": "Local access design requires profile-defined authority, purpose and scope. Consent-only access and automatic anonymity are rejected; revision history is constrained by retention policy." }, { "concept": "Legacy imports and conformance", "disposition": "deferred", "rationale": "Wildcard IEC CIM and DLMS/COSEM imports and legacy conformance claims are not admitted. Candidate object groups and conceptual alignments require executable bindings and tests." }, { "concept": "Source assurance", "disposition": "limited", "rationale": "Selected primary browser evidence was reviewed, with AEMO limited to its index and other version constraints recorded. Direct HTTP checks were not attempted and statuses remain unmeasured." }, { "concept": "Provider independence", "disposition": "waived and held", "rationale": "Both external providers were skipped under the owner override. A separate Codex self-audit cannot be represented as independent external agreement." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; this separate local Codex no-tools self-audit is not a second-provider review.", "Live source and version verification is incomplete. Eight admitted URLs have selected browser evidence only; direct HTTP checks were not attempted under the owner-reported sandbox restriction and all HTTP statuses are unmeasured. The AEMO procedure PDF timed out, so only index-level evidence is admitted. The coordinator must run check_sources.py and review applicability separately.", "Utility, jurisdiction, engineering, privacy, retention and licensing profiles require qualified review before operational use. Detailed thermal return, sewer discharge, multi-feed, unmetered allocation and embedded-network cases remain incomplete; no safety or legal certification is claimed.", "Executable nested schemas, required instance fields, pinned neighbor masters, unit code lists, exact standard mappings and adversarial fixtures are incomplete. Legacy wildcard imports are deferred; no runtime or exchange conformance is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify exact source editions, direct retrieval, source licensing and utility-specific applicability before closing the source hold.", "Develop pinned utility profiles and test virtual aggregates, shared meters, meter exchanges, corrected readings, split responsibility and restricted historical usage.", "Restore independent external review before any canonical or publishable-draft promotion." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }