# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:12:00Z", "synthesisSha256": "6d757143848d8e41bffed5cc52141cde1ce1ce0c9bc5f7904f47334733d62113", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-011", "registryId": "vr.wm-act-011", "name": "Agriculture Operation", "version": "0.1.0-reviewable", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.AGR" ], "tags": [ "agriculture", "operation", "act.agr" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-011-agriculture-operation/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-011", "model": { "registry_id": "vr.wm-act-011", "model_id": "WM-ACT-011", "name": "Agriculture Operation", "entry_kind": "aggregate", "purpose": "Describe a bounded dossier of managed agricultural activity, its production context, interventions, observations and output evidence.", "scope_statement": "One operation dossier groups agricultural work for a declared management scope and interval. It may cover a crop campaign, a husbandry episode or a mixed programme, including planned, partial, failed and completed work. It owns the dossier and activity-specific assertions, not the permanent holding, living organism, land, product or official register. Child activity references retain their own identities. This is a proposed research aggregate, not an execution engine or the statistical holding itself.", "in_scope": [ "Management scope, responsible roles, effective site/field bindings and applicable crop or husbandry modules", "Production-cycle references, intervention evidence, resource allocations and environmental observation links", "Harvest and recurring collection evidence, loss and output lineage, restriction decisions, reporting views and local record continuity" ], "out_of_scope": [ "Biological identity, taxonomy and full lifecycle of crop stands, animals and herds; land title, soil and facility masters", "Manufacturing, commercial inventory, logistics, finance and official animal/holding registers", "Agronomic prescriptions, dosing, veterinary diagnosis, machinery control, safety certification, disease-control execution and legal compliance determinations", "Detailed forestry, capture fisheries, aquaculture and species-specific specialist profiles; private gardens are not excluded merely by size, but need an adopting profile" ], "boundary_notes": [ { "neighbor": "WM-LIV-009 Cultivated Organism", "distinction": "The shared K9 legacy material is reconciled by keeping managed work here and organism identity and biological state in the separately registered sibling. A season or operation is not an organism; dated membership references are evidence snapshots, not a second animal registry.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] }, { "neighbor": "WM-PLC-002 Land Parcel; WM-EAR-003 Soil; WM-BLT-008 Site / Campus", "distinction": "Managed work areas reference external land, soil and facility records; management polygons may cross parcels or change over time. Tenure evidence does not create title. The legacy P5 Site alias is not reused because the current registry assigns P5 elsewhere.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "WM-ACT-002 Act; WM-ACT-008 Plan / Schedule", "distinction": "The root aggregates activity evidence and subject-specific crop/husbandry context. Atomic acts and schedules retain separate identities; no universal Act inheritance or scheduling implementation is claimed.", "source_refs": [ "SRC-007" ] }, { "neighbor": "WM-ACT-010 Production Run; WM-FLW-003 Food Supply Chain; WM-OBJ-004 Food Product", "distinction": "Agricultural output links end at the declared handover. Processing, product masters and supply-chain events remain external. On-farm location alone does not make an activity primary production, and collection need not imply processing.", "source_refs": [ "SRC-005", "SRC-008" ] }, { "neighbor": "WM-PER-001 Person; WM-ORG-001 Organization; WM-XCT-001 Ownership / Stewardship; WM-XCT-002 Access Contract / Consent; WM-XCT-004 Access Audit", "distinction": "Hold role assignments and policy references here. Legal ownership, consent evaluation and access-audit execution belong to their masters. Management, custody, data stewardship and land ownership are separate roles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "title": "World Programme for the Census of Agriculture 2020, Volume 1", "organization": "Food and Agriculture Organization of the United Nations", "url": "https://www.fao.org/4/i4913e/i4913e.pdf", "version_or_date": "WCA 2020; historical programme for 2016-2025; FAO listing dates this edition 2017", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T14:10:29Z", "relevance": "Chapter 6 holding/holder and reference periods; chapter 8 land, cropping, irrigation and livestock concepts. Statistical framing only; the 2030 programme requires separate reconciliation." }, { "id": "SRC-002", "title": "AGROVOC", "organization": "Food and Agriculture Organization of the United Nations", "url": "https://www.fao.org/agrovoc/", "version_or_date": "Dynamic public landing page reviewed 2026-10-06; no vocabulary release pinned", "source_type": "ontology", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T14:10:29Z", "relevance": "Agricultural concept identifiers and multilingual mappings. A vocabulary does not establish biological identity, safe practice or compliance." }, { "id": "SRC-003", "title": "Terrestrial Animal Health Code, Chapter 4.3: Design and implementation of identification systems to achieve animal traceability", "organization": "World Organisation for Animal Health", "url": "https://www.woah.org/fileadmin/Home/eng/Health_standards/tahc/current/en_chapitre_ident_design.htm", "version_or_date": "Chapter 4.3 at a current alias; returned text includes historical terminology; edition unverified", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:10:29Z", "relevance": "Sections on programme scope, individual/group identification, establishment and event registration, confidentiality and competent authority. National applicability remains a profile decision." }, { "id": "SRC-004", "title": "Regulation (EC) No 852/2004, historical consolidated text", "organization": "European Parliament and Council of the European Union", "url": "https://www.legislation.gov.uk/eur/2004/852/pdfs/eur_20040852_2008-10-28_en.pdf", "version_or_date": "Consolidation 2008-10-28; historical evidence only, not verified current EU or UK law", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:10:29Z", "relevance": "Annex I Part A primary-production hygiene and record evidence, including feed, treatment and analysis records; used as a scoped example, not a universal obligation." }, { "id": "SRC-005", "title": "EPCIS Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/epcis/2.0.1/", "version_or_date": "URL 2.0.1; retrieved PDF identifies Release 2.0, June 2022; exact errata pin unresolved", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:10:29Z", "relevance": "Visibility-event identity, source/output links, time, quantities and correction declarations. Conceptual alignment only; no implemented EPCIS mapping." }, { "id": "SRC-006", "title": "OGC SensorThings API Part 1: Sensing Version 1.1", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/18-088/18-088.html", "version_or_date": "Version 1.1, OGC 18-088", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:10:29Z", "relevance": "Sections 8.2.4-8.2.8 distinguish observed property, sensor, feature, units, phenomenon time, result time and quality. Observation links do not imply representativeness." }, { "id": "SRC-007", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:10:29Z", "relevance": "Sections 3 and 5 distinguish activities, entities, agents, derivation and revision. Used for evidence attribution and record changes, not proof of truth." }, { "id": "SRC-008", "title": "Guidance document on implementation of certain provisions of Regulation (EC) No 852/2004", "organization": "European Commission Directorate-General for Health and Food Safety", "url": "https://food.ec.europa.eu/system/files/2018-10/biosafety_fh_legis_guidance_reg-2004-852_en.pdf", "version_or_date": "2018 information document; expressly no formal legal status", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T14:10:29Z", "relevance": "Section 3.1 examples distinguish production, collection and some on-farm handling from downstream activity. Scope varies by product; location alone does not decide it." } ], "structure": { "bundles": [ { "id": "bundle-mandate", "name": "Management scope", "description": "Identify the dossier and bind its operational footprint.", "rationale": "A distinct agricultural decision surface in the proposed dossier; source concepts support the questions, not this exact hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-scope", "name": "Dossier identity and responsibility", "description": "The dossier boundary is a local design choice informed by management and activity concepts. Its identity persists across revisions; official holding numbers are optional references, never assumed universal.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-scope", "name": "Dossier identity and responsibility", "description": "The dossier boundary is a local design choice informed by management and activity concepts. Its identity persists across revisions; official holding numbers are optional references, never assumed universal.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "question-scope-dossier-id", "text": "Which stable dossier identifier and management scope distinguish this programme from a holding, season or individual act?", "kind": "identity", "answer_data": [ "data-scope-dossier-id", "Dossier identifier, issuer and namespace; scoped management boundary and parent reference" ] }, { "id": "question-scope-module-selection", "text": "Which agricultural activity classes and crop or husbandry modules apply to this dossier?", "kind": "classification", "answer_data": [ "data-scope-module-selection", "Profile version, selected modules, classifications and explicit non-applicability reasons" ] }, { "id": "question-scope-responsibility", "text": "Who holds management, custody and record-stewardship roles for the covered interval?", "kind": "ownership", "answer_data": [ "data-scope-responsibility", "External party references, distinct roles, effective intervals and evidence" ] }, { "id": "question-scope-mandate", "text": "What mandate permits the recorder and contractors to act on this operation record?", "kind": "authority", "answer_data": [ "data-scope-mandate", "Authority reference, permitted local actions, expiry and unresolved delegation" ] } ], "data_elements": [ { "id": "data-scope-dossier-id", "name": "Dossier id", "description": "Dossier identifier, issuer and namespace; scoped management boundary and parent reference. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-scope-module-selection", "name": "Module selection", "description": "Profile version, selected modules, classifications and explicit non-applicability reasons. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-scope-responsibility", "name": "Responsibility", "description": "External party references, distinct roles, effective intervals and evidence. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-scope-mandate", "name": "Mandate", "description": "Authority reference, permitted local actions, expiry and unresolved delegation. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-scope", "name": "Dossier identity and responsibility evidence record", "description": "Versioned evidence or reference manifest for dossier identity and responsibility. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-footprint", "name": "Effective work areas", "description": "Work areas are management scopes rather than cadastral facts. Landless husbandry, mobile groups, covered growing spaces and changing boundaries require explicit location and applicability states.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "finding-footprint", "name": "Effective work areas", "description": "Work areas are management scopes rather than cadastral facts. Landless husbandry, mobile groups, covered growing spaces and changing boundaries require explicit location and applicability states.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "question-footprint-work-area", "text": "Where was the work performed and which version of the managed-area geometry applies?", "kind": "spatial", "answer_data": [ "data-footprint-work-area", "Area or facility reference, geometry, coordinate reference system, validity interval and precision" ] }, { "id": "question-footprint-site-links", "text": "How does the work area relate to parcels, soil records, facilities or mobile locations?", "kind": "relationship", "answer_data": [ "data-footprint-site-links", "Typed external references, effective intersections, unresolved links and no-land explanation" ] }, { "id": "question-footprint-use-basis", "text": "What evidence supports access to the production space without asserting legal title?", "kind": "constraint", "answer_data": [ "data-footprint-use-basis", "Tenure or use-permission evidence, scope, time and disputed status" ] }, { "id": "question-footprint-area-basis", "text": "Which area measure was used and how are overlapping or successive uses counted?", "kind": "measurement", "answer_data": [ "data-footprint-area-basis", "Quantity, unit, net/gross basis, geometry version, method and uncertainty" ] } ], "data_elements": [ { "id": "data-footprint-work-area", "name": "Work area", "description": "Area or facility reference, geometry, coordinate reference system, validity interval and precision. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "geometry", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "data-footprint-site-links", "name": "Site links", "description": "Typed external references, effective intersections, unresolved links and no-land explanation. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "data-footprint-use-basis", "name": "Use basis", "description": "Tenure or use-permission evidence, scope, time and disputed status. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "data-footprint-area-basis", "name": "Area basis", "description": "Quantity, unit, net/gross basis, geometry version, method and uncertainty. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-footprint", "name": "Effective work areas evidence record", "description": "Versioned evidence or reference manifest for effective work areas. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-cultivation", "name": "Crop activity", "description": "Distinguish crop management cycles from living crop stands.", "rationale": "A distinct agricultural decision surface in the proposed dossier; source concepts support the questions, not this exact hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ], "layers": [ { "id": "layer-cycle", "name": "Crop cycle and plan", "description": "A management cycle links one or more cultivated-organism references to activity windows. Perennial, intercropped and repeated-cropping cases need explicit cycle boundaries; an annual calendar is not mandatory.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "finding-cycle", "name": "Crop cycle and plan", "description": "A management cycle links one or more cultivated-organism references to activity windows. Perennial, intercropped and repeated-cropping cases need explicit cycle boundaries; an annual calendar is not mandatory.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "question-cycle-cycle-members", "text": "Which crop stands, fields and management subcycles participate in this campaign?", "kind": "composition", "answer_data": [ "data-cycle-cycle-members", "External stand references, activity-specific crop concept mappings and area shares" ] }, { "id": "question-cycle-cycle-time", "text": "What planned and actual windows define the management cycle, including repeated or perennial harvests?", "kind": "temporal", "answer_data": [ "data-cycle-cycle-time", "Cycle identifier, date precision, planned windows, actual intervals and schedule reference" ] }, { "id": "question-cycle-cycle-state", "text": "What is the current crop-work state and what evidence supports it?", "kind": "state", "answer_data": [ "data-cycle-cycle-state", "Proposed local state, evidence, effective time, confidence and unresolved work" ] }, { "id": "question-cycle-cycle-exception", "text": "How are failed establishment, abandonment or mixed cropping represented without inventing a harvest?", "kind": "exception", "answer_data": [ "data-cycle-cycle-exception", "Exception category, affected scope, loss evidence and revised plan reference" ] } ], "data_elements": [ { "id": "data-cycle-cycle-members", "name": "Cycle members", "description": "External stand references, activity-specific crop concept mappings and area shares. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "data-cycle-cycle-time", "name": "Cycle time", "description": "Cycle identifier, date precision, planned windows, actual intervals and schedule reference. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "data-cycle-cycle-state", "name": "Cycle state", "description": "Proposed local state, evidence, effective time, confidence and unresolved work. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "data-cycle-cycle-exception", "name": "Cycle exception", "description": "Exception category, affected scope, loss evidence and revised plan reference. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-cycle", "name": "Crop cycle and plan evidence record", "description": "Versioned evidence or reference manifest for crop cycle and plan. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-intervention", "name": "Recorded crop interventions", "description": "An intervention assertion distinguishes proposed work from observed completion. Inputs and restriction references document what was recorded; this model provides no treatment instructions or application authority.", "source_refs": [ "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-intervention", "name": "Recorded crop interventions", "description": "An intervention assertion distinguishes proposed work from observed completion. Inputs and restriction references document what was recorded; this model provides no treatment instructions or application authority.", "source_refs": [ "SRC-004", "SRC-007" ], "questions": [ { "id": "question-intervention-intervention-event", "text": "Which agricultural act occurred, on what target, and with what actual completion evidence?", "kind": "event", "answer_data": [ "data-intervention-intervention-event", "Act identifier, type, target, performer, actual interval and evidence reference" ] }, { "id": "question-intervention-plan-variance", "text": "How does the completed intervention relate to its request or planned work?", "kind": "process", "answer_data": [ "data-intervention-plan-variance", "Plan revision, completed extent, omitted portion, deviations and stated reason" ] }, { "id": "question-intervention-intervention-origin", "text": "Who reported the intervention and was the record observed, imported or reconstructed?", "kind": "provenance", "answer_data": [ "data-intervention-intervention-origin", "Reporter, source system, recording time, observation method and reconstruction qualification" ] }, { "id": "question-intervention-intervention-policy", "text": "Which approved-use or protected-area policy references and specialist decisions apply to the recorded intervention?", "kind": "constraint", "answer_data": [ "data-intervention-intervention-policy", "Applicable policy versions, scope, decision references and unknown applicability; no procedural treatment content" ] } ], "data_elements": [ { "id": "data-intervention-intervention-event", "name": "Intervention event", "description": "Act identifier, type, target, performer, actual interval and evidence reference. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "data-intervention-plan-variance", "name": "Plan variance", "description": "Plan revision, completed extent, omitted portion, deviations and stated reason. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "data-intervention-intervention-origin", "name": "Intervention origin", "description": "Reporter, source system, recording time, observation method and reconstruction qualification. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "data-intervention-intervention-policy", "name": "Intervention policy", "description": "Applicable policy versions, scope, decision references and unknown applicability; no procedural treatment content. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-intervention", "name": "Recorded crop interventions evidence record", "description": "Versioned evidence or reference manifest for recorded crop interventions. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-husbandry", "name": "Husbandry activity", "description": "Represent care and collection episodes while retaining organism masters.", "rationale": "A distinct agricultural decision surface in the proposed dossier; source concepts support the questions, not this exact hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "layers": [ { "id": "layer-population", "name": "Episode population and movement links", "description": "Programme scope may use individual or group identification. Effective membership and establishment links support event interpretation without changing an official register or assuming all animals are individually tagged.", "source_refs": [ "SRC-003", "SRC-001" ], "findings": [ { "id": "finding-population", "name": "Episode population and movement links", "description": "Programme scope may use individual or group identification. Effective membership and establishment links support event interpretation without changing an official register or assuming all animals are individually tagged.", "source_refs": [ "SRC-003", "SRC-001" ], "questions": [ { "id": "question-population-population-ids", "text": "Which individual or group identifiers bind the husbandry episode and who issued them?", "kind": "identity", "answer_data": [ "data-population-population-ids", "External subject identifiers, issuer, scheme, official or local status and ambiguity" ] }, { "id": "question-population-membership-snapshot", "text": "Which effective membership interval determines the animals covered by a recorded act?", "kind": "temporal", "answer_data": [ "data-population-membership-snapshot", "Subject or group references, entry/exit times, source revision and uncertain counts" ] }, { "id": "question-population-movement-links", "text": "Which movement records explain changes of establishment or seasonal grazing location?", "kind": "relationship", "answer_data": [ "data-population-movement-links", "External movement identifiers, origin/destination, actual times and register acknowledgement state" ] }, { "id": "question-population-identity-exceptions", "text": "How are lost tags, disputed identity or group splits handled without silently merging animals?", "kind": "exception", "answer_data": [ "data-population-identity-exceptions", "Exception evidence, unresolved mappings, proposed reconciliation and authorized registrar reference" ] } ], "data_elements": [ { "id": "data-population-population-ids", "name": "Population ids", "description": "External subject identifiers, issuer, scheme, official or local status and ambiguity. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-001" ] }, { "id": "data-population-membership-snapshot", "name": "Membership snapshot", "description": "Subject or group references, entry/exit times, source revision and uncertain counts. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-001" ] }, { "id": "data-population-movement-links", "name": "Movement links", "description": "External movement identifiers, origin/destination, actual times and register acknowledgement state. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-001" ] }, { "id": "data-population-identity-exceptions", "name": "Identity exceptions", "description": "Exception evidence, unresolved mappings, proposed reconciliation and authorized registrar reference. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-001" ] } ], "artifacts": [ { "id": "artifact-population", "name": "Episode population and movement links evidence record", "description": "Versioned evidence or reference manifest for episode population and movement links. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-003", "SRC-001" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-care", "name": "Care evidence and specialist restrictions", "description": "Care evidence links husbandry acts, feed provenance and specialist records. Health or welfare concerns and product restrictions are represented at policy level; the dossier cannot diagnose, prescribe or declare an animal fit.", "source_refs": [ "SRC-003", "SRC-004" ], "findings": [ { "id": "finding-care", "name": "Care evidence and specialist restrictions", "description": "Care evidence links husbandry acts, feed provenance and specialist records. Health or welfare concerns and product restrictions are represented at policy level; the dossier cannot diagnose, prescribe or declare an animal fit.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "question-care-care-event", "text": "Which care or feeding act was reported for the episode population?", "kind": "event", "answer_data": [ "data-care-care-event", "Act reference, target snapshot, responsible role, date precision and supporting record" ] }, { "id": "question-care-care-evidence", "text": "What specialist or laboratory evidence is linked to the reported care concern?", "kind": "evidence", "answer_data": [ "data-care-care-evidence", "Protected report references, sampled subjects, provenance, result status and unresolved interpretation" ] }, { "id": "question-care-care-restrictions", "text": "Which authority-issued restriction or withdrawal decision covers the affected animals and outputs?", "kind": "constraint", "answer_data": [ "data-care-care-restrictions", "Decision reference, covered products and subjects, effective interval and supersession state; no dose or treatment recipe" ] }, { "id": "question-care-care-escalation", "text": "Who is responsible for reviewing a welfare concern or completing a required notification?", "kind": "authority", "answer_data": [ "data-care-care-escalation", "Competent role reference, applicable procedure, urgency designation and acknowledgement evidence" ] } ], "data_elements": [ { "id": "data-care-care-event", "name": "Care event", "description": "Act reference, target snapshot, responsible role, date precision and supporting record. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-care-care-evidence", "name": "Care evidence", "description": "Protected report references, sampled subjects, provenance, result status and unresolved interpretation. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-care-care-restrictions", "name": "Care restrictions", "description": "Decision reference, covered products and subjects, effective interval and supersession state; no dose or treatment recipe. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-care-care-escalation", "name": "Care escalation", "description": "Competent role reference, applicable procedure, urgency designation and acknowledgement evidence. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-care", "name": "Care evidence and specialist restrictions evidence record", "description": "Versioned evidence or reference manifest for care evidence and specialist restrictions. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-resources", "name": "Resources and observation", "description": "Bind agricultural inputs and observations to their actual uses.", "rationale": "A distinct agricultural decision surface in the proposed dossier; source concepts support the questions, not this exact hierarchy.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-resource-use", "name": "Input and resource allocations", "description": "Resource-use assertions distinguish receipt, allocation and reported consumption. Water, feed, planting material, nutrients, equipment and labour are linked as applicable; availability does not prove actual use.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-resource-use", "name": "Input and resource allocations", "description": "Resource-use assertions distinguish receipt, allocation and reported consumption. Water, feed, planting material, nutrients, equipment and labour are linked as applicable; availability does not prove actual use.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "questions": [ { "id": "question-resource-use-resource-links", "text": "Which input lots, water sources, equipment or workforce assignments supported the agricultural acts?", "kind": "composition", "answer_data": [ "data-resource-use-resource-links", "Typed external resource references, lot/source identifiers and assigned act references" ] }, { "id": "question-resource-use-use-measures", "text": "What quantities were actually used and on what measurement basis?", "kind": "measurement", "answer_data": [ "data-resource-use-use-measures", "Value, unit, measurement or estimate, method, target extent and time" ] }, { "id": "question-resource-use-use-reconciliation", "text": "Which discrepancies separate received, allocated, unused and consumed inputs?", "kind": "quality", "answer_data": [ "data-resource-use-use-reconciliation", "Quantity basis, unexplained variance, loss/return links and reviewer status" ] }, { "id": "question-resource-use-resource-eligibility", "text": "Which competency, availability or use-permission evidence was required by the adopting profile?", "kind": "requirement", "answer_data": [ "data-resource-use-resource-eligibility", "Role/equipment authorization references, policy version, validity and missing evidence" ] } ], "data_elements": [ { "id": "data-resource-use-resource-links", "name": "Resource links", "description": "Typed external resource references, lot/source identifiers and assigned act references. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "data-resource-use-use-measures", "name": "Use measures", "description": "Value, unit, measurement or estimate, method, target extent and time. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "data-resource-use-use-reconciliation", "name": "Use reconciliation", "description": "Quantity basis, unexplained variance, loss/return links and reviewer status. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "data-resource-use-resource-eligibility", "name": "Resource eligibility", "description": "Role/equipment authorization references, policy version, validity and missing evidence. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-resource-use", "name": "Input and resource allocations evidence record", "description": "Versioned evidence or reference manifest for input and resource allocations. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-observations", "name": "Conditions and measurement context", "description": "Observation references attach evidence to the relevant work area or population. A nearby reading does not establish exposure across the entire operation; estimated, measured and inferred values remain distinct.", "source_refs": [ "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-observations", "name": "Conditions and measurement context", "description": "Observation references attach evidence to the relevant work area or population. A nearby reading does not establish exposure across the entire operation; estimated, measured and inferred values remain distinct.", "source_refs": [ "SRC-006", "SRC-007" ], "questions": [ { "id": "question-observations-observation-binding", "text": "What property, unit and method describe the observation associated with this work?", "kind": "measurement", "answer_data": [ "data-observations-observation-binding", "Observation ID, feature of interest, sensor or method, property definition and unit" ] }, { "id": "question-observations-observation-times", "text": "When did the observed condition occur and when was its result recorded or received?", "kind": "temporal", "answer_data": [ "data-observations-observation-times", "Phenomenon, result and ingestion times, precision and any server-assigned time flag" ] }, { "id": "question-observations-representativeness", "text": "What evidence supports applying this observation to the target field or animal group?", "kind": "spatial", "answer_data": [ "data-observations-representativeness", "Location, sampling extent, interpolation assumption, method and applicability limits" ] }, { "id": "question-observations-observation-quality", "text": "Which calibration, uncertainty, missingness or conflicting result limits interpretation?", "kind": "quality", "answer_data": [ "data-observations-observation-quality", "Quality flags, uncertainty, calibration evidence, missing data and competing observations" ] } ], "data_elements": [ { "id": "data-observations-observation-binding", "name": "Observation binding", "description": "Observation ID, feature of interest, sensor or method, property definition and unit. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "data-observations-observation-times", "name": "Observation times", "description": "Phenomenon, result and ingestion times, precision and any server-assigned time flag. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "data-observations-representativeness", "name": "Representativeness", "description": "Location, sampling extent, interpolation assumption, method and applicability limits. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "data-observations-observation-quality", "name": "Observation quality", "description": "Quality flags, uncertainty, calibration evidence, missing data and competing observations. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-observations", "name": "Conditions and measurement context evidence record", "description": "Versioned evidence or reference manifest for conditions and measurement context. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-outputs", "name": "Output evidence", "description": "Connect collection acts to traceable products and qualified measures.", "rationale": "A distinct agricultural decision surface in the proposed dossier; source concepts support the questions, not this exact hierarchy.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-lineage", "name": "Harvest and recurring collection lineage", "description": "Harvest and recurring collection link agricultural acts to externally identified output lots. A collection may span several sources and may be split or mixed; the operation dossier does not become an inventory ledger.", "source_refs": [ "SRC-005", "SRC-008", "SRC-007" ], "findings": [ { "id": "finding-lineage", "name": "Harvest and recurring collection lineage", "description": "Harvest and recurring collection link agricultural acts to externally identified output lots. A collection may span several sources and may be split or mixed; the operation dossier does not become an inventory ledger.", "source_refs": [ "SRC-005", "SRC-008", "SRC-007" ], "questions": [ { "id": "question-lineage-collection-event", "text": "Which harvest or recurring collection act generated the reported output?", "kind": "event", "answer_data": [ "data-lineage-collection-event", "Act identifier, product type, source cycle or population snapshot and collection interval" ] }, { "id": "question-lineage-output-lineage", "text": "How are output lots linked to source areas or animals and later split or mixed lots?", "kind": "relationship", "answer_data": [ "data-lineage-output-lineage", "External lot references, typed lineage edges, known proportions and unresolved contributions" ] }, { "id": "question-lineage-output-hold", "text": "What segregation or restriction state was reported for each output portion?", "kind": "state", "answer_data": [ "data-lineage-output-hold", "External disposition decision, portion, effective interval, review status and unknown state" ] }, { "id": "question-lineage-handover", "text": "Where does the agricultural handover end and which downstream master accepts the output?", "kind": "interoperability", "answer_data": [ "data-lineage-handover", "Receiving model/system reference, handover event, acknowledgement and unaccepted portion" ] } ], "data_elements": [ { "id": "data-lineage-collection-event", "name": "Collection event", "description": "Act identifier, product type, source cycle or population snapshot and collection interval. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-007" ] }, { "id": "data-lineage-output-lineage", "name": "Output lineage", "description": "External lot references, typed lineage edges, known proportions and unresolved contributions. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-007" ] }, { "id": "data-lineage-output-hold", "name": "Output hold", "description": "External disposition decision, portion, effective interval, review status and unknown state. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-007" ] }, { "id": "data-lineage-handover", "name": "Handover", "description": "Receiving model/system reference, handover event, acknowledgement and unaccepted portion. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-lineage", "name": "Harvest and recurring collection lineage evidence record", "description": "Versioned evidence or reference manifest for harvest and recurring collection lineage. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-005", "SRC-008", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-yield", "name": "Yield, quality and loss assertions", "description": "Collection measures and derived yields retain their calculation basis. Failed crops, repeated collections and withheld portions remain visible; a measured quantity or quality label does not establish safety or market release.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-yield", "name": "Yield, quality and loss assertions", "description": "Collection measures and derived yields retain their calculation basis. Failed crops, repeated collections and withheld portions remain visible; a measured quantity or quality label does not establish safety or market release.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "question-yield-output-measure", "text": "What harvested or collected quantity was measured and under which conditions?", "kind": "measurement", "answer_data": [ "data-yield-output-measure", "Quantity, unit, gross/net basis, moisture or other condition if relevant, method and uncertainty" ] }, { "id": "question-yield-yield-basis", "text": "What denominator and time window support a reported yield without double counting collections?", "kind": "validation", "answer_data": [ "data-yield-yield-basis", "Numerator event set, denominator scope, formula version, units and exclusions" ] }, { "id": "question-yield-quality-evidence", "text": "Which grading or test reference supports the reported output quality?", "kind": "quality", "answer_data": [ "data-yield-quality-evidence", "Grade scheme/version, sampled lot, method, report and limitation" ] }, { "id": "question-yield-output-loss", "text": "What unharvested, lost, retained or rejected output is known and what remains unaccounted for?", "kind": "exception", "answer_data": [ "data-yield-output-loss", "Affected portion, event or estimate, reason, amount basis and reconciliation status" ] } ], "data_elements": [ { "id": "data-yield-output-measure", "name": "Output measure", "description": "Quantity, unit, gross/net basis, moisture or other condition if relevant, method and uncertainty. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-yield-yield-basis", "name": "Yield basis", "description": "Numerator event set, denominator scope, formula version, units and exclusions. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-yield-quality-evidence", "name": "Quality evidence", "description": "Grade scheme/version, sampled lot, method, report and limitation. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "id": "data-yield-output-loss", "name": "Output loss", "description": "Affected portion, event or estimate, reason, amount basis and reconciliation status. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-yield", "name": "Yield, quality and loss assertions evidence record", "description": "Versioned evidence or reference manifest for yield, quality and loss assertions. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Assurance and exceptions", "description": "Bind scoped decisions and hazards without claiming universal compliance.", "rationale": "A distinct agricultural decision surface in the proposed dossier; source concepts support the questions, not this exact hierarchy.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-applicability", "name": "Applicable obligations and decision evidence", "description": "Requirements are versioned profile inputs. Food and nonfood outputs, jurisdiction, species and operation type change applicability. Missing evidence is unknown, never an automatic pass.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "findings": [ { "id": "finding-applicability", "name": "Applicable obligations and decision evidence", "description": "Requirements are versioned profile inputs. Food and nonfood outputs, jurisdiction, species and operation type change applicability. Missing evidence is unknown, never an automatic pass.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "question-applicability-applicable-profile", "text": "Which jurisdiction and activity profile determine the requirements for this operation?", "kind": "requirement", "answer_data": [ "data-applicability-applicable-profile", "Profile issuer/version, geography, activity scope, effective dates and exceptions" ] }, { "id": "question-applicability-decision-evidence", "text": "What competent decision evaluates a restriction or permission for a specific target and time?", "kind": "decision", "answer_data": [ "data-applicability-decision-evidence", "Decision identifier, issuer, evidence revision, evaluated scope, outcome and expiry" ] }, { "id": "question-applicability-applicability-gap", "text": "Which exemption, conflicting rule or unresolved applicability issue remains open?", "kind": "exception", "answer_data": [ "data-applicability-applicability-gap", "Rule references, conflict, basis for exemption claim and designated reviewer" ] }, { "id": "question-applicability-assurance-gaps", "text": "What evidence is still needed before the record can support an assurance claim?", "kind": "validation", "answer_data": [ "data-applicability-assurance-gaps", "Missing evidence list, affected claims, verification status and responsible role" ] } ], "data_elements": [ { "id": "data-applicability-applicable-profile", "name": "Applicable profile", "description": "Profile issuer/version, geography, activity scope, effective dates and exceptions. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-applicability-decision-evidence", "name": "Decision evidence", "description": "Decision identifier, issuer, evidence revision, evaluated scope, outcome and expiry. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-applicability-applicability-gap", "name": "Applicability gap", "description": "Rule references, conflict, basis for exemption claim and designated reviewer. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-applicability-assurance-gaps", "name": "Assurance gaps", "description": "Missing evidence list, affected claims, verification status and responsible role. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-applicability", "name": "Applicable obligations and decision evidence evidence record", "description": "Versioned evidence or reference manifest for applicable obligations and decision evidence. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-hazards", "name": "Hazard and corrective-action references", "description": "The dossier records concerns about contamination, biosecurity, welfare, environmental effects or worker exposure at policy level. It links competent response records; a local closure does not prove a hazard was eliminated.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-hazards", "name": "Hazard and corrective-action references", "description": "The dossier records concerns about contamination, biosecurity, welfare, environmental effects or worker exposure at policy level. It links competent response records; a local closure does not prove a hazard was eliminated.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "questions": [ { "id": "question-hazards-hazard-report", "text": "What observed concern or incident affects the operation and how reliable is the report?", "kind": "evidence", "answer_data": [ "data-hazards-hazard-report", "Concern category, affected scope, source evidence, observation time and confidence" ] }, { "id": "question-hazards-response-link", "text": "Which response procedure and assigned role govern follow-up of this concern?", "kind": "process", "answer_data": [ "data-hazards-response-link", "External procedure/action case, accountable role, policy priority and current acknowledgement" ] }, { "id": "question-hazards-corrective-status", "text": "What outstanding corrective evidence prevents closing the local concern record?", "kind": "state", "answer_data": [ "data-hazards-corrective-status", "Action references, evidence links, remaining issues and competent reviewer" ] }, { "id": "question-hazards-sensitivity", "text": "Which sensitive locations, worker details or animal-health records require restricted disclosure?", "kind": "security", "answer_data": [ "data-hazards-sensitivity", "Data categories, recipients, purpose, access-policy reference and redaction needs" ] } ], "data_elements": [ { "id": "data-hazards-hazard-report", "name": "Hazard report", "description": "Concern category, affected scope, source evidence, observation time and confidence. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-hazards-response-link", "name": "Response link", "description": "External procedure/action case, accountable role, policy priority and current acknowledgement. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-hazards-corrective-status", "name": "Corrective status", "description": "Action references, evidence links, remaining issues and competent reviewer. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-hazards-sensitivity", "name": "Sensitivity", "description": "Data categories, recipients, purpose, access-policy reference and redaction needs. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-hazards", "name": "Hazard and corrective-action references evidence record", "description": "Versioned evidence or reference manifest for hazard and corrective-action references. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Reporting and continuity", "description": "Prepare limited projections and preserve attributable corrections.", "rationale": "A distinct agricultural decision surface in the proposed dossier; source concepts support the questions, not this exact hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-reporting", "name": "Reporting and sharing projections", "description": "Statistical, advisory and traceability views have different purposes and scopes. Preparing a view neither files a return nor grants access to the whole farm record. Excluded or unknown data must be visible.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "findings": [ { "id": "finding-reporting", "name": "Reporting and sharing projections", "description": "Statistical, advisory and traceability views have different purposes and scopes. Preparing a view neither files a return nor grants access to the whole farm record. Excluded or unknown data must be visible.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "question-reporting-export-binding", "text": "Which receiving schema and vocabulary versions define this export?", "kind": "interoperability", "answer_data": [ "data-reporting-export-binding", "Recipient format/version, concept mappings, units, unsupported fields and mapping losses" ] }, { "id": "question-reporting-disclosure-basis", "text": "Which recipient and purpose authorize the proposed disclosure?", "kind": "access", "answer_data": [ "data-reporting-disclosure-basis", "Access policy, recipient identity, lawful or contractual basis, scope and validity" ] }, { "id": "question-reporting-report-basis", "text": "Which reference period and aggregation rules prevent the view from double counting area, animals or output?", "kind": "validation", "answer_data": [ "data-reporting-report-basis", "Period, contributing record revisions, distinct-count rules, overlap treatment and missingness" ] }, { "id": "question-reporting-export-manifest", "text": "What export manifest identifies the exact records and redactions used?", "kind": "provenance", "answer_data": [ "data-reporting-export-manifest", "Projection ID, source revisions, generated time, digest and redaction or suppression log" ] } ], "data_elements": [ { "id": "data-reporting-export-binding", "name": "Export binding", "description": "Recipient format/version, concept mappings, units, unsupported fields and mapping losses. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "data-reporting-disclosure-basis", "name": "Disclosure basis", "description": "Access policy, recipient identity, lawful or contractual basis, scope and validity. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "data-reporting-report-basis", "name": "Report basis", "description": "Period, contributing record revisions, distinct-count rules, overlap treatment and missingness. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "data-reporting-export-manifest", "name": "Export manifest", "description": "Projection ID, source revisions, generated time, digest and redaction or suppression log. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-reporting", "name": "Reporting and sharing projections evidence record", "description": "Versioned evidence or reference manifest for reporting and sharing projections. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-record-life", "name": "Record correction, closure and retention", "description": "Record lifecycle and real-world activity are distinct. Corrections preserve attribution and supersession while retention policy limits personal or sensitive payloads. Closing a dossier does not close an official register or authorize produce release.", "source_refs": [ "SRC-007", "SRC-005", "SRC-004" ], "findings": [ { "id": "finding-record-life", "name": "Record correction, closure and retention", "description": "Record lifecycle and real-world activity are distinct. Corrections preserve attribution and supersession while retention policy limits personal or sensitive payloads. Closing a dossier does not close an official register or authorize produce release.", "source_refs": [ "SRC-007", "SRC-005", "SRC-004" ], "questions": [ { "id": "question-record-life-dossier-transition", "text": "What evidence justifies closing, reopening or superseding the operation dossier?", "kind": "lifecycle", "answer_data": [ "data-record-life-dossier-transition", "Previous/new state, authority, reason, supporting evidence and unresolved linked work" ] }, { "id": "question-record-life-correction-chain", "text": "Which prior assertion is corrected and how are affected reports identified?", "kind": "provenance", "answer_data": [ "data-record-life-correction-chain", "Original/correcting record IDs, reason, author, effective and recording times and dependent views" ] }, { "id": "question-record-life-retention-basis", "text": "What retention rule or hold governs each local record and linked artifact?", "kind": "retention", "answer_data": [ "data-record-life-retention-basis", "Policy version, trigger, scope, hold status, disposal authority and external master responsibility" ] }, { "id": "question-record-life-disposal-evidence", "text": "What approved redaction or erasure preserves only the lawful minimum of reference continuity?", "kind": "privacy", "answer_data": [ "data-record-life-disposal-evidence", "Decision reference, payload scope, execution receipt, residual-copy status and minimal tombstone justification" ] } ], "data_elements": [ { "id": "data-record-life-dossier-transition", "name": "Dossier transition", "description": "Previous/new state, authority, reason, supporting evidence and unresolved linked work. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-005", "SRC-004" ] }, { "id": "data-record-life-correction-chain", "name": "Correction chain", "description": "Original/correcting record IDs, reason, author, effective and recording times and dependent views. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-005", "SRC-004" ] }, { "id": "data-record-life-retention-basis", "name": "Retention basis", "description": "Policy version, trigger, scope, hold status, disposal authority and external master responsibility. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-005", "SRC-004" ] }, { "id": "data-record-life-disposal-evidence", "name": "Disposal evidence", "description": "Decision reference, payload scope, execution receipt, residual-copy status and minimal tombstone justification. Candidate answer group; nested schema and applicable cardinality require an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-005", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-record-life", "name": "Record correction, closure and retention evidence record", "description": "Versioned evidence or reference manifest for record correction, closure and retention. Sensitive source payloads remain in authorized stores.", "media_or_form": [ "Structured record", "Document or external evidence reference" ], "serial": true, "identity_strategy": "Use authoritative master-system identifier first, then governed IRI, then Dimension-assigned UUID or ULID; keep stable logical ID and separate revision ID. A date or filename is not identity.", "source_refs": [ "SRC-007", "SRC-005", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-open-dossier", "name": "Open an operation dossier", "description": "Proposed, unimplemented local operation. Create the bounded local aggregate with selected modules and declared unknowns.", "inputs": [ "Dossier master ID", "Management scope and interval", "Party and authority references" ], "outputs": [ "New local dossier revision", "Missing-context report", "Refusal with reason when required authority, evidence or version checks fail" ], "preconditions": [ "Authenticated role with the required local scope and expected dossier revision", "Stable identity is resolved and duplicate candidates reviewed", "Module non-applicability is explicit" ], "effects": [ "Creates only the local dossier; creates no holding or official registration" ], "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "function-bind-context", "name": "Bind effective production context", "description": "Proposed, unimplemented local operation. Attach revision-qualified work areas, crop-cycle and population references.", "inputs": [ "Current dossier revision", "Site/organism references", "Effective intervals" ], "outputs": [ "New context revision", "Unresolved-binding report", "Refusal with reason when required authority, evidence or version checks fail" ], "preconditions": [ "Authenticated role with the required local scope and expected dossier revision", "References are readable under policy", "Overlaps and disputed identities are not silently merged" ], "effects": [ "Adds local bindings without modifying land, organism or schedule masters" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] }, { "id": "function-record-work", "name": "Record agricultural work evidence", "description": "Proposed, unimplemented local operation. Append an evidence-qualified assertion about a crop or husbandry act.", "inputs": [ "External act reference", "Targets and actual extent", "Reporter and evidence" ], "outputs": [ "Recorded assertion revision", "Uncertain or duplicate-evidence flags", "Refusal with reason when required authority, evidence or version checks fail" ], "preconditions": [ "Authenticated role with the required local scope and expected dossier revision", "Evidence distinguishes plans from actual events", "Specialist and controlled-input content remains reference-only" ], "effects": [ "Records the claim locally; does not execute machinery, treatment or register changes" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "function-link-measure", "name": "Link observation and resource evidence", "description": "Proposed, unimplemented local operation. Associate supplied measurements and resource-use claims with the relevant work.", "inputs": [ "Observation/resource references", "Property and unit", "Target and time basis" ], "outputs": [ "Qualified evidence association", "Unit or representativeness issues", "Refusal with reason when required authority, evidence or version checks fail" ], "preconditions": [ "Authenticated role with the required local scope and expected dossier revision", "Observation time and ingestion time distinguished", "Uncertainty and source quality retained" ], "effects": [ "Creates associations; does not certify measurement truth or alter sensors" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "function-trace-output", "name": "Prepare output lineage view", "description": "Proposed, unimplemented local operation. Traverse supplied collection and lot links to show known origins and missing edges.", "inputs": [ "Collection event references", "Source snapshots", "Output lot relationships" ], "outputs": [ "Lineage projection", "Missing or contradictory origin links", "Refusal with reason when required authority, evidence or version checks fail" ], "preconditions": [ "Authenticated role with the required local scope and expected dossier revision", "Read permission covers every included edge", "Mixed or split quantities carry a declared basis" ], "effects": [ "Produces a local read projection; does not release, sell, recall or move product" ], "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "function-prepare-report", "name": "Prepare a scoped operation report", "description": "Proposed, unimplemented local operation. Build a proposed statistical, advisory or traceability projection under an explicit mapping.", "inputs": [ "Recipient and purpose", "Profile and report period", "Source revision set" ], "outputs": [ "Local draft projection", "Manifest of exclusions and unresolved mappings", "Refusal with reason when required authority, evidence or version checks fail" ], "preconditions": [ "Authenticated role with the required local scope and expected dossier revision", "Recipient access policy and aggregation basis supplied", "Incomplete required inputs yield an incomplete report" ], "effects": [ "Writes a local draft only; external filing and transmission remain separate actions" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "function-revise-close", "name": "Correct or close the local dossier", "description": "Proposed, unimplemented local operation. Append a reasoned correction or local lifecycle decision and identify dependent views.", "inputs": [ "Expected current revision", "Correction or closure request", "Authority and supporting evidence" ], "outputs": [ "New revision or refusal", "Affected-view list", "Refusal with reason when required authority, evidence or version checks fail" ], "preconditions": [ "Authenticated role with the required local scope and expected dossier revision", "Concurrency token matches and scoped authority is valid", "Closure does not override unresolved external restrictions", "Retention holds and payload policy are respected" ], "effects": [ "Supersedes local assertions with attribution; no physical reversal, erasure execution or external legal effect" ], "source_refs": [ "SRC-005", "SRC-007" ] } ], "composition": [ { "target": "WM-LIV-009", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference crop stands and farm animals; retain biological identity and lifecycle in their own master.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-PLC-002", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference parcels intersecting effective management areas; this dossier does not establish title.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-EAR-003", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference soil characterization and sampling records; do not own soil state or its observation lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "WM-BLT-008", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference facilities and sites as operational context, using the current model ID instead of the ambiguous legacy alias.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-ACT-002", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference atomic acts with their own identities and authority; aggregate only agriculture-specific evidence.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "WM-ACT-008", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference plans and schedules; no scheduling engine or mandatory seasonal end date.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "WM-ACT-010", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference downstream processing runs after a declared boundary handover.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "WM-FLW-003", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference downstream food-chain events; do not duplicate logistics, recall or inventory functions.", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] }, { "target": "WM-OBJ-004", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference food output product masters when applicable; agriculture can also yield nonfood outputs.", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] }, { "target": "WM-PER-001", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference people in management, workforce or stewardship roles without reproducing their profiles.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference responsible organizations without treating management as ownership of every resource.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "WM-XCT-001", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference stewardship and ownership policy; local role bindings do not adjudicate title.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-XCT-002", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference recipient-specific access and consent decisions; do not implement their evaluation.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-XCT-004", "relation": "REFERENCE", "purpose": "Proposed optional binding, not a registry-ledger edge. Reference access-audit receipts; the audit trail is mastered by the external audit service.", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "target": "AGROVOC", "relation": "ALIGN", "purpose": "Concept mapping only; record release, language and unmatched terms.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "GS1 EPCIS", "relation": "ALIGN", "purpose": "Proposed visibility-event mapping only; retain declared schema version and correction semantics.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "OGC SensorThings API 1.1", "relation": "ALIGN", "purpose": "Proposed observation linkage only; preserve source timestamps and clock-assignment qualifications.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "W3C PROV-O", "relation": "ALIGN", "purpose": "Proposed provenance mapping only; attribution and revision do not certify truth.", "required": false, "source_refs": [ "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Identify the responsible farming person or organization and separate record steward, manager, land owner and keeper roles", "Declare the operation boundary, selected modules, profile versions and external master bindings", "Provide scoped authority, access, retention, specialist escalation and unknown-value rules", "State that this package is a noncanonical reviewable draft with absent external review and source/version holds" ], "namespace_guidance": "Use an adopting-Dimension namespace for operation dossier, local assertions and revisions. Do not mint official animal, parcel or product identifiers by implication.", "registry_links": [ "vr.wm-act-011", "WM-LIV-009", "WM-ACT-002", "WM-ACT-008" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve source identifiers, units, original values and time precision; normalized values retain conversion provenance", "Separate plan, actual act, observation, interpretation and competent decision", "Unknown, absent, not applicable and zero are distinct; retain contradictory evidence" ], "patch_rules": [ "Require expected revision, scoped role, patch reason and affected subject; refuse stale writes", "Append corrections with supersession links; no silent replacement of submitted or shared evidence", "Recompute or mark stale dependent projections after correcting input evidence" ], "compatibility_rules": [ "Version profile and mappings independently from data revisions", "Changing management boundary, role meaning, units or selected modules needs explicit migration review", "Target masters and identifier aliases require confirmed versioned bindings; unresolved neighbors remain visible" ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with issuer and namespace", "Governed global identifier or IRI", "Dimension-assigned UUID or ULID with alias reconciliation" ], "timestamp_rule": "Instants use RFC 3339 with seconds and an explicit offset or Z. Keep event time, observation/result time and ingestion time separate. Preserve source dates and uncertain intervals at their actual precision; do not invent midnight timestamps. Mark server-assigned times explicitly.", "serial_naming_rule": "Stable logical record ID plus independent revision ID; optional descriptive labels and dates never determine identity.", "integrity_rule": "Keep digest, media type, source revision, origin and access class with evidence links. A digest proves byte continuity only. Sensitive payloads follow retention policy rather than indefinite history." }, "policies": [ "Only evidence-backed local record maintenance is in scope; specialist judgement and external acts need the relevant authority", "Controlled inputs, treatments, biosecurity and harmful interventions remain policy and evidence references; do not supply prescriptions or executable instructions", "A clean record, passed schema, elapsed date or closed dossier cannot prove safe product release or legal compliance", "Preserve provenance for estimates, inferred conditions and offline reconstructed events; do not convert them to observations", "No unrestricted sharing of precise farm locations, personal workforce data, commercial yields or animal-health information", "Species, jurisdiction, crop, food/nonfood and smallholder or landless profiles require qualified adoption review" ], "crud": { "read": [ "Resolve current revision, source qualifications and recipient scope; return redacted views and unresolved references explicitly" ], "create": [ "Resolve dossier identity and authority; declare selected modules and bounded interval; allow open intervals and missing actual outcomes" ], "update": [ "Append attributed revisions after concurrency checks; preserve source claims, reversals and disputed bindings" ], "delete": [ "Apply the adopting-Dimension retention and disposal policy to local payloads, checking legal or investigation holds first", "Authorized storage and disposition services execute erasure; this model records their receipt and minimal lawful tombstone only", "Retiring a dossier does not delete external organism, land, product, official register or audit masters; minimize personal data in retained continuity records" ] }, "roles": [ { "name": "Operation manager", "responsibilities": [ "Declare scope and accountable roles; review work completeness without substituting for specialist authority" ] }, { "name": "Record steward", "responsibilities": [ "Resolve identity and provenance; manage local corrections and retention-policy bindings" ] }, { "name": "Recorder or contractor", "responsibilities": [ "Submit attributable work evidence within delegated scope; mark unknowns and estimates" ] }, { "name": "Qualified specialist", "responsibilities": [ "Review applicable agronomic, veterinary, safety or regulatory questions within actual competence" ] }, { "name": "Evidence reviewer", "responsibilities": [ "Inspect contradictory inputs, missing trace links and mapping losses" ] }, { "name": "Authorized recipient", "responsibilities": [ "Use only the permitted projection and purpose; preserve qualifiers" ] } ], "access": { "default_rule": "Deny disclosure unless an applicable scoped policy permits the authenticated recipient and purpose. Management alone does not authorize access to every linked record.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory disclosure or urgent escalation must cite the applicable authority and scope; record what was disclosed", "Public or buyer views require explicit minimization and may omit sensitive field locations and personal information" ], "audit_requirements": [ "Record actor, purpose, scope, source revisions, policy decision reference and result through the bound access-audit service", "Keep evidence of rejected and partial exports without leaking protected payloads into logs" ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Authority and profile bindings", "Review holds" ], "read_order": [ "AGENTS.md and applicable owner/Dimension policies", "spec.yaml boundary, review holds and external bindings", "Relevant bundles, evidence revisions and permitted local operations" ] } }, "coverage": { "claim": "Source-grounded proposed aggregate for a bounded agricultural operation dossier, with selected crop and husbandry modules and external organism, land, act and output masters. Separate frozen local no-tools self-audit completed. This remains a noncanonical reviewable draft with independent-review, source/version, specialist-profile and executable-conformance holds; it is not an operational compliance or treatment engine.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable dossier identity and external issuer-qualified subject references; official registration is conditional." }, { "dimension": "lifecycle", "status": "covered", "notes": "Local opening, correction, closure and reopening remain separate from biological state and official registers." }, { "dimension": "relationships", "status": "covered", "notes": "Proposed optional bindings preserve land, organism, act, schedule, product and policy masters; registry relation ledger has no matching rows." }, { "dimension": "temporal", "status": "covered", "notes": "Plan versus actual intervals, source precision, reference periods, membership and observation/result/ingestion times." }, { "dimension": "provenance", "status": "covered", "notes": "Claims, import origin, revisions, measurement basis and dependent projection manifests." }, { "dimension": "ownership", "status": "covered", "notes": "Manager, land owner, keeper, contractor and record steward are distinct role references." }, { "dimension": "validation", "status": "gap", "notes": "Research schema is testable; nested instance schemas, mandatory profile fields and executable mappings are unfinished." }, { "dimension": "access", "status": "covered", "notes": "Recipient and purpose scopes, sensitivity, redaction and delegated access-audit receipts." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Policy-bound payload disposal, legal holds and minimal lawful continuity; no external-master deletion." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual AGROVOC, EPCIS, SensorThings and PROV-O alignments need version pins and tested mappings." }, { "dimension": "physical properties and recognition", "status": "covered", "notes": "Work footprint, resource and output quantities are qualified by units and evidence; biological properties remain delegated." }, { "dimension": "capability and behavior", "status": "covered", "notes": "Seven proposed local operations distinguish preconditions and evidence effects from physical execution." }, { "dimension": "agricultural diversity", "status": "gap", "notes": "Mixed, perennial, mobile and landless cases are considered; specialist species and production-system profiles remain incomplete." }, { "dimension": "source currency and independent review", "status": "gap", "notes": "Historical sources and version ambiguities remain explicit; direct HTTP unmeasured and second-provider review waived." } ], "known_omissions": [ "Independent second-provider review is absent; local Codex self-audit cannot replace it", "FAO WCA 2030 changes have not been reconciled; FAO WCA 2020 is used only as historical conceptual evidence", "Current law, WOAH edition and EPCIS errata/version matching need verification; direct HTTP is unmeasured in this sandbox", "Nested data schemas, unit conversions, vocabulary releases, machinery exchange, animal identification technology and executable conformance are not implemented", "Detailed agronomy, water rights, nutrient balances, emissions accounting, worker safety, welfare and disease policy need qualified specialist profiles", "Aquaculture, forestry and capture fisheries need separate boundary research; no universal all-agriculture claim" ], "conflicts": [], "regional_assumptions": [ "No universal holding registration, individual animal tag, calendar-year cycle, food output or cadastral field is assumed", "European hygiene texts illustrate record needs only; the historical consolidation and nonbinding guidance do not establish current law anywhere", "International statistical categories and traceability standards are optional alignments, not globally binding operating rules" ], "adversarial_checks": [ "A failed crop and zero harvest remain valid without fabricating an output", "A landless herd and seasonally mobile group retain identity without invented parcels", "A perennial crop and several harvests cannot force one annual cycle or double-count physical land", "A contractor may report work without owning the farm or acquiring disclosure rights", "A shared legacy alias cannot absorb the separately registered cultivated-organism model", "A mixed lot with incomplete origin is explicitly incomplete, never declared fully traced", "A corrected reading invalidates dependent claims without proving the original event did not occur", "An elapsed withdrawal date and dossier closure never automatically authorize product release" ] }, "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 dossier groups managed agricultural activity under a declared scope and interval, with activity references and domain-specific evidence. It is not the permanent holding, an organism or one atomic act. The registry standalone-mm value is not a research subject-kind enum. The aggregate is an explicit local modeling choice and preserves the separately registered cultivated-organism boundary." }, "decisions": [ { "concept": "Operation dossier root", "disposition": "accepted as proposed aggregate", "rationale": "The declared scope, module selection and interval make the composite dossier distinguishable from a statistical holding or single event; no external standard is claimed to mandate this hierarchy." }, { "concept": "Shared K9 legacy alias", "disposition": "reconciled", "rationale": "The frozen registry and split record identify a separate cultivated-organism sibling. Local activity and membership evidence do not duplicate biological identity or lifecycle." }, { "concept": "Legacy Site and Act bindings", "disposition": "qualified", "rationale": "The obsolete Site alias is not reused and the aggregate does not inherit an atomic act. Proposed optional current model references preserve separate target ownership." }, { "concept": "Universal official identifiers", "disposition": "rejected", "rationale": "The draft permits local issuer-qualified identifiers, group schemes and applicability uncertainty. It does not assume every holding is registered or every animal individually tagged." }, { "concept": "Land and management footprint", "disposition": "accepted", "rationale": "Effective work areas, parcel intersections and use evidence are separate from legal title. Mobile and landless production remain representable without invented land records." }, { "concept": "Crop and husbandry temporal cases", "disposition": "accepted", "rationale": "Questions distinguish plans, actual acts, flexible cycles, dated population membership and observations, including failure, partial completion and repeated or perennial collection." }, { "concept": "Measurements and computed yield", "disposition": "accepted with evidence limits", "rationale": "Units, denominator, period, source method, uncertainty and server-assigned times remain explicit. Measurements or estimates cannot silently become universal condition or safety claims." }, { "concept": "Output lineage and handover", "disposition": "accepted", "rationale": "Split and mixed outputs retain external lot and product references with missing origins visible. On-farm location does not automatically determine the processing boundary." }, { "concept": "Specialist authority and controlled inputs", "disposition": "restricted to policy evidence", "rationale": "The draft records policy and competent-decision references and escalation roles. It provides no treatment recipe, prescription, machinery command or automatic release based on elapsed time." }, { "concept": "Proposed function effects", "disposition": "accepted as unimplemented local operations", "rationale": "All seven functions state authority, evidence and revision preconditions, refusal results and bounded local effects. No function files reports or modifies external registers or product state." }, { "concept": "Access and record disposal", "disposition": "accepted with adopting-policy dependency", "rationale": "Recipient and purpose restrictions are distinct from management roles. Revision continuity is limited by lawful payload retention, holds and minimal tombstones; external masters remain separate." }, { "concept": "Primary-source currency", "disposition": "limited and held", "rationale": "Selected browser readings support the admitted concepts, but direct HTTP is unmeasured, FAO 2030 is unreconciled, the legal text is historical and WOAH/EPCIS version pins remain unresolved." }, { "concept": "Instance schemas and specialist profiles", "disposition": "deferred", "rationale": "Candidate data groups and conceptual alignments are research structure only. Nested schemas, required profile fields, regulatory applicability and adversarial fixtures remain unfinished." }, { "concept": "External provider agreement", "disposition": "waived and held", "rationale": "Claude and Grok were skipped with zero attempts by owner instruction. This separate Codex self-audit adds no new facts and cannot count as an independent second-provider review." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not independent review.", "Source and version verification remains incomplete. Direct HTTP was not attempted in the owner-reported blocked sandbox, so no HTTP status was measured. Browser evidence is documented separately. Reconcile WCA 2030, current legal texts, WOAH edition and the EPCIS 2.0.1 URL versus Release 2.0 PDF before asserting currency.", "Qualified adopting-profile review is required for the operation-dossier boundary, jurisdiction, species, crop system, food/nonfood outputs, environmental and worker obligations, specialist authority, access and retention. No safety, treatment or compliance certification is claimed.", "Nested instance schemas, mandatory profile fields, pinned neighbor bindings, vocabulary releases, executable mappings, unit calculations and adversarial fixtures are incomplete. Candidate local functions are unimplemented; schema-valid research does not establish operational conformance.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Restore independent external review before any canonical or publishable-draft promotion.", "Verify source URLs and exact editions outside the sandbox, reconcile WCA 2030 and current local legal applicability, and resolve EPCIS URL/PDF version identity.", "Develop qualified profiles for crop, livestock, smallholder, mobile and nonfood operations, with explicit decisions on additional aquaculture and forestry boundaries.", "Implement and test instance schemas and bindings against failed crops, repeated harvests, group splits, mixed lots, stale observations, correction propagation and lawful record disposal." ] }, "statistics": { "sources": 8, "bundles": 7, "layers": 14, "findings": 14, "questions": 56, "artifacts": 14, "functions": 7 } }