# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T21:18:02Z", "synthesisSha256": "e9c02755f23d36d1f4aa5fb88df40c0363261e64d4d65d3cad238928ba85a2cb", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-FLW-013", "registryId": "vr.wm-flw-013", "name": "Supply-chain Trace / Chain of Custody", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "pattern", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.FLW.LOG" ], "tags": [ "supply", "chain", "trace", "custody", "phy.flw.log" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-flw-013-supply-chain-trace-chain-of-custody/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-flw-013", "model": { "registry_id": "vr.wm-flw-013", "model_id": "WM-FLW-013", "name": "Supply-chain Trace / Chain of Custody", "entry_kind": "pattern", "purpose": "Provide a reusable governed pattern for linking traceable objects, events, custody assertions, transformations, locations, parties and evidence into a federated time-aware trace graph with qualified queries, gaps and corrections.", "scope_statement": "Owns trace scope, semantic kind and graph revision; trace objective, range, direction and chain-of-custody profile; typed bindings to objects, events, parties, places, movements and evidence; aggregation, transformation and custody edges; qualified clocks, sources, proof and quality; gaps, duplicates, conflicts, error declarations and successors; backward, forward, path and exposure query results; federation, access, retention and loss-aware projections. Products, lots, serials, handling units, shipments, inventory movements, journeys, locations, parties, generic events, observations, custody handovers, documents, credentials, incidents, recall actions, claims and evidence masters remain external.", "in_scope": [ "Trace scope, graph and result identity, objective, range, direction, semantic kind, revision and successor lineage", "Typed object-event graph, aggregation, transformation, location, party, custody, clock, source, evidence, proof, quality, gap and conflict assertions", "Backward and forward query, exposure analysis, federation, privacy, access, retention, audit and interoperability" ], "out_of_scope": [ "Owning product, lot, serial, handling unit, shipment, movement, journey, place, party, event, observation, handover, document, credential, incident, recall action, claim or evidence lifecycles", "Equating traceability with tracking, custody with ownership, aggregation with transformation, event assertion with verified fact, physical flow with mass balance or book-and-claim, or exposure result with recall decision", "Executing physical custody, product certification, identity issuance, evidence storage, recall, enforcement, protected disclosure or irreversible deletion" ], "boundary_notes": [ { "neighbor": "WM-FLW-004 Goods Movement / Logistics", "distinction": "Goods Movement owns physical logistics flow. Trace / Chain of Custody links source-qualified histories across movements and organizations; the candidate parent signal remains under review.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-016" ] }, { "neighbor": "WM-ACT-015 Occurrence / Event", "distinction": "The trace pattern composes typed event references and graph edges. Generic event identity, occurrence semantics and lifecycle remain external; the candidate COMPOSE relation is accepted only in that limited sense.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-021" ] }, { "neighbor": "WM-FLW-011 Shipment / Consignment", "distinction": "Shipment / Consignment owns commercial or transport grouping and status assertions. The trace graph references it as an object and event context without importing that lifecycle.", "source_refs": [ "SRC-007", "SRC-008", "SRC-016", "SRC-017", "SRC-018" ] }, { "neighbor": "WM-FLW-012 Inventory Movement", "distinction": "Inventory Movement owns one stock-affecting transition and external posting reference. The trace graph links movements across organizations but does not calculate stock positions or post ledgers.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-014" ] }, { "neighbor": "Custody handover and ownership", "distinction": "The pattern links custody intervals, transfers, acceptance and refusal assertions. The handover event and legal ownership remain independently mastered and must not be inferred from location alone.", "source_refs": [ "SRC-003", "SRC-010", "SRC-012", "SRC-013", "SRC-021" ] }, { "neighbor": "Evidence, credential and certification", "distinction": "Artifacts, digests, signatures, credentials and verification results are references that support assertions. Their issuance, storage, cryptographic validity, certification scope and legal effect remain external.", "source_refs": [ "SRC-013", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] }, { "neighbor": "Recall, investigation and enforcement", "distinction": "The pattern may derive a qualified affected set with gaps and uncertainty. Accountable domain authorities own recall, alert, enforcement, remedy and public-disclosure decisions.", "source_refs": [ "SRC-003", "SRC-006", "SRC-012", "SRC-014", "SRC-015" ] } ] }, "sources": [ { "id": "SRC-001", "title": "EPCIS Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/epcis/2.0.1/", "version_or_date": "EPCIS 2.0.1, 1 July 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines interoperable visibility events, event and record clocks, sources, destinations, queries and error declarations." }, { "id": "SRC-002", "title": "Core Business Vocabulary Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/cbv/2.0.0/", "version_or_date": "CBV 2.0.0, June 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines controlled business steps, dispositions, source and destination types used with EPCIS." }, { "id": "SRC-003", "title": "GS1 Global Traceability Standard", "organization": "GS1", "url": "https://ref.gs1.org/standards/global-traceability/2.0.0/", "version_or_date": "Release 2.0, August 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines traceable objects, critical tracking events, key data elements and one-up one-down responsibilities." }, { "id": "SRC-004", "title": "EPCIS ObjectEvent linked-data definition", "organization": "GS1", "url": "https://ref.gs1.org/epcis/ObjectEvent", "version_or_date": "EPCIS linked-data model accessed 2026-09-06", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines instance and class-level observations, actions, locations, quantities and business context." }, { "id": "SRC-005", "title": "EPCIS AggregationEvent linked-data definition", "organization": "GS1", "url": "https://ref.gs1.org/epcis/AggregationEvent", "version_or_date": "EPCIS linked-data model accessed 2026-09-06", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines time-qualified parent-child aggregation and disaggregation assertions." }, { "id": "SRC-006", "title": "EPCIS TransformationEvent linked-data definition", "organization": "GS1", "url": "https://ref.gs1.org/epcis/TransformationEvent", "version_or_date": "EPCIS linked-data model accessed 2026-09-06", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines input-output transformation events and transformation identifiers." }, { "id": "SRC-007", "title": "Integrated Track and Trace for Multi-Modal Transportation BRS", "organization": "UN/CEFACT", "url": "https://unece.org/trade/documents/2022/09/business-requirements-specifications-brs-integrated-track-and-trace-multi", "version_or_date": "Approved version 1.1, 14 September 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines cross-industry tracking of identified trade and transport objects across multimodal journeys." }, { "id": "SRC-008", "title": "White Paper on Integrated Track and Trace for Multimodal Transportation", "organization": "UN/CEFACT", "url": "https://unece.org/trade/publications/white-paper-integrated-track-and-trace-multimodal-transportation-ecetrade466", "version_or_date": "ECE/TRADE/466, January 2022", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Explains end-to-end visibility across shipments, consignments, assets, modes and organizations." }, { "id": "SRC-009", "title": "Visibility and Collaborative Planning in Multimodal Supply Chain Operations BRS", "organization": "UN/CEFACT", "url": "https://unece.org/trade/documents/2026/07/standards/brs-visibility-and-collaborative-planning-multimodal-supply-chain", "version_or_date": "BRS published July 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines a transport event registry and scoped auditable delegation for multimodal visibility." }, { "id": "SRC-010", "title": "ISO 22095:2020 Chain of custody", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/72532.html", "version_or_date": "ISO 22095:2020 with Amendment 1:2026 noted", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines generic chain-of-custody terminology, system design and models for materials and products." }, { "id": "SRC-011", "title": "ISO 22095-2:2026 Chain of custody mass balance", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/84427.html", "version_or_date": "ISO 22095-2:2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines mass-balance system boundaries, attribution, conversion factors, credit methods and claims." }, { "id": "SRC-012", "title": "ISO 22005:2007 Feed and food traceability", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/36297.html", "version_or_date": "ISO 22005:2007, confirmed 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines principles and requirements for determining product or component history and location." }, { "id": "SRC-013", "title": "ISO 28000:2022 Security and resilience", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/79612.html", "version_or_date": "ISO 28000:2022 with Amendment 1:2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines supply-chain-relevant security management requirements and controls." }, { "id": "SRC-014", "title": "FSMA Food Traceability Final Rule", "organization": "United States Food and Drug Administration", "url": "https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods", "version_or_date": "21 CFR Part 1 Subpart S; page accessed 2026-09-06", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines food critical tracking events, key data elements, traceability lots and record provision duties." }, { "id": "SRC-015", "title": "Regulation EU 2024/1781 Ecodesign for Sustainable Products", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/reg/2024/1781/2024-06-28/eng", "version_or_date": "Regulation EU 2024/1781, consolidated 28 June 2024", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines Digital Product Passport identity, item or batch scope, open interoperability, access and retention duties." }, { "id": "SRC-016", "title": "Track and Trace Standard Documentation", "organization": "Digital Container Shipping Association", "url": "https://dcsa.org/standards/track-and-trace/standard-documentation-track-and-trace", "version_or_date": "Track and Trace 2.2 documentation accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines container-shipping event semantics and interoperable cross-carrier tracking phases and APIs." }, { "id": "SRC-017", "title": "ONE Record", "organization": "International Air Transport Association", "url": "https://www.iata.org/one-record/", "version_or_date": "Standard overview accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines a federated air-cargo data-sharing model, secured API and shared shipment record." }, { "id": "SRC-018", "title": "ONE Record Ontology", "organization": "International Air Transport Association", "url": "https://onerecord.iata.org/ns/cargo/3.2.0", "version_or_date": "Ontology revision 3.2.0, modified 24 June 2025", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines linked air-cargo objects, events, logistics actions, parties and shipment data." }, { "id": "SRC-019", "title": "RFC 3339 Date and Time on the Internet", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines timestamps with seconds and explicit numeric offsets or Z." }, { "id": "SRC-020", "title": "RFC 8785 JSON Canonicalization Scheme", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc8785.html", "version_or_date": "RFC 8785, June 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines deterministic JSON canonicalization for repeatable hashing and signing." }, { "id": "SRC-021", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines entities, activities, agents, attribution, derivation, delegation, revision and invalidation." }, { "id": "SRC-022", "title": "Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note, 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines quality measurements, annotations, policies and provenance." }, { "id": "SRC-023", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "W3C Recommendation, 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines permissions, prohibitions, duties and constraints for governed trace data use." }, { "id": "SRC-024", "title": "Verifiable Credential Data Integrity 1.0", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vc-data-integrity/", "version_or_date": "W3C Recommendation, 15 May 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:18:00Z", "relevance": "Defines integrity proofs and verification material for constrained digital documents." } ], "structure": { "bundles": [ { "id": "trace-identity-scope-and-semantic-kind", "name": "Trace identity, scope and semantic kind", "description": "Groups the governed Route / Itinerary concern for trace identity, scope and semantic kind.", "rationale": "Define the trace graph, query result and chain-of-custody claim boundaries before linking evidence.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-019", "SRC-021", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "layers": [ { "id": "trace-identity-revision-and-result-kind", "name": "Trace identity, revision and result kind", "description": "Groups Route / Itinerary context for trace identity, revision and result kind without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-019", "SRC-021" ], "findings": [ { "id": "trace-graph-scope-identifier-namespace-and-revision", "name": "Trace graph scope, identifier, namespace and revision", "description": "Records trace graph scope, identifier, namespace and revision as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-019", "SRC-021" ], "questions": [ { "id": "trace-graph-scope-identifier-namespace-and-revision-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish trace graph scope, identifier, namespace and revision?", "kind": "identity", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "trace-graph-scope-identifier-namespace-and-revision-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on trace graph scope, identifier, namespace and revision, and under which authority?", "kind": "provenance", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "trace-graph-scope-identifier-namespace-and-revision-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify trace graph scope, identifier, namespace and revision?", "kind": "quality", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "trace-graph-scope-identifier-namespace-and-revision-data", "name": "Trace graph scope, identifier, namespace and revision data", "description": "Typed trace-scoped values and references required to answer the governed questions for trace graph scope, identifier, namespace and revision.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-019", "SRC-021" ] } ], "artifacts": [ { "id": "trace-graph-scope-identifier-namespace-and-revision-artifact", "name": "Trace graph scope, identifier, namespace and revision evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting trace graph scope, identifier, namespace and revision.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-019", "SRC-021" ] } ], "inline_only_rationale": null }, { "id": "persistent-graph-query-request-result-snapshot-and-claim-kind", "name": "Persistent graph, query request, result, snapshot and claim kind", "description": "Records persistent graph, query request, result, snapshot and claim kind as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-019", "SRC-021" ], "questions": [ { "id": "persistent-graph-query-request-result-snapshot-and-claim-kind-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish persistent graph, query request, result, snapshot and claim kind?", "kind": "classification", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "persistent-graph-query-request-result-snapshot-and-claim-kind-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on persistent graph, query request, result, snapshot and claim kind, and under which authority?", "kind": "ownership", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "persistent-graph-query-request-result-snapshot-and-claim-kind-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify persistent graph, query request, result, snapshot and claim kind?", "kind": "validation", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "persistent-graph-query-request-result-snapshot-and-claim-kind-data", "name": "Persistent graph, query request, result, snapshot and claim kind data", "description": "Typed trace-scoped values and references required to answer the governed questions for persistent graph, query request, result, snapshot and claim kind.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-019", "SRC-021" ] } ], "artifacts": [ { "id": "persistent-graph-query-request-result-snapshot-and-claim-kind-artifact", "name": "Persistent graph, query request, result, snapshot and claim kind evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting persistent graph, query request, result, snapshot and claim kind.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-019", "SRC-021" ] } ], "inline_only_rationale": null } ] }, { "id": "coverage-objective-profile-and-system-boundary", "name": "Coverage objective, profile and system boundary", "description": "Groups Route / Itinerary context for coverage objective, profile and system boundary without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "findings": [ { "id": "traceability-objective-subject-range-depth-and-direction", "name": "Traceability objective, subject range, depth and direction", "description": "Records traceability objective, subject range, depth and direction as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "traceability-objective-subject-range-depth-and-direction-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish traceability objective, subject range, depth and direction?", "kind": "requirement", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "traceability-objective-subject-range-depth-and-direction-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on traceability objective, subject range, depth and direction, and under which authority?", "kind": "authority", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "traceability-objective-subject-range-depth-and-direction-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify traceability objective, subject range, depth and direction?", "kind": "security", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "traceability-objective-subject-range-depth-and-direction-data", "name": "Traceability objective, subject range, depth and direction data", "description": "Typed trace-scoped values and references required to answer the governed questions for traceability objective, subject range, depth and direction.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "traceability-objective-subject-range-depth-and-direction-artifact", "name": "Traceability objective, subject range, depth and direction evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting traceability objective, subject range, depth and direction.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "physical-segregation-controlled-blending-mass-balance-and-book-and-claim-profile", "name": "Physical segregation, controlled blending, mass balance and book-and-claim profile", "description": "Records physical segregation, controlled blending, mass balance and book-and-claim profile as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "physical-segregation-controlled-blending-mass-balance-and-book-and-claim-profile-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish physical segregation, controlled blending, mass balance and book-and-claim profile?", "kind": "classification", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "physical-segregation-controlled-blending-mass-balance-and-book-and-claim-profile-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on physical segregation, controlled blending, mass balance and book-and-claim profile, and under which authority?", "kind": "requirement", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "physical-segregation-controlled-blending-mass-balance-and-book-and-claim-profile-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify physical segregation, controlled blending, mass balance and book-and-claim profile?", "kind": "privacy", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "physical-segregation-controlled-blending-mass-balance-and-book-and-claim-profile-data", "name": "Physical segregation, controlled blending, mass balance and book-and-claim profile data", "description": "Typed trace-scoped values and references required to answer the governed questions for physical segregation, controlled blending, mass balance and book-and-claim profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "physical-segregation-controlled-blending-mass-balance-and-book-and-claim-profile-artifact", "name": "Physical segregation, controlled blending, mass balance and book-and-claim profile evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting physical segregation, controlled blending, mass balance and book-and-claim profile.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "traceable-object-event-and-composition-graph", "name": "Traceable-object, event and composition graph", "description": "Groups the governed Route / Itinerary concern for traceable-object, event and composition graph.", "rationale": "Link externally mastered objects and events through time-qualified aggregation and transformation edges.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015", "SRC-018", "SRC-002", "SRC-006", "SRC-016", "SRC-021" ], "layers": [ { "id": "object-identity-class-and-membership", "name": "Object identity, class and membership", "description": "Groups Route / Itinerary context for object identity, class and membership without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015", "SRC-018" ], "findings": [ { "id": "product-material-lot-serial-item-handling-unit-shipment-and-asset-reference", "name": "Product, material, lot, serial, item, handling-unit, shipment and asset reference", "description": "Records product, material, lot, serial, item, handling-unit, shipment and asset reference as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015", "SRC-018" ], "questions": [ { "id": "product-material-lot-serial-item-handling-unit-shipment-and-asset-reference-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish product, material, lot, serial, item, handling-unit, shipment and asset reference?", "kind": "relationship", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "product-material-lot-serial-item-handling-unit-shipment-and-asset-reference-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on product, material, lot, serial, item, handling-unit, shipment and asset reference, and under which authority?", "kind": "constraint", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "product-material-lot-serial-item-handling-unit-shipment-and-asset-reference-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify product, material, lot, serial, item, handling-unit, shipment and asset reference?", "kind": "retention", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "product-material-lot-serial-item-handling-unit-shipment-and-asset-reference-data", "name": "Product, material, lot, serial, item, handling-unit, shipment and asset reference data", "description": "Typed trace-scoped values and references required to answer the governed questions for product, material, lot, serial, item, handling-unit, shipment and asset reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015", "SRC-018" ] } ], "artifacts": [ { "id": "product-material-lot-serial-item-handling-unit-shipment-and-asset-reference-artifact", "name": "Product, material, lot, serial, item, handling-unit, shipment and asset reference evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting product, material, lot, serial, item, handling-unit, shipment and asset reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "aggregation-disaggregation-containment-and-membership-interval", "name": "Aggregation, disaggregation, containment and membership interval", "description": "Records aggregation, disaggregation, containment and membership interval as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015", "SRC-018" ], "questions": [ { "id": "aggregation-disaggregation-containment-and-membership-interval-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish aggregation, disaggregation, containment and membership interval?", "kind": "composition", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "aggregation-disaggregation-containment-and-membership-interval-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on aggregation, disaggregation, containment and membership interval, and under which authority?", "kind": "process", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "aggregation-disaggregation-containment-and-membership-interval-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify aggregation, disaggregation, containment and membership interval?", "kind": "access", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "aggregation-disaggregation-containment-and-membership-interval-data", "name": "Aggregation, disaggregation, containment and membership interval data", "description": "Typed trace-scoped values and references required to answer the governed questions for aggregation, disaggregation, containment and membership interval.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015", "SRC-018" ] } ], "artifacts": [ { "id": "aggregation-disaggregation-containment-and-membership-interval-artifact", "name": "Aggregation, disaggregation, containment and membership interval evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting aggregation, disaggregation, containment and membership interval.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015", "SRC-018" ] } ], "inline_only_rationale": null } ] }, { "id": "critical-event-transformation-and-causality", "name": "Critical event, transformation and causality", "description": "Groups Route / Itinerary context for critical event, transformation and causality without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-021" ], "findings": [ { "id": "commission-observe-pack-ship-receive-store-use-return-and-dispose-event", "name": "Commission, observe, pack, ship, receive, store, use, return and dispose event", "description": "Records commission, observe, pack, ship, receive, store, use, return and dispose event as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-021" ], "questions": [ { "id": "commission-observe-pack-ship-receive-store-use-return-and-dispose-event-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish commission, observe, pack, ship, receive, store, use, return and dispose event?", "kind": "event", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "commission-observe-pack-ship-receive-store-use-return-and-dispose-event-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on commission, observe, pack, ship, receive, store, use, return and dispose event, and under which authority?", "kind": "event", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "commission-observe-pack-ship-receive-store-use-return-and-dispose-event-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify commission, observe, pack, ship, receive, store, use, return and dispose event?", "kind": "exception", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "commission-observe-pack-ship-receive-store-use-return-and-dispose-event-data", "name": "Commission, observe, pack, ship, receive, store, use, return and dispose event data", "description": "Typed trace-scoped values and references required to answer the governed questions for commission, observe, pack, ship, receive, store, use, return and dispose event.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-021" ] } ], "artifacts": [ { "id": "commission-observe-pack-ship-receive-store-use-return-and-dispose-event-artifact", "name": "Commission, observe, pack, ship, receive, store, use, return and dispose event evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting commission, observe, pack, ship, receive, store, use, return and dispose event.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-021" ] } ], "inline_only_rationale": null }, { "id": "transformation-input-output-process-step-causality-and-yield", "name": "Transformation input, output, process step, causality and yield", "description": "Records transformation input, output, process step, causality and yield as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-021" ], "questions": [ { "id": "transformation-input-output-process-step-causality-and-yield-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish transformation input, output, process step, causality and yield?", "kind": "process", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "transformation-input-output-process-step-causality-and-yield-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on transformation input, output, process step, causality and yield, and under which authority?", "kind": "measurement", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "transformation-input-output-process-step-causality-and-yield-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify transformation input, output, process step, causality and yield?", "kind": "interoperability", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "transformation-input-output-process-step-causality-and-yield-data", "name": "Transformation input, output, process step, causality and yield data", "description": "Typed trace-scoped values and references required to answer the governed questions for transformation input, output, process step, causality and yield.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-021" ] } ], "artifacts": [ { "id": "transformation-input-output-process-step-causality-and-yield-artifact", "name": "Transformation input, output, process step, causality and yield evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting transformation input, output, process step, causality and yield.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-021" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "location-party-and-custody-chain", "name": "Location, party and custody chain", "description": "Groups the governed Route / Itinerary concern for location, party and custody chain.", "rationale": "Represent where and by whom assertions arise while custody and ownership remain independent.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-014", "SRC-016", "SRC-018", "SRC-003", "SRC-010", "SRC-012", "SRC-013", "SRC-015", "SRC-017", "SRC-021" ], "layers": [ { "id": "read-point-business-location-source-and-destination", "name": "Read point, business location, source and destination", "description": "Groups Route / Itinerary context for read point, business location, source and destination without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-014", "SRC-016", "SRC-018" ], "findings": [ { "id": "event-read-point-business-location-jurisdiction-and-facility", "name": "Event read point, business location, jurisdiction and facility", "description": "Records event read point, business location, jurisdiction and facility as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-014", "SRC-016", "SRC-018" ], "questions": [ { "id": "event-read-point-business-location-jurisdiction-and-facility-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish event read point, business location, jurisdiction and facility?", "kind": "spatial", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "event-read-point-business-location-jurisdiction-and-facility-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on event read point, business location, jurisdiction and facility, and under which authority?", "kind": "evidence", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "event-read-point-business-location-jurisdiction-and-facility-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify event read point, business location, jurisdiction and facility?", "kind": "decision", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "event-read-point-business-location-jurisdiction-and-facility-data", "name": "Event read point, business location, jurisdiction and facility data", "description": "Typed trace-scoped values and references required to answer the governed questions for event read point, business location, jurisdiction and facility.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-014", "SRC-016", "SRC-018" ] } ], "artifacts": [ { "id": "event-read-point-business-location-jurisdiction-and-facility-artifact", "name": "Event read point, business location, jurisdiction and facility evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting event read point, business location, jurisdiction and facility.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-014", "SRC-016", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "source-destination-business-step-disposition-and-movement-reference", "name": "Source, destination, business step, disposition and movement reference", "description": "Records source, destination, business step, disposition and movement reference as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-014", "SRC-016", "SRC-018" ], "questions": [ { "id": "source-destination-business-step-disposition-and-movement-reference-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish source, destination, business step, disposition and movement reference?", "kind": "relationship", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "source-destination-business-step-disposition-and-movement-reference-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on source, destination, business step, disposition and movement reference, and under which authority?", "kind": "quality", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "source-destination-business-step-disposition-and-movement-reference-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify source, destination, business step, disposition and movement reference?", "kind": "identity", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "source-destination-business-step-disposition-and-movement-reference-data", "name": "Source, destination, business step, disposition and movement reference data", "description": "Typed trace-scoped values and references required to answer the governed questions for source, destination, business step, disposition and movement reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-014", "SRC-016", "SRC-018" ] } ], "artifacts": [ { "id": "source-destination-business-step-disposition-and-movement-reference-artifact", "name": "Source, destination, business step, disposition and movement reference evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting source, destination, business step, disposition and movement reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-008", "SRC-009", "SRC-014", "SRC-016", "SRC-018" ] } ], "inline_only_rationale": null } ] }, { "id": "party-role-custody-and-handover", "name": "Party role, custody and handover", "description": "Groups Route / Itinerary context for party role, custody and handover without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021" ], "findings": [ { "id": "owner-custodian-possessor-controller-responsible-party-and-steward", "name": "Owner, custodian, possessor, controller, responsible party and steward", "description": "Records owner, custodian, possessor, controller, responsible party and steward as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021" ], "questions": [ { "id": "owner-custodian-possessor-controller-responsible-party-and-steward-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish owner, custodian, possessor, controller, responsible party and steward?", "kind": "ownership", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "owner-custodian-possessor-controller-responsible-party-and-steward-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on owner, custodian, possessor, controller, responsible party and steward, and under which authority?", "kind": "validation", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "owner-custodian-possessor-controller-responsible-party-and-steward-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify owner, custodian, possessor, controller, responsible party and steward?", "kind": "classification", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "owner-custodian-possessor-controller-responsible-party-and-steward-data", "name": "Owner, custodian, possessor, controller, responsible party and steward data", "description": "Typed trace-scoped values and references required to answer the governed questions for owner, custodian, possessor, controller, responsible party and steward.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021" ] } ], "artifacts": [ { "id": "owner-custodian-possessor-controller-responsible-party-and-steward-artifact", "name": "Owner, custodian, possessor, controller, responsible party and steward evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting owner, custodian, possessor, controller, responsible party and steward.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021" ] } ], "inline_only_rationale": null }, { "id": "custody-interval-transfer-handover-acceptance-refusal-and-exception", "name": "Custody interval, transfer, handover, acceptance, refusal and exception", "description": "Records custody interval, transfer, handover, acceptance, refusal and exception as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021" ], "questions": [ { "id": "custody-interval-transfer-handover-acceptance-refusal-and-exception-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish custody interval, transfer, handover, acceptance, refusal and exception?", "kind": "lifecycle", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "custody-interval-transfer-handover-acceptance-refusal-and-exception-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on custody interval, transfer, handover, acceptance, refusal and exception, and under which authority?", "kind": "security", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "custody-interval-transfer-handover-acceptance-refusal-and-exception-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify custody interval, transfer, handover, acceptance, refusal and exception?", "kind": "composition", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "custody-interval-transfer-handover-acceptance-refusal-and-exception-data", "name": "Custody interval, transfer, handover, acceptance, refusal and exception data", "description": "Typed trace-scoped values and references required to answer the governed questions for custody interval, transfer, handover, acceptance, refusal and exception.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021" ] } ], "artifacts": [ { "id": "custody-interval-transfer-handover-acceptance-refusal-and-exception-artifact", "name": "Custody interval, transfer, handover, acceptance, refusal and exception evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting custody interval, transfer, handover, acceptance, refusal and exception.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "time-evidence-integrity-and-correction", "name": "Time, evidence, integrity and correction", "description": "Groups the governed Route / Itinerary concern for time, evidence, integrity and correction.", "rationale": "Keep clocks, sources, proof, quality and correction lineage explicit for every trace assertion.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-019", "SRC-021", "SRC-013", "SRC-020", "SRC-022", "SRC-024" ], "layers": [ { "id": "clocks-source-provenance-and-attribution", "name": "Clocks, source, provenance and attribution", "description": "Groups Route / Itinerary context for clocks, source, provenance and attribution without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-019", "SRC-021" ], "findings": [ { "id": "event-effective-observation-record-ingestion-and-publication-time", "name": "Event, effective, observation, record, ingestion and publication time", "description": "Records event, effective, observation, record, ingestion and publication time as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-019", "SRC-021" ], "questions": [ { "id": "event-effective-observation-record-ingestion-and-publication-time-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish event, effective, observation, record, ingestion and publication time?", "kind": "temporal", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "event-effective-observation-record-ingestion-and-publication-time-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on event, effective, observation, record, ingestion and publication time, and under which authority?", "kind": "privacy", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "event-effective-observation-record-ingestion-and-publication-time-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify event, effective, observation, record, ingestion and publication time?", "kind": "relationship", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "event-effective-observation-record-ingestion-and-publication-time-data", "name": "Event, effective, observation, record, ingestion and publication time data", "description": "Typed trace-scoped values and references required to answer the governed questions for event, effective, observation, record, ingestion and publication time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-019", "SRC-021" ] } ], "artifacts": [ { "id": "event-effective-observation-record-ingestion-and-publication-time-artifact", "name": "Event, effective, observation, record, ingestion and publication time evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting event, effective, observation, record, ingestion and publication time.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-019", "SRC-021" ] } ], "inline_only_rationale": null }, { "id": "asserting-agent-source-system-method-authority-and-delegation", "name": "Asserting agent, source system, method, authority and delegation", "description": "Records asserting agent, source system, method, authority and delegation as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-019", "SRC-021" ], "questions": [ { "id": "asserting-agent-source-system-method-authority-and-delegation-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish asserting agent, source system, method, authority and delegation?", "kind": "provenance", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "asserting-agent-source-system-method-authority-and-delegation-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on asserting agent, source system, method, authority and delegation, and under which authority?", "kind": "retention", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "asserting-agent-source-system-method-authority-and-delegation-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify asserting agent, source system, method, authority and delegation?", "kind": "state", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "asserting-agent-source-system-method-authority-and-delegation-data", "name": "Asserting agent, source system, method, authority and delegation data", "description": "Typed trace-scoped values and references required to answer the governed questions for asserting agent, source system, method, authority and delegation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-019", "SRC-021" ] } ], "artifacts": [ { "id": "asserting-agent-source-system-method-authority-and-delegation-artifact", "name": "Asserting agent, source system, method, authority and delegation evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting asserting agent, source system, method, authority and delegation.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-014", "SRC-016", "SRC-018", "SRC-019", "SRC-021" ] } ], "inline_only_rationale": null } ] }, { "id": "evidence-proof-quality-conflict-and-correction", "name": "Evidence, proof, quality, conflict and correction", "description": "Groups Route / Itinerary context for evidence, proof, quality, conflict and correction without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-013", "SRC-014", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ], "findings": [ { "id": "evidence-artifact-digest-signature-credential-and-verification-result", "name": "Evidence artifact, digest, signature, credential and verification result", "description": "Records evidence artifact, digest, signature, credential and verification result as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-013", "SRC-014", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ], "questions": [ { "id": "evidence-artifact-digest-signature-credential-and-verification-result-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish evidence artifact, digest, signature, credential and verification result?", "kind": "evidence", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "evidence-artifact-digest-signature-credential-and-verification-result-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on evidence artifact, digest, signature, credential and verification result, and under which authority?", "kind": "access", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "evidence-artifact-digest-signature-credential-and-verification-result-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify evidence artifact, digest, signature, credential and verification result?", "kind": "lifecycle", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "evidence-artifact-digest-signature-credential-and-verification-result-data", "name": "Evidence artifact, digest, signature, credential and verification result data", "description": "Typed trace-scoped values and references required to answer the governed questions for evidence artifact, digest, signature, credential and verification result.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-013", "SRC-014", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] } ], "artifacts": [ { "id": "evidence-artifact-digest-signature-credential-and-verification-result-artifact", "name": "Evidence artifact, digest, signature, credential and verification result evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting evidence artifact, digest, signature, credential and verification result.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-013", "SRC-014", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "completeness-confidence-gap-duplicate-conflict-error-declaration-and-successor", "name": "Completeness, confidence, gap, duplicate, conflict, error declaration and successor", "description": "Records completeness, confidence, gap, duplicate, conflict, error declaration and successor as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-013", "SRC-014", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ], "questions": [ { "id": "completeness-confidence-gap-duplicate-conflict-error-declaration-and-successor-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish completeness, confidence, gap, duplicate, conflict, error declaration and successor?", "kind": "quality", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "completeness-confidence-gap-duplicate-conflict-error-declaration-and-successor-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on completeness, confidence, gap, duplicate, conflict, error declaration and successor, and under which authority?", "kind": "exception", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "completeness-confidence-gap-duplicate-conflict-error-declaration-and-successor-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify completeness, confidence, gap, duplicate, conflict, error declaration and successor?", "kind": "temporal", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "completeness-confidence-gap-duplicate-conflict-error-declaration-and-successor-data", "name": "Completeness, confidence, gap, duplicate, conflict, error declaration and successor data", "description": "Typed trace-scoped values and references required to answer the governed questions for completeness, confidence, gap, duplicate, conflict, error declaration and successor.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-013", "SRC-014", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] } ], "artifacts": [ { "id": "completeness-confidence-gap-duplicate-conflict-error-declaration-and-successor-artifact", "name": "Completeness, confidence, gap, duplicate, conflict, error declaration and successor evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting completeness, confidence, gap, duplicate, conflict, error declaration and successor.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-013", "SRC-014", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "trace-query-exposure-recall-and-federation", "name": "Trace query, exposure, recall and federation", "description": "Groups the governed Route / Itinerary concern for trace query, exposure, recall and federation.", "rationale": "Return qualified graph slices and risk sets without turning analysis into an external decision.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-016", "SRC-017", "SRC-018", "SRC-006", "SRC-015", "SRC-021", "SRC-022" ], "layers": [ { "id": "backward-forward-history-and-path-query", "name": "Backward, forward, history and path query", "description": "Groups Route / Itinerary context for backward, forward, history and path query without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ], "findings": [ { "id": "one-up-one-down-backward-forward-and-end-to-end-trace", "name": "One-up one-down, backward, forward and end-to-end trace", "description": "Records one-up one-down, backward, forward and end-to-end trace as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "one-up-one-down-backward-forward-and-end-to-end-trace-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish one-up one-down, backward, forward and end-to-end trace?", "kind": "process", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "one-up-one-down-backward-forward-and-end-to-end-trace-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on one-up one-down, backward, forward and end-to-end trace, and under which authority?", "kind": "interoperability", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "one-up-one-down-backward-forward-and-end-to-end-trace-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify one-up one-down, backward, forward and end-to-end trace?", "kind": "spatial", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "one-up-one-down-backward-forward-and-end-to-end-trace-data", "name": "One-up one-down, backward, forward and end-to-end trace data", "description": "Typed trace-scoped values and references required to answer the governed questions for one-up one-down, backward, forward and end-to-end trace.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "one-up-one-down-backward-forward-and-end-to-end-trace-artifact", "name": "One-up one-down, backward, forward and end-to-end trace evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting one-up one-down, backward, forward and end-to-end trace.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "object-event-party-location-time-and-relationship-filter", "name": "Object, event, party, location, time and relationship filter", "description": "Records object, event, party, location, time and relationship filter as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "object-event-party-location-time-and-relationship-filter-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish object, event, party, location, time and relationship filter?", "kind": "constraint", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "object-event-party-location-time-and-relationship-filter-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on object, event, party, location, time and relationship filter, and under which authority?", "kind": "decision", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "object-event-party-location-time-and-relationship-filter-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify object, event, party, location, time and relationship filter?", "kind": "provenance", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "object-event-party-location-time-and-relationship-filter-data", "name": "Object, event, party, location, time and relationship filter data", "description": "Typed trace-scoped values and references required to answer the governed questions for object, event, party, location, time and relationship filter.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "object-event-party-location-time-and-relationship-filter-artifact", "name": "Object, event, party, location, time and relationship filter evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting object, event, party, location, time and relationship filter.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] }, { "id": "exposure-recall-impact-and-qualified-result", "name": "Exposure, recall, impact and qualified result", "description": "Groups Route / Itinerary context for exposure, recall, impact and qualified result without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-021", "SRC-022" ], "findings": [ { "id": "affected-lot-item-party-location-shipment-and-downstream-set", "name": "Affected lot, item, party, location, shipment and downstream set", "description": "Records affected lot, item, party, location, shipment and downstream set as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-021", "SRC-022" ], "questions": [ { "id": "affected-lot-item-party-location-shipment-and-downstream-set-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish affected lot, item, party, location, shipment and downstream set?", "kind": "decision", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "affected-lot-item-party-location-shipment-and-downstream-set-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on affected lot, item, party, location, shipment and downstream set, and under which authority?", "kind": "identity", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "affected-lot-item-party-location-shipment-and-downstream-set-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify affected lot, item, party, location, shipment and downstream set?", "kind": "ownership", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "affected-lot-item-party-location-shipment-and-downstream-set-data", "name": "Affected lot, item, party, location, shipment and downstream set data", "description": "Typed trace-scoped values and references required to answer the governed questions for affected lot, item, party, location, shipment and downstream set.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-021", "SRC-022" ] } ], "artifacts": [ { "id": "affected-lot-item-party-location-shipment-and-downstream-set-artifact", "name": "Affected lot, item, party, location, shipment and downstream set evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting affected lot, item, party, location, shipment and downstream set.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-021", "SRC-022" ] } ], "inline_only_rationale": null }, { "id": "recall-investigation-alert-status-action-reference-and-residual-uncertainty", "name": "Recall, investigation, alert, status, action reference and residual uncertainty", "description": "Records recall, investigation, alert, status, action reference and residual uncertainty as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-021", "SRC-022" ], "questions": [ { "id": "recall-investigation-alert-status-action-reference-and-residual-uncertainty-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish recall, investigation, alert, status, action reference and residual uncertainty?", "kind": "exception", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "recall-investigation-alert-status-action-reference-and-residual-uncertainty-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on recall, investigation, alert, status, action reference and residual uncertainty, and under which authority?", "kind": "classification", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "recall-investigation-alert-status-action-reference-and-residual-uncertainty-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify recall, investigation, alert, status, action reference and residual uncertainty?", "kind": "authority", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "recall-investigation-alert-status-action-reference-and-residual-uncertainty-data", "name": "Recall, investigation, alert, status, action reference and residual uncertainty data", "description": "Typed trace-scoped values and references required to answer the governed questions for recall, investigation, alert, status, action reference and residual uncertainty.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-021", "SRC-022" ] } ], "artifacts": [ { "id": "recall-investigation-alert-status-action-reference-and-residual-uncertainty-artifact", "name": "Recall, investigation, alert, status, action reference and residual uncertainty evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting recall, investigation, alert, status, action reference and residual uncertainty.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-021", "SRC-022" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-access-retention-and-interoperability", "name": "Governance, access, retention and interoperability", "description": "Groups the governed Route / Itinerary concern for governance, access, retention and interoperability.", "rationale": "Federate minimum-necessary trace data and project profiles without hiding authority or semantic loss.", "source_refs": [ "SRC-001", "SRC-003", "SRC-009", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021", "SRC-023", "SRC-002", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-016", "SRC-018", "SRC-019", "SRC-020", "SRC-022", "SRC-024" ], "layers": [ { "id": "federation-discovery-access-privacy-and-retention", "name": "Federation, discovery, access, privacy and retention", "description": "Groups Route / Itinerary context for federation, discovery, access, privacy and retention without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-009", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021", "SRC-023" ], "findings": [ { "id": "registry-endpoint-query-routing-availability-and-freshness", "name": "Registry, endpoint, query routing, availability and freshness", "description": "Records registry, endpoint, query routing, availability and freshness as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-009", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021", "SRC-023" ], "questions": [ { "id": "registry-endpoint-query-routing-availability-and-freshness-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish registry, endpoint, query routing, availability and freshness?", "kind": "interoperability", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "registry-endpoint-query-routing-availability-and-freshness-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on registry, endpoint, query routing, availability and freshness, and under which authority?", "kind": "composition", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "registry-endpoint-query-routing-availability-and-freshness-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify registry, endpoint, query routing, availability and freshness?", "kind": "requirement", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "registry-endpoint-query-routing-availability-and-freshness-data", "name": "Registry, endpoint, query routing, availability and freshness data", "description": "Typed trace-scoped values and references required to answer the governed questions for registry, endpoint, query routing, availability and freshness.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-009", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021", "SRC-023" ] } ], "artifacts": [ { "id": "registry-endpoint-query-routing-availability-and-freshness-artifact", "name": "Registry, endpoint, query routing, availability and freshness evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting registry, endpoint, query routing, availability and freshness.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-009", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021", "SRC-023" ] } ], "inline_only_rationale": null }, { "id": "purpose-role-consent-confidentiality-minimum-disclosure-retention-and-legal-hold", "name": "Purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold", "description": "Records purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-009", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021", "SRC-023" ], "questions": [ { "id": "purpose-role-consent-confidentiality-minimum-disclosure-retention-and-legal-hold-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold?", "kind": "access", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "purpose-role-consent-confidentiality-minimum-disclosure-retention-and-legal-hold-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold, and under which authority?", "kind": "relationship", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "purpose-role-consent-confidentiality-minimum-disclosure-retention-and-legal-hold-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold?", "kind": "constraint", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "purpose-role-consent-confidentiality-minimum-disclosure-retention-and-legal-hold-data", "name": "Purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold data", "description": "Typed trace-scoped values and references required to answer the governed questions for purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-009", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021", "SRC-023" ] } ], "artifacts": [ { "id": "purpose-role-consent-confidentiality-minimum-disclosure-retention-and-legal-hold-artifact", "name": "Purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting purpose, role, consent, confidentiality, minimum disclosure, retention and legal hold.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-009", "SRC-013", "SRC-014", "SRC-015", "SRC-017", "SRC-021", "SRC-023" ] } ], "inline_only_rationale": null } ] }, { "id": "standards-crosswalk-conformance-and-loss", "name": "Standards crosswalk, conformance and loss", "description": "Groups Route / Itinerary context for standards crosswalk, conformance and loss without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "findings": [ { "id": "gs1-uncefact-iso-fda-eu-dcsa-iata-and-provenance-crosswalk", "name": "GS1, UN/CEFACT, ISO, FDA, EU, DCSA, IATA and provenance crosswalk", "description": "Records gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "gs1-uncefact-iso-fda-eu-dcsa-iata-and-provenance-crosswalk-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk?", "kind": "interoperability", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "gs1-uncefact-iso-fda-eu-dcsa-iata-and-provenance-crosswalk-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk, and under which authority?", "kind": "state", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "gs1-uncefact-iso-fda-eu-dcsa-iata-and-provenance-crosswalk-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk?", "kind": "process", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "gs1-uncefact-iso-fda-eu-dcsa-iata-and-provenance-crosswalk-data", "name": "GS1, UN/CEFACT, ISO, FDA, EU, DCSA, IATA and provenance crosswalk data", "description": "Typed trace-scoped values and references required to answer the governed questions for gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "gs1-uncefact-iso-fda-eu-dcsa-iata-and-provenance-crosswalk-artifact", "name": "GS1, UN/CEFACT, ISO, FDA, EU, DCSA, IATA and provenance crosswalk evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting gs1, un/cefact, iso, fda, eu, dcsa, iata and provenance crosswalk.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "profile-version-license-conformance-transformation-and-semantic-loss", "name": "Profile, version, license, conformance, transformation and semantic loss", "description": "Records profile, version, license, conformance, transformation and semantic loss as a typed Supply-chain Trace assertion while objects, events, movements, parties, places, claims, decisions and evidence retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "profile-version-license-conformance-transformation-and-semantic-loss-q01", "text": "Which trace identity, result kind, object and event scope, graph edge, clocks and source establish profile, version, license, conformance, transformation and semantic loss?", "kind": "validation", "answer_data": [ "trace scope identifier, namespace, revision, persistent-graph or result kind and query basis", "traceable-object, event, aggregation, transformation, location, party and custody references", "event, observation, record and ingestion clocks plus source profile and confidence" ] }, { "id": "profile-version-license-conformance-transformation-and-semantic-loss-q02", "text": "Who owns, holds, observes, asserts, verifies, corrects, queries, discloses or acts on profile, version, license, conformance, transformation and semantic loss, and under which authority?", "kind": "lifecycle", "answer_data": [ "owner, custodian, possessor, controller, operator, source steward, verifier and decision roles", "business step, transfer, delegation, purpose, jurisdiction, confidentiality and access basis", "master system, signature or credential issuer, reviewer, correction actor and disputed state" ] }, { "id": "profile-version-license-conformance-transformation-and-semantic-loss-q03", "text": "Which evidence, completeness, gap, conflict, exposure, uncertainty and lineage qualify profile, version, license, conformance, transformation and semantic loss?", "kind": "event", "answer_data": [ "evidence artifact, digest, proof, verification method and quality measurement", "missing link, duplicate, contradiction, error declaration, retraction, successor and residual uncertainty", "backward or forward path, affected set, recall reference, profile mapping and semantic-loss declaration" ] } ], "data_elements": [ { "id": "profile-version-license-conformance-transformation-and-semantic-loss-data", "name": "Profile, version, license, conformance, transformation and semantic loss data", "description": "Typed trace-scoped values and references required to answer the governed questions for profile, version, license, conformance, transformation and semantic loss.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "profile-version-license-conformance-transformation-and-semantic-loss-artifact", "name": "Profile, version, license, conformance, transformation and semantic loss evidence manifest", "description": "Digest-addressed manifest of objects, events, graph edges, sources, proofs, gaps, conflicts, query results and corrections supporting profile, version, license, conformance, transformation and semantic loss.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative trace or source-system event identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-trace-scope", "name": "Register trace scope", "description": "Create one governed trace-graph or result identity with an explicit semantic kind and objective.", "inputs": [ "trace kind", "subject range", "owner and source" ], "outputs": [ "trace identifier", "initial revision" ], "preconditions": [ "active Dimension", "create authority" ], "effects": [ "identity, system boundary and unknowns are appended" ], "source_refs": [ "SRC-003", "SRC-007", "SRC-010", "SRC-012", "SRC-019", "SRC-021" ] }, { "id": "bind-traceable-objects", "name": "Bind traceable objects", "description": "Bind product, material, lot, serial, item, handling-unit, shipment and asset identities without importing their lifecycles.", "inputs": [ "trace revision", "object references", "validity scope" ], "outputs": [ "typed object bindings" ], "preconditions": [ "external identities resolvable" ], "effects": [ "membership remains source-qualified and time-aware" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015" ] }, { "id": "append-critical-event", "name": "Append critical event", "description": "Link an externally mastered event with business, spatial, temporal, party and evidence context.", "inputs": [ "trace revision", "event reference", "critical data elements" ], "outputs": [ "immutable graph event edge" ], "preconditions": [ "event identity and source known" ], "effects": [ "assertion is appended without overwriting the event master" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-014", "SRC-016", "SRC-018" ] }, { "id": "link-composition-transformation", "name": "Link composition or transformation", "description": "Append aggregation, disaggregation or input-output transformation edges with validity and yield context.", "inputs": [ "trace revision", "input and output or parent and child references", "event and time" ], "outputs": [ "typed composition or transformation edge" ], "preconditions": [ "subjects and event resolvable" ], "effects": [ "prior membership and provenance remain visible" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-014", "SRC-021" ] }, { "id": "record-custody-assertion", "name": "Record custody assertion", "description": "Append custody, possession, control, responsibility or handover assertions without inferring ownership.", "inputs": [ "trace revision", "party and object references", "role interval and evidence" ], "outputs": [ "custody-chain edge" ], "preconditions": [ "asserting authority known" ], "effects": [ "acceptance, refusal and exceptions remain source-qualified" ], "source_refs": [ "SRC-003", "SRC-007", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-021" ] }, { "id": "attach-evidence-proof", "name": "Attach evidence and proof", "description": "Bind evidence artifacts, digests, signatures, credentials, verification results and quality statements.", "inputs": [ "trace assertion", "evidence reference", "verification method" ], "outputs": [ "evidence binding", "verification assertion" ], "preconditions": [ "media type, issuer and scope known" ], "effects": [ "proof status never substitutes for claim truth or authority" ], "source_refs": [ "SRC-013", "SRC-020", "SRC-021", "SRC-022", "SRC-024" ] }, { "id": "correct-or-contest", "name": "Correct or contest trace assertion", "description": "Append error declaration, retraction, competing assertion or successor without deleting the original.", "inputs": [ "trace revision", "affected assertion", "reason and authority" ], "outputs": [ "correction or contested-set revision" ], "preconditions": [ "affected scope known" ], "effects": [ "history, source and conflict remain resolvable" ], "source_refs": [ "SRC-001", "SRC-019", "SRC-020", "SRC-021", "SRC-022" ] }, { "id": "trace-path", "name": "Trace backward or forward", "description": "Return a qualified graph slice across object, event, party, location and time filters.", "inputs": [ "trace scope", "anchor", "direction, depth and filters" ], "outputs": [ "versioned trace result", "gap set" ], "preconditions": [ "authorized query", "source freshness known" ], "effects": [ "result preserves evidence, uncertainty and omitted-scope declaration" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-016", "SRC-017" ] }, { "id": "compute-exposure-set", "name": "Compute qualified exposure set", "description": "Derive candidate affected objects, parties, locations and shipments without making a recall or enforcement decision.", "inputs": [ "trace result", "hazard or affected anchor", "inclusion and exclusion rules" ], "outputs": [ "qualified exposure set", "residual uncertainty" ], "preconditions": [ "rules, graph horizon and evidence thresholds known" ], "effects": [ "analysis is attributable and decision remains external" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-012", "SRC-014", "SRC-021", "SRC-022" ] }, { "id": "project-trace-view", "name": "Project authorized trace view", "description": "Produce minimum-necessary standards-aligned trace, custody, regulatory or modal views.", "inputs": [ "trace revision or result", "target profile", "access purpose" ], "outputs": [ "versioned projection", "semantic-loss declaration" ], "preconditions": [ "authorized recipient", "pinned target version" ], "effects": [ "projection is logged and source identities preserved" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "composition": [ { "target": "WM-FLW-004 Goods Movement / Logistics", "relation": "REFERENCE", "purpose": "Resolve broader logistics flow while the candidate parent relation remains under joint boundary review.", "required": false, "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-016" ] }, { "target": "WM-ACT-015 Occurrence / Event", "relation": "COMPOSE", "purpose": "Compose typed event references into the trace graph without importing generic event identity or lifecycle.", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-021" ] }, { "target": "WM-FLW-011 Shipment / Consignment and WM-FLW-012 Inventory Movement", "relation": "REFERENCE", "purpose": "Resolve logistics groupings and stock-affecting transitions while trace owns only cross-source graph linkage.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-014", "SRC-016", "SRC-017" ] }, { "target": "Product, lot, serial, handling-unit, place and party masters", "relation": "REFERENCE", "purpose": "Resolve traceable objects and participants while preserving external identity and lifecycle authority.", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-014", "SRC-015" ] }, { "target": "Custody handover, document, credential, claim, recall and evidence masters", "relation": "REFERENCE", "purpose": "Resolve supporting records and accountable decisions without converting them into trace-owned payloads.", "required": false, "source_refs": [ "SRC-003", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-021", "SRC-024" ] }, { "target": "GS1 EPCIS 2.0.1, CBV 2.0.0 and Global Traceability 2.0", "relation": "ALIGN", "purpose": "Project critical events, objects, aggregation, transformation, locations, business context, queries and error declarations.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] }, { "target": "UN/CEFACT Integrated Track and Trace", "relation": "ALIGN", "purpose": "Project cross-industry multimodal visibility and delegated event-registry views.", "required": false, "source_refs": [ "SRC-007", "SRC-008", "SRC-009" ] }, { "target": "ISO 22095, ISO 22095-2, ISO 22005 and ISO 28000", "relation": "ALIGN", "purpose": "Project generic custody models, mass-balance attribution, food traceability and security management as pinned profiles.", "required": false, "source_refs": [ "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] }, { "target": "FDA Food Traceability Rule and EU Digital Product Passport", "relation": "ALIGN", "purpose": "Project jurisdiction-specific trace records, lots, critical events, product identifiers, access and retention duties.", "required": false, "source_refs": [ "SRC-014", "SRC-015" ] }, { "target": "DCSA Track and Trace and IATA ONE Record", "relation": "ALIGN", "purpose": "Project container-shipping and air-cargo event and federation views as modal profiles.", "required": false, "source_refs": [ "SRC-016", "SRC-017", "SRC-018" ] }, { "target": "RFC 3339, RFC 8785, PROV-O, DQV, ODRL and Data Integrity", "relation": "ALIGN", "purpose": "Project temporal, canonicalization, provenance, quality, access and proof semantics with exact pins and loss declarations.", "required": false, "source_refs": [ "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, trace steward, source authorities, custodians, verifiers, query operators and accountable decision roles.", "Register authoritative product, lot, serial, handling-unit, shipment, inventory-movement, journey, place, party, event, observation, handover, document, credential, recall, claim and evidence masters.", "Publish trace-object, event-type, business-step, disposition, location, custody-role, quality, access, retention and interoperability registries.", "Pin chain-of-custody model, sector, jurisdiction, claim, certification, security, privacy, licensing and exchange profiles." ], "namespace_guidance": "Mint trace-scope, graph-revision, edge, gap, contested-set, query-result, exposure-set and projection identifiers only in the adopting Dimension namespace; preserve external master identities as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local trace, event, custody-role, classifier, source, access, retention and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, trace scope, mandatory semantic kind, authoritative source IDs, immutable graph revision, query basis and source profile; never use date, lot code, barcode, party, location, document or hash alone as identity.", "Keep trace graph, query, result, snapshot, custody claim, object, event, aggregation, transformation, handover, evidence, exposure analysis and recall decision distinct and preserve corrections and successors." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare target node, chain-of-custody or sector profile, authority, source, rationale, access, time and interoperability impact.", "Breaking changes require a new version, migration and crosswalk maps, compatibility declaration and continued resolution of prior graph revisions, query results and identifiers." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when trace identity, semantic kind, object and event scope, edge meaning, clocks, authority, provenance and access remain intact.", "GS1, UN/CEFACT, ISO, FDA, EU, DCSA, IATA and provenance mappings pin source and target versions and declare transformed, omitted or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative traceability master-system identifier and immutable revision.", "Governed globally resolvable trace, edge, query-result or exposure-set IRI.", "Adopting-Dimension UUID or ULID when no authoritative external identifier exists." ], "timestamp_rule": "Record timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep event, effective, observation, record, ingestion, publication and correction times distinct.", "serial_naming_rule": "Name serial artifacts as {trace-id}--{artifact-kind}--{revision-or-event-id}; never use a date, lot code, barcode, party, location, filename or hash alone as identity.", "integrity_rule": "Store digest, canonicalization profile, media type, byte length, issuer, source and vocabulary versions, graph scope, event and record times, provenance, verification, assurance, license and access marking for each retained artifact." }, "policies": [ "The adopting Dimension declares who may register scope, bind objects, append events, assert custody, attach proofs, correct, query, derive exposure sets, disclose, retain and tombstone trace records.", "Every assertion requires trace and graph revision, semantic kind, subject and edge scope, source, authority, clocks, confidence, quality, access and lineage as applicable.", "Agents never infer ownership, custody, product characteristic, safety, compliance, authenticity, recall scope or legal responsibility from location, event, document, digest, signature or credential alone.", "Objects, events, movements, parties, places, handovers, observations, documents, credentials, claims, recall actions and evidence remain external masters.", "Automated agents may append low-risk source-qualified edges, gap reports, queries and projections under delegation, but custody acceptance, certification, recall, enforcement, protected disclosure and irreversible deletion require accountable external authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, trace scope and revision, object and time horizon, source freshness, quality, assurance, license and access policy; return the minimum permitted graph projection." ], "create": [ "Create stable trace scope, semantic kind, objective, object range, direction, source authorities, chain-of-custody profile and explicit unknowns before adding graph edges." ], "update": [ "Append an immutable object binding, event edge, custody assertion, proof, gap, conflict or correction with actor, authority, reason, RFC 3339 clocks and predecessor." ], "delete": [ "Apply safety, certification, regulatory, dispute, audit, retention, disposition and legal-hold policy; tombstone eligible Trace-owned records or withdraw projections while preserving identity, material provenance and non-cascading external references. The adopting Dimension policy owns execution." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Traceability steward", "responsibilities": [ "Own trace scope, graph semantics, chain-of-custody profiles, quality and correction policy." ] }, { "name": "Source-system authority", "responsibilities": [ "Own object, event, clock, location and business assertions within its system boundary." ] }, { "name": "Custodian or operator", "responsibilities": [ "Assert custody, possession, handling and handover evidence within delegated scope." ] }, { "name": "Evidence issuer or verifier", "responsibilities": [ "Own artifacts, digests, proof methods, verification results and limitations." ] }, { "name": "Query or investigation operator", "responsibilities": [ "Run authorized backward, forward, path and exposure analyses with declared rules." ] }, { "name": "Recall or regulatory authority", "responsibilities": [ "Own recall, enforcement, certification or regulatory decisions outside the trace pattern." ] }, { "name": "Disclosure reviewer", "responsibilities": [ "Review recipient, purpose, minimum disclosure, redaction and publication timing." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless active Dimension, role, purpose, commercial confidentiality, location, personal data, security, license and field policy grant the action; expose the minimum necessary graph slice.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency or regulatory access must be legally grounded, time-limited, purpose-bound, attributable, independently reviewed and unable to erase immutable trace, conflict, correction or legal-hold evidence." ], "audit_requirements": [ "Log actor, role, purpose, trace and revision identity, query or action, decision, policy and vocabulary versions, RFC 3339 timestamp with offset, affected graph scope, source evidence and outcome for privileged mutation or disclosure." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md, trace and source authorities, active custody model, sector, jurisdiction, time, access, retention, licensing and disclosure policies.", "Read this model AGENTS.md, pinned spec.yaml and required object, event, movement, party, place, handover, document, credential, recall, claim and evidence instructions before mutation." ] } }, "coverage": { "claim": "WM-FLW-013 covers a reusable Supply-chain Trace / Chain of Custody pattern with graph and result identity, trace objective, object-event composition, aggregation, transformation, location, parties, custody, clocks, evidence, integrity, quality, correction, backward and forward query, exposure analysis, federation, governance and loss-aware interoperability. Sector, jurisdiction, certification, claims, implementation-conformance and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Trace scope, graph revision, query request, result, snapshot, claim, edge and exposure-set identities remain distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Trace objective, direction, coverage and chain-of-custody profile are mandatory and versioned." }, { "dimension": "direct properties", "status": "covered", "notes": "Graph scope, edge semantics, gaps, conflicts and query basis are covered without importing external masters." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Authoritative identity, physical observation, business assertion, document, signature and verification result are distinguished." }, { "dimension": "lifecycle", "status": "covered", "notes": "Registration, append, validation, contest, correction, supersession, withdrawal, retention and tombstone preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Objects, events, aggregation, transformation, locations, parties, movements, handovers, documents and decisions use typed edges." }, { "dimension": "temporal", "status": "covered", "notes": "Event, effective, observation, record, ingestion, publication and correction clocks remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Read point, business location, source, destination, facility and jurisdiction functions are explicit." }, { "dimension": "provenance", "status": "covered", "notes": "Sources, agents, methods, delegations, evidence, derivations, revisions and invalidations are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Ownership, custody, possession, control, responsibility and data mastership are not conflated." }, { "dimension": "validation", "status": "covered", "notes": "Identity, edge, clock, composition, transformation, custody, proof, quality, path and crosswalk checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose, confidentiality, personal data, location sensitivity, minimum graph projection and audit are represented." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Corrections, contested sets, recall or legal hold, withdrawal and tombstones are explicit and non-cascading." }, { "dimension": "interoperability", "status": "covered", "notes": "GS1, UN/CEFACT, ISO, FDA, EU, DCSA, IATA, RFC, PROV, DQV, ODRL and Data Integrity mappings disclose loss." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Scope registration, object and event linking, custody assertion, proof, correction, query, exposure and projection declare controlled effects." } ], "known_omissions": [ "Sector, jurisdiction, chain-of-custody claim, certification, customs, dangerous-goods, safety, privacy, security, licensing and retention profiles require exact current rules and competent review.", "Objects, events, movements, parties, places, handovers, observations, documents, credentials, claims, recall actions and evidence lifecycles remain in neighboring models.", "Certified field crosswalks, identity resolution, graph completeness metrics, secure federation, signature suites, exposure algorithms, recall decision rules and legal evidence requirements remain future work." ], "conflicts": [ "Traceability covers product history and relationship paths, tracking often emphasizes current location or status, and chain of custody governs characteristic attribution; the model requires an explicit semantic kind and profile.", "Physical segregation, controlled blending, mass balance and book-and-claim permit different relationships between physical material and attributed characteristics and cannot share one inference rule.", "An event assertion, document, digest, signature, credential and successful verification establish different properties and do not by themselves prove real-world truth, custody or product conformity." ], "regional_assumptions": [ "FDA food traceability and EU Digital Product Passport are jurisdictional and product-scope profiles rather than universal supply-chain rules.", "DCSA and IATA are maritime-container and air-cargo modal profiles and do not define all transport or custody contexts.", "Recall, certification, title, custody, privacy, security, retention and evidential consequences depend on sector, contract and jurisdiction." ], "adversarial_checks": [ "Reject a trace without stable scope identity, semantic kind, revision, object and event range, graph basis, source authority and lineage.", "Reject traceability, tracking, chain of custody, provenance, audit log, shipment history and distributed software trace treated as universal aliases.", "Reject custody inferred from location, ownership inferred from custody, conformity inferred from a signature or recall inferred from an exposure result.", "Reject aggregation and transformation collapsed into one relationship or membership represented without a validity interval and source.", "Reject event, observation, record, ingestion and correction times collapsed into one timestamp.", "Reject last-write-wins when sources conflict; preserve competing assertions, gaps, evidence, correction and precedence policy.", "Reject protected graph disclosure, certification, recall, enforcement or record destruction outside delegated authority." ] }, "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": "pattern", "status": "accepted", "rationale": "The root is a reusable cross-organizational graph and query pattern. It links externally mastered objects, events and evidence while preserving source authority, gaps and corrections." }, "decisions": [ { "concept": "Trace and chain-of-custody pattern boundary", "disposition": "accepted", "rationale": "The pattern owns graph scope, typed edges, query results, gaps and correction lineage rather than the lifecycle of linked records." }, { "concept": "Persistent graph query result snapshot and claim", "disposition": "accepted-as-distinct-semantic-kinds", "rationale": "A query and its qualified result do not replace the underlying graph, and a chain-of-custody claim has additional attribution rules." }, { "concept": "WM-FLW-004 parent signal", "disposition": "held-as-compositional-reference", "rationale": "Goods Movement is a broader physical-flow context, while the trace pattern also covers custody claims and federated evidence." }, { "concept": "WM-ACT-015 COMPOSE relation", "disposition": "accepted-as-typed-event-composition-only", "rationale": "The trace graph composes event references and edges but generic event identity and lifecycle remain external." }, { "concept": "Aggregation and transformation", "disposition": "accepted-as-distinct-time-qualified-edges", "rationale": "Parent-child membership changes and input-output process changes have different semantics and evidence." }, { "concept": "Custody possession control responsibility and ownership", "disposition": "accepted-as-independent-roles-and-assertions", "rationale": "Neither location nor custody alone establishes ownership or legal responsibility." }, { "concept": "Physical segregation controlled blending mass balance and book-and-claim", "disposition": "accepted-as-profile-discriminated-models", "rationale": "The profiles permit different links between physical material flow and attributed product characteristics." }, { "concept": "Evidence digest signature credential and verification", "disposition": "accepted-as-support-not-automatic-truth", "rationale": "Integrity or successful verification can establish document properties while the real-world assertion and authority still require evaluation." }, { "concept": "Exposure and recall", "disposition": "accepted-with-decision-boundary", "rationale": "The pattern derives a qualified affected set and uncertainty; accountable external authorities own recall, alert and enforcement decisions." }, { "concept": "Single-provider waiver and local no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet and one bounded Grok attempt each timed out after 120 seconds. Codex separately audited the frozen validated result and comparison without acquiring new facts, so assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-FLW-013 each timed out after 120 seconds; no external result was admitted.", "Relation hold: WM-FLW-004 remains a compositional reference rather than an approved parent until joint boundary review.", "Composition hold: WM-ACT-015 is composed only as typed event references; generic event identity and lifecycle remain external.", "Boundary hold: products, lots, serials, handling units, shipments, movements, journeys, places, parties, events, observations, handovers, documents, credentials, incidents, recalls, claims and evidence remain external masters.", "Claim-model hold: physical segregation, controlled blending, mass balance and book-and-claim require explicit profile and attribution rules.", "Truth hold: an event, location, document, digest, signature, credential or verification result does not alone prove custody, ownership, conformity, safety or legal responsibility.", "Decision hold: exposure results require an accountable external authority for recall, certification, enforcement, remedy or public disclosure.", "Profile hold: food, pharmaceuticals, mining, forestry, energy, circularity, maritime, air cargo, customs, dangerous-goods and jurisdiction profiles need independent validation.", "Interoperability hold: GS1, UN/CEFACT, ISO, FDA, EU, DCSA, IATA, RFC and W3C projections require exact release pins, conformance tests and semantic-loss declarations.", "Completeness hold: the 24-source draft is broad but does not claim universal sector, legal, evidential or operational coverage.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [] }, "statistics": { "sources": 24, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }