# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T15:47:28Z", "synthesisSha256": "707d3f7fc557d090f1581cdb2660fcc79dd1bd2d41a70b50ba78d4abfab86667", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ECO-025", "registryId": "vr.wm-eco-025", "name": "Return / Refund", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ECO.RET" ], "tags": [ "return", "refund", "soc.eco.ret" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-eco-025-return-refund/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-eco-025", "model": { "registry_id": "vr.wm-eco-025", "model_id": "WM-ECO-025", "name": "Return / Refund", "entry_kind": "aggregate", "purpose": "Represent a governed return and refund case so agents can distinguish request, eligibility, authorization, reverse movement, inspection, disposition, financial obligation and refund execution without confusing the case with order, fulfilment, shipment, invoice, payment, warranty, recall or dispute masters.", "scope_statement": "Owns case identity, versions, profiles and state; trigger, reason and evidence; order, fulfilment, entitlement and payment bindings; claimant, merchant, seller, provider, payer, refund recipient, carrier and authority roles; rule version, jurisdiction, window, conditions, exclusions and eligibility assertions; requested remedies, alternatives, authorization and instructions; subject, quantity, lot, serial, component, condition and digital-access observations; reverse movement, custody, handover and receipt evidence; inspection, acceptance and disposition assertions; refund basis, taxes, fees, discounts, deductions, allocation, currency and rounding inputs; credit, refund obligation, instruction, execution, settlement and notification references; failures, duplicates, fraud signals, chargeback, appeals, disputes, reconciliation and closure assertions; distinct clocks, provenance, privacy, retention, validation and loss-aware projections. External commerce, logistics, inventory, financial, legal and records masters remain authoritative.", "in_scope": [ "Case identity, trigger, source-transaction and party bindings, eligibility, remedy request, decision, authorization, subject, quantity, condition, reverse movement, receipt and inspection evidence", "Disposition, financial calculation, refund obligation and execution references, exceptions, reconciliation, closure, clocks, provenance, access, retention and projections" ], "out_of_scope": [ "Owning Order, Contract, Fulfilment, Party, Product, Service, Inventory, Shipment, Package, Location, Entitlement, Invoice, Credit Note, Payment, Account, Warranty, Recall, Dispute, Adjudication, Waste or Records masters", "Treating item return, authorization, receipt, inspection, credit adjustment, payment instruction, execution, settlement or closure as universal proof of refund entitlement, customer receipt or legal finality", "Autonomous legal eligibility, return authorization, custody transfer, condition judgment, disposition, credit issuance, payment execution, disclosure or record destruction" ], "boundary_notes": [ { "neighbor": "WM-ECO-024 Fulfilment / Delivery", "distinction": "The unified registry supplies only a provisional parent signal. Fulfilment owns forward obligation-performance evidence; this model owns the requested or required reverse case and remedy evidence without a settled containment edge.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] }, { "neighbor": "Order, item, shipment, inventory, entitlement, invoice and payment", "distinction": "These systems own commercial commitments, object identity, movement execution, stock, access, accounting documents and funds. This model stores typed references and subject-specific assertions.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-010" ] }, { "neighbor": "Warranty, product recall, chargeback, complaint, dispute and adjudication", "distinction": "These lifecycles can trigger or challenge a remedy but remain external; return/refund evidence does not decide their authority or final state.", "source_refs": [ "SRC-006", "SRC-012", "SRC-013", "SRC-015" ] }, { "neighbor": "UBL, UN/EDIFACT, ISO 20022, EU law, IFRS, EPCIS, CBV, Schema.org, RFC, PROV, DQV, ODRL and OpenAPI", "distinction": "Each representation has a distinct scope; every mapping is version-pinned, profile-qualified and loss-declaring.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Universal Business Language Version 2.3", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/UBL-2.3.html", "version_or_date": "OASIS Standard 15 June 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines Order Cancellation and Credit Note business documents, parties, lines, quantities, allowances, charges, taxes and references." }, { "id": "SRC-002", "title": "UN/EDIFACT Announcement for returns message", "organization": "United Nations Economic Commission for Europe", "url": "https://service.unece.org/trade/untdid/d00a/trmd/retann_c.htm", "version_or_date": "UN/EDIFACT D.00A RETANN", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines announcements of goods returns, reasons, item identity, quantities, condition, transport, requested disposition, cost responsibility and requested documents." }, { "id": "SRC-003", "title": "UN/EDIFACT Instruction for returns message", "organization": "United Nations Economic Commission for Europe", "url": "https://service.unece.org/trade/untdid/d00a/trmd/retins_c.htm", "version_or_date": "UN/EDIFACT D.00A RETINS", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines acceptance or refusal and instructions for return, repair, destruction or other disposition of goods." }, { "id": "SRC-004", "title": "ISO 20022 Message Definitions: PaymentReturnV15", "organization": "ISO 20022 Registration Authority", "url": "https://www.iso20022.org/iso-20022-message-definitions?search=pacs.004", "version_or_date": "pacs.004.001.15, catalogue updated 19 March 2026", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines the current inter-agent PaymentReturn message while commercial refund entitlement and customer communication remain separate." }, { "id": "SRC-005", "title": "Directive 2011/83/EU on consumer rights", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2011/83/oj", "version_or_date": "Official Journal 22 November 2011", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines scoped withdrawal notice, return duties, reimbursement timing, original payment means, delivery-cost limits and evidence-of-dispatch dependency." }, { "id": "SRC-006", "title": "Directive EU 2019/771 on contracts for the sale of goods", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2019/771/oj", "version_or_date": "Directive 20 May 2019", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines scoped conformity remedies, repair, replacement, price reduction, termination, return and reimbursement of consumer goods." }, { "id": "SRC-007", "title": "Directive EU 2019/770 on digital content and digital services", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2019/770/oj", "version_or_date": "Directive 20 May 2019", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines scoped digital termination, proportionate reimbursement, same payment means, content retrieval and access disabling duties." }, { "id": "SRC-008", "title": "IFRS 15 Revenue from Contracts with Customers", "organization": "IFRS Foundation", "url": "https://www.ifrs.org/content/dam/ifrs/publications/pdf-standards/english/2023/issued/part-a/ifrs-15-revenue-from-contracts-with-customers.pdf?bypass=on", "version_or_date": "2023 issued standard, paragraphs B20 to B27", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines accounting for sales with a right of return, refund liabilities and recovery assets without determining individual legal eligibility." }, { "id": "SRC-009", "title": "EPCIS Standard 2.0.1", "organization": "GS1", "url": "https://ref.gs1.org/standards/epcis/2.0.1/", "version_or_date": "Release 2.0.1, ratified 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines interoperable event capture and query for object, quantity, aggregation, transaction and association observations with event and record times." }, { "id": "SRC-010", "title": "Core Business Vocabulary 2.0", "organization": "GS1", "url": "https://ref.gs1.org/standards/cbv/2.0.0/", "version_or_date": "Release 2.0, ratified 22 June 2022", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines return-related business steps and dispositions including returned, recalled, non-conformant, disposed and destroyed." }, { "id": "SRC-011", "title": "MerchantReturnPolicy", "organization": "Schema.org Community Group", "url": "https://schema.org/MerchantReturnPolicy", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines public discovery fields for applicable country, window, method, label, fees, conditions, seasonal override and refund type." }, { "id": "SRC-012", "title": "International Sale of Goods CISG and related transactions", "organization": "United Nations Commission on International Trade Law", "url": "https://uncitral.un.org/en/texts/salegoods", "version_or_date": "CISG adopted 11 April 1980; portal accessed 6 September 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines scoped conformity, examination, notice and buyer or seller remedies for international sales." }, { "id": "SRC-013", "title": "Regulation EU 2023/988 on general product safety", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/reg/2023/988/oj", "version_or_date": "Regulation 10 May 2023; current consolidated context checked 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines scoped product-safety recall notices and effective, cost-free and timely repair, replacement or refund remedies." }, { "id": "SRC-014", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339 July 2002, updated by RFC 9557", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines interoperable timestamps with seconds and an explicit UTC relationship." }, { "id": "SRC-015", "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-06T15:42:00Z", "relevance": "Defines entities, activities, agents, attribution, generation, derivation and revision provenance." }, { "id": "SRC-016", "title": "Data on the Web Best Practices: 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-06T15:42:00Z", "relevance": "Defines quality dimensions, measurements, annotations, policies and certificates." }, { "id": "SRC-017", "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-06T15:42:00Z", "relevance": "Defines permissions, prohibitions, duties, constraints, assets and parties for policy projections." }, { "id": "SRC-018", "title": "OpenAPI Specification 3.1.1", "organization": "OpenAPI Initiative", "url": "https://spec.openapis.org/oas/v3.1.1.html", "version_or_date": "Version 3.1.1, 24 October 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T15:42:00Z", "relevance": "Defines HTTP API operations, schemas, responses, security and reusable components for service projections." } ], "structure": { "bundles": [ { "id": "case-identity-origin-parties-and-policy", "name": "Case identity, origin, parties and policy", "description": "Groups case identity, origin, parties and policy without duplicating authoritative sibling lifecycles.", "rationale": "Identify one return and refund case, its trigger and accountable roles without remastering commerce identities", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-015", "SRC-003", "SRC-004", "SRC-012", "SRC-013" ], "layers": [ { "id": "case-identity-classification-and-trigger", "name": "Case identity, classification and trigger", "description": "Groups case identity, classification and trigger for the governed return/refund case.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-015" ], "findings": [ { "id": "case-id-version-head-profile-status-and-master-system", "name": "Case ID, version head, profile, status and master system", "description": "Records case id, version head, profile, status and master system as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-015" ], "questions": [ { "id": "case-id-version-head-profile-status-and-master-system-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish case id, version head, profile, status and master system?", "kind": "identity", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "case-id-version-head-profile-status-and-master-system-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of case id, version head, profile, status and master system applies, to what scope, under which rule and authority?", "kind": "spatial", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "case-id-version-head-profile-status-and-master-system-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support case id, version head, profile, status and master system, and what remains unknown or disputed?", "kind": "evidence", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "case-id-version-head-profile-status-and-master-system-data", "name": "Case ID, version head, profile, status and master system data", "description": "Structured fields for case id, version head, profile, status and master system, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-015" ] } ], "artifacts": [ { "id": "case-id-version-head-profile-status-and-master-system-record", "name": "Case ID, version head, profile, status and master system record", "description": "Immutable or versioned evidence record for case id, version head, profile, status and master system with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for case-id-version-head-profile-status-and-master-system; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "request-origin-reason-defect-withdrawal-recall-goodwill-and-evidence", "name": "Request origin, reason, defect, withdrawal, recall, goodwill and evidence", "description": "Records request origin, reason, defect, withdrawal, recall, goodwill and evidence as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-015" ], "questions": [ { "id": "request-origin-reason-defect-withdrawal-recall-goodwill-and-evidence-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish request origin, reason, defect, withdrawal, recall, goodwill and evidence?", "kind": "classification", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "request-origin-reason-defect-withdrawal-recall-goodwill-and-evidence-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of request origin, reason, defect, withdrawal, recall, goodwill and evidence applies, to what scope, under which rule and authority?", "kind": "provenance", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "request-origin-reason-defect-withdrawal-recall-goodwill-and-evidence-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support request origin, reason, defect, withdrawal, recall, goodwill and evidence, and what remains unknown or disputed?", "kind": "quality", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "request-origin-reason-defect-withdrawal-recall-goodwill-and-evidence-data", "name": "Request origin, reason, defect, withdrawal, recall, goodwill and evidence data", "description": "Structured fields for request origin, reason, defect, withdrawal, recall, goodwill and evidence, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-015" ] } ], "artifacts": [ { "id": "request-origin-reason-defect-withdrawal-recall-goodwill-and-evidence-record", "name": "Request origin, reason, defect, withdrawal, recall, goodwill and evidence record", "description": "Immutable or versioned evidence record for request origin, reason, defect, withdrawal, recall, goodwill and evidence with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for request-origin-reason-defect-withdrawal-recall-goodwill-and-evidence; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "source-transaction-parties-roles-and-authority", "name": "Source transaction, parties, roles and authority", "description": "Groups source transaction, parties, roles and authority for the governed return/refund case.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ], "findings": [ { "id": "order-contract-fulfilment-delivery-entitlement-and-payment-reference", "name": "Order, contract, fulfilment, delivery, entitlement and payment reference", "description": "Records order, contract, fulfilment, delivery, entitlement and payment reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ], "questions": [ { "id": "order-contract-fulfilment-delivery-entitlement-and-payment-reference-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish order, contract, fulfilment, delivery, entitlement and payment reference?", "kind": "relationship", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "order-contract-fulfilment-delivery-entitlement-and-payment-reference-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of order, contract, fulfilment, delivery, entitlement and payment reference applies, to what scope, under which rule and authority?", "kind": "ownership", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "order-contract-fulfilment-delivery-entitlement-and-payment-reference-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support order, contract, fulfilment, delivery, entitlement and payment reference, and what remains unknown or disputed?", "kind": "validation", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "order-contract-fulfilment-delivery-entitlement-and-payment-reference-data", "name": "Order, contract, fulfilment, delivery, entitlement and payment reference data", "description": "Structured fields for order, contract, fulfilment, delivery, entitlement and payment reference, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "order-contract-fulfilment-delivery-entitlement-and-payment-reference-record", "name": "Order, contract, fulfilment, delivery, entitlement and payment reference record", "description": "Immutable or versioned evidence record for order, contract, fulfilment, delivery, entitlement and payment reference with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for order-contract-fulfilment-delivery-entitlement-and-payment-reference; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "claimant-purchaser-recipient-merchant-seller-provider-payer-refundrecipient-carrier-and-authority-role", "name": "Claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role", "description": "Records claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ], "questions": [ { "id": "claimant-purchaser-recipient-merchant-seller-provider-payer-refundrecipient-carrier-and-authority-role-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role?", "kind": "ownership", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "claimant-purchaser-recipient-merchant-seller-provider-payer-refundrecipient-carrier-and-authority-role-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role applies, to what scope, under which rule and authority?", "kind": "authority", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "claimant-purchaser-recipient-merchant-seller-provider-payer-refundrecipient-carrier-and-authority-role-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role, and what remains unknown or disputed?", "kind": "security", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "claimant-purchaser-recipient-merchant-seller-provider-payer-refundrecipient-carrier-and-authority-role-data", "name": "Claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role data", "description": "Structured fields for claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "claimant-purchaser-recipient-merchant-seller-provider-payer-refundrecipient-carrier-and-authority-role-record", "name": "Claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role record", "description": "Immutable or versioned evidence record for claimant, purchaser, recipient, merchant, seller, provider, payer, refund recipient, carrier and authority role with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for claimant-purchaser-recipient-merchant-seller-provider-payer-refundrecipient-carrier-and-authority-role; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "eligibility-remedy-and-authorization", "name": "Eligibility, remedy and authorization", "description": "Groups eligibility, remedy and authorization without duplicating authoritative sibling lifecycles.", "rationale": "Preserve policy evaluation and the authorized remedy without treating a request as an entitlement", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "layers": [ { "id": "rule-version-window-conditions-and-exceptions", "name": "Rule version, window, conditions and exceptions", "description": "Groups rule version, window, conditions and exceptions for the governed return/refund case.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "findings": [ { "id": "policy-jurisdiction-contract-channel-member-tier-window-start-deadline-and-rule-version", "name": "Policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version", "description": "Records policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "questions": [ { "id": "policy-jurisdiction-contract-channel-member-tier-window-start-deadline-and-rule-version-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version?", "kind": "constraint", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "policy-jurisdiction-contract-channel-member-tier-window-start-deadline-and-rule-version-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version applies, to what scope, under which rule and authority?", "kind": "requirement", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "policy-jurisdiction-contract-channel-member-tier-window-start-deadline-and-rule-version-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version, and what remains unknown or disputed?", "kind": "privacy", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "policy-jurisdiction-contract-channel-member-tier-window-start-deadline-and-rule-version-data", "name": "Policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version data", "description": "Structured fields for policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "artifacts": [ { "id": "policy-jurisdiction-contract-channel-member-tier-window-start-deadline-and-rule-version-record", "name": "Policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version record", "description": "Immutable or versioned evidence record for policy, jurisdiction, contract, channel, member tier, window start, deadline and rule version with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for policy-jurisdiction-contract-channel-member-tier-window-start-deadline-and-rule-version; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "goods-service-digital-access-condition-use-exclusion-proof-and-eligibility-assertion", "name": "Goods, service, digital access, condition, use, exclusion, proof and eligibility assertion", "description": "Records goods, service, digital access, condition, use, exclusion, proof and eligibility assertion as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ], "questions": [ { "id": "goods-service-digital-access-condition-use-exclusion-proof-and-eligibility-assertion-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish goods, service, digital access, condition, use, exclusion, proof and eligibility assertion?", "kind": "validation", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "goods-service-digital-access-condition-use-exclusion-proof-and-eligibility-assertion-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of goods, service, digital access, condition, use, exclusion, proof and eligibility assertion applies, to what scope, under which rule and authority?", "kind": "constraint", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "goods-service-digital-access-condition-use-exclusion-proof-and-eligibility-assertion-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support goods, service, digital access, condition, use, exclusion, proof and eligibility assertion, and what remains unknown or disputed?", "kind": "retention", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "goods-service-digital-access-condition-use-exclusion-proof-and-eligibility-assertion-data", "name": "Goods, service, digital access, condition, use, exclusion, proof and eligibility assertion data", "description": "Structured fields for goods, service, digital access, condition, use, exclusion, proof and eligibility assertion, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "artifacts": [ { "id": "goods-service-digital-access-condition-use-exclusion-proof-and-eligibility-assertion-record", "name": "Goods, service, digital access, condition, use, exclusion, proof and eligibility assertion record", "description": "Immutable or versioned evidence record for goods, service, digital access, condition, use, exclusion, proof and eligibility assertion with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for goods-service-digital-access-condition-use-exclusion-proof-and-eligibility-assertion; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "requested-remedy-decision-authorization-and-instructions", "name": "Requested remedy, decision, authorization and instructions", "description": "Groups requested remedy, decision, authorization and instructions for the governed return/refund case.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013" ], "findings": [ { "id": "refund-exchange-repair-replacement-price-reduction-credit-and-no-remedy-request", "name": "Refund, exchange, repair, replacement, price reduction, credit and no-remedy request", "description": "Records refund, exchange, repair, replacement, price reduction, credit and no-remedy request as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013" ], "questions": [ { "id": "refund-exchange-repair-replacement-price-reduction-credit-and-no-remedy-request-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish refund, exchange, repair, replacement, price reduction, credit and no-remedy request?", "kind": "decision", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "refund-exchange-repair-replacement-price-reduction-credit-and-no-remedy-request-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of refund, exchange, repair, replacement, price reduction, credit and no-remedy request applies, to what scope, under which rule and authority?", "kind": "process", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "refund-exchange-repair-replacement-price-reduction-credit-and-no-remedy-request-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support refund, exchange, repair, replacement, price reduction, credit and no-remedy request, and what remains unknown or disputed?", "kind": "access", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "refund-exchange-repair-replacement-price-reduction-credit-and-no-remedy-request-data", "name": "Refund, exchange, repair, replacement, price reduction, credit and no-remedy request data", "description": "Structured fields for refund, exchange, repair, replacement, price reduction, credit and no-remedy request, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "refund-exchange-repair-replacement-price-reduction-credit-and-no-remedy-request-record", "name": "Refund, exchange, repair, replacement, price reduction, credit and no-remedy request record", "description": "Immutable or versioned evidence record for refund, exchange, repair, replacement, price reduction, credit and no-remedy request with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for refund-exchange-repair-replacement-price-reduction-credit-and-no-remedy-request; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "authorization-rma-decision-reason-scope-instructions-label-deadline-and-expiry", "name": "Authorization, RMA, decision, reason, scope, instructions, label, deadline and expiry", "description": "Records authorization, rma, decision, reason, scope, instructions, label, deadline and expiry as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013" ], "questions": [ { "id": "authorization-rma-decision-reason-scope-instructions-label-deadline-and-expiry-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish authorization, rma, decision, reason, scope, instructions, label, deadline and expiry?", "kind": "authority", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "authorization-rma-decision-reason-scope-instructions-label-deadline-and-expiry-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of authorization, rma, decision, reason, scope, instructions, label, deadline and expiry applies, to what scope, under which rule and authority?", "kind": "event", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "authorization-rma-decision-reason-scope-instructions-label-deadline-and-expiry-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support authorization, rma, decision, reason, scope, instructions, label, deadline and expiry, and what remains unknown or disputed?", "kind": "exception", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "authorization-rma-decision-reason-scope-instructions-label-deadline-and-expiry-data", "name": "Authorization, RMA, decision, reason, scope, instructions, label, deadline and expiry data", "description": "Structured fields for authorization, rma, decision, reason, scope, instructions, label, deadline and expiry, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "authorization-rma-decision-reason-scope-instructions-label-deadline-and-expiry-record", "name": "Authorization, RMA, decision, reason, scope, instructions, label, deadline and expiry record", "description": "Immutable or versioned evidence record for authorization, rma, decision, reason, scope, instructions, label, deadline and expiry with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for authorization-rma-decision-reason-scope-instructions-label-deadline-and-expiry; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "returned-subject-reverse-movement-and-receipt", "name": "Returned subject, reverse movement and receipt", "description": "Groups returned subject, reverse movement and receipt without duplicating authoritative sibling lifecycles.", "rationale": "Represent what is reversed and the custody evidence while item, shipment and inventory masters stay external", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-005", "SRC-011" ], "layers": [ { "id": "subject-identity-quantity-condition-and-digital-state", "name": "Subject identity, quantity, condition and digital state", "description": "Groups subject identity, quantity, condition and digital state for the governed return/refund case.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013" ], "findings": [ { "id": "product-service-content-entitlement-unit-lot-serial-version-and-component-reference", "name": "Product, service, content, entitlement, unit, lot, serial, version and component reference", "description": "Records product, service, content, entitlement, unit, lot, serial, version and component reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013" ], "questions": [ { "id": "product-service-content-entitlement-unit-lot-serial-version-and-component-reference-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish product, service, content, entitlement, unit, lot, serial, version and component reference?", "kind": "relationship", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "product-service-content-entitlement-unit-lot-serial-version-and-component-reference-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of product, service, content, entitlement, unit, lot, serial, version and component reference applies, to what scope, under which rule and authority?", "kind": "measurement", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "product-service-content-entitlement-unit-lot-serial-version-and-component-reference-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support product, service, content, entitlement, unit, lot, serial, version and component reference, and what remains unknown or disputed?", "kind": "interoperability", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "product-service-content-entitlement-unit-lot-serial-version-and-component-reference-data", "name": "Product, service, content, entitlement, unit, lot, serial, version and component reference data", "description": "Structured fields for product, service, content, entitlement, unit, lot, serial, version and component reference, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013" ] } ], "artifacts": [ { "id": "product-service-content-entitlement-unit-lot-serial-version-and-component-reference-record", "name": "Product, service, content, entitlement, unit, lot, serial, version and component reference record", "description": "Immutable or versioned evidence record for product, service, content, entitlement, unit, lot, serial, version and component reference with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for product-service-content-entitlement-unit-lot-serial-version-and-component-reference; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "requested-authorized-handedover-received-inspected-accepted-and-dispositioned-quantity-condition", "name": "Requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition", "description": "Records requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013" ], "questions": [ { "id": "requested-authorized-handedover-received-inspected-accepted-and-dispositioned-quantity-condition-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition?", "kind": "measurement", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "requested-authorized-handedover-received-inspected-accepted-and-dispositioned-quantity-condition-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition applies, to what scope, under which rule and authority?", "kind": "evidence", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "requested-authorized-handedover-received-inspected-accepted-and-dispositioned-quantity-condition-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition, and what remains unknown or disputed?", "kind": "decision", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "requested-authorized-handedover-received-inspected-accepted-and-dispositioned-quantity-condition-data", "name": "Requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition data", "description": "Structured fields for requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013" ] } ], "artifacts": [ { "id": "requested-authorized-handedover-received-inspected-accepted-and-dispositioned-quantity-condition-record", "name": "Requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition record", "description": "Immutable or versioned evidence record for requested, authorized, handed over, received, inspected, accepted and dispositioned quantity and condition with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for requested-authorized-handedover-received-inspected-accepted-and-dispositioned-quantity-condition; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "reverse-logistics-custody-handover-and-receipt", "name": "Reverse logistics, custody, handover and receipt", "description": "Groups reverse logistics, custody, handover and receipt for the governed return/refund case.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-013" ], "findings": [ { "id": "return-method-label-package-shipment-route-location-cost-responsibility-and-deadline-reference", "name": "Return method, label, package, shipment, route, location, cost responsibility and deadline reference", "description": "Records return method, label, package, shipment, route, location, cost responsibility and deadline reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-013" ], "questions": [ { "id": "return-method-label-package-shipment-route-location-cost-responsibility-and-deadline-reference-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish return method, label, package, shipment, route, location, cost responsibility and deadline reference?", "kind": "process", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "return-method-label-package-shipment-route-location-cost-responsibility-and-deadline-reference-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of return method, label, package, shipment, route, location, cost responsibility and deadline reference applies, to what scope, under which rule and authority?", "kind": "quality", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "return-method-label-package-shipment-route-location-cost-responsibility-and-deadline-reference-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support return method, label, package, shipment, route, location, cost responsibility and deadline reference, and what remains unknown or disputed?", "kind": "identity", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "return-method-label-package-shipment-route-location-cost-responsibility-and-deadline-reference-data", "name": "Return method, label, package, shipment, route, location, cost responsibility and deadline reference data", "description": "Structured fields for return method, label, package, shipment, route, location, cost responsibility and deadline reference, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "return-method-label-package-shipment-route-location-cost-responsibility-and-deadline-reference-record", "name": "Return method, label, package, shipment, route, location, cost responsibility and deadline reference record", "description": "Immutable or versioned evidence record for return method, label, package, shipment, route, location, cost responsibility and deadline reference with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for return-method-label-package-shipment-route-location-cost-responsibility-and-deadline-reference; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "handover-carrier-custody-attempt-loss-delay-delivery-receipt-and-proof", "name": "Handover, carrier custody, attempt, loss, delay, delivery, receipt and proof", "description": "Records handover, carrier custody, attempt, loss, delay, delivery, receipt and proof as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-013" ], "questions": [ { "id": "handover-carrier-custody-attempt-loss-delay-delivery-receipt-and-proof-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish handover, carrier custody, attempt, loss, delay, delivery, receipt and proof?", "kind": "event", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "handover-carrier-custody-attempt-loss-delay-delivery-receipt-and-proof-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of handover, carrier custody, attempt, loss, delay, delivery, receipt and proof applies, to what scope, under which rule and authority?", "kind": "validation", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "handover-carrier-custody-attempt-loss-delay-delivery-receipt-and-proof-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support handover, carrier custody, attempt, loss, delay, delivery, receipt and proof, and what remains unknown or disputed?", "kind": "classification", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "handover-carrier-custody-attempt-loss-delay-delivery-receipt-and-proof-data", "name": "Handover, carrier custody, attempt, loss, delay, delivery, receipt and proof data", "description": "Structured fields for handover, carrier custody, attempt, loss, delay, delivery, receipt and proof, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "handover-carrier-custody-attempt-loss-delay-delivery-receipt-and-proof-record", "name": "Handover, carrier custody, attempt, loss, delay, delivery, receipt and proof record", "description": "Immutable or versioned evidence record for handover, carrier custody, attempt, loss, delay, delivery, receipt and proof with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for handover-carrier-custody-attempt-loss-delay-delivery-receipt-and-proof; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "inspection-disposition-and-refund-calculation", "name": "Inspection, disposition and refund calculation", "description": "Groups inspection, disposition and refund calculation without duplicating authoritative sibling lifecycles.", "rationale": "Separate physical or digital outcome from financial calculation and external ledger execution", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-016", "SRC-001", "SRC-004", "SRC-005", "SRC-008", "SRC-011" ], "layers": [ { "id": "receipt-inspection-conformity-and-disposition", "name": "Receipt, inspection, conformity and disposition", "description": "Groups receipt, inspection, conformity and disposition for the governed return/refund case.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-016" ], "findings": [ { "id": "inspection-method-actor-condition-defect-damage-completeness-authenticity-and-evidence", "name": "Inspection method, actor, condition, defect, damage, completeness, authenticity and evidence", "description": "Records inspection method, actor, condition, defect, damage, completeness, authenticity and evidence as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-016" ], "questions": [ { "id": "inspection-method-actor-condition-defect-damage-completeness-authenticity-and-evidence-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish inspection method, actor, condition, defect, damage, completeness, authenticity and evidence?", "kind": "evidence", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "inspection-method-actor-condition-defect-damage-completeness-authenticity-and-evidence-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of inspection method, actor, condition, defect, damage, completeness, authenticity and evidence applies, to what scope, under which rule and authority?", "kind": "security", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "inspection-method-actor-condition-defect-damage-completeness-authenticity-and-evidence-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support inspection method, actor, condition, defect, damage, completeness, authenticity and evidence, and what remains unknown or disputed?", "kind": "composition", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "inspection-method-actor-condition-defect-damage-completeness-authenticity-and-evidence-data", "name": "Inspection method, actor, condition, defect, damage, completeness, authenticity and evidence data", "description": "Structured fields for inspection method, actor, condition, defect, damage, completeness, authenticity and evidence, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-016" ] } ], "artifacts": [ { "id": "inspection-method-actor-condition-defect-damage-completeness-authenticity-and-evidence-record", "name": "Inspection method, actor, condition, defect, damage, completeness, authenticity and evidence record", "description": "Immutable or versioned evidence record for inspection method, actor, condition, defect, damage, completeness, authenticity and evidence with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for inspection-method-actor-condition-defect-damage-completeness-authenticity-and-evidence; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "accept-reject-restock-refurbish-repair-quarantine-returntosupplier-recycle-destroy-and-access-revoke-reference", "name": "Accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference", "description": "Records accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-016" ], "questions": [ { "id": "accept-reject-restock-refurbish-repair-quarantine-returntosupplier-recycle-destroy-and-access-revoke-reference-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference?", "kind": "lifecycle", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "accept-reject-restock-refurbish-repair-quarantine-returntosupplier-recycle-destroy-and-access-revoke-reference-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference applies, to what scope, under which rule and authority?", "kind": "privacy", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "accept-reject-restock-refurbish-repair-quarantine-returntosupplier-recycle-destroy-and-access-revoke-reference-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference, and what remains unknown or disputed?", "kind": "relationship", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "accept-reject-restock-refurbish-repair-quarantine-returntosupplier-recycle-destroy-and-access-revoke-reference-data", "name": "Accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference data", "description": "Structured fields for accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-016" ] } ], "artifacts": [ { "id": "accept-reject-restock-refurbish-repair-quarantine-returntosupplier-recycle-destroy-and-access-revoke-reference-record", "name": "Accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference record", "description": "Immutable or versioned evidence record for accept, reject, restock, refurbish, repair, quarantine, return-to-supplier, recycle, destroy and access-revoke reference with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for accept-reject-restock-refurbish-repair-quarantine-returntosupplier-recycle-destroy-and-access-revoke-reference; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "refund-basis-allocation-deductions-and-rounding", "name": "Refund basis, allocation, deductions and rounding", "description": "Groups refund basis, allocation, deductions and rounding for the governed return/refund case.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-013" ], "findings": [ { "id": "paid-price-tax-fee-delivery-discount-promotion-deposit-credit-restocking-and-deduction-input", "name": "Paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input", "description": "Records paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-013" ], "questions": [ { "id": "paid-price-tax-fee-delivery-discount-promotion-deposit-credit-restocking-and-deduction-input-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input?", "kind": "measurement", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "paid-price-tax-fee-delivery-discount-promotion-deposit-credit-restocking-and-deduction-input-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input applies, to what scope, under which rule and authority?", "kind": "retention", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "paid-price-tax-fee-delivery-discount-promotion-deposit-credit-restocking-and-deduction-input-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input, and what remains unknown or disputed?", "kind": "state", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "paid-price-tax-fee-delivery-discount-promotion-deposit-credit-restocking-and-deduction-input-data", "name": "Paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input data", "description": "Structured fields for paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "paid-price-tax-fee-delivery-discount-promotion-deposit-credit-restocking-and-deduction-input-record", "name": "Paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input record", "description": "Immutable or versioned evidence record for paid price, tax, fee, delivery, discount, promotion, deposit, credit, restocking and deduction input with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for paid-price-tax-fee-delivery-discount-promotion-deposit-credit-restocking-and-deduction-input; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "partial-multiple-combined-splittender-currency-rounding-allocation-and-refund-obligation", "name": "Partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation", "description": "Records partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-013" ], "questions": [ { "id": "partial-multiple-combined-splittender-currency-rounding-allocation-and-refund-obligation-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation?", "kind": "other", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "partial-multiple-combined-splittender-currency-rounding-allocation-and-refund-obligation-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation applies, to what scope, under which rule and authority?", "kind": "access", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "partial-multiple-combined-splittender-currency-rounding-allocation-and-refund-obligation-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation, and what remains unknown or disputed?", "kind": "lifecycle", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "partial-multiple-combined-splittender-currency-rounding-allocation-and-refund-obligation-data", "name": "Partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation data", "description": "Structured fields for partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "partial-multiple-combined-splittender-currency-rounding-allocation-and-refund-obligation-record", "name": "Partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation record", "description": "Immutable or versioned evidence record for partial, multiple, combined, split-tender, currency, rounding, allocation and refund obligation with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for partial-multiple-combined-splittender-currency-rounding-allocation-and-refund-obligation; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "refund-execution-exceptions-reconciliation-and-closure", "name": "Refund execution, exceptions, reconciliation and closure", "description": "Groups refund execution, exceptions, reconciliation and closure without duplicating authoritative sibling lifecycles.", "rationale": "Track authorized financial remedy evidence without owning invoice, payment, account or dispute masters", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-015", "SRC-012", "SRC-013", "SRC-016" ], "layers": [ { "id": "adjustment-instruction-execution-settlement-and-notification", "name": "Adjustment, instruction, execution, settlement and notification", "description": "Groups adjustment, instruction, execution, settlement and notification for the governed return/refund case.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-015" ], "findings": [ { "id": "creditnote-refundliability-storecredit-exchange-replacement-and-accounting-adjustment-reference", "name": "Credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference", "description": "Records credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-015" ], "questions": [ { "id": "creditnote-refundliability-storecredit-exchange-replacement-and-accounting-adjustment-reference-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference?", "kind": "relationship", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "creditnote-refundliability-storecredit-exchange-replacement-and-accounting-adjustment-reference-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference applies, to what scope, under which rule and authority?", "kind": "exception", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "creditnote-refundliability-storecredit-exchange-replacement-and-accounting-adjustment-reference-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference, and what remains unknown or disputed?", "kind": "temporal", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "creditnote-refundliability-storecredit-exchange-replacement-and-accounting-adjustment-reference-data", "name": "Credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference data", "description": "Structured fields for credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-015" ] } ], "artifacts": [ { "id": "creditnote-refundliability-storecredit-exchange-replacement-and-accounting-adjustment-reference-record", "name": "Credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference record", "description": "Immutable or versioned evidence record for credit note, refund liability, store credit, exchange, replacement and accounting adjustment reference with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for creditnote-refundliability-storecredit-exchange-replacement-and-accounting-adjustment-reference; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "refund-instruction-paymentreturn-reversal-route-status-settlement-customerreceipt-and-notification", "name": "Refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification", "description": "Records refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-015" ], "questions": [ { "id": "refund-instruction-paymentreturn-reversal-route-status-settlement-customerreceipt-and-notification-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification?", "kind": "state", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "refund-instruction-paymentreturn-reversal-route-status-settlement-customerreceipt-and-notification-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification applies, to what scope, under which rule and authority?", "kind": "interoperability", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "refund-instruction-paymentreturn-reversal-route-status-settlement-customerreceipt-and-notification-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification, and what remains unknown or disputed?", "kind": "spatial", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "refund-instruction-paymentreturn-reversal-route-status-settlement-customerreceipt-and-notification-data", "name": "Refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification data", "description": "Structured fields for refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-015" ] } ], "artifacts": [ { "id": "refund-instruction-paymentreturn-reversal-route-status-settlement-customerreceipt-and-notification-record", "name": "Refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification record", "description": "Immutable or versioned evidence record for refund instruction, payment return, reversal, route, status, settlement, customer receipt and notification with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for refund-instruction-paymentreturn-reversal-route-status-settlement-customerreceipt-and-notification; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "failure-fraud-dispute-reconciliation-and-closure", "name": "Failure, fraud, dispute, reconciliation and closure", "description": "Groups failure, fraud, dispute, reconciliation and closure for the governed return/refund case.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013", "SRC-015", "SRC-016" ], "findings": [ { "id": "failed-delayed-duplicate-overrefund-underrefund-fraudsignal-chargeback-retry-and-escalation", "name": "Failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation", "description": "Records failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013", "SRC-015", "SRC-016" ], "questions": [ { "id": "failed-delayed-duplicate-overrefund-underrefund-fraudsignal-chargeback-retry-and-escalation-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation?", "kind": "exception", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "failed-delayed-duplicate-overrefund-underrefund-fraudsignal-chargeback-retry-and-escalation-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation applies, to what scope, under which rule and authority?", "kind": "decision", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "failed-delayed-duplicate-overrefund-underrefund-fraudsignal-chargeback-retry-and-escalation-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation, and what remains unknown or disputed?", "kind": "provenance", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "failed-delayed-duplicate-overrefund-underrefund-fraudsignal-chargeback-retry-and-escalation-data", "name": "Failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation data", "description": "Structured fields for failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "failed-delayed-duplicate-overrefund-underrefund-fraudsignal-chargeback-retry-and-escalation-record", "name": "Failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation record", "description": "Immutable or versioned evidence record for failed, delayed, duplicate, over-refund, under-refund, fraud signal, chargeback, retry and escalation with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for failed-delayed-duplicate-overrefund-underrefund-fraudsignal-chargeback-retry-and-escalation; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "item-quantity-disposition-adjustment-payment-balance-appeal-dispute-and-closure-reconciliation", "name": "Item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation", "description": "Records item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013", "SRC-015", "SRC-016" ], "questions": [ { "id": "item-quantity-disposition-adjustment-payment-balance-appeal-dispute-and-closure-reconciliation-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation?", "kind": "validation", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "item-quantity-disposition-adjustment-payment-balance-appeal-dispute-and-closure-reconciliation-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation applies, to what scope, under which rule and authority?", "kind": "identity", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "item-quantity-disposition-adjustment-payment-balance-appeal-dispute-and-closure-reconciliation-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation, and what remains unknown or disputed?", "kind": "ownership", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "item-quantity-disposition-adjustment-payment-balance-appeal-dispute-and-closure-reconciliation-data", "name": "Item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation data", "description": "Structured fields for item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "item-quantity-disposition-adjustment-payment-balance-appeal-dispute-and-closure-reconciliation-record", "name": "Item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation record", "description": "Immutable or versioned evidence record for item, quantity, disposition, adjustment, payment, balance, appeal, dispute and closure reconciliation with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for item-quantity-disposition-adjustment-payment-balance-appeal-dispute-and-closure-reconciliation; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-013", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-provenance-time-access-and-interoperability", "name": "Governance, provenance, time, access and interoperability", "description": "Groups governance, provenance, time, access and interoperability without duplicating authoritative sibling lifecycles.", "rationale": "Qualify authority, clocks, evidence, privacy, retention and loss-aware projections", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-018" ], "layers": [ { "id": "source-provenance-access-privacy-retention-and-correction", "name": "Source, provenance, access, privacy, retention and correction", "description": "Groups source, provenance, access, privacy, retention and correction for the governed return/refund case.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-013", "SRC-015", "SRC-016", "SRC-017" ], "findings": [ { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit", "name": "Owner, steward, source system, actor, activity, derivation, revision, conflict and audit", "description": "Records owner, steward, source system, actor, activity, derivation, revision, conflict and audit as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-013", "SRC-015", "SRC-016", "SRC-017" ], "questions": [ { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish owner, steward, source system, actor, activity, derivation, revision, conflict and audit?", "kind": "provenance", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of owner, steward, source system, actor, activity, derivation, revision, conflict and audit applies, to what scope, under which rule and authority?", "kind": "classification", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support owner, steward, source system, actor, activity, derivation, revision, conflict and audit, and what remains unknown or disputed?", "kind": "authority", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-data", "name": "Owner, steward, source system, actor, activity, derivation, revision, conflict and audit data", "description": "Structured fields for owner, steward, source system, actor, activity, derivation, revision, conflict and audit, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-013", "SRC-015", "SRC-016", "SRC-017" ] } ], "artifacts": [ { "id": "owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit-record", "name": "Owner, steward, source system, actor, activity, derivation, revision, conflict and audit record", "description": "Immutable or versioned evidence record for owner, steward, source system, actor, activity, derivation, revision, conflict and audit with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for owner-steward-source-system-actor-activity-derivation-revision-conflict-and-audit; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-013", "SRC-015", "SRC-016", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "purpose-party-account-address-item-evidence-access-disclosure-retention-legalhold-correction-and-tombstone", "name": "Purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone", "description": "Records purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-013", "SRC-015", "SRC-016", "SRC-017" ], "questions": [ { "id": "purpose-party-account-address-item-evidence-access-disclosure-retention-legalhold-correction-and-tombstone-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone?", "kind": "privacy", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "purpose-party-account-address-item-evidence-access-disclosure-retention-legalhold-correction-and-tombstone-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone applies, to what scope, under which rule and authority?", "kind": "composition", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "purpose-party-account-address-item-evidence-access-disclosure-retention-legalhold-correction-and-tombstone-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone, and what remains unknown or disputed?", "kind": "requirement", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "purpose-party-account-address-item-evidence-access-disclosure-retention-legalhold-correction-and-tombstone-data", "name": "Purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone data", "description": "Structured fields for purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-013", "SRC-015", "SRC-016", "SRC-017" ] } ], "artifacts": [ { "id": "purpose-party-account-address-item-evidence-access-disclosure-retention-legalhold-correction-and-tombstone-record", "name": "Purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone record", "description": "Immutable or versioned evidence record for purpose, party, account, address, item, evidence, access, disclosure, retention, legal hold, correction and tombstone with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for purpose-party-account-address-item-evidence-access-disclosure-retention-legalhold-correction-and-tombstone; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-013", "SRC-015", "SRC-016", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "event-clocks-validation-and-loss-aware-projections", "name": "Event clocks, validation and loss-aware projections", "description": "Groups event clocks, validation and loss-aware projections for the governed return/refund case.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "findings": [ { "id": "purchase-fulfilment-discovery-request-authorization-handover-receipt-inspection-decision-refunddue-executed-settled-observed-and-known-time", "name": "Purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time", "description": "Records purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "purchase-fulfilment-discovery-request-authorization-handover-receipt-inspection-decision-refunddue-executed-settled-observed-and-known-time-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time?", "kind": "temporal", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "purchase-fulfilment-discovery-request-authorization-handover-receipt-inspection-decision-refunddue-executed-settled-observed-and-known-time-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time applies, to what scope, under which rule and authority?", "kind": "relationship", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "purchase-fulfilment-discovery-request-authorization-handover-receipt-inspection-decision-refunddue-executed-settled-observed-and-known-time-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time, and what remains unknown or disputed?", "kind": "constraint", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "purchase-fulfilment-discovery-request-authorization-handover-receipt-inspection-decision-refunddue-executed-settled-observed-and-known-time-data", "name": "Purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time data", "description": "Structured fields for purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "purchase-fulfilment-discovery-request-authorization-handover-receipt-inspection-decision-refunddue-executed-settled-observed-and-known-time-record", "name": "Purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time record", "description": "Immutable or versioned evidence record for purchase, fulfilment, discovery, request, authorization, handover, receipt, inspection, decision, refund due, executed, settled, observed and known time with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for purchase-fulfilment-discovery-request-authorization-handover-receipt-inspection-decision-refunddue-executed-settled-observed-and-known-time; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "identity-eligibility-sequence-quantity-condition-amount-policy-privacy-ubl-edifact-iso20022-eu-ifrs-epcis-schemaorg-prov-and-api-validation", "name": "Identity, eligibility, sequence, quantity, condition, amount, policy, privacy, UBL, EDIFACT, ISO 20022, EU, IFRS, EPCIS, Schema.org, PROV and API validation", "description": "Records identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation as source-qualified return/refund context while order, fulfilment, item, shipment, inventory, invoice, payment, warranty, recall, dispute and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "identity-eligibility-sequence-quantity-condition-amount-policy-privacy-ubl-edifact-iso20022-eu-ifrs-epcis-schemaorg-prov-and-api-validation-q01", "text": "Which stable case, version, source-transaction, subject, party and external-master identifiers plus explicit profile and unknown state establish identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation?", "kind": "interoperability", "answer_data": [ "case and version IDs", "external master references", "profile, assertion status and mastering system" ] }, { "id": "identity-eligibility-sequence-quantity-condition-amount-policy-privacy-ubl-edifact-iso20022-eu-ifrs-epcis-schemaorg-prov-and-api-validation-q02", "text": "Which requested, asserted, observed, authorized, rejected, corrected or superseded state of identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation applies, to what scope, under which rule and authority?", "kind": "state", "answer_data": [ "state axis and scope", "rule, authority and reason", "predecessor and successor assertions" ] }, { "id": "identity-eligibility-sequence-quantity-condition-amount-policy-privacy-ubl-edifact-iso20022-eu-ifrs-epcis-schemaorg-prov-and-api-validation-q03", "text": "What evidence, method, actor, event time, observation time, confidence, access marking and validation rule support identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation, and what remains unknown or disputed?", "kind": "process", "answer_data": [ "evidence and method", "actor and distinct times", "confidence, access, validation and conflict" ] } ], "data_elements": [ { "id": "identity-eligibility-sequence-quantity-condition-amount-policy-privacy-ubl-edifact-iso20022-eu-ifrs-epcis-schemaorg-prov-and-api-validation-data", "name": "Identity, eligibility, sequence, quantity, condition, amount, policy, privacy, UBL, EDIFACT, ISO 20022, EU, IFRS, EPCIS, Schema.org, PROV and API validation data", "description": "Structured fields for identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation, including stable identity, external references, value or state, scope, authority, source, times, confidence, access and conflict status.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "identity-eligibility-sequence-quantity-condition-amount-policy-privacy-ubl-edifact-iso20022-eu-ifrs-epcis-schemaorg-prov-and-api-validation-record", "name": "Identity, eligibility, sequence, quantity, condition, amount, policy, privacy, UBL, EDIFACT, ISO 20022, EU, IFRS, EPCIS, Schema.org, PROV and API validation record", "description": "Immutable or versioned evidence record for identity, eligibility, sequence, quantity, condition, amount, policy, privacy, ubl, edifact, iso 20022, eu, ifrs, epcis, schema.org, prov and api validation with declared profile and projection loss.", "media_or_form": [ "application/yaml", "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Return/refund case ID plus independent version, source, subject, decision, movement, adjustment, payment or event ID and artifact kind for identity-eligibility-sequence-quantity-condition-amount-policy-privacy-ubl-edifact-iso20022-eu-ifrs-epcis-schemaorg-prov-and-api-validation; party, order number, date, amount, filename or digest never identifies the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-return-refund-case", "name": "Register return/refund case", "description": "Governed operation to register return/refund case without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "request or trigger evidence", "source transaction references", "actor and profile" ], "outputs": [ "versioned case assertion" ], "preconditions": [ "unique case identity, purpose, authority and source pass" ], "effects": [ "does not alter order, fulfilment, payment or entitlement masters" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-015" ] }, { "id": "assess-eligibility", "name": "Assess eligibility", "description": "Governed operation to assess eligibility without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "case", "policy and jurisdiction profile", "subject evidence" ], "outputs": [ "reasoned eligibility assertion" ], "preconditions": [ "rule version, window, conditions, exclusions, evidence and authority pass" ], "effects": [ "assessment is not authorization or legal adjudication" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-011", "SRC-012", "SRC-013" ] }, { "id": "propose-remedy", "name": "Propose remedy", "description": "Governed operation to propose remedy without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "eligible case", "requested outcome", "available remedy rules" ], "outputs": [ "ranked remedy proposal with limitations" ], "preconditions": [ "scope, alternatives, cost, safety, proportionality and authority pass" ], "effects": [ "proposal cannot bind parties or execute a remedy" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-013" ] }, { "id": "authorize-return-and-issue-instructions", "name": "Authorize return and issue instructions", "description": "Governed operation to authorize return and issue instructions without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "case", "eligibility decision", "delegated authority" ], "outputs": [ "authorization and instruction record" ], "preconditions": [ "subject, quantity, method, destination, cost, deadline, label and expiry pass" ], "effects": [ "authorization does not prove handover, receipt or refund" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-011" ] }, { "id": "record-handover-and-receipt", "name": "Record handover and receipt", "description": "Governed operation to record handover and receipt without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "authorized case", "reverse-movement and custody evidence" ], "outputs": [ "source-qualified handover and receipt assertions" ], "preconditions": [ "subject, quantity, custodian, location, condition, proof and times pass" ], "effects": [ "receipt does not prove acceptance, disposition or refund entitlement" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-009", "SRC-010" ] }, { "id": "inspect-and-select-disposition", "name": "Inspect and select disposition", "description": "Governed operation to inspect and select disposition without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "received subject", "inspection method and evidence", "authorized decision" ], "outputs": [ "inspection and disposition assertion" ], "preconditions": [ "criteria, actor, condition, safety, authority, reason and time pass" ], "effects": [ "inventory, repair, recycling and destruction execution remain external" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-009", "SRC-010", "SRC-013", "SRC-016" ] }, { "id": "calculate-refund-obligation", "name": "Calculate refund obligation", "description": "Governed operation to calculate refund obligation without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "authorized remedy", "commercial adjustment inputs", "currency and rounding rules" ], "outputs": [ "auditable proposed refund obligation" ], "preconditions": [ "scope, price, tax, fees, discounts, deductions, allocation and rule version pass" ], "effects": [ "calculation does not issue credit or move funds" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011" ] }, { "id": "record-refund-instruction-and-execution", "name": "Record refund instruction and execution", "description": "Governed operation to record refund instruction and execution without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "authorized refund obligation", "external adjustment and payment evidence" ], "outputs": [ "instruction, execution, settlement and notification references" ], "preconditions": [ "amount, currency, route, original payment, authority, status and reconciliation pass" ], "effects": [ "the model never executes a payment or asserts customer receipt without evidence" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-007", "SRC-015" ] }, { "id": "reconcile-exceptions-and-close", "name": "Reconcile exceptions and close", "description": "Governed operation to reconcile exceptions and close without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "case", "movement, inspection, adjustment and payment evidence", "open exceptions" ], "outputs": [ "reconciliation and proposed closure assertion" ], "preconditions": [ "quantities, disposition, amounts, payment state, appeals, disputes and authority pass" ], "effects": [ "closure does not erase evidence or close external disputes" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-012", "SRC-016" ] }, { "id": "correct-project-retain-and-audit", "name": "Correct, project, retain and audit", "description": "Governed operation to correct, project, retain and audit without autonomous legal eligibility, custody, disposition, accounting, payment, disclosure or record destruction.", "inputs": [ "case", "authorized correction or target profile", "purpose-bound access", "retention policy" ], "outputs": [ "linked successor, filtered projection, retention result or audit event" ], "preconditions": [ "authority, scope, mapping, digest, privacy, legal hold and non-cascade checks pass" ], "effects": [ "prior evidence remains traceable and external masters are not mutated" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "composition": [ { "target": "WM-ECO-024", "relation": "REFERENCE", "purpose": "Resolve the provisional fulfilment parent signal without granting containment or cascade mutation authority.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] }, { "target": "Order, Contract, Party, Product, Service, Inventory, Shipment, Package, Location, Entitlement, Invoice, Credit Note, Payment, Account, Warranty, Recall, Dispute, Adjudication, Waste and Records models", "relation": "REFERENCE", "purpose": "Resolve external identities, states, operations and evidence without duplicating their masters.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-015" ] }, { "target": "UBL 2.3; UN/EDIFACT RETANN and RETINS; ISO 20022 PaymentReturnV15; scoped EU consumer, goods, digital and product-safety law; IFRS 15; EPCIS and CBV 2.0; Schema.org; RFC 3339; PROV-O; DQV; ODRL; OpenAPI 3.1.1", "relation": "ALIGN", "purpose": "Project version-pinned commerce, logistics, finance, legal, accounting, traceability, discovery, temporal, provenance, quality, policy and API views with declared loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension owner, namespace authority, accountable return owner and delegated commercial, logistics, inspection, finance, legal, privacy and safety authorities", "Authoritative Order, Contract, Fulfilment, Party, Product, Service, Entitlement, Inventory, Shipment, Location, Invoice, Payment, Warranty, Recall, Dispute and Records registries", "Approved goods, service, digital, consumer, business, sector, jurisdiction, tax, safety, privacy, retention and interoperability profiles", "Role, delegation, eligibility, authorization, custody, inspection, disposition, adjustment, refund, disclosure and agent-operation policies" ], "namespace_guidance": "Mint case, version, request, decision, authorization, subject-line, handover, receipt, inspection, disposition, adjustment, refund and projection IDs; preserve external master identifiers.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative return/refund case identifier, owner namespace and version head, never by order number, RMA label, party, date, amount, filename or digest alone.", "Keep request, eligibility, authorization, reverse movement, receipt, inspection, disposition, refund obligation, credit adjustment, payment return, settlement and dispute independently identifiable." ], "patch_rules": [ "Extensions declare profile, identity, source transaction, parties, subject, quantity, condition, eligibility, remedy, movement, disposition, amount, lifecycle, time, privacy and interoperability effects.", "Issued versions are immutable; partial returns, additional receipts, re-inspections, recalculations, retries, corrections and cancellations create linked successors.", "Never silently change subject, quantity, condition, reason, eligibility rule, authorization, remedy, disposition, amount, currency, deduction, payment route, authority or privacy marking." ], "compatibility_rules": [ "Ignore additive fields only when identity, version, policy, parties, subject, quantities, states, amounts, times, authority, access and provenance survive.", "Every projection pins specification version and declares loss in policy, subject, quantity, condition, state, timing, amount, authority and evidence semantics." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for return/refund case, version, request, authorization, subject line, movement, receipt, inspection, disposition, adjustment, refund or artifact, qualified by namespace and kind.", "Governed globally resolvable case or artifact IRI.", "Dimension UUID or ULID when neither preceding identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; distinguish purchase, fulfilment, discovery, request, authorization, label issue, handover, receipt, inspection, decision, refund due, instruction, execution, settlement, notification, observation, ingestion and knowledge times whenever they differ.", "serial_naming_rule": "Use {case-id}--{version-id}--{request-decision-movement-adjustment-refund-or-event-id}--{artifact-kind}--{revision-id}.", "integrity_rule": "Store digest, media type, record kind, case and version IDs, profile, source transaction, subject, actor, quantity and unit, amount and currency, event and knowledge times, confidentiality and provenance." }, "policies": [ "The model owns return/refund case context but not order, fulfilment, item, shipment, inventory, entitlement, invoice, payment, warranty, recall, dispute or records masters.", "Request, eligibility, authorization, handover, receipt, inspection, disposition, refund obligation, instruction, execution, settlement, customer receipt and closure states and clocks remain distinct.", "Returned, accepted, credited, instructed, executed, settled or closed status never alone proves legal entitlement, customer receipt, ledger finality or dispute closure.", "Agents cannot autonomously determine legal eligibility, authorize a return, transfer custody, judge condition, choose physical disposition, issue credit, instruct or execute payment, disclose or destroy records without delegated authority." ], "crud": { "read": [ "Resolve case head, source transaction, parties, subject, policy, eligibility, authorization, movement, receipt, inspection, disposition, calculation, refund evidence, exceptions, access and projection loss." ], "create": [ "Bind identity, owner, purpose, profile, source transaction, claimant, subject, reason, evidence, rule version, source authority and initial state before assertions are accepted." ], "update": [ "Append successor eligibility, authorization, movement, receipt, inspection, disposition, calculation, refund, exception, reconciliation and correction assertions with reason, authority, event time and knowledge time." ], "delete": [ "Apply legal hold, commercial, consumer, safety, financial, privacy and Dimension retention policy; tombstone only the catalogue view without cascading to external masters, and let authoritative systems execute financial or physical disposition." ] }, "roles": [ { "name": "Return/refund owner", "responsibilities": [ "Own purpose, scope, profile, lifecycle, compatibility and accountable use." ] }, { "name": "Commercial and policy steward", "responsibilities": [ "Own order bindings, policy versions, eligibility inputs, remedy terms, price and adjustment references." ] }, { "name": "Logistics and custody steward", "responsibilities": [ "Own authorization, return instructions, reverse movement, custody and receipt bindings." ] }, { "name": "Inspection and disposition authority", "responsibilities": [ "Own inspection criteria, condition evidence, acceptance and disposition decisions." ] }, { "name": "Finance and payment steward", "responsibilities": [ "Own credit, refund obligation, payment instruction, execution, settlement and reconciliation references." ] }, { "name": "Legal, privacy and safety authority", "responsibilities": [ "Own jurisdiction, disputes, protected commerce data, product safety, access and retention limitations." ] }, { "name": "Interoperability and records steward", "responsibilities": [ "Own mappings, conformance evidence, declared loss, legal hold and disposition policy." ] } ], "access": { "default_rule": "Deny party, address, account, payment, item, serial, condition, fraud, dispute, evidence and security-sensitive data unless purpose-bound policy permits the minimum necessary view.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Declared operational, safety, legal, audit, regulatory, consumer-rights or subject-rights access must cite authority, scope, purpose and time limit and be logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, case and version, operation, authority, policy, RFC 3339 time, affected subject, quantity or amount, source revision and outcome without duplicating restricted data." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension namespace, commerce, return, payment, safety, privacy, retention and agent policies.", "Read this model and linked order, fulfilment, party, product, shipment, inventory, entitlement, invoice, payment, warranty, recall, dispute and records models before mutation." ] } }, "coverage": { "claim": "WM-ECO-025 covers one governed return/refund case from trigger and eligibility through authorization, reverse movement or access effect, receipt, inspection, disposition, refund calculation, execution evidence, exceptions, reconciliation, closure, governance and loss-aware projections. Relation, jurisdiction, sector, payment-scheme, conformance and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "classification and direct properties", "status": "covered", "notes": "Classification and direct properties is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Recognition and observation is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Capabilities and possible actions is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "composition", "status": "covered", "notes": "Composition is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "lifecycle", "status": "covered", "notes": "Lifecycle is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "relationships", "status": "covered", "notes": "Relationships is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "temporal", "status": "covered", "notes": "Temporal is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "spatial", "status": "covered", "notes": "Spatial is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "provenance", "status": "covered", "notes": "Provenance is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "ownership", "status": "covered", "notes": "Ownership is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "validation", "status": "covered", "notes": "Validation is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "access", "status": "covered", "notes": "Access is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention and deletion is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "interoperability", "status": "covered", "notes": "Interoperability is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." }, { "dimension": "authority and ethics", "status": "covered", "notes": "Authority and ethics is explicit; sector, jurisdiction, tax, safety, legal-effect, relation and external-review profiles remain held where applicable." } ], "known_omissions": [ "Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.", "WM-ECO-024 is only a provisional parent signal and the frozen candidate relation ledger contains no settled WM-ECO-025 edge.", "Consumer, business, marketplace, subscription, travel, financial, healthcare, food, hazardous-goods and cross-border returns need separate profiles.", "National contract, tax, accounting, product-safety, privacy, signature, payment-scheme, chargeback and records rules require jurisdiction or scheme review.", "UNECE and IFRS source pages had direct-access limitations, and every UBL, EDIFACT, ISO 20022, EU, IFRS, EPCIS and Schema.org mapping needs release-pinned conformance tests." ], "conflicts": [ "Return request, entitlement, authorization, reverse shipment, receipt, inspection, disposition, refund obligation, credit note, payment return or reversal, chargeback and dispute are related but not interchangeable.", "Item return does not imply refund, refund can occur without item return, credit does not prove payment, and payment return does not determine the commercial obligation.", "Requested, promised, effective, event, observation, ingestion and knowledge times must not be collapsed.", "Merchant policy, contract, statute, safety recall and goodwill may yield competing remedies and must coexist with authority and precedence evidence." ], "regional_assumptions": [ "Eligibility, windows, evidence, cost allocation, deductions, tax treatment, refund means, deadlines and remedies depend on governing law, party type, contract, channel, sector and payment scheme.", "CISG and EU consumer, digital and product-safety rules are scoped profiles, not universal governing law; IFRS is accounting evidence, not legal entitlement." ], "adversarial_checks": [ "Reject a case that collapses into order, fulfilment, shipment, inventory, invoice, payment, warranty, recall, dispute or records masters.", "Reject request as entitlement, authorization as custody, return receipt as acceptance, credit note as refund payment, execution as settlement, or closure as dispute finality.", "Reject quantity, condition or amount without subject identity, unit or currency, method, source, event time, uncertainty and reconciliation state.", "Reject correction, cancellation or reopening that erases prior decisions, custody, inspections, adjustments or payment evidence.", "Reject autonomous legal eligibility, authorization, custody, disposition, accounting, payment, disclosure or destruction without delegated authority.", "Reject a projection that hides policy, subject, quantity, condition, state axis, amount, time, authority, provenance or information loss." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "The root is a versioned return-and-refund case aggregate. Order, fulfilment, party, item, shipment, inventory, entitlement, invoice, credit note, payment, warranty, recall, dispute, waste and records remain external masters." }, "decisions": [ { "concept": "Return/refund case root", "disposition": "accepted-with-explicit-boundary", "rationale": "One case can bind request, decision, reverse movement, inspection, adjustment and payment evidence without owning the referenced commercial, physical, financial or legal masters." }, { "concept": "WM-ECO-024 parent signal", "disposition": "accepted-as-provisional-reference", "rationale": "The unified registry supplies a parent hint but the frozen relation ledger has no settled edge. It is retained as a non-canonical reference and grants no containment or cascade authority." }, { "concept": "Eligibility, remedy and authorization", "disposition": "accepted-as-separate-assertions", "rationale": "A request is not entitlement and an eligibility assessment is not authorization. Each assertion keeps rule version, scope, evidence, authority, event time and knowledge time." }, { "concept": "Goods, service, digital and non-return refund profiles", "disposition": "accepted-with-profile-gates", "rationale": "The aggregate can express these profiles, but no one movement, inspection, access-revocation or refund path is made universal across them." }, { "concept": "Reverse movement and returned-subject evidence", "disposition": "accepted-with-external-master-boundary", "rationale": "Subject identity, quantity, condition, custody and receipt are local bindings and observations; shipment, package, inventory, location and waste execution remain external." }, { "concept": "Inspection and disposition", "disposition": "accepted-as-independent-decisions", "rationale": "Receipt, inspection, return acceptance and disposition are not equivalent, and restock, repair, quarantine, recycle, destroy or access-revoke execution remains in authoritative sibling systems." }, { "concept": "Refund basis and obligation", "disposition": "accepted-with-financial-boundary", "rationale": "Price, tax, fee, discount, deposit, deduction, allocation, currency and rounding inputs support an auditable obligation, but the case does not issue accounting records or move funds." }, { "concept": "Credit, refund instruction, execution and settlement", "disposition": "accepted-as-distinct-evidence", "rationale": "A credit note is not a payment, a payment instruction is not execution, execution is not settlement, and settlement does not prove receipt by the intended beneficiary without evidence." }, { "concept": "Recall, warranty, chargeback and dispute", "disposition": "accepted-as-external-triggers-or-challenges", "rationale": "These lifecycles can create, constrain or contest a return/refund case but remain independently authoritative and cannot be closed by this aggregate." }, { "concept": "Legal and accounting profiles", "disposition": "accepted-with-jurisdiction-and-purpose-holds", "rationale": "CISG and EU rules are scoped legal profiles, while IFRS describes accounting treatment rather than individual entitlement. None is presented as universal law." }, { "concept": "Interoperability projections", "disposition": "accepted-with-loss-declaration", "rationale": "UBL, UN/EDIFACT, ISO 20022, EU, IFRS, EPCIS, CBV, Schema.org, RFC, PROV, DQV, ODRL and OpenAPI cover different facets and never replace the canonical case aggregate." }, { "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 new facts, so assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-ECO-025 each timed out after 120 seconds; no external result was admitted.", "Relation hold: WM-ECO-024 is only a provisional parent signal and the frozen relation ledger contains no settled WM-ECO-025 edge.", "Boundary hold: return request, eligibility, authorization, reverse shipment, receipt, inspection, disposition, refund obligation, credit note, payment return or reversal, chargeback and dispute retain separate identities.", "Profile hold: goods, services, digital content, access, consumer, business, marketplace, subscription, travel and regulated-sector cases require separate conformance profiles.", "Quantity and condition hold: every requested, authorized, handed-over, received, inspected, accepted and dispositioned value requires subject, unit, lot or serial, source, method, time and uncertainty.", "Financial hold: price, tax, fee, discount, deposit, deduction, allocation, currency and rounding require authoritative invoice, tax, accounting and payment references.", "State-axis hold: request, eligibility, authorization, custody, receipt, inspection, disposition, credit, instruction, execution, settlement, customer receipt and closure states and clocks must not collapse.", "Authority hold: legal eligibility, return authorization, custody, condition judgment, physical disposition, accounting adjustment, refund execution, disclosure and destruction require delegated authority.", "Jurisdiction hold: CISG and EU consumer, goods, digital and product-safety rules are scoped profiles; national, sector, tax, payment-scheme and contract rules need validation.", "Source-access hold: UNECE pages were indexed but direct automated access was publisher-blocked, and the official IFRS issued-standard document redirected to sign-in.", "Interoperability hold: every UBL, UN/EDIFACT, ISO 20022, EU, IFRS, EPCIS, CBV, Schema.org, RFC, PROV, DQV, ODRL and OpenAPI projection needs release pins, conformance evidence and loss declarations.", "Privacy hold: party, address, account, payment, item, serial, condition, fraud, dispute and evidence data require purpose-bound access, minimization and retention controls.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Canonically adjudicate the WM-ECO-024 parent signal and register return/refund relations to order, fulfilment, shipment, inventory, invoice, payment, warranty, recall, chargeback, dispute and waste models.", "Create consumer, business, marketplace, subscription, travel, digital, regulated-goods, hazardous-material and cross-border return profiles.", "Conformance-test return, receipt, inspection, disposition, adjustment, payment and projection mappings against concrete implementations.", "Validate organization-specific eligibility, evidence, fraud, tax, accounting, payment-route, safety, privacy, retention and exception policies.", "Obtain authorized legal, consumer, finance, tax, logistics, product-safety and records review before jurisdiction-specific claims.", "Obtain independent external research review before promotion beyond reviewable-draft assurance." ] }, "statistics": { "sources": 18, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }