# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T20:44:41Z", "synthesisSha256": "8b9be3d265cbb3b8e1f91e1fe5aa0026a74801408bc6e86e0b5004003cc632d5", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-FLW-005", "registryId": "vr.wm-flw-005", "name": "Waste / Circular", "version": "0.1.0-reviewable-draft", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.FLW.WST" ], "tags": [ "waste", "circular", "phy.flw.wst" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-flw-005-waste-circular/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-005", "model": { "registry_id": "vr.wm-flw-005", "model_id": "WM-FLW-005", "name": "Waste / Circular", "entry_kind": "aggregate", "purpose": "Represent a bounded waste-flow account with material lineage, qualified waste status, custody evidence and substantiated recovery or disposal outcomes.", "scope_statement": "One aggregate is an accountable waste-flow dossier anchored to an identified arising lot or an explicitly bounded generation cohort. It indexes local assertions about quantities, descendant lots, transfers, treatment and outcomes. Each physical lot and event retains its own identity. Cohort, period and allocation boundaries are explicit; an unbounded industry or facility is not the root. The account may remain open while outcomes or legal status are unknown.", "in_scope": [ "Waste-status and classification assertions, including unresolved or disputed classifications", "Arising origin, measured quantities, split and merge allocations and residual uncertainty", "Waste-specific custody, authorization and treatment evidence references", "Recovered-output status, circularity claim basis, disposal and aftercare linkage", "Local provenance, access, retention and corrective revisions" ], "out_of_scope": [ "Generic transport planning, dispatch, physical handling, treatment control or emergency response execution", "Facility, land parcel, party, permit, product and emissions master lifecycles", "Binding legal determinations, automatic export permission or certification of end-of-waste status", "Product carbon footprints, certified recycled-content claims and national official statistics production", "Operational instructions for dangerous or controlled materials; these require specialist policy profiles" ], "boundary_notes": [ { "neighbor": "WM-FLW-004 Goods Movement / Logistics", "distinction": "Candidate reference to consignment and handover masters. The legacy EXTEND is narrowed to waste-specific assertions; generic transport and custody machinery are not reimplemented.", "source_refs": [ "SRC-003", "SRC-004" ] }, { "neighbor": "WM-FLW-006 Emission", "distinction": "Releases and emission measurements have external masters. A waste-flow account can link an emitted quantity in a balance without owning emission monitoring or permitting.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "WM-PLC-002 Land Parcel and external facility master", "distinction": "Only site identifiers and disposal/aftercare evidence links belong here. Capacity, land title, equipment and site operation remain external.", "source_refs": [ "SRC-006" ] }, { "neighbor": "WM-FLW-002 Water Supply and WM-FLW-003 Food Supply Chain", "distinction": "Legacy F4 covers two successors. Record origin or destination references when relevant; neither water service nor food production is contained in this account.", "source_refs": [ "SRC-001", "SRC-008" ] }, { "neighbor": "WM-ECO-014 Sustainability Claim / PCF and product/material masters", "distinction": "Quantity allocation supports downstream claims but does not establish product recycled content, environmental benefit or a product carbon footprint. F6 alias alone cannot select a target.", "source_refs": [ "SRC-005", "SRC-007" ] }, { "neighbor": "External classifiers and legal profiles", "distinction": "Codes carry scheme, edition and jurisdiction. EU, US and Basel concepts are separate mappings, never interchangeable code values or universal legal rules.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Waste Framework Directive 2008/98/EC, consolidated text", "organization": "European Parliament and Council of the European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02008L0098-20251016", "version_or_date": "Consolidation 2025-10-16; selected Articles 2-7 reviewed; national implementation not verified", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:43:13Z", "relevance": "Waste and by-product boundaries, hierarchy, separate recovery and recycling concepts, and evidenced end-of-waste status." }, { "id": "SRC-002", "title": "Decision 2000/532/EC, List of Waste", "organization": "European Commission", "url": "https://eur-lex.europa.eu/eli/dec/2000/532/2015-06-01/eng", "version_or_date": "Consolidation 2015-06-01; Annex definitions and assessment reviewed; later amendments require checking", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:43:13Z", "relevance": "Versioned waste classification, hazardous properties and assessment evidence; list membership alone is insufficient for all status decisions." }, { "id": "SRC-003", "title": "Basel Convention, text and annexes revised in 2025", "organization": "Secretariat of the Basel Convention", "url": "https://www.basel.int/Portals/4/download.aspx?e=UNEP-CHW-IMPL-CONVTEXT-2025.English.pdf", "version_or_date": "2025 informational booklet; authentic depositary texts and party applicability remain a hold", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:43:13Z", "relevance": "Waste movement scope, participating authorities, generator and holder roles, notification and movement evidence; policy level only." }, { "id": "SRC-004", "title": "Hazardous Waste Manifest System", "organization": "United States Environmental Protection Agency", "url": "https://www.epa.gov/hwgenerators/hazardous-waste-manifest-system", "version_or_date": "Page updated 2026-05-20; federal overview with state-specific requirements", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:43:13Z", "relevance": "Manifest tracking, quantity and type, signatures and receiving-facility acknowledgement; receipt is not treatment completion." }, { "id": "SRC-005", "title": "SDG indicator 12.5.1 metadata", "organization": "United Nations Statistics Division", "url": "https://unstats.un.org/sdgs/metadata/files/Metadata-12-05-01.pdf", "version_or_date": "Metadata updated 2024-05-24, format 1.1", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:43:13Z", "relevance": "Recycling metrics require reporting boundary, denominator, trade adjustments, loss treatment and attention to informal flows; a national rate is not product recycled content." }, { "id": "SRC-006", "title": "Council Directive 1999/31/EC on landfill of waste", "organization": "Council of the European Union", "url": "https://eur-lex.europa.eu/eli/dir/1999/31/oj/eng", "version_or_date": "Original act 1999-04-26; Articles 12-13 reviewed; current consolidated implementation unverified", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:43:13Z", "relevance": "Separate disposal acceptance, closure and continuing site aftercare responsibilities; monitoring is referenced without taking over facility operation." }, { "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": "Recommendation 2013-04-30; sections 3.1-3.3", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:43:13Z", "relevance": "Entities, activities, attribution, derivation and revision inform an authored lineage and evidence design; not a waste compliance standard." }, { "id": "SRC-008", "title": "Waste Framework Directive overview", "organization": "European Commission", "url": "https://environment.ec.europa.eu/topics/waste-and-recycling/waste-framework-directive_en", "version_or_date": "Undated living page accessed 2026-10-06; describes 2025 revision", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:43:13Z", "relevance": "Hazard-control policy, producer responsibility, prevention context and material-specific end-of-waste criteria; current implementation details remain unverified." } ], "structure": { "bundles": [ { "id": "bundle-identity", "name": "Scope and classification", "description": "Account identity and qualified waste classification.", "rationale": "Authored waste-account grouping grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-account", "name": "Account boundary", "description": "Define the accountable lot or cohort and preserve the difference between account, material lot, waste stream category, consignment and evidence document. The aggregate boundary is an authored design, not a source-mandated structure.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-account", "name": "Identified flow account", "description": "Define the accountable lot or cohort and preserve the difference between account, material lot, waste stream category, consignment and evidence document. The aggregate boundary is an authored design, not a source-mandated structure.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-account-1", "text": "Which master namespace and identifier identify this waste-flow account?", "kind": "identity", "answer_data": [ "account-identity" ] }, { "id": "q-account-2", "text": "Which arising lot or bounded cohort is included in this account?", "kind": "composition", "answer_data": [ "root-scope" ] }, { "id": "q-account-3", "text": "How are consignment, stream and document identifiers linked without equating them?", "kind": "relationship", "answer_data": [ "identity-links" ] }, { "id": "q-account-4", "text": "Who stewards each local assertion and which responsibilities remain with other parties?", "kind": "ownership", "answer_data": [ "stewardship" ] } ], "data_elements": [ { "id": "data-account-account-identity", "name": "account-identity", "description": "Master namespace, stable account ID, version and verified aliases. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-account-root-scope", "name": "root-scope", "description": "Root lot references, cohort inclusion rule, origin boundary and exclusions. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-account-identity-links", "name": "identity-links", "description": "Typed master references, mapping evidence and unresolved collisions. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-account-stewardship", "name": "stewardship", "description": "Generator, holder, processor and custodian roles with effective scope; liability basis separately reviewed. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-account", "name": "Flow identity register", "description": "Versioned local evidence index or assessment for identified flow account. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-classification", "name": "Waste classification", "description": "Record the basis for waste status and classification as separate assertions. Preserve code-list versions, hazardous-property evidence and disagreements. Labels, market value and container appearance are observations, not sufficient status determinations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "findings": [ { "id": "finding-classification", "name": "Qualified waste status", "description": "Record the basis for waste status and classification as separate assertions. Preserve code-list versions, hazardous-property evidence and disagreements. Labels, market value and container appearance are observations, not sufficient status determinations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "q-classification-1", "text": "What evidence supports waste, by-product, non-waste or unresolved status in the applicable profile?", "kind": "definition", "answer_data": [ "status-basis" ] }, { "id": "q-classification-2", "text": "Which waste scheme, edition and code apply to this material at this time?", "kind": "classification", "answer_data": [ "waste-code" ] }, { "id": "q-classification-3", "text": "Which observations or assessments support the hazardous-property classification?", "kind": "evidence", "answer_data": [ "hazard-evidence" ] }, { "id": "q-classification-4", "text": "What happens when composition evidence or competent assessments disagree?", "kind": "exception", "answer_data": [ "classification-dispute" ] } ], "data_elements": [ { "id": "data-classification-status-basis", "name": "status-basis", "description": "Status, discard/intention/requirement evidence, scope exclusions, applicable rule and assessor. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-classification-waste-code", "name": "waste-code", "description": "Scheme URI, edition, code, jurisdiction and valid interval. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-classification-hazard-evidence", "name": "hazard-evidence", "description": "Sample or assessment references, representativeness, assessor and uncertainty; no handling instructions. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-classification-classification-dispute", "name": "classification-dispute", "description": "Competing assertions, restricted-use flag, review owner and unresolved decision; no silent safe default. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-classification", "name": "Classification assessment index", "description": "Versioned local evidence index or assessment for qualified waste status. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-origin", "name": "Origin and observations", "description": "Generation, collection and measured material properties.", "rationale": "Authored waste-account grouping grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-arising", "name": "Generation and collection", "description": "Separate generation, collection and receipt. Preserve unknown origins and the bounded collection scope rather than fabricating a generator. Prevention and non-waste reuse belong to contextual programme references unless actual waste arises.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ], "findings": [ { "id": "finding-arising", "name": "Traceable origin", "description": "Separate generation, collection and receipt. Preserve unknown origins and the bounded collection scope rather than fabricating a generator. Prevention and non-waste reuse belong to contextual programme references unless actual waste arises.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "q-arising-1", "text": "Where and from which activity did the included waste arise?", "kind": "spatial", "answer_data": [ "origin" ] }, { "id": "q-arising-2", "text": "When did generation, collection and first observation occur?", "kind": "temporal", "answer_data": [ "arising-times" ] }, { "id": "q-arising-3", "text": "Which collection record connects the arising quantity to an identified receiving lot?", "kind": "process", "answer_data": [ "collection-link" ] }, { "id": "q-arising-4", "text": "Which prevention or separate-collection policy applies to this account scope?", "kind": "constraint", "answer_data": [ "prevention-context" ] } ], "data_elements": [ { "id": "data-arising-origin", "name": "origin", "description": "Generator or unknown-origin flag, source activity, site reference and location precision. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-arising-arising-times", "name": "arising-times", "description": "Separate event times or intervals, precision, timezone and recording time. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-arising-collection-link", "name": "collection-link", "description": "Collection evidence, collector reference, received lot and acceptance or rejection state. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-arising-prevention-context", "name": "prevention-context", "description": "Versioned programme or obligation reference, applicability and exceptions; no claim that prevented waste was physically handled. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-arising", "name": "Origin and collection register", "description": "Versioned local evidence index or assessment for traceable origin. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-measurement", "name": "Material observations", "description": "Retain physical state, composition, mass or volume, basis and observation quality. Do not equate wet and dry mass or convert volume to mass without a supported conversion. Unknown is distinct from zero.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-measurement", "name": "Comparable measured quantities", "description": "Retain physical state, composition, mass or volume, basis and observation quality. Do not equate wet and dry mass or convert volume to mass without a supported conversion. Unknown is distinct from zero.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007" ], "questions": [ { "id": "q-measurement-1", "text": "What quantity was measured and on which unit and material basis?", "kind": "measurement", "answer_data": [ "measured-quantity" ] }, { "id": "q-measurement-2", "text": "Which method, instrument and sampling conditions support the observation?", "kind": "quality", "answer_data": [ "measurement-quality" ] }, { "id": "q-measurement-3", "text": "What physical state and composition were observed for the lot?", "kind": "state", "answer_data": [ "material-state" ] }, { "id": "q-measurement-4", "text": "Which conversions make two observations comparable and what residual difference remains?", "kind": "validation", "answer_data": [ "quantity-comparison" ] } ], "data_elements": [ { "id": "data-measurement-measured-quantity", "name": "measured-quantity", "description": "Value, unit, gross/tare/net or wet/dry basis, measured or estimated flag and uncertainty. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "data-measurement-measurement-quality", "name": "measurement-quality", "description": "Method, instrument reference, calibration evidence, conditions, sample coverage and precision. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "data-measurement-material-state", "name": "material-state", "description": "State, constituent fractions or unknowns, contamination evidence and observation scope. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "data-measurement-quantity-comparison", "name": "quantity-comparison", "description": "Source units, conversion evidence including density if needed, harmonized basis, tolerance rule and discrepancy. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-measurement", "name": "Quantity observation register", "description": "Versioned local evidence index or assessment for comparable measured quantities. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-custody", "name": "Custody and authority", "description": "Transfer evidence and applicable authorization references.", "rationale": "Authored waste-account grouping grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-custody", "name": "Handover evidence", "description": "Index waste-specific transfer and receiving acknowledgements against external movement records. A signature can support receipt within its scope but cannot establish successful recycling or extinguish responsibility.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-custody", "name": "Qualified custody continuity", "description": "Index waste-specific transfer and receiving acknowledgements against external movement records. A signature can support receipt within its scope but cannot establish successful recycling or extinguish responsibility.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-custody-1", "text": "Which evidenced handover moved custody between identified holders?", "kind": "event", "answer_data": [ "handover" ] }, { "id": "q-custody-2", "text": "What was actually acknowledged by the receiving facility?", "kind": "evidence", "answer_data": [ "receipt" ] }, { "id": "q-custody-3", "text": "Where does the recorded custody chain have a gap or inconsistent quantity?", "kind": "quality", "answer_data": [ "chain-gap" ] }, { "id": "q-custody-4", "text": "Which record distinguishes custody, title and responsibility for this transfer?", "kind": "authority", "answer_data": [ "transfer-responsibility" ] } ], "data_elements": [ { "id": "data-custody-handover", "name": "handover", "description": "Movement master, releasing and receiving roles, time, location and evidence reference. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-custody-receipt", "name": "receipt", "description": "Received quantity and condition, signature scope, rejection or partial acceptance and receipt time. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-custody-chain-gap", "name": "chain-gap", "description": "Missing acknowledgement, inconsistent lot or time, disputed amounts and review state. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-custody-transfer-responsibility", "name": "transfer-responsibility", "description": "Profile and role evidence for each concept; no automatic liability transfer. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-custody", "name": "Custody evidence index", "description": "Versioned local evidence index or assessment for qualified custody continuity. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-authorization", "name": "Authority and restrictions", "description": "Keep applicable facility permissions, shipment consent and restrictions as separate referenced assertions. Planned movement, a notification ID or a software status is not permission. Controlled or dangerous streams remain at policy and evidence level.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "findings": [ { "id": "finding-authorization", "name": "Applicable authorization evidence", "description": "Keep applicable facility permissions, shipment consent and restrictions as separate referenced assertions. Planned movement, a notification ID or a software status is not permission. Controlled or dangerous streams remain at policy and evidence level.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "q-authorization-1", "text": "Which authority and permit evidence cover the recipient, waste category and relevant date?", "kind": "authority", "answer_data": [ "permit-scope" ] }, { "id": "q-authorization-2", "text": "Which export, import and transit rules and consent evidence apply to the proposed movement?", "kind": "requirement", "answer_data": [ "shipment-profile" ] }, { "id": "q-authorization-3", "text": "Which policy restrictions limit access or further action for this material?", "kind": "security", "answer_data": [ "restricted-policy" ] }, { "id": "q-authorization-4", "text": "How are expiry, refusal, suspected misclassification or reported incidents represented?", "kind": "exception", "answer_data": [ "authorization-exception" ] } ], "data_elements": [ { "id": "data-authorization-permit-scope", "name": "permit-scope", "description": "Authority master, permit revision, covered site and codes, validity interval and unresolved applicability. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-authorization-shipment-profile", "name": "shipment-profile", "description": "States and competent authorities, profile editions, notification and consent references, restrictions or not-applicable rationale. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-authorization-restricted-policy", "name": "restricted-policy", "description": "Hazard and controlled-material policy, authorized reviewer and escalation reference; no operational procedure. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-authorization-authorization-exception", "name": "authorization-exception", "description": "Exception evidence, review owner, local hold and external incident master reference. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-authorization", "name": "Authorization evidence register", "description": "Versioned local evidence index or assessment for applicable authorization evidence. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-transformation", "name": "Treatment and lineage", "description": "Treatment assertions, allocations, residues and material balance.", "rationale": "Authored waste-account grouping grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-treatment", "name": "Treatment linkage", "description": "Record the operation actually evidenced, distinguishing planned, accepted, started and completed states and intermediate from final processing. Refer to external facility/process masters; this model cannot execute treatment.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-treatment", "name": "Recorded operation and outcome", "description": "Record the operation actually evidenced, distinguishing planned, accepted, started and completed states and intermediate from final processing. Refer to external facility/process masters; this model cannot execute treatment.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-treatment-1", "text": "Which documented treatment operation applies to the input lots?", "kind": "process", "answer_data": [ "operation" ] }, { "id": "q-treatment-2", "text": "What evidence supports the reported stage and completion of treatment?", "kind": "lifecycle", "answer_data": [ "treatment-stage" ] }, { "id": "q-treatment-3", "text": "Is the outcome preparation for reuse, recycling, other recovery or disposal under the selected profile?", "kind": "classification", "answer_data": [ "operation-class" ] }, { "id": "q-treatment-4", "text": "Which policy conditions or unresolved failures prevent accepting the outcome assertion?", "kind": "constraint", "answer_data": [ "outcome-hold" ] } ], "data_elements": [ { "id": "data-treatment-operation", "name": "operation", "description": "Operation master, code scheme and edition, facility reference, inputs and actual versus planned state. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-treatment-treatment-stage", "name": "treatment-stage", "description": "Event evidence, occurrence time, observation time, assessor and incomplete or rejected state. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-treatment-operation-class", "name": "operation-class", "description": "Profile concept, classification rationale and exceptions; Basel disposal terminology is mapped separately. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-treatment-outcome-hold", "name": "outcome-hold", "description": "Condition references, missing evidence, incident links and responsible reviewer; no corrective operating instructions. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-treatment", "name": "Treatment assertion register", "description": "Versioned local evidence index or assessment for recorded operation and outcome. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-lineage", "name": "Output lineage and balance", "description": "Model input/output lineage through split, merge and transformation, with explicit allocation scope. The authored balance compares inputs plus opening stock and documented additions against outputs plus closing stock, losses and releases on a compatible basis. An unexplained residual is reported, never forced to zero.", "source_refs": [ "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-lineage", "name": "Allocated outputs and residues", "description": "Model input/output lineage through split, merge and transformation, with explicit allocation scope. The authored balance compares inputs plus opening stock and documented additions against outputs plus closing stock, losses and releases on a compatible basis. An unexplained residual is reported, never forced to zero.", "source_refs": [ "SRC-005", "SRC-007" ], "questions": [ { "id": "q-lineage-1", "text": "Which output and residue lots derive from each input or merged group?", "kind": "composition", "answer_data": [ "lot-lineage" ] }, { "id": "q-lineage-2", "text": "What balance boundary includes stocks, additives, outputs, residues and documented losses?", "kind": "measurement", "answer_data": [ "balance-scope" ] }, { "id": "q-lineage-3", "text": "What prevents the same physical quantity being counted twice across linked accounts?", "kind": "validation", "answer_data": [ "allocation-control" ] }, { "id": "q-lineage-4", "text": "Which unresolved balance residual or attribution uncertainty limits this recovery claim?", "kind": "quality", "answer_data": [ "balance-result" ] } ], "data_elements": [ { "id": "data-lineage-lot-lineage", "name": "lot-lineage", "description": "Input and output IDs, transformation reference, allocation fractions and shared account links. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "data-lineage-balance-scope", "name": "balance-scope", "description": "Period, material basis, boundary, quantities, measurement references and uncertainty. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "data-lineage-allocation-control", "name": "allocation-control", "description": "Unique observation and allocation IDs, exclusive allocation rule, overlaps and unresolved shared quantities. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "data-lineage-balance-result", "name": "balance-result", "description": "Residual, tolerance source, unknown flows, attribution limits and review status. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-lineage", "name": "Material lineage and balance register", "description": "Versioned local evidence index or assessment for allocated outputs and residues. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-circularity", "name": "Recovered status and circularity", "description": "Qualified non-waste status and bounded reporting claims.", "rationale": "Authored waste-account grouping grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-008" ], "layers": [ { "id": "layer-recovered-status", "name": "Recovered material status", "description": "Recovered output retains an explicit legal-status assertion. Recovery, sale, quality grade, disposal or an internal closure flag cannot alone establish end-of-waste. Downstream product identity remains separately mastered.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "findings": [ { "id": "finding-recovered-status", "name": "Evidenced transition to non-waste", "description": "Recovered output retains an explicit legal-status assertion. Recovery, sale, quality grade, disposal or an internal closure flag cannot alone establish end-of-waste. Downstream product identity remains separately mastered.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "q-recovered-status-1", "text": "Which material-specific end-of-waste criteria or case decision are being relied on?", "kind": "requirement", "answer_data": [ "end-waste-profile" ] }, { "id": "q-recovered-status-2", "text": "What evidence supports each applicable condition and what remains unmet or unknown?", "kind": "evidence", "answer_data": [ "condition-evidence" ] }, { "id": "q-recovered-status-3", "text": "From when and for which output quantity does the status assertion apply?", "kind": "temporal", "answer_data": [ "status-transition" ] }, { "id": "q-recovered-status-4", "text": "Which product or secondary-material master receives the qualified output reference?", "kind": "relationship", "answer_data": [ "product-link" ] } ], "data_elements": [ { "id": "data-recovered-status-end-waste-profile", "name": "end-waste-profile", "description": "Jurisdiction, instrument and edition, output scope and determination authority. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-recovered-status-condition-evidence", "name": "condition-evidence", "description": "Condition-to-evidence links, assessment status, quality/use evidence and missing items. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-recovered-status-status-transition", "name": "status-transition", "description": "Effective time or interval, quantity scope, provenance and disputed or withdrawn state. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-recovered-status-product-link", "name": "product-link", "description": "External material ID, accepted quantity, destination use and mapping; no automatic market authorization. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-recovered-status", "name": "Recovered-status assessment register", "description": "Versioned local evidence index or assessment for evidenced transition to non-waste. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-circularity", "name": "Circularity reporting", "description": "Record what a recycling or return-to-use metric measures. Keep a flow-account metric separate from national statistics, product recycled content and environmental benefit. Collection for recycling is not proof of final recycling; prevention, repair and reuse require their own evidence.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "findings": [ { "id": "finding-circularity", "name": "Bounded circularity claim", "description": "Record what a recycling or return-to-use metric measures. Keep a flow-account metric separate from national statistics, product recycled content and environmental benefit. Collection for recycling is not proof of final recycling; prevention, repair and reuse require their own evidence.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ], "questions": [ { "id": "q-circularity-1", "text": "What claim and reporting population are being measured?", "kind": "definition", "answer_data": [ "claim-boundary" ] }, { "id": "q-circularity-2", "text": "Which numerator, denominator and reporting point produce the stated rate?", "kind": "measurement", "answer_data": [ "metric-inputs" ] }, { "id": "q-circularity-3", "text": "How are residues, repeat transfers, imports, exports and uncertain destinations treated?", "kind": "validation", "answer_data": [ "metric-adjustments" ] }, { "id": "q-circularity-4", "text": "What qualifies this metric for reuse in an external reporting or claim system?", "kind": "interoperability", "answer_data": [ "claim-mapping" ] } ], "data_elements": [ { "id": "data-circularity-claim-boundary", "name": "claim-boundary", "description": "Metric definition, geography, period, included material, claimant and methodological scope. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-circularity-metric-inputs", "name": "metric-inputs", "description": "Evidence-backed quantities, units, formula version, trade adjustments where relevant and zero-denominator rule. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-circularity-metric-adjustments", "name": "metric-adjustments", "description": "Deduplication keys, exclusions, allocation and estimate methods, missing-data bounds and reconciliation. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] }, { "id": "data-circularity-claim-mapping", "name": "claim-mapping", "description": "Target profile, mapping version, boundary differences, loss report and certification gap. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-circularity", "name": "Circularity claim worksheet", "description": "Versioned local evidence index or assessment for bounded circularity claim. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Disposal and continuing duties", "description": "Disposal evidence and site aftercare links with records continuity.", "rationale": "Authored waste-account grouping grounded in the cited concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-disposal", "name": "Disposal outcome", "description": "Separate facility receipt, actual disposal evidence and account closure. Closure describes local record progress and does not establish legal release or erase disposed material and its continuing obligations.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "finding-disposal", "name": "Supported disposal record", "description": "Separate facility receipt, actual disposal evidence and account closure. Closure describes local record progress and does not establish legal release or erase disposed material and its continuing obligations.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "q-disposal-1", "text": "Which site and documented operation received the disposal quantity?", "kind": "spatial", "answer_data": [ "disposal-destination" ] }, { "id": "q-disposal-2", "text": "What demonstrates actual disposal rather than storage, dispatch or receipt alone?", "kind": "evidence", "answer_data": [ "disposal-proof" ] }, { "id": "q-disposal-3", "text": "Which portions of the account can close and which outcomes remain unresolved?", "kind": "lifecycle", "answer_data": [ "closure-scope" ] }, { "id": "q-disposal-4", "text": "Which schedule and legal holds preserve disposal evidence and permit lawful disposition?", "kind": "retention", "answer_data": [ "disposal-retention" ] } ], "data_elements": [ { "id": "data-disposal-disposal-destination", "name": "disposal-destination", "description": "Facility and parcel references, operation scheme, quantity scope and acceptance evidence. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "data-disposal-disposal-proof", "name": "disposal-proof", "description": "Completion record, accountable actor, event time and uncertainty or missing confirmation. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "data-disposal-closure-scope", "name": "closure-scope", "description": "Lot allocations, supported outcomes, open claims and closure reason with expected revision. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "data-disposal-disposal-retention", "name": "disposal-retention", "description": "Profile, record class, retention trigger, hold owner and disposition authority. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-disposal", "name": "Disposal outcome index", "description": "Versioned local evidence index or assessment for supported disposal record. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-aftercare", "name": "Continuing obligations", "description": "Link the waste account to site-level aftercare obligations and observations. The account does not own monitoring equipment, remediation, permits or a complete site lifecycle. A single clean inspection cannot discharge continuing duties.", "source_refs": [ "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-aftercare", "name": "Aftercare and evidence continuity", "description": "Link the waste account to site-level aftercare obligations and observations. The account does not own monitoring equipment, remediation, permits or a complete site lifecycle. A single clean inspection cannot discharge continuing duties.", "source_refs": [ "SRC-006", "SRC-007" ], "questions": [ { "id": "q-aftercare-1", "text": "Who is responsible for the linked aftercare obligation and which authority can change it?", "kind": "ownership", "answer_data": [ "aftercare-duty" ] }, { "id": "q-aftercare-2", "text": "Which monitoring period and review trigger apply after disposal or site closure?", "kind": "temporal", "answer_data": [ "aftercare-window" ] }, { "id": "q-aftercare-3", "text": "Which monitoring or incident records affect this account and what conclusions are actually supported?", "kind": "evidence", "answer_data": [ "aftercare-evidence" ] }, { "id": "q-aftercare-4", "text": "Which recipient may view aftercare evidence and its protected supporting records?", "kind": "access", "answer_data": [ "aftercare-access" ] } ], "data_elements": [ { "id": "data-aftercare-aftercare-duty", "name": "aftercare-duty", "description": "Site obligation master, responsible role, competent authority and effective decision. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "data-aftercare-aftercare-window", "name": "aftercare-window", "description": "Profile-based interval, due review, last observation and unknown endpoint. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "data-aftercare-aftercare-evidence", "name": "aftercare-evidence", "description": "External observation references, scoped conclusions, adverse-effect flags and unresolved follow-up. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "data-aftercare-aftercare-access", "name": "aftercare-access", "description": "Recipient purpose, authorization, redactions, release basis and audit reference. Candidate field group; nested schema and applicable requiredness need a pinned implementation profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-aftercare", "name": "Aftercare linkage register", "description": "Versioned local evidence index or assessment for aftercare and evidence continuity. External source records retain their authoritative identity and access policy.", "media_or_form": [ "structured record", "authorized human-readable projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier and namespace first, then governed IRI, then local opaque UUID. Use account reference, artifact type and immutable sequence/revision; never a date or waste code alone.", "source_refs": [ "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-flow-reference", "name": "Resolve an account reference", "description": "Proposed operation, not implemented. Resolve account, lot and consignment identifiers without merging by code, date or material similarity.", "inputs": [ "qualified master reference", "authorized scope" ], "outputs": [ "resolved reference or ambiguity report" ], "preconditions": [ "Verified role, purpose and access for all source records", "Pinned profile and sufficient supporting evidence; refuse unsupported authority or calculation", "For mutation require expected revision and idempotency key; report conflicts without overwriting" ], "effects": [ "Read-only identity result; no master merge." ], "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "record-assessment", "name": "Record a supported status assessment", "description": "Proposed operation, not implemented. Append a qualified classification or end-of-waste assessment supplied by an authorized reviewer; never decide legal status automatically.", "inputs": [ "account and lot scope", "profile and assessment evidence", "expected revision" ], "outputs": [ "assessment revision or refusal" ], "preconditions": [ "Verified role, purpose and access for all source records", "Pinned profile and sufficient supporting evidence; refuse unsupported authority or calculation", "For mutation require expected revision and idempotency key; report conflicts without overwriting" ], "effects": [ "Local assertion changes only; unresolved evidence remains unresolved." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "link-transfer-evidence", "name": "Link transfer and receipt evidence", "description": "Proposed operation, not implemented. Index evidenced custody and receiving acknowledgement while reporting missing links and quantity disputes.", "inputs": [ "movement master reference", "receipt evidence", "expected revision" ], "outputs": [ "custody index revision or discrepancy report" ], "preconditions": [ "Verified role, purpose and access for all source records", "Pinned profile and sufficient supporting evidence; refuse unsupported authority or calculation", "For mutation require expected revision and idempotency key; report conflicts without overwriting" ], "effects": [ "Append local linkage; no shipment dispatch, signing or consent." ], "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "reconcile-flow-quantities", "name": "Prepare a scoped quantity reconciliation", "description": "Proposed operation, not implemented. Compare compatible observed quantities with documented allocations, stocks and losses. Refuse missing conversion basis and expose double-counting or residual uncertainty.", "inputs": [ "account revision", "boundary and basis", "quantity observations and allocation ledger" ], "outputs": [ "balance worksheet with residuals or refusal" ], "preconditions": [ "Verified role, purpose and access for all source records", "Pinned profile and sufficient supporting evidence; refuse unsupported authority or calculation", "For mutation require expected revision and idempotency key; report conflicts without overwriting" ], "effects": [ "Create local analysis artifact only; no physical operation or compliance certification." ], "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "link-outcome-evidence", "name": "Record treatment or disposal outcome evidence", "description": "Proposed operation, not implemented. Link external operation evidence and output lots; distinguish receipt, completion, status transition and continuing obligations.", "inputs": [ "operation and output references", "completion evidence and authority scope", "expected revision" ], "outputs": [ "outcome index revision or unresolved report" ], "preconditions": [ "Verified role, purpose and access for all source records", "Pinned profile and sufficient supporting evidence; refuse unsupported authority or calculation", "For mutation require expected revision and idempotency key; report conflicts without overwriting" ], "effects": [ "Append supported outcome; do not execute treatment or discharge aftercare duties." ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "prepare-scoped-report", "name": "Prepare an authorized circularity projection", "description": "Proposed operation, not implemented. Produce a recipient-scoped local claim worksheet with methodology, exclusions and unresolved evidence. Reject incompatible target definitions.", "inputs": [ "recipient authorization", "account revisions", "metric and target profile" ], "outputs": [ "local report with qualifications or refusal" ], "preconditions": [ "Verified role, purpose and access for all source records", "Pinned profile and sufficient supporting evidence; refuse unsupported authority or calculation", "For mutation require expected revision and idempotency key; report conflicts without overwriting" ], "effects": [ "Create a local report and access audit reference; no submission or certification." ], "source_refs": [ "SRC-005", "SRC-007", "SRC-008" ] } ], "composition": [ { "target": "WM-FLW-004", "relation": "REFERENCE", "purpose": "Candidate generic movement master binding; preserve transport and custody event ownership outside the waste account. Legacy EXTEND not automatically ratified.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "WM-FLW-006", "relation": "REFERENCE", "purpose": "Candidate emission master reference for measured releases included in a reconciliation; no emissions lifecycle here.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "WM-PLC-002", "relation": "REFERENCE", "purpose": "Candidate parcel reference for origin or disposal site; facility and aftercare masters remain external.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-FLW-002", "relation": "REFERENCE", "purpose": "Optional water-chain origin/destination reference after F4 split; no water-supply operations.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-FLW-003", "relation": "REFERENCE", "purpose": "Optional food-chain origin/destination reference after F4 split; no food-chain lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "target": "WM-ECO-014", "relation": "REFERENCE", "purpose": "Optional downstream sustainability-claim reference. A waste quantity or national recycling measure does not establish product carbon footprint or certified recycled content.", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "target": "European List of Waste", "relation": "ALIGN", "purpose": "Versioned classification mapping, not a copied classifier or automatic hazardous-status decision.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "Basel Convention notification and movement documents", "relation": "ALIGN", "purpose": "Policy-level field and authority alignment; exact party and shipment profile must be checked.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "US hazardous waste manifest", "relation": "ALIGN", "purpose": "Regional evidence mapping only, not a globally applicable form or implemented electronic filing.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "SDG 12.5.1", "relation": "ALIGN", "purpose": "Conceptual reporting-boundary alignment; account measures are not automatically national indicator results.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "PROV-O", "relation": "ALIGN", "purpose": "Conceptual attribution and derivation mapping without executable RDF conformance claim.", "required": false, "source_refs": [ "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Identify accountable generator, holder, processor and local record custodian roles with authority scope", "Pin jurisdiction, waste category, legal-profile versions and review/escalation roles", "Declare account/cohort boundary, master namespaces, allocation policy, access and retention schedule" ], "namespace_guidance": "Authority-qualified opaque account and lot IDs; codes classify and dates locate events but neither identifies the account alone.", "registry_links": [ "vr.wm-flw-005", "Candidate sibling bindings require version and boundary review before integration" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve source assertions separately from normalized values; unknown is not zero or non-hazardous.", "Retain distinct lot, stream, account, consignment and document identities; no merge from a shared code.", "Waste status, custody, ownership, permit scope and local workflow state remain distinct." ], "patch_rules": [ "Use actor, purpose, evidence, expected revision and idempotency key for each append or correction.", "Supersede erroneous assertions with linked revisions; do not falsify original measurements or silently reallocate shared quantities." ], "compatibility_rules": [ "Pin classification, unit, legal and reporting profiles. Reject target mappings that lose waste-status, authority, quantity-basis or uncertainty qualifiers." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier plus namespace and revision", "Governed global identifier or stable IRI with version", "Opaque UUID or ULID assigned by the adopting Dimension with reconciliation state" ], "timestamp_rule": "Use RFC 3339 with seconds and explicit UTC offset for recording instants. Keep generation, collection, transfer, treatment and legal-effective event time separate from observation and ingestion time. Preserve date-only values and intervals with precision; never invent midnight instants.", "serial_naming_rule": "Use opaque account key, artifact type and immutable sequence or revision; no personal identifiers or dates as sole identity.", "integrity_rule": "Record digest, algorithm, source and transformation history where available; a hash proves neither truth, authority, lawful shipment nor final recycling." }, "policies": [ "Reviewable draft under a single-provider waiver; independent review and current-source verification remain outstanding.", "Apply jurisdiction and material-specific policy before interpreting any code, permission, responsibility or end-of-waste assertion.", "Dangerous and controlled streams remain at authorization, restriction and evidence level; no handling, treatment or evasion instructions.", "Disclose minimal evidence for the recipient purpose; aggregate totals can still reveal commercially sensitive or personal information.", "Custody changes do not automatically transfer all responsibility. Product-producer responsibility and waste-generator duties require separate legal scope." ], "crud": { "read": [ "Enforce authorized recipient scope and preserve redaction, provenance, uncertainty and missing-evidence qualifiers." ], "create": [ "Require account identity, bounded scope and accountable custodian; permit explicit unknown classifications without claiming safe or authorized status." ], "update": [ "Append supported revisions and allocation corrections after concurrency checks; keep disputed source observations visible to authorized reviewers." ], "delete": [ "Apply record-class retention, legal holds and lawful erasure to local evidence payloads and projections. The adopting Dimension records officer owns disposition execution.", "Use minimal non-identifying tombstones where lawful; local deletion cannot delete external masters, terminate aftercare or establish legal discharge." ] }, "roles": [ { "name": "Generator or origin steward", "responsibilities": [ "Attest origin and generation evidence within verified scope" ] }, { "name": "Holder or carrier record steward", "responsibilities": [ "Supply transfer and receipt evidence without inferring treatment completion" ] }, { "name": "Processor record steward", "responsibilities": [ "Supply operation, output and residue evidence linked to facility masters" ] }, { "name": "Qualified classification reviewer", "responsibilities": [ "Assess profile applicability, status and disputes; no automatic legal certification" ] }, { "name": "Records and access officer", "responsibilities": [ "Govern recipient scopes, retention, legal holds and disposition" ] }, { "name": "Reporting reviewer", "responsibilities": [ "Check metric boundaries, double counting, uncertainty and claim qualifications" ] } ], "access": { "default_rule": "Deny disclosure unless recipient, purpose and scope are authorized; infrastructure control grants no authority over another holder records.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory or emergency disclosure requires documented legal basis, responsible actor and narrow scope; no blanket bypass.", "Public statistical views require disclosure assessment, aggregation and suppression where needed." ], "audit_requirements": [ "Record actor, purpose, scope, revision and outcome for reads, exports and mutations using an external audit reference and a minimal-data retention policy." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and adopting Dimension authority/access policies", "spec.yaml with all publication holds", "Pinned profile and authorized evidence for the selected account" ] } }, "coverage": { "claim": "Source-grounded authored structure for a bounded waste-flow account, with lot lineage, qualified status, custody evidence and circularity or disposal outcomes. Selected EU, Basel, US and statistical examples do not establish universal applicability. This noncanonical reviewable draft has no independent external review and retains source, legal-profile and executable-conformance holds.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Separate account, cohort, lot, stream, consignment and document references." }, { "dimension": "lifecycle", "status": "covered", "notes": "Generation through qualified outcomes, corrections and continuing obligations." }, { "dimension": "relationships", "status": "covered", "notes": "References preserve movement, site, product, emissions and claim masters." }, { "dimension": "temporal", "status": "covered", "notes": "Event, effective, observation and recording times with precision and unknowns." }, { "dimension": "provenance", "status": "covered", "notes": "Assertion attribution, source versions, derivation and supersession." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based record stewardship distinct from title, custody and legal responsibility." }, { "dimension": "validation", "status": "gap", "notes": "Research schema gate only; instance and profile conformance remain open." }, { "dimension": "access", "status": "covered", "notes": "Recipient-scoped evidence and aggregation disclosure checks." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Record-class schedules, legal holds, lawful erasure and minimal tombstones." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual mappings require pinned executable profiles and loss tests." }, { "dimension": "direct properties", "status": "covered", "notes": "Physical state, composition and quantity with method, basis, uncertainty and time." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Origin and assessments distinguish waste from by-products and recovered outputs." }, { "dimension": "capabilities and hazards", "status": "covered", "notes": "Proposed local functions with refusal; no physical treatment or shipment authorization." }, { "dimension": "context and evidence", "status": "covered", "notes": "Legal and material scope, duty references, metric boundaries and unresolved evidence." } ], "known_omissions": [ "Independent external review is absent; the local Codex no-tools audit is a self-audit.", "Direct HTTP status and response hashes are unmeasured in the sandbox; current legal versions, national transposition, party status and material-specific criteria remain unverified.", "Nested instance schemas, allocation constraints, runtime functions, target mappings and conformance fixtures are not implemented.", "Sector-specific waste regimes, radioactive or other specially controlled streams and operational safety procedures require separate specialist profiles.", "Producer-responsibility fee accounting, certified product recycled content, life-cycle impacts and complete national statistics are outside this account boundary." ], "conflicts": [], "regional_assumptions": [ "EU classifications and legal concepts, US manifest practice and Basel international controls are separate scoped examples; national law and effective implementation require review.", "The landfill source is the original act and the List of Waste source is a dated consolidation; neither is asserted to be the complete current applicable law.", "SDG 12.5.1 is a national indicator method; local account metrics require a separately declared reporting boundary." ], "adversarial_checks": [ "Reject recovered, sold, disposed or locally closed as automatic non-waste status.", "Reject notification identifiers or receiving signatures as shipment authorization or completed recycling.", "Reject double-counting a physical quantity after split, merge, repeated transfer or cross-account attribution.", "Reject unqualified persistence or extinction of generator liability from a custody event.", "Reject automatic inheritance of legacy conformance claims or ambiguous F4/F6 target bindings." ] }, "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 account groups identified arising and descendant lots, allocations and outcome assertions under an explicit lot or cohort boundary. It does not own every linked physical object or external master. The registry standalone-mm value describes the record plane and is not a subject-kind enum." }, "decisions": [ { "concept": "Bounded waste-flow aggregate", "disposition": "accepted", "rationale": "A defined origin lot or cohort and retained descendant identities support an aggregate. An industry, an entire facility and a stream classifier are excluded as roots, preventing an unbounded circular-economy model." }, { "concept": "Legacy and supplement authority", "disposition": "rejected as source of truth", "rationale": "The supplement declared no new source reading. Its structure is a lead only, and neither its author label nor the legacy conformance labels supplies an admitted provider review or tested conformance." }, { "concept": "Automatic exit from waste status", "disposition": "rejected", "rationale": "The result consistently separates recovery, sale, disposal and local closure from a supported end-of-waste assertion. By-product status is assessed separately, so the supplement's unconditional class-exit wording is not inherited." }, { "concept": "Identity and classifications", "disposition": "separated", "rationale": "Account, lot, stream category, consignment and evidence document retain different identifiers. A waste code, note number or date alone cannot merge these identities, and code schemes retain editions and jurisdictions." }, { "concept": "Custody and legal responsibility", "disposition": "qualified", "rationale": "Transfer evidence supports a scoped custody assertion. Ownership, record stewardship, generator duties and producer responsibility need separate authority and profile evidence; no universal liability persistence or extinction is claimed." }, { "concept": "Shipment and treatment authority", "disposition": "separated from record state", "rationale": "Notification identifiers and receiving acknowledgements are not shipment permission or proof of completed recycling. Permit scope, dates, consent and unresolved exceptions are separately elicited, and dangerous streams remain at policy level." }, { "concept": "Split, merge and quantity reconciliation", "disposition": "accepted as authored design", "rationale": "Lot lineage, allocation identifiers, stock changes, additions and unresolved residuals prevent silent double counting or forced balances. Quantity basis and conversion evidence are required conceptually; executable allocation and measurement constraints remain a conformance hold." }, { "concept": "Circularity metric scope", "disposition": "qualified", "rationale": "The reporting finding distinguishes collection from final recycling and requires numerator, denominator, boundary and adjustments. National indicator concepts are not silently promoted into product recycled content or environmental benefit certification." }, { "concept": "Neighbor ownership and legacy alias splits", "disposition": "accepted as candidate references", "rationale": "F3 transport ownership stays external; F4 water and food successors are separate references. F6 emission and sustainability claim targets have different purposes. Parcel, facility, product, audit and aftercare masters are not recreated by local indices." }, { "concept": "Disposal and continuing duties", "disposition": "separated", "rationale": "The result distinguishes receipt, actual disposal, local account closure and site aftercare. A clean observation, deleted local record or closed account cannot discharge a site obligation or establish legal release." }, { "concept": "Artifacts, access and retention", "disposition": "accepted with implementation dependency", "rationale": "Artifact identity follows authoritative namespaces and revisions, while timestamps distinguish event and recording precision. Recipient scopes and lawful disposition apply to local payloads; minimal tombstones do not imply perpetual personal-data retention or deletion of external masters." }, { "concept": "Proposed functions and candidate schemas", "disposition": "accepted as research only", "rationale": "All six functions declare that they are unimplemented local operations with evidence, access and revision preconditions. Optional candidate field groups do not constitute operational instance schemas or implementations of measurement, legal or reporting logic." }, { "concept": "Source and regional authority", "disposition": "limited", "rationale": "Selected browser text supports the concepts, but the dated List of Waste and original landfill act cannot certify complete current law. Basel party scope, national implementation and current criteria remain unresolved. Direct HTTP was not attempted and no response status was measured." }, { "concept": "Independent review", "disposition": "waived and held", "rationale": "Only the Codex result is admitted. This separate no-tools assessment is a local self-audit of frozen evidence, not a second provider or independent review; no additions or fabricated provider agreement are permitted." } ], "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 independent review.", "Live source and version verification remains incomplete. Eight source URLs returned browser document text for selected review, but direct HTTP checks were not attempted under the owner-reported sandbox restriction. Status codes, redirect chains and body hashes are unmeasured; the coordinator checker is prepared. Dated legal sources do not establish current applicable law.", "Jurisdiction, national transposition, Basel party applicability, material-specific criteria, permit scope, responsibility, legal-status determinations, retention and source-reuse rights require qualified adoption-profile review before operational use. Specially controlled streams need separate specialist profiles.", "Nested instance schemas, pinned neighbor bindings, executable quantity/allocation constraints, target mappings, implemented functions and adversarial conformance fixtures remain incomplete. No runtime, legal-compliance, recycling or product-content certification is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify current consolidated legal instruments, material-specific rules, national implementation, party status and authoritative source versions for each adopted profile.", "Develop and test nested schemas and mappings against split/merge, partial rejection, wet/dry basis, unknown origin, disputed status, shared allocations, zero denominator and continuing aftercare cases.", "Restore independent external review before promotion beyond a noncanonical reviewable draft." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }