# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T20:35:18Z", "synthesisSha256": "d5928ac18e4bc0dd7c5a97dc625edeaa118091185a1bb55c582df82d0c0e6844", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-FLW-001", "registryId": "vr.wm-flw-001", "name": "Energy", "version": "0.3.0", "previousVersions": [ { "version": "0.2.0-legacy", "url": "https://ver.cy/models/world-f1-energy/" } ], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.FLW.EN" ], "tags": [ "energy", "phy.flw.en" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-flw-001-energy/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-001", "model": { "registry_id": "vr.wm-flw-001", "model_id": "WM-FLW-001", "name": "Energy", "entry_kind": "aggregate", "purpose": "Describe a governed energy account that brings carrier quantities, observations and reconciliations together for a declared boundary and period.", "scope_statement": "The proposed aggregate root is an energy account for a named physical or statistical boundary, reporting interval and accounting profile. It owns local quantity assertions, derivations and balance revisions. A multi-carrier account retains separate carrier ledgers and explicit transformation links. It is an information model, not energy itself, a physical network, a settlement authority or a control system.", "in_scope": [ "Account identity and revision, carrier classification, quantity basis, measurement evidence and time semantics", "Production, transformation, end use, stock and interchange assertions within an explicit accounting perimeter", "Reconciliation results, discrepancies, review state and governed evidence projections" ], "out_of_scope": [ "Asset, meter, site, network topology, organization and contract master lifecycles", "Dispatch, switching, load shedding, disconnection, physical plant operation and real-time stability protection", "Tariffs, market clearing, imbalance settlement, payment execution, emissions calculation and environmental certificates", "Detailed controlled-material handling or hazardous engineering procedures; only policy and qualified external references" ], "boundary_notes": [ { "neighbor": "Legacy F1 Energy", "distinction": "Retain carrier, production, consumption, balance and storage concerns as account assertions. Move asset masters and operations outside. Wildcard imports and legacy conformance labels are not carried forward.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "neighbor": "Physical asset, metering point and network models", "distinction": "Account membership references an external master and its effective revision. Referencing capacity or an outage does not grant authority to maintain or operate equipment.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008" ] }, { "neighbor": "Money, trading contract and settlement models", "distinction": "Commercial schedules may be compared as labeled evidence; local closure has no settlement or legal effect. Legacy mandatory money composition is rejected for accounts without money.", "source_refs": [ "SRC-005", "SRC-007" ] }, { "neighbor": "Emission and environmental claim models", "distinction": "Export qualified activity-data references only. Neither energy balance nor fuel classification establishes an emission value or renewable ownership claim.", "source_refs": [ "SRC-001", "SRC-007" ] }, { "neighbor": "Statistical and electricity operating profiles", "distinction": "Territorial annual statistics and physical electricity intervals are distinct profiles. No universal sign, interval, storage convention or residence/territory mapping is inferred.", "source_refs": [ "SRC-001", "SRC-005" ] } ] }, "sources": [ { "id": "SRC-001", "title": "International Recommendations for Energy Statistics (IRES)", "organization": "United Nations Statistics Division", "url": "https://unstats.un.org/unsd/energystats/methodology/documents/IRES-web.pdf", "version_or_date": "2018, ST/ESA/STAT/SER.M/93; adopted 2011", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:33:42Z", "relevance": "Selected chapters 3-5 and 8: product classification, quantities, flows, stock changes and statistical balance. Profile design inspiration, not universal settlement rules." }, { "id": "SRC-002", "title": "NIST Guide to the SI, Chapter 4: The Two Classes of SI Units and the SI Prefixes", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/pml/special-publication-811/nist-guide-si-chapter-4-two-classes-si-units-and-si-prefixes", "version_or_date": "SP 811 web chapter; accessed 2026-10-06; latest revision unverified", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:33:42Z", "relevance": "Derived unit tables distinguish energy from power and warn that a unit alone does not define the measured quantity. No current SI prefix catalogue is imported." }, { "id": "SRC-003", "title": "Heat Content of Natural Gas Consumed: Definitions, Sources and Explanatory Notes", "organization": "U.S. Energy Information Administration", "url": "https://www.eia.gov/dnav/ng/TblDefs/ng_cons_heat_tbldef2.asp", "version_or_date": "Undated live definitions page accessed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:33:42Z", "relevance": "Heat content per physical quantity and gross versus net heat content support explicit conversion basis. No fixed fuel factor is adopted." }, { "id": "SRC-004", "title": "IEC 61968-9:2024 - Interfaces for meter reading and control", "organization": "International Electrotechnical Commission", "url": "https://webstore.iec.ch/en/publication/75041", "version_or_date": "Edition 3.0, 2024-07-18; public abstract only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:33:42Z", "relevance": "Public scope supports meter-data exchange alignment and separates message semantics from communication protocols. Full paid clauses and conformance were not reviewed." }, { "id": "SRC-005", "title": "Form EIA-930: Hourly and Daily Balancing Authority Operations Report - Instructions", "organization": "U.S. Energy Information Administration", "url": "https://www.eia.gov/survey/form/eia_930/instructions.pdf", "version_or_date": "Retrieved form displays approval expiration 2029-07-31; revision date not stated", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:33:42Z", "relevance": "Selected data definitions and quality sections support a US electricity profile: physical boundary, forecast versus actual, signed interchange, storage treatment and revisions. Not a worldwide requirement." }, { "id": "SRC-006", "title": "Guidelines for Smart Grid Cybersecurity", "organization": "National Institute of Standards and Technology", "url": "https://csrc.nist.gov/pubs/ir/7628/r1/final", "version_or_date": "NIST IR 7628 Revision 1, September 2014; landing abstract only", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:33:42Z", "relevance": "Risk-based security and privacy guidance motivates access controls on energy information. Detailed controls and current adequacy require separate review." }, { "id": "SRC-007", "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", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:33:42Z", "relevance": "Entities, activities, attribution, derivation and revision provide conceptual evidence lineage. No implemented RDF binding or authenticity guarantee is claimed." }, { "id": "SRC-008", "title": "Energy storage for electricity generation", "organization": "U.S. Energy Information Administration", "url": "https://www.eia.gov/energyexplained/electricity/energy-storage-for-electricity-generation.php", "version_or_date": "Explanatory page accessed 2026-10-06; historical statistics not imported", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:33:42Z", "relevance": "Storage explanation distinguishes stored energy, power capability and duration. Used for concepts only; no historical fleet totals or forecasts are adopted." } ], "structure": { "bundles": [ { "id": "energy-account", "name": "Account boundary", "description": "Proposed account concern: account boundary.", "rationale": "Keep account boundary explicit so the account remains interpretable and independently reviewable.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "layers": [ { "id": "energy-account-identity", "name": "Account identity and perimeter", "description": "Proposed account key binds the steward, perimeter revision, period and profile. Physical connectivity, territory and organizational ownership must not silently substitute for each other.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "findings": [ { "id": "account-scope", "name": "Governed account perimeter", "description": "Proposed account key binds the steward, perimeter revision, period and profile. Physical connectivity, territory and organizational ownership must not silently substitute for each other.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "questions": [ { "id": "account-scope-q1", "text": "Which authoritative account identifier and steward namespace distinguish this account from another view of the same energy?", "kind": "identity", "answer_data": [ "accountId", "masterNamespace", "stewardRef" ] }, { "id": "account-scope-q2", "text": "Which included points, excluded flows and effective boundary revision define this accounting perimeter?", "kind": "spatial", "answer_data": [ "boundaryRef", "boundaryRevision", "membershipRefs", "exclusions" ] }, { "id": "account-scope-q3", "text": "What are the exact start and end instants and the interval inclusion convention for this account?", "kind": "temporal", "answer_data": [ "startTime", "endTime", "timeZone", "endpointConvention" ] }, { "id": "account-scope-q4", "text": "Which pinned profile makes this a statistical, operational or other qualified account?", "kind": "classification", "answer_data": [ "profileRef", "profileVersion", "accountClass" ] } ], "data_elements": [ { "id": "account-scope-data-accountid", "name": "accountId", "description": "Candidate accountId value for: Which authoritative account identifier and steward namespace distinguish this account from another view of the same energy? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-masternamespace", "name": "masterNamespace", "description": "Candidate masterNamespace value for: Which authoritative account identifier and steward namespace distinguish this account from another view of the same energy? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-stewardref", "name": "stewardRef", "description": "Candidate stewardRef value for: Which authoritative account identifier and steward namespace distinguish this account from another view of the same energy? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-boundaryref", "name": "boundaryRef", "description": "Candidate boundaryRef value for: Which included points, excluded flows and effective boundary revision define this accounting perimeter? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-boundaryrevision", "name": "boundaryRevision", "description": "Candidate boundaryRevision value for: Which included points, excluded flows and effective boundary revision define this accounting perimeter? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-membershiprefs", "name": "membershipRefs", "description": "Candidate membershipRefs value for: Which included points, excluded flows and effective boundary revision define this accounting perimeter? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-exclusions", "name": "exclusions", "description": "Candidate exclusions value for: Which included points, excluded flows and effective boundary revision define this accounting perimeter? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-starttime", "name": "startTime", "description": "Candidate startTime value for: What are the exact start and end instants and the interval inclusion convention for this account? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-endtime", "name": "endTime", "description": "Candidate endTime value for: What are the exact start and end instants and the interval inclusion convention for this account? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-timezone", "name": "timeZone", "description": "Candidate timeZone value for: What are the exact start and end instants and the interval inclusion convention for this account? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-endpointconvention", "name": "endpointConvention", "description": "Candidate endpointConvention value for: What are the exact start and end instants and the interval inclusion convention for this account? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-profileref", "name": "profileRef", "description": "Candidate profileRef value for: Which pinned profile makes this a statistical, operational or other qualified account? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-profileversion", "name": "profileVersion", "description": "Candidate profileVersion value for: Which pinned profile makes this a statistical, operational or other qualified account? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "account-scope-data-accountclass", "name": "accountClass", "description": "Candidate accountClass value for: Which pinned profile makes this a statistical, operational or other qualified account? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "account-scope-artifact", "name": "Account boundary declaration", "description": "A versioned local declaration of the perimeter, time interval and externally governed profile.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "energy-account-authority", "name": "Revision and review", "description": "Proposed local states are draft, reviewed, closed, superseded and withdrawn. State changes record accountable decisions and never certify physical balance, regulatory filing or financial settlement.", "source_refs": [ "SRC-005", "SRC-007" ], "findings": [ { "id": "account-revision", "name": "Account revision authority", "description": "Proposed local states are draft, reviewed, closed, superseded and withdrawn. State changes record accountable decisions and never certify physical balance, regulatory filing or financial settlement.", "source_refs": [ "SRC-005", "SRC-007" ], "questions": [ { "id": "account-revision-q1", "text": "Who may approve a local account revision and on what delegated authority?", "kind": "authority", "answer_data": [ "approverRef", "authorityEvidence", "approvalScope" ] }, { "id": "account-revision-q2", "text": "Which prior revision is superseded and which review state applies to this revision?", "kind": "lifecycle", "answer_data": [ "revisionId", "predecessorRef", "reviewState" ] }, { "id": "account-revision-q3", "text": "What discrepancy or late evidence prevents local closure or requires a new revision?", "kind": "exception", "answer_data": [ "blockingIssues", "lateEvidenceRefs", "reopenReason" ] }, { "id": "account-revision-q4", "text": "Which retention rule and hold govern disposal of this account revision and its restricted payloads?", "kind": "retention", "answer_data": [ "retentionPolicyRef", "holdRefs", "dispositionDecisionRef" ] } ], "data_elements": [ { "id": "account-revision-data-approverref", "name": "approverRef", "description": "Candidate approverRef value for: Who may approve a local account revision and on what delegated authority? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-authorityevidence", "name": "authorityEvidence", "description": "Candidate authorityEvidence value for: Who may approve a local account revision and on what delegated authority? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-approvalscope", "name": "approvalScope", "description": "Candidate approvalScope value for: Who may approve a local account revision and on what delegated authority? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-revisionid", "name": "revisionId", "description": "Candidate revisionId value for: Which prior revision is superseded and which review state applies to this revision? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-predecessorref", "name": "predecessorRef", "description": "Candidate predecessorRef value for: Which prior revision is superseded and which review state applies to this revision? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-reviewstate", "name": "reviewState", "description": "Candidate reviewState value for: Which prior revision is superseded and which review state applies to this revision? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-blockingissues", "name": "blockingIssues", "description": "Candidate blockingIssues value for: What discrepancy or late evidence prevents local closure or requires a new revision? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-lateevidencerefs", "name": "lateEvidenceRefs", "description": "Candidate lateEvidenceRefs value for: What discrepancy or late evidence prevents local closure or requires a new revision? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-reopenreason", "name": "reopenReason", "description": "Candidate reopenReason value for: What discrepancy or late evidence prevents local closure or requires a new revision? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-retentionpolicyref", "name": "retentionPolicyRef", "description": "Candidate retentionPolicyRef value for: Which retention rule and hold govern disposal of this account revision and its restricted payloads? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-holdrefs", "name": "holdRefs", "description": "Candidate holdRefs value for: Which retention rule and hold govern disposal of this account revision and its restricted payloads? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "account-revision-data-dispositiondecisionref", "name": "dispositionDecisionRef", "description": "Candidate dispositionDecisionRef value for: Which retention rule and hold govern disposal of this account revision and its restricted payloads? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "account-revision-artifact", "name": "Account review record", "description": "Revision-specific decision with reasons, unresolved issues and separate effective and recorded times.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "energy-basis", "name": "Carrier and quantity basis", "description": "Proposed account concern: carrier and quantity basis.", "rationale": "Keep carrier and quantity basis explicit so the account remains interpretable and independently reviewable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "layers": [ { "id": "energy-basis-classification", "name": "Carrier classification", "description": "Use versioned product codes and distinguish carrier from primary source, technology and environmental claim. This proposed mapping can preserve local grades without inventing equivalence.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "carrier-basis", "name": "Carrier identity and quality basis", "description": "Use versioned product codes and distinguish carrier from primary source, technology and environmental claim. This proposed mapping can preserve local grades without inventing equivalence.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "carrier-basis-q1", "text": "Which carrier code, code-list version and local grade describe this quantity?", "kind": "classification", "answer_data": [ "carrierCode", "schemeRef", "schemeVersion", "grade" ] }, { "id": "carrier-basis-q2", "text": "Is the asserted concept an energy product, a primary source or a generating technology?", "kind": "definition", "answer_data": [ "conceptRole", "definitionRef", "mappingStatus" ] }, { "id": "carrier-basis-q3", "text": "Which composition, moisture or reference-condition evidence controls this fuel quantity basis?", "kind": "measurement", "answer_data": [ "qualityEvidenceRef", "conditions", "qualityValidity" ] }, { "id": "carrier-basis-q4", "text": "What information is lost or unmapped when the local carrier code is projected to the selected classification?", "kind": "interoperability", "answer_data": [ "mappingRef", "unmappedTerms", "lossReport" ] } ], "data_elements": [ { "id": "carrier-basis-data-carriercode", "name": "carrierCode", "description": "Candidate carrierCode value for: Which carrier code, code-list version and local grade describe this quantity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-schemeref", "name": "schemeRef", "description": "Candidate schemeRef value for: Which carrier code, code-list version and local grade describe this quantity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-schemeversion", "name": "schemeVersion", "description": "Candidate schemeVersion value for: Which carrier code, code-list version and local grade describe this quantity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-grade", "name": "grade", "description": "Candidate grade value for: Which carrier code, code-list version and local grade describe this quantity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-conceptrole", "name": "conceptRole", "description": "Candidate conceptRole value for: Is the asserted concept an energy product, a primary source or a generating technology? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-definitionref", "name": "definitionRef", "description": "Candidate definitionRef value for: Is the asserted concept an energy product, a primary source or a generating technology? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-mappingstatus", "name": "mappingStatus", "description": "Candidate mappingStatus value for: Is the asserted concept an energy product, a primary source or a generating technology? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-qualityevidenceref", "name": "qualityEvidenceRef", "description": "Candidate qualityEvidenceRef value for: Which composition, moisture or reference-condition evidence controls this fuel quantity basis? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-conditions", "name": "conditions", "description": "Candidate conditions value for: Which composition, moisture or reference-condition evidence controls this fuel quantity basis? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-qualityvalidity", "name": "qualityValidity", "description": "Candidate qualityValidity value for: Which composition, moisture or reference-condition evidence controls this fuel quantity basis? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-mappingref", "name": "mappingRef", "description": "Candidate mappingRef value for: What information is lost or unmapped when the local carrier code is projected to the selected classification? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-unmappedterms", "name": "unmappedTerms", "description": "Candidate unmappedTerms value for: What information is lost or unmapped when the local carrier code is projected to the selected classification? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "carrier-basis-data-lossreport", "name": "lossReport", "description": "Candidate lossReport value for: What information is lost or unmapped when the local carrier code is projected to the selected classification? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "carrier-basis-artifact", "name": "Carrier mapping record", "description": "Explicit code and quality mappings scoped to the account; not a replacement product registry.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "energy-basis-units", "name": "Quantity normalization", "description": "Keep source values and their quantity kinds. Power, interval energy, mass and volume are distinct. Unit normalization cannot transform a physical carrier; calorific conversion requires a stated factor and conditions.", "source_refs": [ "SRC-002", "SRC-003" ], "findings": [ { "id": "quantity-basis", "name": "Dimensionally qualified quantity", "description": "Keep source values and their quantity kinds. Power, interval energy, mass and volume are distinct. Unit normalization cannot transform a physical carrier; calorific conversion requires a stated factor and conditions.", "source_refs": [ "SRC-002", "SRC-003" ], "questions": [ { "id": "quantity-basis-q1", "text": "What quantity kind, numerical value, unit and uncertainty were originally reported?", "kind": "measurement", "answer_data": [ "quantityKind", "rawValue", "rawUnit", "uncertainty" ] }, { "id": "quantity-basis-q2", "text": "Which factor, gross or net calorific basis and reference conditions permit this conversion?", "kind": "constraint", "answer_data": [ "factorValue", "factorUnit", "factorSource", "calorificBasis", "referenceConditions" ] }, { "id": "quantity-basis-q3", "text": "If power is integrated to energy, which sampling, duration and missing-interval method applies?", "kind": "temporal", "answer_data": [ "integrationMethod", "sampleIntervals", "elapsedDuration", "gapPolicy" ] }, { "id": "quantity-basis-q4", "text": "Does the normalized value retain dimensional consistency and a reversible trail to the original report?", "kind": "validation", "answer_data": [ "normalizedValue", "normalizedUnit", "derivationRef", "validationIssues" ] } ], "data_elements": [ { "id": "quantity-basis-data-quantitykind", "name": "quantityKind", "description": "Candidate quantityKind value for: What quantity kind, numerical value, unit and uncertainty were originally reported? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-rawvalue", "name": "rawValue", "description": "Candidate rawValue value for: What quantity kind, numerical value, unit and uncertainty were originally reported? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-rawunit", "name": "rawUnit", "description": "Candidate rawUnit value for: What quantity kind, numerical value, unit and uncertainty were originally reported? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-uncertainty", "name": "uncertainty", "description": "Candidate uncertainty value for: What quantity kind, numerical value, unit and uncertainty were originally reported? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-factorvalue", "name": "factorValue", "description": "Candidate factorValue value for: Which factor, gross or net calorific basis and reference conditions permit this conversion? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-factorunit", "name": "factorUnit", "description": "Candidate factorUnit value for: Which factor, gross or net calorific basis and reference conditions permit this conversion? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-factorsource", "name": "factorSource", "description": "Candidate factorSource value for: Which factor, gross or net calorific basis and reference conditions permit this conversion? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-calorificbasis", "name": "calorificBasis", "description": "Candidate calorificBasis value for: Which factor, gross or net calorific basis and reference conditions permit this conversion? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-referenceconditions", "name": "referenceConditions", "description": "Candidate referenceConditions value for: Which factor, gross or net calorific basis and reference conditions permit this conversion? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-integrationmethod", "name": "integrationMethod", "description": "Candidate integrationMethod value for: If power is integrated to energy, which sampling, duration and missing-interval method applies? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-sampleintervals", "name": "sampleIntervals", "description": "Candidate sampleIntervals value for: If power is integrated to energy, which sampling, duration and missing-interval method applies? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-elapsedduration", "name": "elapsedDuration", "description": "Candidate elapsedDuration value for: If power is integrated to energy, which sampling, duration and missing-interval method applies? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-gappolicy", "name": "gapPolicy", "description": "Candidate gapPolicy value for: If power is integrated to energy, which sampling, duration and missing-interval method applies? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-normalizedvalue", "name": "normalizedValue", "description": "Candidate normalizedValue value for: Does the normalized value retain dimensional consistency and a reversible trail to the original report? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-normalizedunit", "name": "normalizedUnit", "description": "Candidate normalizedUnit value for: Does the normalized value retain dimensional consistency and a reversible trail to the original report? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-derivationref", "name": "derivationRef", "description": "Candidate derivationRef value for: Does the normalized value retain dimensional consistency and a reversible trail to the original report? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "quantity-basis-data-validationissues", "name": "validationIssues", "description": "Candidate validationIssues value for: Does the normalized value retain dimensional consistency and a reversible trail to the original report? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "quantity-basis-artifact", "name": "Quantity derivation sheet", "description": "Inputs, factors, precision, method and output of a proposed conversion with refusal reasons for unsupported conversions.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "energy-evidence", "name": "Observation and demand", "description": "Proposed account concern: observation and demand.", "rationale": "Keep observation and demand explicit so the account remains interpretable and independently reviewable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007" ], "layers": [ { "id": "energy-evidence-metering", "name": "Observation evidence", "description": "The account holds a revision-pinned observation reference and local acceptance assessment. A meter, register, delivery point and observation are different identities. Missing, estimated and invalid values are not zero.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ], "findings": [ { "id": "observation-quality", "name": "Qualified observation", "description": "The account holds a revision-pinned observation reference and local acceptance assessment. A meter, register, delivery point and observation are different identities. Missing, estimated and invalid values are not zero.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ], "questions": [ { "id": "observation-quality-q1", "text": "Which meter or source system, register channel and delivery point identify the observation?", "kind": "identity", "answer_data": [ "sourceSystemRef", "meterRef", "channelRef", "pointRef", "observationId" ] }, { "id": "observation-quality-q2", "text": "Which observation interval, reading time and ingestion time apply, including offset and daylight-saving ambiguity?", "kind": "temporal", "answer_data": [ "intervalStart", "intervalEnd", "readingTime", "ingestionTime", "clockIssue" ] }, { "id": "observation-quality-q3", "text": "Is this an actual, estimated, substituted, missing or rejected value and what method justifies that status?", "kind": "quality", "answer_data": [ "qualityState", "methodRef", "uncertainty", "reason" ] }, { "id": "observation-quality-q4", "text": "Which source revision and integrity evidence allow a corrected or cumulative reading to be checked without double counting?", "kind": "evidence", "answer_data": [ "sourceRevision", "digest", "cumulativeFlag", "resetEvidence", "acceptanceRef" ] } ], "data_elements": [ { "id": "observation-quality-data-sourcesystemref", "name": "sourceSystemRef", "description": "Candidate sourceSystemRef value for: Which meter or source system, register channel and delivery point identify the observation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-meterref", "name": "meterRef", "description": "Candidate meterRef value for: Which meter or source system, register channel and delivery point identify the observation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-channelref", "name": "channelRef", "description": "Candidate channelRef value for: Which meter or source system, register channel and delivery point identify the observation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-pointref", "name": "pointRef", "description": "Candidate pointRef value for: Which meter or source system, register channel and delivery point identify the observation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-observationid", "name": "observationId", "description": "Candidate observationId value for: Which meter or source system, register channel and delivery point identify the observation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-intervalstart", "name": "intervalStart", "description": "Candidate intervalStart value for: Which observation interval, reading time and ingestion time apply, including offset and daylight-saving ambiguity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-intervalend", "name": "intervalEnd", "description": "Candidate intervalEnd value for: Which observation interval, reading time and ingestion time apply, including offset and daylight-saving ambiguity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-readingtime", "name": "readingTime", "description": "Candidate readingTime value for: Which observation interval, reading time and ingestion time apply, including offset and daylight-saving ambiguity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-ingestiontime", "name": "ingestionTime", "description": "Candidate ingestionTime value for: Which observation interval, reading time and ingestion time apply, including offset and daylight-saving ambiguity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-clockissue", "name": "clockIssue", "description": "Candidate clockIssue value for: Which observation interval, reading time and ingestion time apply, including offset and daylight-saving ambiguity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-qualitystate", "name": "qualityState", "description": "Candidate qualityState value for: Is this an actual, estimated, substituted, missing or rejected value and what method justifies that status? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-methodref", "name": "methodRef", "description": "Candidate methodRef value for: Is this an actual, estimated, substituted, missing or rejected value and what method justifies that status? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-uncertainty", "name": "uncertainty", "description": "Candidate uncertainty value for: Is this an actual, estimated, substituted, missing or rejected value and what method justifies that status? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-reason", "name": "reason", "description": "Candidate reason value for: Is this an actual, estimated, substituted, missing or rejected value and what method justifies that status? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-sourcerevision", "name": "sourceRevision", "description": "Candidate sourceRevision value for: Which source revision and integrity evidence allow a corrected or cumulative reading to be checked without double counting? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-digest", "name": "digest", "description": "Candidate digest value for: Which source revision and integrity evidence allow a corrected or cumulative reading to be checked without double counting? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-cumulativeflag", "name": "cumulativeFlag", "description": "Candidate cumulativeFlag value for: Which source revision and integrity evidence allow a corrected or cumulative reading to be checked without double counting? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-resetevidence", "name": "resetEvidence", "description": "Candidate resetEvidence value for: Which source revision and integrity evidence allow a corrected or cumulative reading to be checked without double counting? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "observation-quality-data-acceptanceref", "name": "acceptanceRef", "description": "Candidate acceptanceRef value for: Which source revision and integrity evidence allow a corrected or cumulative reading to be checked without double counting? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "observation-quality-artifact", "name": "Observation acceptance record", "description": "Acceptance or quarantine decision for external reading evidence; raw source records remain separately mastered.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "energy-evidence-demand", "name": "Consumption and profiles", "description": "Proposed allocations retain consumption role and measurement coverage. Separate actual consumption, forecasts and scenarios; avoid counting both a meter and the profile estimate for the same coverage.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "demand-allocation", "name": "Qualified demand allocation", "description": "Proposed allocations retain consumption role and measurement coverage. Separate actual consumption, forecasts and scenarios; avoid counting both a meter and the profile estimate for the same coverage.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "demand-allocation-q1", "text": "Which use sector and energy or non-energy use category applies to this quantity?", "kind": "classification", "answer_data": [ "sectorCode", "sectorScheme", "useCategory" ] }, { "id": "demand-allocation-q2", "text": "Was demand measured, allocated from a profile or forecast, and which evidence and method support it?", "kind": "provenance", "answer_data": [ "assertionClass", "evidenceRefs", "profileRef", "methodVersion" ] }, { "id": "demand-allocation-q3", "text": "Which points and intervals contribute to the allocation and how are overlaps or behind-the-meter gaps identified?", "kind": "composition", "answer_data": [ "memberPointRefs", "coverageIntervals", "overlapReport", "coverageGaps" ] }, { "id": "demand-allocation-q4", "text": "Are forecast and actual demand comparable in boundary, interval, unit and gross or net treatment?", "kind": "validation", "answer_data": [ "comparisonBasis", "forecastRevision", "actualRevision", "comparabilityIssues" ] } ], "data_elements": [ { "id": "demand-allocation-data-sectorcode", "name": "sectorCode", "description": "Candidate sectorCode value for: Which use sector and energy or non-energy use category applies to this quantity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-sectorscheme", "name": "sectorScheme", "description": "Candidate sectorScheme value for: Which use sector and energy or non-energy use category applies to this quantity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-usecategory", "name": "useCategory", "description": "Candidate useCategory value for: Which use sector and energy or non-energy use category applies to this quantity? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-assertionclass", "name": "assertionClass", "description": "Candidate assertionClass value for: Was demand measured, allocated from a profile or forecast, and which evidence and method support it? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-evidencerefs", "name": "evidenceRefs", "description": "Candidate evidenceRefs value for: Was demand measured, allocated from a profile or forecast, and which evidence and method support it? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-profileref", "name": "profileRef", "description": "Candidate profileRef value for: Was demand measured, allocated from a profile or forecast, and which evidence and method support it? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-methodversion", "name": "methodVersion", "description": "Candidate methodVersion value for: Was demand measured, allocated from a profile or forecast, and which evidence and method support it? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-memberpointrefs", "name": "memberPointRefs", "description": "Candidate memberPointRefs value for: Which points and intervals contribute to the allocation and how are overlaps or behind-the-meter gaps identified? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-coverageintervals", "name": "coverageIntervals", "description": "Candidate coverageIntervals value for: Which points and intervals contribute to the allocation and how are overlaps or behind-the-meter gaps identified? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-overlapreport", "name": "overlapReport", "description": "Candidate overlapReport value for: Which points and intervals contribute to the allocation and how are overlaps or behind-the-meter gaps identified? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-coveragegaps", "name": "coverageGaps", "description": "Candidate coverageGaps value for: Which points and intervals contribute to the allocation and how are overlaps or behind-the-meter gaps identified? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-comparisonbasis", "name": "comparisonBasis", "description": "Candidate comparisonBasis value for: Are forecast and actual demand comparable in boundary, interval, unit and gross or net treatment? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-forecastrevision", "name": "forecastRevision", "description": "Candidate forecastRevision value for: Are forecast and actual demand comparable in boundary, interval, unit and gross or net treatment? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-actualrevision", "name": "actualRevision", "description": "Candidate actualRevision value for: Are forecast and actual demand comparable in boundary, interval, unit and gross or net treatment? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "demand-allocation-data-comparabilityissues", "name": "comparabilityIssues", "description": "Candidate comparabilityIssues value for: Are forecast and actual demand comparable in boundary, interval, unit and gross or net treatment? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "demand-allocation-artifact", "name": "Demand allocation worksheet", "description": "Locally proposed mapping of accepted quantities to use categories, with overlap checks and unresolved coverage.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "energy-conversion", "name": "Production and transformation", "description": "Proposed account concern: production and transformation.", "rationale": "Keep production and transformation explicit so the account remains interpretable and independently reviewable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-008" ], "layers": [ { "id": "energy-conversion-production", "name": "Production assertions", "description": "Reference a generating or extraction source and keep gross output, own use and net contribution distinguished by profile. A capacity rating is context, not a measured amount generated.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "findings": [ { "id": "production-entry", "name": "Production contribution", "description": "Reference a generating or extraction source and keep gross output, own use and net contribution distinguished by profile. A capacity rating is context, not a measured amount generated.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "questions": [ { "id": "production-entry-q1", "text": "Which external production source and effective asset revision support this contribution?", "kind": "relationship", "answer_data": [ "assetRef", "assetRevision", "productionEvidenceRef" ] }, { "id": "production-entry-q2", "text": "What gross, own-use and net output quantities are reported and which convention relates them?", "kind": "measurement", "answer_data": [ "grossOutput", "ownUse", "netOutput", "profileConvention" ] }, { "id": "production-entry-q3", "text": "Which availability or outage assertion affects this period without changing the asset master?", "kind": "state", "answer_data": [ "availabilityEvidenceRef", "validInterval", "unknownStatus" ] }, { "id": "production-entry-q4", "text": "Which observed or rated power limit is relevant and why cannot it be substituted for energy produced?", "kind": "constraint", "answer_data": [ "capacityRef", "capacityUnit", "capacityBasis", "applicability" ] } ], "data_elements": [ { "id": "production-entry-data-assetref", "name": "assetRef", "description": "Candidate assetRef value for: Which external production source and effective asset revision support this contribution? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-assetrevision", "name": "assetRevision", "description": "Candidate assetRevision value for: Which external production source and effective asset revision support this contribution? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-productionevidenceref", "name": "productionEvidenceRef", "description": "Candidate productionEvidenceRef value for: Which external production source and effective asset revision support this contribution? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-grossoutput", "name": "grossOutput", "description": "Candidate grossOutput value for: What gross, own-use and net output quantities are reported and which convention relates them? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-ownuse", "name": "ownUse", "description": "Candidate ownUse value for: What gross, own-use and net output quantities are reported and which convention relates them? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-netoutput", "name": "netOutput", "description": "Candidate netOutput value for: What gross, own-use and net output quantities are reported and which convention relates them? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-profileconvention", "name": "profileConvention", "description": "Candidate profileConvention value for: What gross, own-use and net output quantities are reported and which convention relates them? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-availabilityevidenceref", "name": "availabilityEvidenceRef", "description": "Candidate availabilityEvidenceRef value for: Which availability or outage assertion affects this period without changing the asset master? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-validinterval", "name": "validInterval", "description": "Candidate validInterval value for: Which availability or outage assertion affects this period without changing the asset master? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-unknownstatus", "name": "unknownStatus", "description": "Candidate unknownStatus value for: Which availability or outage assertion affects this period without changing the asset master? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-capacityref", "name": "capacityRef", "description": "Candidate capacityRef value for: Which observed or rated power limit is relevant and why cannot it be substituted for energy produced? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-capacityunit", "name": "capacityUnit", "description": "Candidate capacityUnit value for: Which observed or rated power limit is relevant and why cannot it be substituted for energy produced? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-capacitybasis", "name": "capacityBasis", "description": "Candidate capacityBasis value for: Which observed or rated power limit is relevant and why cannot it be substituted for energy produced? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "production-entry-data-applicability", "name": "applicability", "description": "Candidate applicability value for: Which observed or rated power limit is relevant and why cannot it be substituted for energy produced? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "production-entry-artifact", "name": "Production contribution record", "description": "Account-specific inclusion of source output and coverage; no asset commissioning or dispatch authority.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "energy-conversion-transformation", "name": "Transformation accounting", "description": "A proposed transformation assertion links qualified carrier inputs and outputs over the same declared process boundary. Losses, own use, coproducts and unmeasured terms remain explicit; conversion is not a unit change.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "transformation-entry", "name": "Linked conversion inputs and outputs", "description": "A proposed transformation assertion links qualified carrier inputs and outputs over the same declared process boundary. Losses, own use, coproducts and unmeasured terms remain explicit; conversion is not a unit change.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "transformation-entry-q1", "text": "Which input and output quantity references belong to the same transformation boundary and interval?", "kind": "composition", "answer_data": [ "processRef", "inputRefs", "outputRefs", "boundaryRef", "interval" ] }, { "id": "transformation-entry-q2", "text": "Which losses, own use and coproduct allocations are included or excluded from the calculation?", "kind": "measurement", "answer_data": [ "lossRefs", "ownUseRefs", "coproductRule", "excludedTerms" ] }, { "id": "transformation-entry-q3", "text": "What denominator, calorific basis and system boundary make an efficiency or performance ratio interpretable?", "kind": "validation", "answer_data": [ "ratioKind", "numeratorRefs", "denominatorRefs", "basis", "conditions" ] }, { "id": "transformation-entry-q4", "text": "Which missing input, ambient heat term or allocation ambiguity prevents treating this ratio as comparable efficiency?", "kind": "exception", "answer_data": [ "unmeasuredTerms", "ambientContribution", "allocationIssue", "comparisonStatus" ] } ], "data_elements": [ { "id": "transformation-entry-data-processref", "name": "processRef", "description": "Candidate processRef value for: Which input and output quantity references belong to the same transformation boundary and interval? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-inputrefs", "name": "inputRefs", "description": "Candidate inputRefs value for: Which input and output quantity references belong to the same transformation boundary and interval? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-outputrefs", "name": "outputRefs", "description": "Candidate outputRefs value for: Which input and output quantity references belong to the same transformation boundary and interval? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-boundaryref", "name": "boundaryRef", "description": "Candidate boundaryRef value for: Which input and output quantity references belong to the same transformation boundary and interval? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-interval", "name": "interval", "description": "Candidate interval value for: Which input and output quantity references belong to the same transformation boundary and interval? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-lossrefs", "name": "lossRefs", "description": "Candidate lossRefs value for: Which losses, own use and coproduct allocations are included or excluded from the calculation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-ownuserefs", "name": "ownUseRefs", "description": "Candidate ownUseRefs value for: Which losses, own use and coproduct allocations are included or excluded from the calculation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-coproductrule", "name": "coproductRule", "description": "Candidate coproductRule value for: Which losses, own use and coproduct allocations are included or excluded from the calculation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-excludedterms", "name": "excludedTerms", "description": "Candidate excludedTerms value for: Which losses, own use and coproduct allocations are included or excluded from the calculation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-ratiokind", "name": "ratioKind", "description": "Candidate ratioKind value for: What denominator, calorific basis and system boundary make an efficiency or performance ratio interpretable? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-numeratorrefs", "name": "numeratorRefs", "description": "Candidate numeratorRefs value for: What denominator, calorific basis and system boundary make an efficiency or performance ratio interpretable? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-denominatorrefs", "name": "denominatorRefs", "description": "Candidate denominatorRefs value for: What denominator, calorific basis and system boundary make an efficiency or performance ratio interpretable? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-basis", "name": "basis", "description": "Candidate basis value for: What denominator, calorific basis and system boundary make an efficiency or performance ratio interpretable? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-conditions", "name": "conditions", "description": "Candidate conditions value for: What denominator, calorific basis and system boundary make an efficiency or performance ratio interpretable? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-unmeasuredterms", "name": "unmeasuredTerms", "description": "Candidate unmeasuredTerms value for: Which missing input, ambient heat term or allocation ambiguity prevents treating this ratio as comparable efficiency? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-ambientcontribution", "name": "ambientContribution", "description": "Candidate ambientContribution value for: Which missing input, ambient heat term or allocation ambiguity prevents treating this ratio as comparable efficiency? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-allocationissue", "name": "allocationIssue", "description": "Candidate allocationIssue value for: Which missing input, ambient heat term or allocation ambiguity prevents treating this ratio as comparable efficiency? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "transformation-entry-data-comparisonstatus", "name": "comparisonStatus", "description": "Candidate comparisonStatus value for: Which missing input, ambient heat term or allocation ambiguity prevents treating this ratio as comparable efficiency? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "transformation-entry-artifact", "name": "Transformation reconciliation sheet", "description": "Linked input and output evidence plus a named ratio definition; heat-pump performance ratios are not silently constrained as fuel efficiency.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "energy-continuity", "name": "Storage and exchange", "description": "Proposed account concern: storage and exchange.", "rationale": "Keep storage and exchange explicit so the account remains interpretable and independently reviewable.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "energy-continuity-stocks", "name": "Stocks and availability", "description": "Proposed stock assertions separate opening and closing quantities, movements and losses from available power. Storage discharge is not new primary production. Strategic stock designation and operating reserve capability remain qualified references.", "source_refs": [ "SRC-001", "SRC-008" ], "findings": [ { "id": "storage-continuity", "name": "Stock continuity and deliverability", "description": "Proposed stock assertions separate opening and closing quantities, movements and losses from available power. Storage discharge is not new primary production. Strategic stock designation and operating reserve capability remain qualified references.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "storage-continuity-q1", "text": "What opening and closing stock or stored-energy values, times and common basis are evidenced?", "kind": "measurement", "answer_data": [ "openingStock", "closingStock", "stockTimes", "quantityBasis" ] }, { "id": "storage-continuity-q2", "text": "Which charge, discharge, loss and adjustment terms explain the change without being counted twice?", "kind": "process", "answer_data": [ "chargeRefs", "dischargeRefs", "lossRefs", "adjustmentRefs", "accountingConvention" ] }, { "id": "storage-continuity-q3", "text": "What deliverable energy, power limit, duration and observation time qualify claimed availability?", "kind": "constraint", "answer_data": [ "deliverableEnergy", "powerLimit", "duration", "availabilityTime", "conditions" ] }, { "id": "storage-continuity-q4", "text": "Which external policy or commitment supports a strategic-stock or reserve designation and its limits?", "kind": "authority", "answer_data": [ "designationType", "policyRef", "commitmentRef", "validity", "restrictions" ] } ], "data_elements": [ { "id": "storage-continuity-data-openingstock", "name": "openingStock", "description": "Candidate openingStock value for: What opening and closing stock or stored-energy values, times and common basis are evidenced? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-closingstock", "name": "closingStock", "description": "Candidate closingStock value for: What opening and closing stock or stored-energy values, times and common basis are evidenced? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-stocktimes", "name": "stockTimes", "description": "Candidate stockTimes value for: What opening and closing stock or stored-energy values, times and common basis are evidenced? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-quantitybasis", "name": "quantityBasis", "description": "Candidate quantityBasis value for: What opening and closing stock or stored-energy values, times and common basis are evidenced? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-chargerefs", "name": "chargeRefs", "description": "Candidate chargeRefs value for: Which charge, discharge, loss and adjustment terms explain the change without being counted twice? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-dischargerefs", "name": "dischargeRefs", "description": "Candidate dischargeRefs value for: Which charge, discharge, loss and adjustment terms explain the change without being counted twice? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-lossrefs", "name": "lossRefs", "description": "Candidate lossRefs value for: Which charge, discharge, loss and adjustment terms explain the change without being counted twice? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-adjustmentrefs", "name": "adjustmentRefs", "description": "Candidate adjustmentRefs value for: Which charge, discharge, loss and adjustment terms explain the change without being counted twice? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-accountingconvention", "name": "accountingConvention", "description": "Candidate accountingConvention value for: Which charge, discharge, loss and adjustment terms explain the change without being counted twice? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-deliverableenergy", "name": "deliverableEnergy", "description": "Candidate deliverableEnergy value for: What deliverable energy, power limit, duration and observation time qualify claimed availability? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-powerlimit", "name": "powerLimit", "description": "Candidate powerLimit value for: What deliverable energy, power limit, duration and observation time qualify claimed availability? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-duration", "name": "duration", "description": "Candidate duration value for: What deliverable energy, power limit, duration and observation time qualify claimed availability? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-availabilitytime", "name": "availabilityTime", "description": "Candidate availabilityTime value for: What deliverable energy, power limit, duration and observation time qualify claimed availability? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-conditions", "name": "conditions", "description": "Candidate conditions value for: What deliverable energy, power limit, duration and observation time qualify claimed availability? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-designationtype", "name": "designationType", "description": "Candidate designationType value for: Which external policy or commitment supports a strategic-stock or reserve designation and its limits? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-policyref", "name": "policyRef", "description": "Candidate policyRef value for: Which external policy or commitment supports a strategic-stock or reserve designation and its limits? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-commitmentref", "name": "commitmentRef", "description": "Candidate commitmentRef value for: Which external policy or commitment supports a strategic-stock or reserve designation and its limits? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-validity", "name": "validity", "description": "Candidate validity value for: Which external policy or commitment supports a strategic-stock or reserve designation and its limits? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "storage-continuity-data-restrictions", "name": "restrictions", "description": "Candidate restrictions value for: Which external policy or commitment supports a strategic-stock or reserve designation and its limits? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "storage-continuity-artifact", "name": "Storage continuity worksheet", "description": "Proposed local reconciliation with opening/closing evidence and a separate capability context; no storage control instructions.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "energy-continuity-interchange", "name": "Boundary exchanges", "description": "Proposed transfer assertions name both boundaries, direction, time and measurement point. Schedule, physical observation and commercial obligation are different claims. Netting preserves traceable gross contributions when available.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "findings": [ { "id": "boundary-flow", "name": "Directed boundary exchange", "description": "Proposed transfer assertions name both boundaries, direction, time and measurement point. Schedule, physical observation and commercial obligation are different claims. Netting preserves traceable gross contributions when available.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "questions": [ { "id": "boundary-flow-q1", "text": "Which origin, destination and boundary-point identifiers define the directed exchange?", "kind": "relationship", "answer_data": [ "originRef", "destinationRef", "boundaryPointRef", "flowId" ] }, { "id": "boundary-flow-q2", "text": "Is this quantity scheduled, measured, estimated or commercially nominated?", "kind": "classification", "answer_data": [ "flowClass", "sourceRef", "revisionRef" ] }, { "id": "boundary-flow-q3", "text": "Which import/export sign and gross/net convention applies on each side of the interface?", "kind": "constraint", "answer_data": [ "localSignConvention", "counterpartySignConvention", "nettingBasis" ] }, { "id": "boundary-flow-q4", "text": "Which time, loss allocation or counterparty-report difference prevents reciprocal reconciliation?", "kind": "exception", "answer_data": [ "localInterval", "counterpartyInterval", "lossAllocation", "difference", "issueRefs" ] } ], "data_elements": [ { "id": "boundary-flow-data-originref", "name": "originRef", "description": "Candidate originRef value for: Which origin, destination and boundary-point identifiers define the directed exchange? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-destinationref", "name": "destinationRef", "description": "Candidate destinationRef value for: Which origin, destination and boundary-point identifiers define the directed exchange? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-boundarypointref", "name": "boundaryPointRef", "description": "Candidate boundaryPointRef value for: Which origin, destination and boundary-point identifiers define the directed exchange? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-flowid", "name": "flowId", "description": "Candidate flowId value for: Which origin, destination and boundary-point identifiers define the directed exchange? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-flowclass", "name": "flowClass", "description": "Candidate flowClass value for: Is this quantity scheduled, measured, estimated or commercially nominated? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-sourceref", "name": "sourceRef", "description": "Candidate sourceRef value for: Is this quantity scheduled, measured, estimated or commercially nominated? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-revisionref", "name": "revisionRef", "description": "Candidate revisionRef value for: Is this quantity scheduled, measured, estimated or commercially nominated? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-localsignconvention", "name": "localSignConvention", "description": "Candidate localSignConvention value for: Which import/export sign and gross/net convention applies on each side of the interface? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-counterpartysignconvention", "name": "counterpartySignConvention", "description": "Candidate counterpartySignConvention value for: Which import/export sign and gross/net convention applies on each side of the interface? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-nettingbasis", "name": "nettingBasis", "description": "Candidate nettingBasis value for: Which import/export sign and gross/net convention applies on each side of the interface? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-localinterval", "name": "localInterval", "description": "Candidate localInterval value for: Which time, loss allocation or counterparty-report difference prevents reciprocal reconciliation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-counterpartyinterval", "name": "counterpartyInterval", "description": "Candidate counterpartyInterval value for: Which time, loss allocation or counterparty-report difference prevents reciprocal reconciliation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-lossallocation", "name": "lossAllocation", "description": "Candidate lossAllocation value for: Which time, loss allocation or counterparty-report difference prevents reciprocal reconciliation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-difference", "name": "difference", "description": "Candidate difference value for: Which time, loss allocation or counterparty-report difference prevents reciprocal reconciliation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "boundary-flow-data-issuerefs", "name": "issueRefs", "description": "Candidate issueRefs value for: Which time, loss allocation or counterparty-report difference prevents reciprocal reconciliation? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "boundary-flow-artifact", "name": "Interchange comparison record", "description": "Local comparison of two reported sides or of schedule and actual; disagreement does not assign liability.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "energy-assurance", "name": "Balance and release", "description": "Proposed account concern: balance and release.", "rationale": "Keep balance and release explicit so the account remains interpretable and independently reviewable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "energy-assurance-balance", "name": "Profile-bound reconciliation", "description": "A proposed balance calculation uses one pinned profile and explicit term membership. Report residuals and unknowns instead of forcing equality. A statistical difference is not automatically a physical loss or a settled imbalance.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "findings": [ { "id": "balance-residual", "name": "Explained balance residual", "description": "A proposed balance calculation uses one pinned profile and explicit term membership. Report residuals and unknowns instead of forcing equality. A statistical difference is not automatically a physical loss or a settled imbalance.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "questions": [ { "id": "balance-residual-q1", "text": "Which signed equation and profile version define this carrier balance and its allowed transformations?", "kind": "definition", "answer_data": [ "equationRef", "profileVersion", "carrierRef", "signConvention" ] }, { "id": "balance-residual-q2", "text": "Which accepted revisions supply each balance term and which terms are excluded to avoid double counting?", "kind": "composition", "answer_data": [ "termBindings", "acceptedRevisionRefs", "exclusions", "coverageReport" ] }, { "id": "balance-residual-q3", "text": "What residual, uncertainty and tolerance result and which unexplained contributions remain?", "kind": "validation", "answer_data": [ "residual", "residualUnit", "uncertainty", "toleranceBasis", "unresolvedTerms" ] }, { "id": "balance-residual-q4", "text": "Who assessed the residual and what qualified conclusion or correction request was recorded?", "kind": "decision", "answer_data": [ "reviewerRef", "decision", "reason", "correctionRequestRefs" ] } ], "data_elements": [ { "id": "balance-residual-data-equationref", "name": "equationRef", "description": "Candidate equationRef value for: Which signed equation and profile version define this carrier balance and its allowed transformations? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-profileversion", "name": "profileVersion", "description": "Candidate profileVersion value for: Which signed equation and profile version define this carrier balance and its allowed transformations? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-carrierref", "name": "carrierRef", "description": "Candidate carrierRef value for: Which signed equation and profile version define this carrier balance and its allowed transformations? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-signconvention", "name": "signConvention", "description": "Candidate signConvention value for: Which signed equation and profile version define this carrier balance and its allowed transformations? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-termbindings", "name": "termBindings", "description": "Candidate termBindings value for: Which accepted revisions supply each balance term and which terms are excluded to avoid double counting? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-acceptedrevisionrefs", "name": "acceptedRevisionRefs", "description": "Candidate acceptedRevisionRefs value for: Which accepted revisions supply each balance term and which terms are excluded to avoid double counting? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-exclusions", "name": "exclusions", "description": "Candidate exclusions value for: Which accepted revisions supply each balance term and which terms are excluded to avoid double counting? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-coveragereport", "name": "coverageReport", "description": "Candidate coverageReport value for: Which accepted revisions supply each balance term and which terms are excluded to avoid double counting? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-residual", "name": "residual", "description": "Candidate residual value for: What residual, uncertainty and tolerance result and which unexplained contributions remain? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-residualunit", "name": "residualUnit", "description": "Candidate residualUnit value for: What residual, uncertainty and tolerance result and which unexplained contributions remain? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-uncertainty", "name": "uncertainty", "description": "Candidate uncertainty value for: What residual, uncertainty and tolerance result and which unexplained contributions remain? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-tolerancebasis", "name": "toleranceBasis", "description": "Candidate toleranceBasis value for: What residual, uncertainty and tolerance result and which unexplained contributions remain? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-unresolvedterms", "name": "unresolvedTerms", "description": "Candidate unresolvedTerms value for: What residual, uncertainty and tolerance result and which unexplained contributions remain? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-reviewerref", "name": "reviewerRef", "description": "Candidate reviewerRef value for: Who assessed the residual and what qualified conclusion or correction request was recorded? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-decision", "name": "decision", "description": "Candidate decision value for: Who assessed the residual and what qualified conclusion or correction request was recorded? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-reason", "name": "reason", "description": "Candidate reason value for: Who assessed the residual and what qualified conclusion or correction request was recorded? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "balance-residual-data-correctionrequestrefs", "name": "correctionRequestRefs", "description": "Candidate correctionRequestRefs value for: Who assessed the residual and what qualified conclusion or correction request was recorded? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "balance-residual-artifact", "name": "Balance assessment report", "description": "Reproducible local calculation and reviewer assessment, distinct from a grid stability assessment or settlement decision.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "energy-assurance-release", "name": "Evidence projection", "description": "Proposed release manifests identify exactly which account revision and derivations a recipient can see. Aggregation alone is not proof of confidentiality. Public, operator and consumer views require separate authority and disclosure review.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "findings": [ { "id": "release-evidence", "name": "Authorized evidence projection", "description": "Proposed release manifests identify exactly which account revision and derivations a recipient can see. Aggregation alone is not proof of confidentiality. Public, operator and consumer views require separate authority and disclosure review.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "questions": [ { "id": "release-evidence-q1", "text": "Which recipient, purpose and field-level grant authorize this projection of energy information?", "kind": "access", "answer_data": [ "recipientRef", "purpose", "grantRef", "fieldScope" ] }, { "id": "release-evidence-q2", "text": "Which fine-grained observations or infrastructure details must be withheld or aggregated for this recipient?", "kind": "privacy", "answer_data": [ "restrictedFields", "aggregationRule", "disclosureAssessmentRef" ] }, { "id": "release-evidence-q3", "text": "Which revision, derivations and source limitations must travel with this released view?", "kind": "provenance", "answer_data": [ "accountRevision", "derivationRefs", "sourceLimitations", "releaseDigest" ] }, { "id": "release-evidence-q4", "text": "Which pinned exchange profile, mapping and validation evidence describe the projection without claiming untested conformance?", "kind": "interoperability", "answer_data": [ "exchangeProfileRef", "mappingVersion", "validationEvidence", "knownLosses" ] } ], "data_elements": [ { "id": "release-evidence-data-recipientref", "name": "recipientRef", "description": "Candidate recipientRef value for: Which recipient, purpose and field-level grant authorize this projection of energy information? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-purpose", "name": "purpose", "description": "Candidate purpose value for: Which recipient, purpose and field-level grant authorize this projection of energy information? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-grantref", "name": "grantRef", "description": "Candidate grantRef value for: Which recipient, purpose and field-level grant authorize this projection of energy information? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-fieldscope", "name": "fieldScope", "description": "Candidate fieldScope value for: Which recipient, purpose and field-level grant authorize this projection of energy information? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-restrictedfields", "name": "restrictedFields", "description": "Candidate restrictedFields value for: Which fine-grained observations or infrastructure details must be withheld or aggregated for this recipient? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-aggregationrule", "name": "aggregationRule", "description": "Candidate aggregationRule value for: Which fine-grained observations or infrastructure details must be withheld or aggregated for this recipient? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-disclosureassessmentref", "name": "disclosureAssessmentRef", "description": "Candidate disclosureAssessmentRef value for: Which fine-grained observations or infrastructure details must be withheld or aggregated for this recipient? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-accountrevision", "name": "accountRevision", "description": "Candidate accountRevision value for: Which revision, derivations and source limitations must travel with this released view? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-derivationrefs", "name": "derivationRefs", "description": "Candidate derivationRefs value for: Which revision, derivations and source limitations must travel with this released view? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-sourcelimitations", "name": "sourceLimitations", "description": "Candidate sourceLimitations value for: Which revision, derivations and source limitations must travel with this released view? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-releasedigest", "name": "releaseDigest", "description": "Candidate releaseDigest value for: Which revision, derivations and source limitations must travel with this released view? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-exchangeprofileref", "name": "exchangeProfileRef", "description": "Candidate exchangeProfileRef value for: Which pinned exchange profile, mapping and validation evidence describe the projection without claiming untested conformance? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-mappingversion", "name": "mappingVersion", "description": "Candidate mappingVersion value for: Which pinned exchange profile, mapping and validation evidence describe the projection without claiming untested conformance? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-validationevidence", "name": "validationEvidence", "description": "Candidate validationEvidence value for: Which pinned exchange profile, mapping and validation evidence describe the projection without claiming untested conformance? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "release-evidence-data-knownlosses", "name": "knownLosses", "description": "Candidate knownLosses value for: Which pinned exchange profile, mapping and validation evidence describe the projection without claiming untested conformance? Nested typing, controlled values and conditional requirements must be specified by an adopting profile.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "release-evidence-artifact", "name": "Projection manifest", "description": "Local release candidate and authorization evidence; no automatic transmission or external publication.", "media_or_form": [ "structured record", "human-readable report" ], "serial": true, "identity_strategy": "Authoritative master-system ID first; governed IRI second; otherwise Dimension UUID or ULID. Keep stable artifact ID separate from revision and digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-account", "name": "Register account revision", "description": "Create a proposed local account revision with stable identity and immutable boundary and profile bindings. Proposed function contract only; no implementation is claimed.", "inputs": [ "Account declaration", "Authority evidence", "Expected predecessor revision" ], "outputs": [ "Draft account revision", "Refusal report" ], "preconditions": [ "Authorized adopting-Dimension role and concurrency precondition satisfied", "Account identity is resolved", "Boundary, interval and pinned profile are explicit" ], "effects": [ "Adds a local draft; does not create an asset or legal obligation" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "admit-observation", "name": "Assess observation evidence", "description": "Assess a source observation for local account inclusion while retaining its raw value and revision. Proposed function contract only; no implementation is claimed.", "inputs": [ "Observation reference and revision", "Point/channel mapping", "Quality evidence" ], "outputs": [ "Accepted or quarantined local reference", "Coverage and duplication issues" ], "preconditions": [ "Authorized adopting-Dimension role and concurrency precondition satisfied", "Source access authorized", "Observation identity and time basis resolved" ], "effects": [ "Records a local assessment only; does not modify a meter or upstream observation" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "normalize-quantity", "name": "Derive normalized quantity", "description": "Proposed dimensional conversion using a documented factor or power integration method. Proposed function contract only; no implementation is claimed.", "inputs": [ "Original quantity and unit", "Factor and conditions", "Method version and interval" ], "outputs": [ "Derived quantity and provenance", "Refusal on incompatible or missing basis" ], "preconditions": [ "Authorized adopting-Dimension role and concurrency precondition satisfied", "Quantity kind known", "Calorific basis, conditions and uncertainty policy explicit where applicable" ], "effects": [ "Appends a derivation; preserves original values; cannot physically convert a carrier" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] }, { "id": "reconcile-account", "name": "Assess account balance", "description": "Proposed computation of a profile-specific residual from accepted revisions. Proposed function contract only; no implementation is claimed.", "inputs": [ "Pinned signed equation", "Quantity revisions", "Coverage, stock and transformation bindings" ], "outputs": [ "Balance assessment and residual", "Unknown terms and overlap report" ], "preconditions": [ "Authorized adopting-Dimension role and concurrency precondition satisfied", "Compatible carrier, interval, units and profile", "No unidentified duplicate contribution", "Tolerance source stated" ], "effects": [ "Appends local assessment; never forces residual to zero, dispatches equipment or settles money" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "revise-account", "name": "Supersede account revision", "description": "Record a justified correction and mark dependent projections stale. Proposed function contract only; no implementation is claimed.", "inputs": [ "Prior revision", "Correction evidence", "Reviewer authority" ], "outputs": [ "New account revision", "Impacted derivation and projection references" ], "preconditions": [ "Authorized adopting-Dimension role and concurrency precondition satisfied", "Expected revision matches", "Closed-account correction policy satisfied" ], "effects": [ "Supersedes rather than overwrites; does not revise external settlement or evidence masters" ], "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "prepare-projection", "name": "Prepare authorized projection", "description": "Build a local view candidate for a specific recipient with full assurance limitations. Proposed function contract only; no implementation is claimed.", "inputs": [ "Account revision", "Recipient grant", "Disclosure and mapping profiles" ], "outputs": [ "Local projection candidate", "Manifest and withheld-field report" ], "preconditions": [ "Authorized adopting-Dimension role and concurrency precondition satisfied", "Purpose and access evaluated by authorized policy owner", "Disclosure assessment completed", "No unresolved critical mapping issue" ], "effects": [ "Creates local candidate only; transmission and external publication require separate authority" ], "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "composition": [ { "target": "Physical asset and metering point master", "relation": "REFERENCE", "purpose": "Candidate binding for equipment, source and delivery point identifiers and revisions. Target owns maintenance, topology and operation.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] }, { "target": "Organization and authority master", "relation": "REFERENCE", "purpose": "Candidate binding for steward, operator and reviewer identity; local account assignments do not create external authority.", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "target": "Site or land parcel master", "relation": "REFERENCE", "purpose": "Optional location evidence for included assets; energy perimeter is not necessarily a parcel boundary.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "Money and settlement record", "relation": "REFERENCE", "purpose": "Optional link if a separate settlement uses the account; mandatory legacy money composition is not retained.", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "target": "Emission activity-data consumer", "relation": "REFERENCE", "purpose": "Optional outgoing revision-pinned evidence; external model owns factors, calculations and environmental claims.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "IRES 2018 / SIEC", "relation": "ALIGN", "purpose": "Conceptual statistical category alignment, with explicit mapping gaps and no blanket conformance claim.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "IEC 61968-9:2024", "relation": "ALIGN", "purpose": "Meter exchange scope alignment based only on public abstract; licensed clauses and executable mapping deferred.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "PROV-O 2013", "relation": "ALIGN", "purpose": "Conceptual derivation and revision mapping; not an implemented provenance store or truth certification.", "required": false, "source_refs": [ "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Adopting Dimension declares a generic account steward role, authority delegations and namespace; no company is designated owner", "Pin the boundary, time, carrier, quantity and accounting profiles plus mappings to external masters", "Declare access, retention, audit and disclosure policies before any instance population", "Record research status as reviewable-draft; Codex only, Claude and Grok skipped, separate self-audit is not independent review" ], "namespace_guidance": "Use a governed namespace for account, assertion and artifact identifiers. Revisions and timestamps are separate metadata; prohibit collisions across operator and statistical scopes.", "registry_links": [ "vr.wm-flw-001", "Legacy F1 / world.energy is a migration input, not a conformance authority" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve raw values, original units, original profile signs and source revisions alongside derived values", "Bind every derived value to immutable inputs, method and profile version; never infer missing values as zero", "A local accepted instance revision does not promote this research specification to canonical" ], "patch_rules": [ "Use explicit expected-revision checks, correction reason, actor and evidence; corrections create successor revisions", "Changes of perimeter, calorific basis or accounting convention invalidate affected calculations and projections" ], "compatibility_rules": [ "Schema-compatible fields can still be semantically incompatible when profile, basis or interval changes", "Do not merge territorial statistics and operating grid data without an evidenced transformation; retain unmapped terms" ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "UUID or ULID assigned by the adopting Dimension" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; distinguish event or interval time from observation and ingestion time. Preserve source timezone and endpoint convention; ambiguous time stays unresolved.", "serial_naming_rule": "Stable artifact ID plus explicit revision; export names may include sequence and display date but neither is sole identity.", "integrity_rule": "Digest each released revision and retain origin, derivation and correction lineage. A digest proves byte identity, not measurement truth or authority." }, "policies": [ "Maintain a strict information-only boundary: no asset dispatch, disconnection, plant control or market execution", "Minimize fine-grained consumption and infrastructure exposure; authorize each recipient and purpose before projection", "Document scientific and statistical assumptions, missing coverage and uncertainty; do not disguise residuals as losses", "Hazardous or controlled subjects remain at policy level with qualified external references; no operational instructions", "Independent review, source/version checks, adoption profiles and executable conformance remain open holds" ], "crud": { "read": [ "Resolve account revision and access grant; return source and profile limitations with each view" ], "create": [ "Create a draft only after account identity, boundary, interval and authority are present; optional candidate fields do not relax profile prerequisites" ], "update": [ "Create a revision with evidence, reason and concurrency check; preserve or lawfully dispose prior payload according to policy" ], "delete": [ "Adopting-Dimension retention and disposition authority executes deletion of local account payloads after holds and downstream dependencies are checked", "Retain only policy-permitted minimal tombstones and reference continuity; deletion never erases external meter, asset, settlement or audit masters and is not a physical reversal" ] }, "roles": [ { "name": "Account steward", "responsibilities": [ "Defines account boundary, profile and delegated roles" ] }, { "name": "Observation custodian", "responsibilities": [ "Maintains source identity and quality evidence; owns no external account approval" ] }, { "name": "Account analyst", "responsibilities": [ "Proposes conversions, allocations and residual assessments without control authority" ] }, { "name": "Independent account reviewer", "responsibilities": [ "Reviews local revisions and unresolved discrepancies; a proposed operational role, not a claim of independent research review" ] }, { "name": "Access and records custodian", "responsibilities": [ "Applies recipient grants, retention, holds and lawful disposition through Dimension policy" ] } ], "access": { "default_rule": "Deny by default; authorize by owner delegation, purpose, revision and field scope. An aggregate is not automatically safe for public release.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency access requires an externally authorized bounded grant, expiry and subsequent review; it never implies actuation permission", "A public statistical profile can authorize a reviewed aggregate without releasing underlying household observations" ], "audit_requirements": [ "Record accesses, approval evidence, conversion inputs and correction reasons through the external audit service", "Protect audit metadata and logs under their own retention policy; local digest and event references do not replace an audit master" ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md", "spec.yaml research assurance and scope", "Adopting Dimension ownership and policy package", "Pinned accounting and exchange profiles", "External master references before local changes" ] } }, "coverage": { "claim": "Source-grounded proposed energy-account structure with explicit carrier, boundary, period and accounting-profile semantics. The separate frozen no-tools local self-audit found no critical conflicts. Independent review, source/version verification, adoption profiles and executable conformance remain holds. This is a noncanonical reviewable draft, not a universal balance engine or control authority.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Account, boundary, point, source and artifact identities are distinct" }, { "dimension": "lifecycle", "status": "covered", "notes": "Local revision, review, closure and withdrawal are defined as proposed states" }, { "dimension": "relationships", "status": "covered", "notes": "External masters remain references; no registry relation rows exist for this model" }, { "dimension": "temporal", "status": "covered", "notes": "Intervals, endpoints, observations, ingestion, clock ambiguity and profile validity are explicit" }, { "dimension": "provenance", "status": "covered", "notes": "Raw values, derivations, source revisions and correction evidence retained" }, { "dimension": "ownership", "status": "covered", "notes": "Generic steward and custodial roles; identity does not imply operating authority" }, { "dimension": "validation", "status": "covered", "notes": "Dimension, coverage, profile and residual checks proposed; executable engine absent" }, { "dimension": "access", "status": "covered", "notes": "Purpose-bound, scoped projections and restricted evidence" }, { "dimension": "retention and deletion", "status": "covered", "notes": "Dimension authority owns disposal with holds and minimal lawful tombstones" }, { "dimension": "interoperability", "status": "gap", "notes": "Only conceptual alignments; exact versioned bindings and fixtures required" }, { "dimension": "direct properties", "status": "covered", "notes": "Carrier, quantity, basis, time, quality and state are explicit; account is informational" }, { "dimension": "recognition and observation", "status": "covered", "notes": "Source and channel references plus evidence quality distinguish measured and modeled assertions" }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Six local record operations with preconditions and refusal results; actuation excluded" }, { "dimension": "source verification", "status": "gap", "notes": "Selected browser evidence only; direct HTTP unattempted under reported sandbox restriction" }, { "dimension": "independent review", "status": "gap", "notes": "Claude and Grok skipped; separate local no-tools self-audit does not restore independent review" } ], "known_omissions": [ "Executable instance schemas, conditional field constraints, full quantity types and acceptance fixtures remain to be designed", "Licensed IEC clauses, exact CIM bindings, EIC and meter protocol profiles were not verified; no blanket alignment to entire standard families", "Sector and jurisdiction profiles for district heat, hydrogen, fuel mixtures, off-grid systems, cogeneration and reserve policy need expert review", "No network power-flow, frequency stability, exergy, plant engineering, forecasting engine, dispatch or settlement implementation", "No actual meter, operator or private infrastructure records were accessed" ], "conflicts": [], "regional_assumptions": [ "IRES is statistical guidance; US EIA-930 is an example electricity reporting profile and is not imposed globally", "National market identifiers, legal retention, operator authority and timezone rules require adoption-specific review", "Legacy and supplement inputs are unreviewed leads; their mandatory money, universal continuous-consumption and blanket conformance implications are rejected" ], "adversarial_checks": [ "Test that MW cannot be silently added to MWh, and mass/volume cannot become energy without a qualified factor", "Keep physical transformation distinct from unit normalization; heat-pump performance is not mislabeled fuel efficiency", "Do not count charging twice when importing a net-generation storage convention; stock build signs remain profile-bound", "Do not turn missing observations into zero or use a schedule as proof of actual delivery", "Do not treat a zero residual as measurement truth, operating safety or financial finality", "Preserve correction lineage without mandating perpetual personal-data retention" ] }, "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": "aggregate", "status": "accepted", "rationale": "The root owns a coherent set of account-specific quantity assertions, derivations and balance revisions under one perimeter, interval and profile. It is neither a physical energy object nor an asset inventory. The registry standalone-mm value is a record-plane classification. The local word account does not assert conformance to an external national-account framework." }, "decisions": [ { "concept": "Account root and identity", "disposition": "accepted", "rationale": "The declared perimeter, interval, profile and steward make a stable informational root. Revisions own local assertions while source, point and asset identities remain distinct. This reconciles legacy balance concerns without pretending to model energy as one physical entity." }, { "concept": "Territorial and operating boundaries", "disposition": "qualified", "rationale": "The proposal does not treat parcel location, organizational ownership, statistical territory and physical grid connectivity as interchangeable. Profile-bound membership and explicit gaps allow each to be represented without a universal perimeter rule." }, { "concept": "Carrier, source and technology", "disposition": "separated", "rationale": "The classification questions distinguish these roles and preserve code versions and unmapped terms. Carrier classification cannot prove renewable ownership or an emissions claim. No universal identifier scheme is inferred from the supplement." }, { "concept": "Unit normalization and physical conversion", "disposition": "separated", "rationale": "The quantity questions retain dimensional kind, calorific basis, conditions, method and raw value. Transformation is a separate linked assertion; a unit conversion never changes a physical carrier. Stored raw values make rounding compatible with traceability." }, { "concept": "Source-specific unit representation", "disposition": "deferred to binding review", "rationale": "The frozen source review exposes the EIA-930 wording difference between hourly integrated megawatts and MWh examples. The result imports no numeric dataset or executable EIA binding, so the unresolved representation is a source/profile hold rather than a contradiction in a deployed calculation." }, { "concept": "Observation quality and demand", "disposition": "accepted", "rationale": "Meter, channel, point, observation and revision remain distinct. Actual, estimated, substituted, missing and forecast values retain their labels. Coverage, cumulative reset evidence and overlap questions prevent silent zero-filling and duplicated measurement/profile contributions." }, { "concept": "Production and transformation ratios", "disposition": "qualified", "rationale": "Asset capacity and availability are references rather than evidence of delivered energy. Ratios require a numerator, denominator, boundary and basis; ambient terms and coproduct allocation remain visible exceptions. No universal efficiency ceiling or plant operation is asserted." }, { "concept": "Storage and reserves", "disposition": "separated", "rationale": "Stocks, stock changes, charging, discharging, deliverable energy and power limits are not interchangeable. Imported profile netting must not count charging twice. Strategic stock and operating commitment claims require external evidence instead of being inferred from a stored quantity." }, { "concept": "Interchange and commercial liability", "disposition": "separated", "rationale": "Both endpoints, directions, source revisions and sign conventions are elicited. Measured flow does not establish a schedule, contract or liability, and mismatched reports remain unresolved evidence rather than a forced agreement." }, { "concept": "Residual, physical loss and finality", "disposition": "separated", "rationale": "The balance finding requires a pinned signed equation and exact term membership. Unknowns and discrepancies remain visible. A residual is not automatically a loss, and local review or closure cannot certify grid safety, measurement truth or financial settlement." }, { "concept": "Legacy composition and absent registry relations", "disposition": "qualified", "rationale": "The frozen relation ledger contains no rows for this model. Named targets are openly unpinned candidates. Optional settlement reference replaces legacy mandatory money composition; assets, organizations, parcels and emission calculations keep their own masters." }, { "concept": "Functions and operational authority", "disposition": "accepted as proposed only", "rationale": "All six functions are bounded local record operations with authority and concurrency preconditions, refusal outputs and limited effects. None dispatches, disconnects, changes upstream source records, settles money or transmits a release automatically." }, { "concept": "Artifact identity, access and retention", "disposition": "accepted with policy dependency", "rationale": "Master identifiers outrank timestamps; revisions and integrity evidence remain separate. Recipient-specific projections require grants and disclosure assessment. Revision continuity does not require perpetual personal-data retention; Dimension policy owns disposal and lawful minimal tombstones." }, { "concept": "Optional candidates and conformance", "disposition": "deferred", "rationale": "Candidate field types, cardinalities and conceptual standards alignments are research design. They are insufficient for executable instance validation, complete nested schemas or external conformance. The acceptance-design table is a proposed case set, not a passed runtime test suite." }, { "concept": "Source support and independent review", "disposition": "limited and held", "rationale": "Eight primary references support selected concepts, with public abstract limits for IEC and the cybersecurity report. Direct HTTP was not attempted and no status was measured. No external provider result exists; this frozen local self-audit cannot claim provider agreement or independent external review." } ], "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.", "Live source and version verification remains incomplete. Direct HTTP was not attempted under the owner-reported sandbox restriction: zero attempts, zero measured responses, null source statuses. Selected browser evidence is documented; IEC and NIST cybersecurity evidence is limited to public abstracts. The coordinator checker is prepared but has not run.", "Adopting sector and jurisdiction profiles must verify perimeter membership, time intervals, unit representation, calorific basis, stock signs, storage netting, transformation ratios, reserve authority and disclosure/retention rules. EIA-930 hourly integrated MW wording versus MWh examples requires explicit binding review. No physical-operation, settlement, safety or regulatory compliance claim is made.", "Nested instance schemas, conditional field requirements, pinned neighbor identifiers, exact IRES/IEC/PROV mappings and executable conformance remain incomplete. Proposed acceptance cases have not been run against a runtime energy engine. Licensed standard clauses require separate access and review.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Coordinator to run check_sources.py outside the sandbox, then independently review claim support, source revisions and applicability rather than equating HTTP success with verification.", "Design and review sector-specific accounting profiles for statistical and operating contexts, resolving source-specific quantity representations and storage/sign mappings.", "Specify nested schemas and pinned master bindings and exercise the proposed adversarial cases, including repeated hours, mixed calorific bases, cumulative resets, storage netting and corrected closed accounts.", "Restore independent external provider review before any canonical or publishable-draft promotion." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }