# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T12:11:26Z", "synthesisSha256": "527d374ee1430090d73f1352bb708cb529e5fadff81ef6bf44729daf3d7fef59", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-POL-026", "registryId": "vr.wm-pol-026", "name": "Customs Declaration / Clearance", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.POL.CUS2" ], "tags": [ "customs", "declaration", "clearance", "soc.pol.cus2" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-pol-026-customs-declaration-clearance/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-pol-026", "model": { "registry_id": "vr.wm-pol-026", "model_id": "WM-POL-026", "name": "Customs Declaration / Clearance", "entry_kind": "entity", "purpose": "Represent one customs declaration and its attributed processing, assessment and release evidence across revisions.", "scope_statement": "A persistent declaration record, including a draft or a record of an allowed non-electronic declaration. Clearance is represented by linked acts, scoped status assertions and outstanding obligations. The model is a proposed information structure, not a filing agent, universal customs workflow or authority to move goods.", "in_scope": [ "Declaration-specific identity, parties, procedure profile and line assertions", "Supporting evidence, assessed amounts and financial conditions as references", "Lodgement, authority responses, release scopes, amendment continuity and post-clearance links" ], "out_of_scope": [ "Goods, consignments, transport movements, parties, customs offices and tariff or legal-rule masters", "Security summary filings, migration cases and border management policy as independent domains", "Risk scoring, operational control tactics, enforcement, detention operations or controlled-item handling", "Binding classification, origin or valuation decisions; tax calculation, payment, filing, legal advice and authorisation to release goods" ], "boundary_notes": [ { "neighbor": "WM-POL-006 Border / Customs / Migration", "distinction": "Registry parent is a candidate domain alignment. This model specialises a declaration instance; border policy, migration and institutional operations remain external.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "Goods, consignment and transport records", "distinction": "Declaration lines reference these masters. A tariff code is a class, not line identity; release does not establish physical departure.", "source_refs": [ "SRC-004", "SRC-005" ] }, { "neighbor": "WM-REC-010 Decision / Approval Record", "distinction": "Authority acts retain external identity and scope. A declaration can exist before any decision, and local receipt does not issue an approval.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-POL-017 Administrative Procedure / Case", "distinction": "An audit, appeal or other administrative case is linked when present; the declaration is neither the complete case nor the procedure definition.", "source_refs": [ "SRC-002" ] }, { "neighbor": "WCO Data Model and EUCDM", "distinction": "Alignment targets only. No mapping, runtime dependency or exact schema conformance is implemented; conflicting EUCDM overview version labels remain unresolved.", "source_refs": [ "SRC-004", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Revised Kyoto Convention - General Annex, Chapter 3", "organization": "World Customs Organization", "url": "https://www.wcoomd.org/en/topics/facilitation/instrument-and-tools/conventions/pf_revised_kyoto_conv/kyoto_new/gach3.aspx", "version_or_date": "Revised Convention general annex; official web text read 2026-10-06; national implementation not verified", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T12:10:22Z", "relevance": "Standards 3.6-3.8, 3.11-3.32 and 3.40-3.43 support declarant responsibility, declaration content, amendments, simplifications and qualified release. Treaty implementation is jurisdiction-specific." }, { "id": "SRC-002", "title": "Agreement on Trade Facilitation", "organization": "World Trade Organization", "url": "https://www.wto.org/english/docs_e/legal_e/tfa-nov14_e.htm", "version_or_date": "Official agreement text; entry into force 22 February 2017; member implementation not verified", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T12:10:22Z", "relevance": "Articles 4, 7.1-7.5, 10.4 and 12 support review, pre-arrival processing, separation of release and final assessment, post-clearance review and confidential information exchange." }, { "id": "SRC-003", "title": "Customs declaration", "organization": "European Commission", "url": "https://taxation-customs.ec.europa.eu/customs/customs-procedures-import-and-export/customs-operations/customs-declaration_en", "version_or_date": "Undated official guidance read 2026-10-06; consolidated legal pin unresolved", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T12:10:22Z", "relevance": "EU illustration of declaration purpose, parties, office, oral and other forms, simplified declarations, centralised clearance and entry in records. Guidance is not a universal legal profile." }, { "id": "SRC-004", "title": "WCO Data Model", "organization": "World Customs Organization", "url": "https://www.wcoomd.org/en/topics/facilitation/instrument-and-tools/tools/data-model.aspx", "version_or_date": "Overview describes version 4; exact information package and patch release not pinned", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T12:10:22Z", "relevance": "Reusable data definitions and messages for cross-border agencies; conceptual alignment only. The overview does not supply a validated instance schema." }, { "id": "SRC-005", "title": "What is the Harmonized System (HS)?", "organization": "World Customs Organization", "url": "https://www.wcoomd.org/en/topics/nomenclature/overview/what-is-the-harmonized-system.aspx", "version_or_date": "Undated overview read 2026-10-06; applicable nomenclature edition not pinned", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T12:10:22Z", "relevance": "Commodity classification differs from item identity; national tariff extensions, effective editions and classification decisions require explicit bindings." }, { "id": "SRC-006", "title": "Calculation of customs duties", "organization": "European Commission", "url": "https://taxation-customs.ec.europa.eu/customs/common-customs-tariff-cct/calculation-customs-duties_en", "version_or_date": "Undated official guidance read 2026-10-06; tariff rates and legal amendments not verified", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T12:10:22Z", "relevance": "EU illustration of tariff, value and origin dependencies; valuation methods and adjustments motivate separate declared value, assessment basis and evidence." }, { "id": "SRC-007", "title": "Rules of origin for goods", "organization": "European Commission", "url": "https://taxation-customs.ec.europa.eu/customs/rules-origin-goods_en", "version_or_date": "Undated official guidance read 2026-10-06; arrangement-specific rule versions not verified", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T12:10:22Z", "relevance": "Origin is distinct from shipment location; preferential and non-preferential origin and origin rulings require separate assertions and applicable arrangements." }, { "id": "SRC-008", "title": "EU Customs Data Model (EUCDM)", "organization": "European Commission", "url": "https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs/eu-customs-data-model-eucdm_en", "version_or_date": "Page news cites 7.0.11 (August 2026), while legal-text paragraph cites 7.0.1; release pin unresolved", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T12:10:22Z", "relevance": "Data requirements, national customisation and WCO mapping motivate versioned projections. Conflicting page version labels are retained as a verification hold; no release is silently selected." } ], "structure": { "bundles": [ { "id": "b-context", "name": "Declaration context", "description": "Identity, applicable procedure and accountable participation.", "rationale": "Separate this concern so evidence and authority can be assessed without collapsing other declaration states.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "layers": [ { "id": "l-identity", "name": "Declaration identity and profile", "description": "One declaration record persists across local revisions and authority messages. Proposed local identity must also cover drafts and non-electronic forms without inventing an official registration number.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "f-identity", "name": "Declaration identity and profile", "description": "One declaration record persists across local revisions and authority messages. Proposed local identity must also cover drafts and non-electronic forms without inventing an official registration number.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "questions": [ { "id": "q-identity-1", "text": "Which authoritative declaration identifier or provisional local identifier identifies this record?", "kind": "identity", "answer_data": [ "issuer and namespace", "identifier and assignment status", "aliases and revision" ] }, { "id": "q-identity-2", "text": "Which jurisdiction, movement direction and requested customs procedure govern this declaration?", "kind": "classification", "answer_data": [ "jurisdiction profile and version", "import export transit or other procedure code", "effective period and applicability evidence" ] }, { "id": "q-identity-3", "text": "Which declaration form and simplification basis apply to this instance?", "kind": "definition", "answer_data": [ "standard simplified oral act or records-entry form", "authorisation reference or exception basis", "supplementary declaration linkage" ] }, { "id": "q-identity-4", "text": "What evidence distinguishes this declaration from an invoice, security filing or duplicate registration?", "kind": "quality", "answer_data": [ "authoritative acknowledgment or observed act", "document role and correlation evidence", "unresolved match candidates" ] } ], "data_elements": [ { "id": "d-identity-1", "name": "Declaration identity and profile - identity context", "description": "Candidate object fields: issuer and namespace; identifier and assignment status; aliases and revision. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "d-identity-2", "name": "Declaration identity and profile - classification context", "description": "Candidate object fields: jurisdiction profile and version; import export transit or other procedure code; effective period and applicability evidence. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "d-identity-3", "name": "Declaration identity and profile - definition context", "description": "Candidate object fields: standard simplified oral act or records-entry form; authorisation reference or exception basis; supplementary declaration linkage. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "d-identity-4", "name": "Declaration identity and profile - quality context", "description": "Candidate object fields: authoritative acknowledgment or observed act; document role and correlation evidence; unresolved match candidates. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "a-identity", "name": "Declaration identity and profile evidence record", "description": "Versioned evidence index or controlled snapshot for declaration identity and profile. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "l-parties", "name": "Declarant and representation", "description": "Declarant, representative and authority are roles with evidence of capacity. Neither goods ownership nor local data stewardship establishes authority to declare.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "f-parties", "name": "Declarant and representation", "description": "Declarant, representative and authority are roles with evidence of capacity. Neither goods ownership nor local data stewardship establishes authority to declare.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "q-parties-1", "text": "Who is entitled to act as declarant under the selected profile?", "kind": "authority", "answer_data": [ "party master reference", "capacity and eligibility basis", "effective time and evidence" ] }, { "id": "q-parties-2", "text": "Who represents whom and within which documented mandate?", "kind": "relationship", "answer_data": [ "principal and representative references", "representation type and mandate scope", "validity period and disputed authority" ] }, { "id": "q-parties-3", "text": "Who maintains the declaration record and which authority owns its official status assertions?", "kind": "ownership", "answer_data": [ "local custodian role", "authority of record", "responsibility and escalation route" ] }, { "id": "q-parties-4", "text": "Which party-role conflicts or expired mandates prevent a proposed local action?", "kind": "constraint", "answer_data": [ "conflicting role assertions", "mandate expiry or missing proof", "blocked action and resolution owner" ] } ], "data_elements": [ { "id": "d-parties-1", "name": "Declarant and representation - authority context", "description": "Candidate object fields: party master reference; capacity and eligibility basis; effective time and evidence. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "d-parties-2", "name": "Declarant and representation - relationship context", "description": "Candidate object fields: principal and representative references; representation type and mandate scope; validity period and disputed authority. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "d-parties-3", "name": "Declarant and representation - ownership context", "description": "Candidate object fields: local custodian role; authority of record; responsibility and escalation route. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "d-parties-4", "name": "Declarant and representation - constraint context", "description": "Candidate object fields: conflicting role assertions; mandate expiry or missing proof; blocked action and resolution owner. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "a-parties", "name": "Declarant and representation evidence record", "description": "Versioned evidence index or controlled snapshot for declarant and representation. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-declared-goods", "name": "Declared goods", "description": "Line-scoped quantities, classification and origin assertions.", "rationale": "Separate this concern so evidence and authority can be assessed without collapsing other declaration states.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "l-goods", "name": "Declaration lines and goods references", "description": "Declaration-specific lines refer to goods and consignments without mastering their physical lifecycle. Line identity remains distinct from a commodity class or changing display sequence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-008" ], "findings": [ { "id": "f-goods", "name": "Declaration lines and goods references", "description": "Declaration-specific lines refer to goods and consignments without mastering their physical lifecycle. Line identity remains distinct from a commodity class or changing display sequence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-008" ], "questions": [ { "id": "q-goods-1", "text": "Which stable declaration lines cover which goods, consignments and packages?", "kind": "composition", "answer_data": [ "line identity and displayed item number", "goods consignment package references", "allocation quantities and revision lineage" ] }, { "id": "q-goods-2", "text": "Which quantities and masses are declared or observed for each line?", "kind": "measurement", "answer_data": [ "value unit and measurement basis", "declared or observed status with method time and uncertainty", "source and discrepancy" ] }, { "id": "q-goods-3", "text": "Which commodity classification is asserted for each line under which edition?", "kind": "classification", "answer_data": [ "HS or national tariff code and scheme version", "asserting party and ruling reference", "effective date and disputed classification" ] }, { "id": "q-goods-4", "text": "Which presentation place and customs offices are relevant to these goods?", "kind": "spatial", "answer_data": [ "presentation location reference", "lodgement supervising and presentation office roles", "arrival evidence and centralised-clearance basis" ] } ], "data_elements": [ { "id": "d-goods-1", "name": "Declaration lines and goods references - composition context", "description": "Candidate object fields: line identity and displayed item number; goods consignment package references; allocation quantities and revision lineage. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-008" ] }, { "id": "d-goods-2", "name": "Declaration lines and goods references - measurement context", "description": "Candidate object fields: value unit and measurement basis; declared or observed status with method time and uncertainty; source and discrepancy. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-008" ] }, { "id": "d-goods-3", "name": "Declaration lines and goods references - classification context", "description": "Candidate object fields: HS or national tariff code and scheme version; asserting party and ruling reference; effective date and disputed classification. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-008" ] }, { "id": "d-goods-4", "name": "Declaration lines and goods references - spatial context", "description": "Candidate object fields: presentation location reference; lodgement supervising and presentation office roles; arrival evidence and centralised-clearance basis. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "a-goods", "name": "Declaration lines and goods references evidence record", "description": "Versioned evidence index or controlled snapshot for declaration lines and goods references. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "l-origin", "name": "Origin and preference assertions", "description": "Origin assertions carry their own rule basis and evidence. Preference requested and preference accepted are separate observations; shipment origin is a separate logistics property.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "f-origin", "name": "Origin and preference assertions", "description": "Origin assertions carry their own rule basis and evidence. Preference requested and preference accepted are separate observations; shipment origin is a separate logistics property.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-origin-1", "text": "Which non-preferential origin is asserted and under which applicable rule?", "kind": "definition", "answer_data": [ "country assertion", "rule version and rationale", "supporting evidence and uncertainty" ] }, { "id": "q-origin-2", "text": "Which preferential arrangement and proof support the preference claim?", "kind": "requirement", "answer_data": [ "arrangement and effective version", "proof reference issuer and validity", "line scope and unmet conditions" ] }, { "id": "q-origin-3", "text": "What authority response accepts, limits or disputes the claimed preference?", "kind": "decision", "answer_data": [ "response reference and authority", "affected lines and reason", "effective time and review state" ] }, { "id": "q-origin-4", "text": "How are conflicting origin, dispatch-country and ruling records kept distinguishable?", "kind": "validation", "answer_data": [ "competing assertions and role labels", "ruling scope and validity", "review outcome without overwriting original claim" ] } ], "data_elements": [ { "id": "d-origin-1", "name": "Origin and preference assertions - definition context", "description": "Candidate object fields: country assertion; rule version and rationale; supporting evidence and uncertainty. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "d-origin-2", "name": "Origin and preference assertions - requirement context", "description": "Candidate object fields: arrangement and effective version; proof reference issuer and validity; line scope and unmet conditions. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "d-origin-3", "name": "Origin and preference assertions - decision context", "description": "Candidate object fields: response reference and authority; affected lines and reason; effective time and review state. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "d-origin-4", "name": "Origin and preference assertions - validation context", "description": "Candidate object fields: competing assertions and role labels; ruling scope and validity; review outcome without overwriting original claim. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "a-origin", "name": "Origin and preference assertions evidence record", "description": "Versioned evidence index or controlled snapshot for origin and preference assertions. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-financial-basis", "name": "Financial basis", "description": "Attributed valuation, assessment and financial-condition evidence.", "rationale": "Separate this concern so evidence and authority can be assessed without collapsing other declaration states.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "layers": [ { "id": "l-value", "name": "Valuation evidence", "description": "A proposed valuation context records amounts, adjustments and methodology as attributed assertions. It does not determine a legally binding value or assume the invoice total is the customs value.", "source_refs": [ "SRC-006" ], "findings": [ { "id": "f-value", "name": "Valuation evidence", "description": "A proposed valuation context records amounts, adjustments and methodology as attributed assertions. It does not determine a legally binding value or assume the invoice total is the customs value.", "source_refs": [ "SRC-006" ], "questions": [ { "id": "q-value-1", "text": "Which customs value and currency are asserted for each affected line?", "kind": "measurement", "answer_data": [ "amount and currency", "line scope and declared or assessed status", "valuation effective time" ] }, { "id": "q-value-2", "text": "Which valuation method and supporting rationale were used?", "kind": "process", "answer_data": [ "method code and legal profile", "method selection rationale", "source document references" ] }, { "id": "q-value-3", "text": "Which price adjustments and currency-conversion inputs support the asserted value?", "kind": "provenance", "answer_data": [ "invoice amount and adjustment components", "exchange rate source and applicable date", "derivation rounding and evidence references" ] }, { "id": "q-value-4", "text": "Which missing or disputed valuation inputs require review before use?", "kind": "exception", "answer_data": [ "missing evidence or conflicting amount", "uncertainty and affected calculation", "review role and disposition" ] } ], "data_elements": [ { "id": "d-value-1", "name": "Valuation evidence - measurement context", "description": "Candidate object fields: amount and currency; line scope and declared or assessed status; valuation effective time. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "d-value-2", "name": "Valuation evidence - process context", "description": "Candidate object fields: method code and legal profile; method selection rationale; source document references. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "d-value-3", "name": "Valuation evidence - provenance context", "description": "Candidate object fields: invoice amount and adjustment components; exchange rate source and applicable date; derivation rounding and evidence references. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "d-value-4", "name": "Valuation evidence - exception context", "description": "Candidate object fields: missing evidence or conflicting amount; uncertainty and affected calculation; review role and disposition. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "a-value", "name": "Valuation evidence evidence record", "description": "Versioned evidence index or controlled snapshot for valuation evidence. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "l-assessment", "name": "Assessment and financial conditions", "description": "Store assessment and security references with clear monetary scope. Estimated liability, authoritative assessment, payment and guarantee evidence are distinct; the root is not a tax engine or payment ledger.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "findings": [ { "id": "f-assessment", "name": "Assessment and financial conditions", "description": "Store assessment and security references with clear monetary scope. Estimated liability, authoritative assessment, payment and guarantee evidence are distinct; the root is not a tax engine or payment ledger.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "q-assessment-1", "text": "Which duties, taxes and charges were estimated or assessed and by which authority?", "kind": "decision", "answer_data": [ "amount currency and charge type", "line allocation and assessment reference", "provisional or final status" ] }, { "id": "q-assessment-2", "text": "Which dated tariff and assessment basis applies to the recorded amounts?", "kind": "temporal", "answer_data": [ "tariff version and effective date", "classification origin value inputs", "legal basis and calculation record reference" ] }, { "id": "q-assessment-3", "text": "What payment or guarantee evidence satisfies each stated financial condition?", "kind": "evidence", "answer_data": [ "condition and obligation reference", "payment or security instrument reference", "authority confirmation and remaining balance" ] }, { "id": "q-assessment-4", "text": "Which disputed, deferred or adjusted amounts remain unresolved?", "kind": "exception", "answer_data": [ "dispute or deferment basis", "affected amount and currency", "review reference and unresolved obligation" ] } ], "data_elements": [ { "id": "d-assessment-1", "name": "Assessment and financial conditions - decision context", "description": "Candidate object fields: amount currency and charge type; line allocation and assessment reference; provisional or final status. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "d-assessment-2", "name": "Assessment and financial conditions - temporal context", "description": "Candidate object fields: tariff version and effective date; classification origin value inputs; legal basis and calculation record reference. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "d-assessment-3", "name": "Assessment and financial conditions - evidence context", "description": "Candidate object fields: condition and obligation reference; payment or security instrument reference; authority confirmation and remaining balance. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "d-assessment-4", "name": "Assessment and financial conditions - exception context", "description": "Candidate object fields: dispute or deferment basis; affected amount and currency; review reference and unresolved obligation. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "a-assessment", "name": "Assessment and financial conditions evidence record", "description": "Versioned evidence index or controlled snapshot for assessment and financial conditions. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-processing", "name": "Authority processing", "description": "Lodgement, acceptance, supporting material and control observations.", "rationale": "Separate this concern so evidence and authority can be assessed without collapsing other declaration states.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ], "layers": [ { "id": "l-lodgement", "name": "Lodgement and acceptance evidence", "description": "Submission, technical receipt and legal acceptance are separate assertions. Preserve original messages and legal-profile terminology instead of forcing every national system into a single ordered state machine.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "f-lodgement", "name": "Lodgement and acceptance evidence", "description": "Submission, technical receipt and legal acceptance are separate assertions. Preserve original messages and legal-profile terminology instead of forcing every national system into a single ordered state machine.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "q-lodgement-1", "text": "What was lodged, through which permitted channel and by which actor?", "kind": "event", "answer_data": [ "payload revision or non-electronic declaration evidence", "channel and submitting actor", "submission event time and correlation identifier" ] }, { "id": "q-lodgement-2", "text": "What evidence establishes receipt, acceptance or rejection by the competent authority?", "kind": "state", "answer_data": [ "authority message or recorded act", "status vocabulary and reason", "affected revision and official identifier" ] }, { "id": "q-lodgement-3", "text": "Which event times, due dates and legal clock rules apply to lodgement?", "kind": "temporal", "answer_data": [ "pre-arrival presentation and acceptance times", "deadline basis calendar and exception", "observation time and unresolved precision" ] }, { "id": "q-lodgement-4", "text": "Which missing particulars or documents are permitted and when must they be supplied?", "kind": "requirement", "answer_data": [ "simplification authority or exception", "required supplement and deadline basis", "responsible role and completion evidence" ] } ], "data_elements": [ { "id": "d-lodgement-1", "name": "Lodgement and acceptance evidence - event context", "description": "Candidate object fields: payload revision or non-electronic declaration evidence; channel and submitting actor; submission event time and correlation identifier. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "d-lodgement-2", "name": "Lodgement and acceptance evidence - state context", "description": "Candidate object fields: authority message or recorded act; status vocabulary and reason; affected revision and official identifier. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "d-lodgement-3", "name": "Lodgement and acceptance evidence - temporal context", "description": "Candidate object fields: pre-arrival presentation and acceptance times; deadline basis calendar and exception; observation time and unresolved precision. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "d-lodgement-4", "name": "Lodgement and acceptance evidence - requirement context", "description": "Candidate object fields: simplification authority or exception; required supplement and deadline basis; responsible role and completion evidence. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "a-lodgement", "name": "Lodgement and acceptance evidence evidence record", "description": "Versioned evidence index or controlled snapshot for lodgement and acceptance evidence. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "l-support", "name": "Supporting documents and controls", "description": "Index evidence and control outcomes at policy level. A document upload or a permit reference is not proof of authenticity, applicability, remaining quota or permission to release.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "f-support", "name": "Supporting documents and controls", "description": "Index evidence and control outcomes at policy level. A document upload or a permit reference is not proof of authenticity, applicability, remaining quota or permission to release.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "q-support-1", "text": "Which supporting documents substantiate each declaration assertion?", "kind": "evidence", "answer_data": [ "invoice transport origin and certificate references", "assertion and line coverage", "issuer revision and verification state" ] }, { "id": "q-support-2", "text": "Which prohibitions, restrictions or agency permissions require a documented policy decision?", "kind": "constraint", "answer_data": [ "applicable policy and effective version", "permit scope status and responsible authority", "unresolved restriction and review reference" ] }, { "id": "q-support-3", "text": "Which documentary or physical control outcome has the authority recorded?", "kind": "process", "answer_data": [ "control reference and type", "affected lines and attributed result", "event time and follow-up requirement" ] }, { "id": "q-support-4", "text": "Which control details and personal or commercial information must be restricted?", "kind": "security", "answer_data": [ "sensitivity and authorised audience", "disclosure basis and redacted projection", "access decision and audit reference" ] } ], "data_elements": [ { "id": "d-support-1", "name": "Supporting documents and controls - evidence context", "description": "Candidate object fields: invoice transport origin and certificate references; assertion and line coverage; issuer revision and verification state. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "d-support-2", "name": "Supporting documents and controls - constraint context", "description": "Candidate object fields: applicable policy and effective version; permit scope status and responsible authority; unresolved restriction and review reference. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "d-support-3", "name": "Supporting documents and controls - process context", "description": "Candidate object fields: control reference and type; affected lines and attributed result; event time and follow-up requirement. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "d-support-4", "name": "Supporting documents and controls - security context", "description": "Candidate object fields: sensitivity and authorised audience; disclosure basis and redacted projection; access decision and audit reference. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "a-support", "name": "Supporting documents and controls evidence record", "description": "Versioned evidence index or controlled snapshot for supporting documents and controls. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-outcomes", "name": "Outcomes and change", "description": "Qualified release, continuing obligations and versioned corrections.", "rationale": "Separate this concern so evidence and authority can be assessed without collapsing other declaration states.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "layers": [ { "id": "l-release", "name": "Release scope and continuing obligations", "description": "Goods release is an authority-qualified outcome over a specified scope. It need not establish final monetary determination, physical departure, procedure discharge or the absence of later review.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "f-release", "name": "Release scope and continuing obligations", "description": "Goods release is an authority-qualified outcome over a specified scope. It need not establish final monetary determination, physical departure, procedure discharge or the absence of later review.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "q-release-1", "text": "Which authority act establishes release or a policy-level hold for which goods?", "kind": "decision", "answer_data": [ "decision and authority reference", "line or quantity scope", "effective time and reason category" ] }, { "id": "q-release-2", "text": "Which conditions remain attached to the recorded release outcome?", "kind": "constraint", "answer_data": [ "payment security document or other condition", "evidence and responsible role", "unfulfilled obligation and due basis" ] }, { "id": "q-release-3", "text": "How are mixed release states across declaration lines represented?", "kind": "state", "answer_data": [ "released held or unresolved line scopes", "conflicting message revisions", "aggregation rule that preserves exceptions" ] }, { "id": "q-release-4", "text": "What evidence separately establishes exit, procedure discharge or continued supervision when applicable?", "kind": "lifecycle", "answer_data": [ "procedure-specific external record references", "status and outstanding obligations", "authority confirmation or explicit unknown" ] } ], "data_elements": [ { "id": "d-release-1", "name": "Release scope and continuing obligations - decision context", "description": "Candidate object fields: decision and authority reference; line or quantity scope; effective time and reason category. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-release-2", "name": "Release scope and continuing obligations - constraint context", "description": "Candidate object fields: payment security document or other condition; evidence and responsible role; unfulfilled obligation and due basis. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-release-3", "name": "Release scope and continuing obligations - state context", "description": "Candidate object fields: released held or unresolved line scopes; conflicting message revisions; aggregation rule that preserves exceptions. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-release-4", "name": "Release scope and continuing obligations - lifecycle context", "description": "Candidate object fields: procedure-specific external record references; status and outstanding obligations; authority confirmation or explicit unknown. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "a-release", "name": "Release scope and continuing obligations evidence record", "description": "Versioned evidence index or controlled snapshot for release scope and continuing obligations. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "l-revision", "name": "Amendment and invalidation continuity", "description": "Proposed changes and authority-approved changes are distinct. Local corrections preserve prior assertions and do not themselves amend or invalidate the legally effective declaration.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "f-revision", "name": "Amendment and invalidation continuity", "description": "Proposed changes and authority-approved changes are distinct. Local corrections preserve prior assertions and do not themselves amend or invalidate the legally effective declaration.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "q-revision-1", "text": "Which amendment, withdrawal or invalidation request concerns which declaration revision?", "kind": "lifecycle", "answer_data": [ "request type and grounds", "target revision and affected lines", "requester authority and submitted evidence" ] }, { "id": "q-revision-2", "text": "Which authority response permits or refuses the requested change?", "kind": "authority", "answer_data": [ "response reference and legal basis", "effective time and approved scope", "refusal reason and review route" ] }, { "id": "q-revision-3", "text": "How is the original assertion linked to each superseding assertion without erasing history?", "kind": "provenance", "answer_data": [ "before and after revisions", "actor reason and source message", "supersession lineage and payload retention rule" ] }, { "id": "q-revision-4", "text": "How are duplicates, late messages and concurrent correction requests reconciled?", "kind": "exception", "answer_data": [ "message identity and correlation", "expected revision and conflicting proposals", "quarantine disposition and reviewer" ] } ], "data_elements": [ { "id": "d-revision-1", "name": "Amendment and invalidation continuity - lifecycle context", "description": "Candidate object fields: request type and grounds; target revision and affected lines; requester authority and submitted evidence. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "d-revision-2", "name": "Amendment and invalidation continuity - authority context", "description": "Candidate object fields: response reference and legal basis; effective time and approved scope; refusal reason and review route. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "d-revision-3", "name": "Amendment and invalidation continuity - provenance context", "description": "Candidate object fields: before and after revisions; actor reason and source message; supersession lineage and payload retention rule. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "d-revision-4", "name": "Amendment and invalidation continuity - exception context", "description": "Candidate object fields: message identity and correlation; expected revision and conflicting proposals; quarantine disposition and reviewer. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "a-revision", "name": "Amendment and invalidation continuity evidence record", "description": "Versioned evidence index or controlled snapshot for amendment and invalidation continuity. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-continuity", "name": "Review and exchange", "description": "External review links, governed records and explicit projection limits.", "rationale": "Separate this concern so evidence and authority can be assessed without collapsing other declaration states.", "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ], "layers": [ { "id": "l-review", "name": "Post-clearance review and record disposition", "description": "Post-clearance audit and challenge outcomes remain external proceedings linked to this declaration. Local retention follows the adopting legal profile and lawful holds, not indefinite storage by default.", "source_refs": [ "SRC-002" ], "findings": [ { "id": "f-review", "name": "Post-clearance review and record disposition", "description": "Post-clearance audit and challenge outcomes remain external proceedings linked to this declaration. Local retention follows the adopting legal profile and lawful holds, not indefinite storage by default.", "source_refs": [ "SRC-002" ], "questions": [ { "id": "q-review-1", "text": "Which audit, appeal or repayment proceeding concerns this declaration?", "kind": "relationship", "answer_data": [ "external proceeding identifier", "scope and originating decision", "responsible authority and current reference status" ] }, { "id": "q-review-2", "text": "Which notified review outcome changes the declaration view or leaves obligations open?", "kind": "event", "answer_data": [ "outcome and notification evidence", "affected assertions and obligations", "effective time and contested status" ] }, { "id": "q-review-3", "text": "Which retention schedule and legal holds govern each declaration artifact?", "kind": "retention", "answer_data": [ "jurisdiction and record category", "trigger and retention basis", "hold scope review date and disposal authority" ] }, { "id": "q-review-4", "text": "What can be lawfully disposed of or redacted while retaining required accountability?", "kind": "privacy", "answer_data": [ "payload and recipient scope", "disposition decision and minimum lawful tombstone", "execution evidence and protected references" ] } ], "data_elements": [ { "id": "d-review-1", "name": "Post-clearance review and record disposition - relationship context", "description": "Candidate object fields: external proceeding identifier; scope and originating decision; responsible authority and current reference status. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "d-review-2", "name": "Post-clearance review and record disposition - event context", "description": "Candidate object fields: outcome and notification evidence; affected assertions and obligations; effective time and contested status. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "d-review-3", "name": "Post-clearance review and record disposition - retention context", "description": "Candidate object fields: jurisdiction and record category; trigger and retention basis; hold scope review date and disposal authority. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "d-review-4", "name": "Post-clearance review and record disposition - privacy context", "description": "Candidate object fields: payload and recipient scope; disposition decision and minimum lawful tombstone; execution evidence and protected references. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] } ], "artifacts": [ { "id": "a-review", "name": "Post-clearance review and record disposition evidence record", "description": "Versioned evidence index or controlled snapshot for post-clearance review and record disposition. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "l-exchange", "name": "Exchange profiles and reconciliation", "description": "External data models supply alignment targets. A projection must preserve declaration meaning, revision, message role and uncertainty; no exact WCO or national conformance is claimed.", "source_refs": [ "SRC-004", "SRC-008" ], "findings": [ { "id": "f-exchange", "name": "Exchange profiles and reconciliation", "description": "External data models supply alignment targets. A projection must preserve declaration meaning, revision, message role and uncertainty; no exact WCO or national conformance is claimed.", "source_refs": [ "SRC-004", "SRC-008" ], "questions": [ { "id": "q-exchange-1", "text": "Which pinned data model and national message profile define an intended exchange?", "kind": "interoperability", "answer_data": [ "model release and information package", "national schema and code-list versions", "applicable message role" ] }, { "id": "q-exchange-2", "text": "Which required fields, cardinalities and code constraints remain unresolved for that profile?", "kind": "validation", "answer_data": [ "profile rule identifiers", "local-to-external mapping and loss report", "conformance result or untested status" ] }, { "id": "q-exchange-3", "text": "How will an imported response preserve its source meaning when vocabularies differ?", "kind": "quality", "answer_data": [ "raw external status and message reference", "mapping revision and uncertainty", "unmapped values and reconciliation reviewer" ] }, { "id": "q-exchange-4", "text": "Who may receive which declaration projection for a stated purpose?", "kind": "access", "answer_data": [ "recipient role and purpose", "authorised field and artifact scope", "redaction policy and export audit reference" ] } ], "data_elements": [ { "id": "d-exchange-1", "name": "Exchange profiles and reconciliation - interoperability context", "description": "Candidate object fields: model release and information package; national schema and code-list versions; applicable message role. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] }, { "id": "d-exchange-2", "name": "Exchange profiles and reconciliation - validation context", "description": "Candidate object fields: profile rule identifiers; local-to-external mapping and loss report; conformance result or untested status. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] }, { "id": "d-exchange-3", "name": "Exchange profiles and reconciliation - quality context", "description": "Candidate object fields: raw external status and message reference; mapping revision and uncertainty; unmapped values and reconciliation reviewer. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] }, { "id": "d-exchange-4", "name": "Exchange profiles and reconciliation - access context", "description": "Candidate object fields: recipient role and purpose; authorised field and artifact scope; redaction policy and export audit reference. Preserve unknown, disputed and not-applicable values distinctly; nested constraints require a pinned profile.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "a-exchange", "name": "Exchange profiles and reconciliation evidence record", "description": "Versioned evidence index or controlled snapshot for exchange profiles and reconciliation. Retain assertion status, source references and recipient-specific access.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier with issuer and revision; otherwise governed IRI, then local UUID or ULID. Digest identifies bytes, not legal effect.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "fn-register", "name": "Register local declaration context", "description": "Proposed, unimplemented local operation. Create a proposed local record or reconcile an authoritative identifier without submitting a declaration.", "inputs": [ "jurisdiction profile", "party and provisional or authoritative identity evidence" ], "outputs": [ "local record reference and reconciliation result", "refusal when identity or authority is ambiguous" ], "preconditions": [ "Policy-authorised actor and stated purpose", "Expected local revision matches; access and evidence checks pass", "Applicable jurisdiction/profile and uncertainty are explicit" ], "effects": [ "Create a local draft with source and actor provenance; preserve aliases without asserting official acceptance." ], "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "fn-reconcile-lines", "name": "Reconcile line assertions", "description": "Proposed, unimplemented local operation. Attach goods references, declared quantities, classifications and source evidence to the expected local revision.", "inputs": [ "line identity and evidence", "quantity unit classification and origin assertions" ], "outputs": [ "revision proposal and discrepancy report", "refusal for missing line scope or conflicting identity" ], "preconditions": [ "Policy-authorised actor and stated purpose", "Expected local revision matches; access and evidence checks pass", "Applicable jurisdiction/profile and uncertainty are explicit" ], "effects": [ "Append attributed assertions; do not replace goods masters or determine classification or origin." ], "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "fn-link-assessment", "name": "Link assessment evidence", "description": "Proposed, unimplemented local operation. Record an external valuation, assessment, payment or guarantee reference and its exact scope.", "inputs": [ "authority assessment or valuation evidence", "currency amount condition and line scope" ], "outputs": [ "financial evidence view with unresolved conditions", "refusal for unqualified amount or incompatible scope" ], "preconditions": [ "Policy-authorised actor and stated purpose", "Expected local revision matches; access and evidence checks pass", "Applicable jurisdiction/profile and uncertainty are explicit" ], "effects": [ "Update only the local evidence view; no payment execution, guarantee issuance or binding tax computation." ], "source_refs": [ "SRC-002", "SRC-006" ] }, { "id": "fn-record-response", "name": "Record authority response", "description": "Proposed, unimplemented local operation. Reconcile a receipt, acceptance, control or release assertion from a validated source message.", "inputs": [ "source message identity and authority", "status vocabulary event time revision and affected scope" ], "outputs": [ "scoped status assertions or quarantined conflict", "refusal when authority or message correlation cannot be established" ], "preconditions": [ "Policy-authorised actor and stated purpose", "Expected local revision matches; access and evidence checks pass", "Applicable jurisdiction/profile and uncertainty are explicit" ], "effects": [ "Append status evidence and preserve raw code; technical receipt cannot imply legal acceptance or release." ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "fn-propose-amendment", "name": "Prepare amendment proposal", "description": "Proposed, unimplemented local operation. Prepare a local revision proposal for qualified review without changing the accepted declaration.", "inputs": [ "expected revision and proposed changes", "request grounds evidence and mandate" ], "outputs": [ "reviewable difference record and outstanding requirements", "refusal for stale revision or absent mandate" ], "preconditions": [ "Policy-authorised actor and stated purpose", "Expected local revision matches; access and evidence checks pass", "Applicable jurisdiction/profile and uncertainty are explicit" ], "effects": [ "Create a reversible local proposal; only a separately evidenced authority response establishes its legal disposition." ], "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "fn-project", "name": "Build authorised declaration view", "description": "Proposed, unimplemented local operation. Produce a proposed recipient-specific projection against a pinned profile with a loss report.", "inputs": [ "recipient purpose and access policy", "source revision and target schema/code-list versions" ], "outputs": [ "local projection and validation/loss report", "refusal when disclosure authority or required mapping is unresolved" ], "preconditions": [ "Policy-authorised actor and stated purpose", "Expected local revision matches; access and evidence checks pass", "Applicable jurisdiction/profile and uncertainty are explicit" ], "effects": [ "Read locally authorised evidence; mark untested conformance and unresolved mappings; no transmission or legal filing." ], "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] } ], "composition": [ { "target": "WM-POL-006", "relation": "ALIGN", "purpose": "Candidate registry parent retained as domain context; no inherited executable border or migration semantics.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-REC-010", "relation": "REFERENCE", "purpose": "Optional external authority acts, assessments and amendment/release decisions with identity and scope.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-POL-017", "relation": "REFERENCE", "purpose": "Optional administrative review or audit case master; this model stores declaration-specific links only.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "Goods and consignment master", "relation": "REFERENCE", "purpose": "External master binding to be pinned by adopter; local lines carry allocations and assertions only.", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] }, { "target": "Party and customs-office masters", "relation": "REFERENCE", "purpose": "External actor and location identities with declaration-specific roles and mandate evidence.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WCO Data Model", "relation": "ALIGN", "purpose": "Version and information-package mapping must be pinned and tested before exchange.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "EU Customs Data Model", "relation": "ALIGN", "purpose": "Regional mapping only; overview version conflict and national implementation remain open.", "required": false, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Name a competent customs authority as authority of record and a role-based local custodian; ownership does not grant legal powers.", "Pin jurisdiction, procedure, effective legal sources and external master bindings before operational adoption.", "Declare access purposes, retention schedule, lawful holds, authoritative status sources and escalation roles." ], "namespace_guidance": "Use a governed declaration namespace. Keep issuer-qualified official IDs, provisional local IDs, line IDs and revision IDs distinct. Do not use a date, tariff code or transport reference as root identity.", "registry_links": [ "vr.wm-pol-026", "WM-POL-006 candidate domain alignment", "Neighbor bindings require version and ownership review" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve original declarations, raw authority codes, units, currency, scope and source revision; derived views never overwrite evidence.", "Keep declared, observed, proposed, accepted and disputed values separate. Missing is not zero, false or permission." ], "patch_rules": [ "Require expected revision, actor, purpose, evidence and field-level change reason; quarantine concurrent or uncorrelated responses.", "A local patch cannot amend an official declaration. Record external approval, rejection or invalidation separately." ], "compatibility_rules": [ "Schema and code-list upgrades require a versioned migration and loss report.", "Do not silently equate acceptance with release or release with discharge/final assessment." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with issuer, record role and revision", "Governed global identifier or IRI", "UUID or ULID assigned by the adopting Dimension" ], "timestamp_rule": "Use RFC 3339 with seconds and an explicit offset or Z for timestamps. Keep event time and observation/ingestion time separate; preserve date-only values and uncertainty without inventing precision.", "serial_naming_rule": "Use stable artifact identity and explicit revision or sequence; dates may be descriptive metadata but not identity. Keep line renumbering mappings.", "integrity_rule": "Keep media type, digest algorithm, byte digest, source and verification state for retained payloads. A digest proves neither truth, admissibility nor legal effect. Minimise and dispose of payloads under policy." }, "policies": [ "Research is a reviewable draft under a single-provider waiver; no canonical completeness or legal-conformance claim.", "Source pages inform proposed questions and distinctions; no universal deadlines, tariff rates or eligibility rules are encoded.", "Restrictions, holds and controlled items are policy references only. Do not infer permission from missing evidence or help evade controls.", "Protect commercial and personal information. Applicable domestic law and case-specific disclosure conditions govern sharing; treaty confidentiality examples do not define a universal privacy regime.", "Agent operations are proposed local functions only. Filing, payment, authority decisions and physical actions require a separate authorised implementation." ], "crud": { "read": [ "Return only purpose-authorised fields and artifacts with source, revision, status uncertainty and visible holds." ], "create": [ "Create a local draft after identity/profile checks; record source actor and mandate, and clearly mark official identifiers not yet assigned." ], "update": [ "Append attributed changes using expected revision and authority evidence. Preserve conflicting assertions for review rather than selecting the newest arrival as legally controlling." ], "delete": [ "Adopting-Dimension records policy and authorised records service own retention and deletion execution. Check legal holds and the applicable schedule before disposing of local payloads; retain only a lawful minimal tombstone.", "Local deletion never withdraws a declaration, releases goods or erases independently mastered authority records. History is not a mandate for perpetual personal-data retention." ] }, "roles": [ { "name": "Declarant", "responsibilities": [ "Provide supported assertions and evidence of capacity; review local proposals." ] }, { "name": "Authorised representative", "responsibilities": [ "Act only within a current evidenced mandate and keep principal attribution." ] }, { "name": "Competent customs authority", "responsibilities": [ "Own official acceptance, assessment, control and release assertions under the applicable profile." ] }, { "name": "Declaration data custodian", "responsibilities": [ "Maintain local identity, evidence provenance and revision reconciliation without exercising public powers." ] }, { "name": "Records and access steward", "responsibilities": [ "Apply recipient access, minimisation, retention and lawful hold policy." ] }, { "name": "Independent reviewer", "responsibilities": [ "Review legal/profile applicability and conformance before operational adoption." ] } ], "access": { "default_rule": "Deny disclosure unless recipient, purpose and applicable policy authorise it at every requested scope.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory exchange, audit or review requires an evidenced legal basis, bounded purpose and protected recipient view; no blanket emergency bypass.", "Withhold sensitive operational control detail; use policy-level reason categories and qualified review channels." ], "audit_requirements": [ "Record access, projection, amendment and disposal decisions with actor, purpose, scope, source revision and result; restrict and retain these records under their own policy." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and owner authority/access policies", "spec.yaml and research publication holds", "Pinned customs profile, external source records and recipient-specific projection" ] } }, "coverage": { "claim": "Source-grounded reviewable draft for one persistent customs declaration, with line-scoped assertions and qualified clearance evidence. A separate frozen no-tools local self-audit found no critical conflicts. Source/version checks, current legal profiles, independent review and executable conformance remain open; no operational or universal legal completeness is claimed.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Issuer-qualified root and line identity; provisional and non-electronic forms remain possible." }, { "dimension": "lifecycle", "status": "covered", "notes": "Separate receipt, acceptance, release, amendment, review and continuing obligations." }, { "dimension": "relationships", "status": "covered", "notes": "External goods, parties, authority acts and review cases retain independent masters." }, { "dimension": "temporal", "status": "covered", "notes": "Legal effective and observed time, profile deadlines and uncertain precision stay distinct." }, { "dimension": "provenance", "status": "covered", "notes": "Attributed assertions and source revisions preserve contested evidence." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based custodian and competent authority responsibilities are separate." }, { "dimension": "validation", "status": "gap", "notes": "Research schema can be validated; nested instance schemas and legal applicability are not yet implemented." }, { "dimension": "access", "status": "covered", "notes": "Purpose and recipient-scoped projections with sensitive control evidence restricted." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Profile-specific schedules, legal holds and lawful minimised tombstones." }, { "dimension": "interoperability", "status": "gap", "notes": "WCO and EUCDM conceptual alignment only; release pins, mappings and test fixtures remain incomplete." }, { "dimension": "direct properties", "status": "covered", "notes": "Procedure, currency, status and time are record properties; measurements describe referenced goods assertions, not the physical declaration." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Authority messages and document roles distinguish declaration, invoice and separate security filing." }, { "dimension": "capabilities and hazards", "status": "covered", "notes": "Six proposed local operations include refusal outputs; false release, stale mandate and unqualified amounts are explicit hazards." }, { "dimension": "context and evidence", "status": "covered", "notes": "International instruments and EU examples require adopting-jurisdiction legal review." } ], "known_omissions": [ "Independent external review is absent; the separate local Codex self-audit cannot replace it.", "Direct HTTP verification is blocked by the sandbox and has not been attempted; coordinator-run check_sources.py is required. Browser text access does not establish HTTP status, licensing or current legal applicability.", "EUCDM overview cites both 7.0.11 and 7.0.1. Exact released schemas, national profiles and applicable code lists must be reconciled.", "Full consolidated legal texts, treaty membership/implementation, national exceptions, retention rules and jurisdiction-specific deadlines require qualified review.", "Nested schemas, data-element mappings, classifier edition pins and adversarial instance conformance fixtures remain incomplete.", "Transit discharge, export exit, warehousing, reliefs, refunds, low-value, postal and traveller procedures require separate profiles; no operational controls are provided." ], "conflicts": [], "regional_assumptions": [ "International instruments are frameworks subject to implementation and applicability; they are not a universal executable clearance procedure.", "EU guidance illustrates selected concepts only and does not establish rules for every jurisdiction or prove current consolidated EU law." ], "adversarial_checks": [ "Reject a tariff code as line identity and an official registration number as mandatory for every draft or declaration form.", "Reject receipt as acceptance, release as final assessment, and release as proof of exit or procedure discharge.", "Reject proposed amendments as effective authority decisions and guarantee references as payment.", "Reject automatic preference from dispatch country or unverified origin documents.", "Reject disclosure or operational permission inferred from a missing restriction or document field.", "Reject an overview data-model alignment as executable conformance or an independent-provider review." ] }, "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": "entity", "status": "accepted", "rationale": "The declaration persists across messages and revisions. Clearance acts are scoped evidence and external references, not a second root or an owned border-management process. Entity is an appropriate semantic kind; standalone-mm is a registry-plane label." }, "decisions": [ { "concept": "Persistent declaration boundary", "disposition": "accepted", "rationale": "The declaration persists across messages and revisions. Clearance acts are scoped evidence and external references, not a second root or an owned border-management process. Entity is an appropriate semantic kind; standalone-mm is a registry-plane label." }, { "concept": "Parent and neighboring masters", "disposition": "qualified", "rationale": "The registry parent remains an alignment. No relation-ledger row mandates inheritance or containment. Goods, parties, authority acts and review cases retain their own masters, and no function operates those external lifecycles." }, { "concept": "Official and provisional identity", "disposition": "accepted", "rationale": "Draft and non-electronic forms can use provisional local identity. Issuer-qualified official identity takes priority when available. This avoids the supplement assumption that every instance has an official movement reference." }, { "concept": "Commodity code versus line identity", "disposition": "corrected from untrusted lead", "rationale": "Local lines retain stable identities and sequence mappings. Classification codes identify commodity classes and cannot distinguish two declaration lines in the same class." }, { "concept": "Origin and valuation assertions", "disposition": "accepted with qualification", "rationale": "Origin differs from dispatch location. Preference claims, accepted treatment, declared value and assessed value remain attributed, potentially conflicting assertions. No binding rule evaluation or tariff computation is implemented." }, { "concept": "Lifecycle and monetary finality", "disposition": "separated", "rationale": "Technical receipt, acceptance, release, physical exit, discharge and final monetary determination are separate evidence states. Mixed line states and remaining obligations prevent a blanket clearance flag from silently implying completion." }, { "concept": "Amendment and concurrency", "disposition": "accepted", "rationale": "A proposed local revision is not an effective official amendment. Source identity, expected revision, original messages and authority disposition prevent a late-arriving message from silently overriding a legally controlling assertion." }, { "concept": "Policy controls and restriction handling", "disposition": "accepted within limited scope", "rationale": "The draft records policy basis, permit scope, unresolved restrictions and attributed control outcomes. It contains no operational control tactics or directions for controlled-item movement. Missing evidence never grants permission." }, { "concept": "Local function authority", "disposition": "accepted as unimplemented proposals", "rationale": "All six functions operate on local context, evidence or proposed views with authority and revision preconditions plus refusal outputs. None files a declaration, transfers money, issues a guarantee or releases goods." }, { "concept": "Confidentiality and retention", "disposition": "qualified", "rationale": "The service rules require an adopting legal profile, scoped disclosure, lawful holds and minimised disposal. Treaty exchange confidentiality is not generalised into a universal privacy regime, and historical continuity does not require perpetual personal-data storage." }, { "concept": "Source currency and implementation", "disposition": "held", "rationale": "Selected official browser text supports conceptual distinctions, but direct HTTP has not been run. The EUCDM page has inconsistent version labels, and current consolidated legal texts and transitions are not established. These limits prohibit operational or current-law certification." }, { "concept": "Question and data-schema completeness", "disposition": "accepted as research only", "rationale": "All 48 questions elicit distinct declaration context. Optional candidate object groups are insufficient for executable instance validation, and mappings and national profiles remain unimplemented. This is an explicit conformance hold rather than a critical contradiction in the research draft." }, { "concept": "Provider assurance", "disposition": "waived and held", "rationale": "Only Codex supplied evidence. This frozen local no-tools self-audit is a separate phase, not an independent provider result. No agreement with skipped providers or canonical completeness may be claimed." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorised single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not independent review.", "Source and version verification is incomplete. Eight official pages were readable through browser retrieval, but direct HTTP checks were not attempted because of the sandbox restriction; zero HTTP 200 responses were measured. The coordinator must run check_sources.py. EUCDM page labels 7.0.11 and 7.0.1 conflict; current consolidated legal texts, transitions and exact schema releases remain unverified.", "Treaty implementation, jurisdiction, procedure, legal authority, exceptions, restrictions, deadlines, financial effects, remedies, licensing and records/privacy obligations require qualified profile review before operational use. No filing, legal-compliance or clearance certification is provided.", "Nested instance schemas, pinned external masters, national message/code-list profiles, exact WCO/EUCDM mappings and adversarial conformance fixtures remain incomplete. All six local functions are proposed and unimplemented.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify current legal instruments, amendments and transitional application for each adopting customs territory; resolve the EUCDM version conflict against released schemas and legal data requirements.", "Create profile-specific nested schemas and conformance fixtures covering provisional IDs, multiple lines with one tariff code, partial or conditional release, late responses, denied amendments and lawful disposal.", "Restore independent external review before any canonical or publishable-draft promotion; investigate procedure-specific export, transit, low-value and other exceptions separately." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }