{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-flw-002","code":"wm-flw-002-water-supply","url":"https://ver.cy/models/wm-flw-002-water-supply/","name":"Water Supply","alternateNames":["F4"],"kind":"world-model","status":"published","version":"0.1.0","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"aggregate","plane":"","domain":["PHY.FLW.H2O"],"industry":["Cross-industry"],"navPath":"NAV.PHY.FLW.H2O","tags":["water","supply","phy.flw.h2o"],"facets":{}},"whatItIs":"One declared supply-system aggregate links independently mastered sources, facilities, zones and delivery points across an effective period. Drinking-water service is the core profile; nonpotable use must carry an explicit separate profile. The aggregate owns supply-specific assertions and evidence references, not the assets, water bodies, regulator, laboratory or physical controls.","purpose":"Describe a governed water supply system and its evidence of source, treatment, delivery, quality and continuity.","scope":{"in":["System identity, service area, intended use, accountable roles and responsibility interfaces","Source and abstraction evidence, treatment assurance, monitoring and quality assessment references","Time-qualified distribution, storage, supply quantity, continuity and authorized communication records"],"out":["Food production, agricultural lots, food processing, cold chains and food recalls belong to WM-FLW-003","Water body hydrology, land and asset master lifecycles, energy dispatch, generic consignment custody, wastewater and residuals processing","Engineering design, treatment dosing, network actuation, emergency command, public notice issuance, billing and legal compliance certification"],"boundaries":[{"neighbor":"Legacy F4 and WM-FLW-003 Food Supply Chain","distinction":"F4 mixed water and food. Retain only water supply concerns. Do not require a batch for continuous flow or retain agriculture and cold-chain layers. The unreviewed supplement repeats this scope leakage and is not evidence."},{"neighbor":"WM-PLC-003 Water Body and WM-PLC-002 Land Parcel","distinction":"Reference catchments, water bodies and locations; keep hydrologic behavior, rights registers and parcel identity externally mastered."},{"neighbor":"WM-FLW-004 Goods Movement / Logistics and WM-FLW-001 Energy","distinction":"Optional delivery and energy dependency references do not imply generic logistics inheritance for a continuous pipe network."},{"neighbor":"Premise plumbing, wastewater and treatment assets","distinction":"Record the point of supply separately from the compliance point and consumer tap. Link premise responsibilities and residual handoffs without taking ownership of those systems."}]},"distinguishingFeatures":["Unlike Legacy F4 and WM-FLW-003 Food Supply Chain: F4 mixed water and food. Retain only water supply concerns. Do not require a batch for continuous flow or retain agriculture and cold-chain layers. The unreviewed supplement repeats this scope leakage and is not evidence.","Unlike WM-PLC-003 Water Body and WM-PLC-002 Land Parcel: Reference catchments, water bodies and locations; keep hydrologic behavior, rights registers and parcel identity externally mastered.","Unlike WM-FLW-004 Goods Movement / Logistics and WM-FLW-001 Energy: Optional delivery and energy dependency references do not imply generic logistics inheritance for a continuous pipe network.","Unlike Premise plumbing, wastewater and treatment assets: Record the point of supply separately from the compliance point and consumer tap. Link premise responsibilities and residual handoffs without taking ownership of those systems."],"structure":{"bundles":[{"id":"bundle-boundary","name":"Supply identity and responsibility","description":"Define the system, use profile and accountable interfaces.","layers":[{"id":"layer-identity","name":"System identity and service boundary","description":"Proposed aggregate boundary ties a service area and intended use to time-qualified member references; membership does not transfer asset ownership.","findings":[{"id":"finding-identity","name":"System identity and service boundary","description":"Proposed aggregate boundary ties a service area and intended use to time-qualified member references; membership does not transfer asset ownership.","questions":[{"text":"Which master identifier and aliases identify this supply system across renaming or operator change?","id":"q-identity-1","kind":"identity"},{"text":"Which intended uses and delivery modes define the service profile and its exclusions?","id":"q-identity-2","kind":"classification"},{"text":"What service-area geometry and effective dates determine the included zones and delivery points?","id":"q-identity-3","kind":"spatial"}]}]},{"id":"layer-authority","name":"Responsibility and applicable profile","description":"Responsibility, regulatory applicability and data stewardship are distinct assertions. A supplier handoff need not coincide with a legal compliance location.","findings":[{"id":"finding-authority","name":"Responsibility and applicable profile","description":"Responsibility, regulatory applicability and data stewardship are distinct assertions. A supplier handoff need not coincide with a legal compliance location.","questions":[{"text":"Which role stewards each segment and evidence record without assuming ownership of every linked asset?","id":"q-authority-1","kind":"ownership"},{"text":"Which jurisdiction, competent authority and versioned rules govern this use and supply size?","id":"q-authority-2","kind":"authority"},{"text":"Where do supplier responsibility, premise responsibility and compliance-point boundaries differ?","id":"q-authority-3","kind":"relationship"}]}]}]},{"id":"bundle-source","name":"Sources and resource availability","description":"Connect source context to recorded abstractions and supply availability.","layers":[{"id":"layer-origin","name":"Source context and protection","description":"Source context references catchment and raw-water risk evidence. This model does not calculate hydrology or grant abstraction rights.","findings":[{"id":"finding-origin","name":"Source context and protection","description":"Source context references catchment and raw-water risk evidence. This model does not calculate hydrology or grant abstraction rights.","questions":[{"text":"Which water bodies, intakes or bulk suppliers contribute to this system and during which periods?","id":"q-origin-1","kind":"composition"},{"text":"Which catchment assessment and protection records support the identified source risks?","id":"q-origin-2","kind":"evidence"},{"text":"How are source substitution and blending changes recorded when provenance is incomplete?","id":"q-origin-3","kind":"exception"}]}]},{"id":"layer-quantity","name":"Abstraction and availability evidence","description":"Record permitted, measured and estimated quantities distinctly. A capacity figure does not establish sustainable yield or a right to abstract.","findings":[{"id":"finding-quantity","name":"Abstraction and availability evidence","description":"Record permitted, measured and estimated quantities distinctly. A capacity figure does not establish sustainable yield or a right to abstract.","questions":[{"text":"Which permit or supply agreement, if applicable, constrains abstraction for the recorded interval?","id":"q-quantity-1","kind":"requirement"},{"text":"What volume or flow was measured or estimated at each intake with units and uncertainty?","id":"q-quantity-2","kind":"measurement"},{"text":"Which seasonal, drought or dependency assumptions limit the stated available capacity?","id":"q-quantity-3","kind":"constraint"}]}]}]},{"id":"bundle-assurance","name":"Treatment and risk assurance","description":"Separate preventive assurance plans from evidence of actual control performance.","layers":[{"id":"layer-risk","name":"Risk and improvement context","description":"Maintain local links between hazards, control evidence, review decisions and improvement actions; no technical threat procedures or universal scoring scheme.","findings":[{"id":"finding-risk","name":"Risk and improvement context","description":"Maintain local links between hazards, control evidence, review decisions and improvement actions; no technical threat procedures or universal scoring scheme.","questions":[{"text":"Which hazard categories and hazardous events are covered by the current supply risk assessment?","id":"q-risk-1","kind":"quality"},{"text":"Who accepted the residual-risk assessment and prioritized improvements using which method?","id":"q-risk-2","kind":"decision"},{"text":"What changes or review triggers require the safety plan and improvement register to be reconsidered?","id":"q-risk-3","kind":"lifecycle"}]}]},{"id":"layer-treatment","name":"Treatment assurance and operational monitoring","description":"Link externally mastered treatment stages and their authorized operating envelopes to monitoring records. Monitoring completion does not certify all delivered water.","findings":[{"id":"finding-treatment","name":"Treatment assurance and operational monitoring","description":"Link externally mastered treatment stages and their authorized operating envelopes to monitoring records. Monitoring completion does not certify all delivered water.","questions":[{"text":"Which treatment stages and control measures apply to this water stream or identified delivered lot?","id":"q-treatment-1","kind":"process"},{"text":"What evidence validates each claimed control measure under its stated conditions?","id":"q-treatment-2","kind":"validation"},{"text":"Which operational deviations were observed and which authorized corrective-action records address them?","id":"q-treatment-3","kind":"event"}]}]}]},{"id":"bundle-quality","name":"Observations and quality interpretation","description":"Preserve sampling provenance and constrain what a quality assessment can establish.","layers":[{"id":"layer-observation","name":"Sampling and observation context","description":"Observation identity and target must survive correction. A sample applies to its declared location, time and method, not automatically the entire supply.","findings":[{"id":"finding-observation","name":"Sampling and observation context","description":"Observation identity and target must survive correction. A sample applies to its declared location, time and method, not automatically the entire supply.","questions":[{"text":"Which sample or sensor observation, collection method and laboratory or instrument produced this result?","id":"q-observation-1","kind":"provenance"},{"text":"How do collection time, phenomenon interval, result time and ingestion time differ?","id":"q-observation-2","kind":"temporal"},{"text":"Which property, location, value, unit, detection qualifier and uncertainty describe the result?","id":"q-observation-3","kind":"measurement"}]}]},{"id":"layer-assessment","name":"Quality assessment and limits","description":"An authored assessment links observations to the applicable versioned rule and comparison method. Unknown, pending and invalid inputs cannot silently become passing results.","findings":[{"id":"finding-assessment","name":"Quality assessment and limits","description":"An authored assessment links observations to the applicable versioned rule and comparison method. Unknown, pending and invalid inputs cannot silently become passing results.","questions":[{"text":"Which parameter rule, sampling plan and compliance location apply to this assessment?","id":"q-assessment-1","kind":"requirement"},{"text":"Were units, method suitability, sample coverage and censored results sufficient for the stated comparison?","id":"q-assessment-2","kind":"validation"},{"text":"What assessment status and competent review evidence distinguish an exceedance flag from a safety determination?","id":"q-assessment-3","kind":"state"}]}]}]},{"id":"bundle-delivery","name":"Distribution and storage","description":"Time-qualified network and storage assertions describe delivery without inventing complete physical traceability.","layers":[{"id":"layer-network","name":"Network connectivity and delivery context","description":"Topology, pressure and delivery evidence have separate time and confidence. Continuous-flow mixing makes exact lot-to-tap attribution an unsupported default.","findings":[{"id":"finding-network","name":"Network connectivity and delivery context","description":"Topology, pressure and delivery evidence have separate time and confidence. Continuous-flow mixing makes exact lot-to-tap attribution an unsupported default.","questions":[{"text":"Which active network links, bulk interfaces and endpoints define the delivery path for the interval?","id":"q-network-1","kind":"relationship"},{"text":"Which pressure, flow and delivered-volume observations support the claimed service state?","id":"q-network-2","kind":"measurement"},{"text":"Which simulated source fractions or water-age estimates are used and how are assumptions and calibration identified?","id":"q-network-3","kind":"interoperability"}]}]},{"id":"layer-storage","name":"Storage and distribution integrity","description":"Quantity and quality availability are separate. Reserve volume can be unavailable for supply because of restrictions or uncertain quality.","findings":[{"id":"finding-storage","name":"Storage and distribution integrity","description":"Quantity and quality availability are separate. Reserve volume can be unavailable for supply because of restrictions or uncertain quality.","questions":[{"text":"What observed storage level and usable volume are supported by tank geometry, units and observation time?","id":"q-storage-1","kind":"measurement"},{"text":"Which inspection, maintenance and distribution-integrity records qualify the storage or network state?","id":"q-storage-2","kind":"quality"},{"text":"Which reserve, isolation or quality restrictions limit the amount considered available for delivery?","id":"q-storage-3","kind":"constraint"}]}]}]},{"id":"bundle-continuity","name":"Continuity and communication","description":"Describe service disruption and approved communication with privacy and safety controls.","layers":[{"id":"layer-continuity","name":"Disruptions and recovery evidence","description":"Record interruption scope and resilience dependencies at policy level. Local record state cannot restart a system or authorize an allocation.","findings":[{"id":"finding-continuity","name":"Disruptions and recovery evidence","description":"Record interruption scope and resilience dependencies at policy level. Local record state cannot restart a system or authorize an allocation.","questions":[{"text":"Which planned or unplanned interruption affected which service area and interval?","id":"q-continuity-1","kind":"event"},{"text":"What demand, reserve, power and alternative-supply assumptions support the continuity estimate?","id":"q-continuity-2","kind":"constraint"},{"text":"Which authorized recovery decision and verification evidence distinguish restored service from a closed work order?","id":"q-continuity-3","kind":"lifecycle"}]}]},{"id":"layer-communication","name":"Notices, access and record continuity","description":"Link approved advisories and their scope without autonomously issuing them. Preserve correction lineage while obeying adopted retention and privacy rules.","findings":[{"id":"finding-communication","name":"Notices, access and record continuity","description":"Link approved advisories and their scope without autonomously issuing them. Preserve correction lineage while obeying adopted retention and privacy rules.","questions":[{"text":"Which competent role approved the notice, restriction or lifting decision for the affected area?","id":"q-communication-1","kind":"authority"},{"text":"Which public summary and restricted evidence views serve recipients without disclosing sensitive network or household details?","id":"q-communication-2","kind":"access"},{"text":"Which record schedule and hold govern correction, archival transfer or lawful payload disposal?","id":"q-communication-3","kind":"retention"}]}]}]}]},"agentConduct":{"may":["Register supply boundary: Proposed local operation records a versioned system boundary and external master references.","Link qualified observation: Proposed local operation attaches evidence without changing a laboratory or sensor master record.","Record scoped assessment: Proposed local operation records a reviewed comparison and flags unknown inputs; it does not determine potability.","Record delivery scenario: Proposed local operation links a supplied simulation result; it does not run hydraulic calculations or operate equipment.","Record continuity event: Proposed local operation links interruption and recovery evidence without executing response actions.","Prepare authorized evidence view: Proposed local operation prepares a locally reviewable summary with approved notice links; it does not send or publish a notice."],"mustNot":["Treat public health restrictions and control changes as externally authorized decisions; local functions cannot issue notices or actuate systems.","Deny detailed infrastructure and personal-data access unless authorized by purpose and role; release only approved public views."],"requiresHuman":[]},"ethics":{"considerations":["Use minimum necessary personal data, scoped infrastructure access and approved public views."],"affectedParties":[]},"owners":{"steward":"A generic supply-system steward role owns local assertion namespaces and declares external master systems.","roles":[{"name":"Supply-system steward","responsibilities":["Own local assertion quality, namespace and interface references."]},{"name":"Water quality reviewer","responsibilities":["Review sampling context, rule applicability and assessment limits."]},{"name":"Authorized operator","responsibilities":["Supply evidence of treatment and service events; physical controls stay in separately authorized systems."]},{"name":"Competent oversight role","responsibilities":["Provide applicable decisions, review duties and authorized notice references."]},{"name":"Records and access custodian","responsibilities":["Maintain scoped access, lawful retention and disposal evidence."]}],"masterSystems":[]},"relations":[{"target":"WM-FLW-003","type":"references","note":"Food supply is a separate successor to F4. Link water supplied to a food facility without copying food lots or safety processes."},{"target":"WM-PLC-003","type":"references","note":"Water body and catchment context remains externally mastered."},{"target":"WM-PLC-002","type":"references","note":"Use location and parcel references without parcel lifecycle ownership."},{"target":"WM-FLW-004","type":"references","note":"Optional tanker or packaged-water consignment linkage; custody remains in logistics."},{"target":"WM-FLW-001","type":"references","note":"Record pumping or treatment energy dependency references without dispatch control."},{"target":"OGC SensorThings API Part 1: Sensing 1.1","type":"aligned","note":"Conceptual observation mapping only; executable bindings and conformance tests deferred."},{"target":"PROV-O","type":"aligned","note":"Conceptual evidence attribution and derivation mapping; no ownership inference."},{"target":"EPANET 2.2","type":"aligned","note":"Optional simulation evidence interface, not a required runtime or sensor source."},{"target":"Legacy F4 and WM-FLW-003 Food Supply Chain","type":"neighbor","note":"F4 mixed water and food. Retain only water supply concerns. Do not require a batch for continuous flow or retain agriculture and cold-chain layers. The unreviewed supplement repeats this scope leakage and is not evidence."},{"target":"WM-PLC-003 Water Body and WM-PLC-002 Land Parcel","type":"neighbor","note":"Reference catchments, water bodies and locations; keep hydrologic behavior, rights registers and parcel identity externally mastered."},{"target":"WM-FLW-004 Goods Movement / Logistics and WM-FLW-001 Energy","type":"neighbor","note":"Optional delivery and energy dependency references do not imply generic logistics inheritance for a continuous pipe network."},{"target":"Premise plumbing, wastewater and treatment assets","type":"neighbor","note":"Record the point of supply separately from the compliance point and consumer tap. Link premise responsibilities and residual handoffs without taking ownership of those systems."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier","Governed global identifier or IRI","UUID or ULID assigned by the adopting Dimension"]},"properties":{"applicability":"required","items":[]},"recognition":{"applicability":"required","items":[]},"capabilities":{"applicability":"required","items":["Register supply boundary: Proposed local operation records a versioned system boundary and external master references.","Link qualified observation: Proposed local operation attaches evidence without changing a laboratory or sensor master record.","Record scoped assessment: Proposed local operation records a reviewed comparison and flags unknown inputs; it does not determine potability.","Record delivery scenario: Proposed local operation links a supplied simulation result; it does not run hydraulic calculations or operate equipment.","Record continuity event: Proposed local operation links interruption and recovery evidence without executing response actions.","Prepare authorized evidence view: Proposed local operation prepares a locally reviewable summary with approved notice links; it does not send or publish a notice."]},"hazards":{"applicability":"required","items":[]},"interfaces":{"applicability":"required","items":["OGC SensorThings API Part 1: Sensing Version 1.1","PROV-O: The PROV Ontology"]},"context":{"applicability":"required","items":["WHO material is guidance; the 2022 overview is a pinned historical source, and later addenda/corrigenda are not incorporated.","The original EU directive is an illustrative framework, not verified current national law. No numerical limit, deadline or exemption is generalized."]}},"sources":[{"title":"Water safety plan manual, second edition","url":"https://www.who.int/publications/i/item/9789240067691","note":"World Health Organization"},{"title":"Guidelines for drinking-water quality, fourth edition incorporating the first and second addenda","url":"https://www.who.int/publications/i/item/9789240045064","note":"World Health Organization"},{"title":"Directive (EU) 2020/2184 on the quality of water intended for human consumption","url":"https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX%3A32020L2184","note":"European Union"},{"title":"Drinking Water Distribution System Tools and Resources","url":"https://www.epa.gov/dwreginfo/drinking-water-distribution-system-tools-and-resources","note":"United States Environmental Protection Agency"},{"title":"EPANET","url":"https://www.epa.gov/water-research/epanet","note":"United States Environmental Protection Agency"},{"title":"OGC SensorThings API Part 1: Sensing Version 1.1","url":"https://docs.ogc.org/is/18-088/18-088.html","note":"Open Geospatial Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"Internet Engineering Task Force"}],"openQuestions":["Verify source availability, current editions, corrigenda, legal applicability and specialized water-supply profiles without promoting HTTP success into substantive verification.","Develop nested schemas and test mixed sources, stale/censored observations, incompatible units, boundary handoffs, unavailable reserves, unauthorized recovery and lawful disposal.","Restore independent external review before canonical or publishable-draft promotion.","Independent external review and complete live source/version verification.","Nested instance schemas, unit/CRS code lists, profile fixtures, binding implementations and conformance tests.","Small private supplies, rainwater, desalination, reuse, nonpotable service, bottled-water trade and emergency delivery require specialized profiles.","Tariffs, billing, asset engineering, process design, hydrology, detailed leakage accounting and wastewater operations are delegated."],"resources":{"spec":"/models/wm-flw-002-water-supply/spec.yaml","agents":"/models/wm-flw-002-water-supply/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-002"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-flw-002-water-supply/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-06T20:38:19Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"derived","structure":"filled","agentConduct":"derived","ethics":"derived","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"missing","interaction.recognition":"missing","interaction.capabilities":"filled","interaction.hazards":"missing","interaction.interfaces":"derived","interaction.context":"filled","sources":"filled"},"notes":{"distinguishingFeatures":"Derived from boundary notes against neighbouring models.","agentConduct":"Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.","ethics":"Sentences mentioning harm, privacy, consent or similar, collected from the specification."},"score":0.706}}