# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T14:36:55Z", "synthesisSha256": "03a41bfcda3793640f81ec2415595775aa7a7e704d24517daf6531343bed8173", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ECO-021", "registryId": "vr.wm-eco-021", "name": "Offer / Quote", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ECO.OFR" ], "tags": [ "offer", "quote", "soc.eco.ofr" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-eco-021-offer-quote/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/publications/wm-eco-021-offer-quote", "model": { "registry_id": "vr.wm-eco-021", "model_id": "WM-ECO-021", "name": "Offer / Quote", "entry_kind": "aggregate", "purpose": "Represent one governed, versioned pre-contract commercial proposal so agents can understand who proposes what, to whom, for which price and terms, during which validity, with what evidence and response state, without confusing the proposal with a product master, negotiation, order, contract or legal formation decision.", "scope_statement": "Owns proposal identity, version, declared offer, quotation, estimate or informational profile; issuer and addressed-recipient roles; external product, service, right and resource references; lines, lots, bundles, options, alternatives and dependencies; quantities, units and eligibility; prices, currencies, formulas, tiers, recurring and usage terms; taxes, allowances, charges and totals; delivery, payment, quality, warranty, return, service-level, assumption, exclusion, rights and confidentiality terms; issue, effective, receipt, validity, response, expiry and knowledge times; attributable withdrawal, revocation, rejection, counter-offer and acceptance references; amendments, source, approval, quality, access, retention and loss-aware projections. Party, subject, catalogue, RFQ, negotiation, tender, contract, order, invoice, payment, fulfilment, response-event and legal-determination masters remain authoritative.", "in_scope": [ "Proposal identity, versions, profiles, parties by reference, offered subjects, lines, lots, bundles, quantities, eligibility, pricing, taxes, totals and commercial terms", "Fulfilment conditions, validity, lifecycle, response references, amendments, evidence, provenance, validation, access, retention and interoperable projections" ], "out_of_scope": [ "Owning Party, Product, Service, Right, Catalogue, Price List, RFQ, Negotiation, Tender, Contract, Order, Invoice, Payment, Shipment, Performance, Response Event, Legal Decision or Records masters", "Treating a quotation, estimate, acknowledgement, click, conduct or technical status as universal proof of legal offer, acceptance, formation or enforceability", "Autonomous pricing approval, tax or legal determination, acceptance, signature, dispatch, publication, access widening or physical records disposition" ], "boundary_notes": [ { "neighbor": "WM-OBJ-003 parent signal", "distinction": "The unfrozen object parent may supply generic object context but grants no ownership, mutation or cascade authority.", "source_refs": [ "SRC-004", "SRC-013" ] }, { "neighbor": "RFQ, negotiation, tender, order and contract", "distinction": "A request asks for a proposal, negotiation exchanges positions, a tender follows procurement rules, an order requests performance and a contract records obligations. The proposal references but does not absorb them.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ] }, { "neighbor": "Party, product, service, catalogue and price list", "distinction": "These masters supply identities and source terms; the proposal owns only version-specific commercial assertions and references.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009" ] }, { "neighbor": "Acceptance event and contract-formation determination", "distinction": "The proposal records attributable evidence and observed state but does not decide whether acceptance was effective or a contract formed under governing law.", "source_refs": [ "SRC-001", "SRC-002", "SRC-013", "SRC-015" ] }, { "neighbor": "UBL, schema.org, GS1, ODRL, PROV, JSON Schema and OpenAPI", "distinction": "Each representation has different semantics and coverage; mappings are version-pinned and loss-declaring.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-012", "SRC-013", "SRC-016", "SRC-017" ] } ] }, "sources": [ { "id": "SRC-001", "title": "United Nations Convention on Contracts for the International Sale of Goods", "organization": "United Nations Commission on International Trade Law", "url": "https://uncitral.un.org/sites/default/files/media-documents/uncitral/en/v1056997-cisg-e-book.pdf", "version_or_date": "United Nations publication 2010; Convention text adopted 11 April 1980", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Distinguishes offer, effectiveness, withdrawal, revocation, rejection, acceptance, modification and receipt in international sales." }, { "id": "SRC-002", "title": "UNIDROIT Principles of International Commercial Contracts 2016", "organization": "UNIDROIT", "url": "https://www.unidroit.org/instruments/commercial-contracts/unidroit-principles-2016/", "version_or_date": "Fourth edition 2016; published May 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Provides a cross-border reference for offer definiteness, intent, effectiveness, revocation, acceptance, modified acceptance and contract formation." }, { "id": "SRC-003", "title": "Directive 2011/83/EU on consumer rights", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32011L0083", "version_or_date": "Consolidated context current at access; amendments must be pinned per implementation", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Defines pre-contract information including trader identity, total price, taxes, extra charges, payment, delivery, performance and duration for consumer contexts." }, { "id": "SRC-004", "title": "Universal Business Language Version 2.3", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/os-UBL-2.3/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-06T14:31:00Z", "relevance": "Defines quotation and request-for-quotation business processes, parties, items, pricing, taxes, allowances, charges, payment, delivery and validation artifacts." }, { "id": "SRC-005", "title": "UBL 2.3 Quotation data model", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/os-UBL-2.3/mod/summary/reports/UBL-Quotation-2.3.html", "version_or_date": "OASIS Standard data model 15 June 2021", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Defines the Quotation document aggregate, identifiers, dates, validity, parties, lines, totals, taxes, allowances and commercial terms." }, { "id": "SRC-006", "title": "UBL 2.3 Request For Quotation data model", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/ubl/os-UBL-2.3/mod/summary/reports/UBL-RequestForQuotation-2.3.html", "version_or_date": "OASIS Standard data model 15 June 2021", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Separates the buyer-originated request for quotation from the seller quotation response and supplies reusable request references." }, { "id": "SRC-007", "title": "Offer", "organization": "Schema.org Community Group", "url": "https://schema.org/Offer", "version_or_date": "Living vocabulary accessed 6 September 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Defines web-discovery terms for offered item, seller, availability, eligibility, quantity, region, price, price specification, shipping and validity." }, { "id": "SRC-008", "title": "PriceSpecification", "organization": "Schema.org Community Group", "url": "https://schema.org/PriceSpecification", "version_or_date": "Living vocabulary accessed 6 September 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Defines detailed prices and compound components, eligible transaction volume and currency-qualified amounts." }, { "id": "SRC-009", "title": "GS1 Web Vocabulary", "organization": "GS1", "url": "https://ref.gs1.org/voc/", "version_or_date": "Live GS1 vocabulary accessed 6 September 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Defines product offers, organizations, price specifications, eligible quantities, min and max price, currency and validity for commerce discovery." }, { "id": "SRC-010", "title": "Recommendation No. 20: Codes for Units of Measure Used in International Trade", "organization": "United Nations Economic Commission for Europe", "url": "https://unece.org/trade/documents/session-documents/codes-units-measure-used-international-trade-recommendation", "version_or_date": "Revision 7 page current at access", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Provides interoperable codes for quantities and units in commercial lines and eligibility constraints." }, { "id": "SRC-011", "title": "Global Financial Data Standards: ISO 4217 Currency Codes", "organization": "SIX Financial Information", "url": "https://www.six-group.com/en/products-services/financial-information/market-reference-data/data-standards.html", "version_or_date": "ISO 4217 Maintenance Agency lists current at access", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Provides the authoritative maintained alphabetic and numeric currency identifiers and minor-unit context for prices and totals." }, { "id": "SRC-012", "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-06T14:31:00Z", "relevance": "Defines Offer policies, assigner parties, permissions, prohibitions, duties, constraints, inheritance and conflict strategies without implying a grant." }, { "id": "SRC-013", "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-06T14:31:00Z", "relevance": "Defines entities, activities, agents, attribution, generation, derivation, revision and qualified provenance." }, { "id": "SRC-014", "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-06T14:31:00Z", "relevance": "Defines quality dimensions, metrics, measurements, annotations, policies and quality certificates." }, { "id": "SRC-015", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/info/rfc3339/", "version_or_date": "RFC 3339 July 2002, updated by RFC 9557", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Defines interoperable timestamps with seconds and an explicit relationship to UTC." }, { "id": "SRC-016", "title": "JSON Schema Draft 2020-12", "organization": "JSON Schema organization", "url": "https://json-schema.org/draft/2020-12", "version_or_date": "Draft 2020-12 specification set", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:31:00Z", "relevance": "Defines machine-validation vocabularies for JSON projections and extension contracts." }, { "id": "SRC-017", "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-06T14:31:00Z", "relevance": "Defines HTTP API descriptions, operations, parameters, schemas, responses, security and reusable components for service projections." } ], "structure": { "bundles": [ { "id": "identity-classification-and-legal-boundary", "name": "Identity, classification and legal boundary", "description": "Groups governed offer and quotation context for identity, classification and legal boundary.", "rationale": "Identify a proposal and its declared profile without inferring legal effect.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ], "layers": [ { "id": "proposal-root-identity-version-profile-and-status", "name": "Proposal root identity, version, profile and status", "description": "Groups source-qualified proposal context for proposal root identity, version, profile and status.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013" ], "findings": [ { "id": "proposal-id-version-head-title-type-language-purpose-and-status", "name": "Proposal ID, version, head, title, type, language, purpose and status", "description": "Records proposal id, version, head, title, type, language, purpose and status as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013" ], "questions": [ { "id": "proposal-id-version-head-title-type-language-purpose-and-status-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish proposal id, version, head, title, type, language, purpose and status?", "kind": "identity", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "proposal-id-version-head-title-type-language-purpose-and-status-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on proposal id, version, head, title, type, language, purpose and status, for which purpose and under what authority?", "kind": "authority", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "proposal-id-version-head-title-type-language-purpose-and-status-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify proposal id, version, head, title, type, language, purpose and status?", "kind": "security", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "proposal-id-version-head-title-type-language-purpose-and-status-data", "name": "Proposal ID, version, head, title, type, language, purpose and status data", "description": "Typed offer or quotation data for proposal id, version, head, title, type, language, purpose and status, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013" ] } ], "artifacts": [ { "id": "proposal-id-version-head-title-type-language-purpose-and-status-record", "name": "Proposal ID, version, head, title, type, language, purpose and status record", "description": "Immutable or successor-versioned proposal evidence for proposal id, version, head, title, type, language, purpose and status.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for proposal-id-version-head-title-type-language-purpose-and-status; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "legal-offer-quotation-estimate-proposal-tender-order-contract-and-invitation-boundary", "name": "Legal offer, quotation, estimate, proposal, tender, order, contract and invitation boundary", "description": "Records legal offer, quotation, estimate, proposal, tender, order, contract and invitation boundary as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013" ], "questions": [ { "id": "legal-offer-quotation-estimate-proposal-tender-order-contract-and-invitation-boundary-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish legal offer, quotation, estimate, proposal, tender, order, contract and invitation boundary?", "kind": "classification", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "legal-offer-quotation-estimate-proposal-tender-order-contract-and-invitation-boundary-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on legal offer, quotation, estimate, proposal, tender, order, contract and invitation boundary, for which purpose and under what authority?", "kind": "requirement", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "legal-offer-quotation-estimate-proposal-tender-order-contract-and-invitation-boundary-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify legal offer, quotation, estimate, proposal, tender, order, contract and invitation boundary?", "kind": "privacy", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "legal-offer-quotation-estimate-proposal-tender-order-contract-and-invitation-boundary-data", "name": "Legal offer, quotation, estimate, proposal, tender, order, contract and invitation boundary data", "description": "Typed offer or quotation data for legal offer, quotation, estimate, proposal, tender, order, contract and invitation boundary, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013" ] } ], "artifacts": [ { "id": "legal-offer-quotation-estimate-proposal-tender-order-contract-and-invitation-boundary-record", "name": "Legal offer, quotation, estimate, proposal, tender, order, contract and invitation boundary record", "description": "Immutable or successor-versioned proposal evidence for legal offer, quotation, estimate, proposal, tender, order, contract and invitation boundary.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for legal-offer-quotation-estimate-proposal-tender-order-contract-and-invitation-boundary; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "participants-authority-addressing-and-communication", "name": "Participants, authority, addressing and communication", "description": "Groups source-qualified proposal context for participants, authority, addressing and communication.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ], "findings": [ { "id": "issuer-offeror-seller-offeree-buyer-customer-agent-and-beneficiary-roles", "name": "Issuer, offeror, seller, offeree, buyer, customer, agent and beneficiary roles", "description": "Records issuer, offeror, seller, offeree, buyer, customer, agent and beneficiary roles as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ], "questions": [ { "id": "issuer-offeror-seller-offeree-buyer-customer-agent-and-beneficiary-roles-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish issuer, offeror, seller, offeree, buyer, customer, agent and beneficiary roles?", "kind": "relationship", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "issuer-offeror-seller-offeree-buyer-customer-agent-and-beneficiary-roles-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on issuer, offeror, seller, offeree, buyer, customer, agent and beneficiary roles, for which purpose and under what authority?", "kind": "constraint", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "issuer-offeror-seller-offeree-buyer-customer-agent-and-beneficiary-roles-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify issuer, offeror, seller, offeree, buyer, customer, agent and beneficiary roles?", "kind": "retention", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "issuer-offeror-seller-offeree-buyer-customer-agent-and-beneficiary-roles-data", "name": "Issuer, offeror, seller, offeree, buyer, customer, agent and beneficiary roles data", "description": "Typed offer or quotation data for issuer, offeror, seller, offeree, buyer, customer, agent and beneficiary roles, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "issuer-offeror-seller-offeree-buyer-customer-agent-and-beneficiary-roles-record", "name": "Issuer, offeror, seller, offeree, buyer, customer, agent and beneficiary roles record", "description": "Immutable or successor-versioned proposal evidence for issuer, offeror, seller, offeree, buyer, customer, agent and beneficiary roles.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for issuer-offeror-seller-offeree-buyer-customer-agent-and-beneficiary-roles; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "mandate-signing-pricing-authority-address-channel-delivery-receipt-and-acknowledgement", "name": "Mandate, signing and pricing authority, address, channel, delivery, receipt and acknowledgement", "description": "Records mandate, signing and pricing authority, address, channel, delivery, receipt and acknowledgement as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ], "questions": [ { "id": "mandate-signing-pricing-authority-address-channel-delivery-receipt-and-acknowledgement-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish mandate, signing and pricing authority, address, channel, delivery, receipt and acknowledgement?", "kind": "authority", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "mandate-signing-pricing-authority-address-channel-delivery-receipt-and-acknowledgement-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on mandate, signing and pricing authority, address, channel, delivery, receipt and acknowledgement, for which purpose and under what authority?", "kind": "process", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "mandate-signing-pricing-authority-address-channel-delivery-receipt-and-acknowledgement-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify mandate, signing and pricing authority, address, channel, delivery, receipt and acknowledgement?", "kind": "access", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "mandate-signing-pricing-authority-address-channel-delivery-receipt-and-acknowledgement-data", "name": "Mandate, signing and pricing authority, address, channel, delivery, receipt and acknowledgement data", "description": "Typed offer or quotation data for mandate, signing and pricing authority, address, channel, delivery, receipt and acknowledgement, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "mandate-signing-pricing-authority-address-channel-delivery-receipt-and-acknowledgement-record", "name": "Mandate, signing and pricing authority, address, channel, delivery, receipt and acknowledgement record", "description": "Immutable or successor-versioned proposal evidence for mandate, signing and pricing authority, address, channel, delivery, receipt and acknowledgement.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for mandate-signing-pricing-authority-address-channel-delivery-receipt-and-acknowledgement; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "offered-subject-composition-and-eligibility", "name": "Offered subject, composition and eligibility", "description": "Groups governed offer and quotation context for offered subject, composition and eligibility.", "rationale": "Describe what is proposed and for whom while preserving external product and service masters.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012" ], "layers": [ { "id": "subject-lines-lots-bundles-options-and-dependencies", "name": "Subject lines, lots, bundles, options and dependencies", "description": "Groups source-qualified proposal context for subject lines, lots, bundles, options and dependencies.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ], "findings": [ { "id": "product-service-right-resource-sku-gtin-description-classification-and-master-reference", "name": "Product, service, right, resource, SKU, GTIN, description, classification and master reference", "description": "Records product, service, right, resource, sku, gtin, description, classification and master reference as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ], "questions": [ { "id": "product-service-right-resource-sku-gtin-description-classification-and-master-reference-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish product, service, right, resource, sku, gtin, description, classification and master reference?", "kind": "relationship", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "product-service-right-resource-sku-gtin-description-classification-and-master-reference-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on product, service, right, resource, sku, gtin, description, classification and master reference, for which purpose and under what authority?", "kind": "event", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "product-service-right-resource-sku-gtin-description-classification-and-master-reference-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify product, service, right, resource, sku, gtin, description, classification and master reference?", "kind": "exception", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "product-service-right-resource-sku-gtin-description-classification-and-master-reference-data", "name": "Product, service, right, resource, SKU, GTIN, description, classification and master reference data", "description": "Typed offer or quotation data for product, service, right, resource, sku, gtin, description, classification and master reference, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "product-service-right-resource-sku-gtin-description-classification-and-master-reference-record", "name": "Product, service, right, resource, SKU, GTIN, description, classification and master reference record", "description": "Immutable or successor-versioned proposal evidence for product, service, right, resource, sku, gtin, description, classification and master reference.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for product-service-right-resource-sku-gtin-description-classification-and-master-reference; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "line-lot-package-bundle-option-alternative-substitution-dependency-partial-and-all-or-none-rule", "name": "Line, lot, package, bundle, option, alternative, substitution, dependency, partial and all-or-none rule", "description": "Records line, lot, package, bundle, option, alternative, substitution, dependency, partial and all-or-none rule as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ], "questions": [ { "id": "line-lot-package-bundle-option-alternative-substitution-dependency-partial-and-all-or-none-rule-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish line, lot, package, bundle, option, alternative, substitution, dependency, partial and all-or-none rule?", "kind": "composition", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "line-lot-package-bundle-option-alternative-substitution-dependency-partial-and-all-or-none-rule-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on line, lot, package, bundle, option, alternative, substitution, dependency, partial and all-or-none rule, for which purpose and under what authority?", "kind": "measurement", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "line-lot-package-bundle-option-alternative-substitution-dependency-partial-and-all-or-none-rule-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify line, lot, package, bundle, option, alternative, substitution, dependency, partial and all-or-none rule?", "kind": "interoperability", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "line-lot-package-bundle-option-alternative-substitution-dependency-partial-and-all-or-none-rule-data", "name": "Line, lot, package, bundle, option, alternative, substitution, dependency, partial and all-or-none rule data", "description": "Typed offer or quotation data for line, lot, package, bundle, option, alternative, substitution, dependency, partial and all-or-none rule, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "line-lot-package-bundle-option-alternative-substitution-dependency-partial-and-all-or-none-rule-record", "name": "Line, lot, package, bundle, option, alternative, substitution, dependency, partial and all-or-none rule record", "description": "Immutable or successor-versioned proposal evidence for line, lot, package, bundle, option, alternative, substitution, dependency, partial and all-or-none rule.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for line-lot-package-bundle-option-alternative-substitution-dependency-partial-and-all-or-none-rule; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "quantity-recipient-region-channel-and-prerequisites", "name": "Quantity, recipient, region, channel and prerequisites", "description": "Groups source-qualified proposal context for quantity, recipient, region, channel and prerequisites.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012" ], "findings": [ { "id": "quantity-unit-minimum-maximum-multiple-breakpoint-capacity-and-availability", "name": "Quantity, unit, minimum, maximum, multiple, breakpoint, capacity and availability", "description": "Records quantity, unit, minimum, maximum, multiple, breakpoint, capacity and availability as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012" ], "questions": [ { "id": "quantity-unit-minimum-maximum-multiple-breakpoint-capacity-and-availability-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish quantity, unit, minimum, maximum, multiple, breakpoint, capacity and availability?", "kind": "measurement", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "quantity-unit-minimum-maximum-multiple-breakpoint-capacity-and-availability-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on quantity, unit, minimum, maximum, multiple, breakpoint, capacity and availability, for which purpose and under what authority?", "kind": "evidence", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "quantity-unit-minimum-maximum-multiple-breakpoint-capacity-and-availability-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify quantity, unit, minimum, maximum, multiple, breakpoint, capacity and availability?", "kind": "decision", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "quantity-unit-minimum-maximum-multiple-breakpoint-capacity-and-availability-data", "name": "Quantity, unit, minimum, maximum, multiple, breakpoint, capacity and availability data", "description": "Typed offer or quotation data for quantity, unit, minimum, maximum, multiple, breakpoint, capacity and availability, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012" ] } ], "artifacts": [ { "id": "quantity-unit-minimum-maximum-multiple-breakpoint-capacity-and-availability-record", "name": "Quantity, unit, minimum, maximum, multiple, breakpoint, capacity and availability record", "description": "Immutable or successor-versioned proposal evidence for quantity, unit, minimum, maximum, multiple, breakpoint, capacity and availability.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for quantity-unit-minimum-maximum-multiple-breakpoint-capacity-and-availability; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "eligible-recipient-customer-segment-region-channel-transaction-volume-and-precondition", "name": "Eligible recipient, customer segment, region, channel, transaction volume and precondition", "description": "Records eligible recipient, customer segment, region, channel, transaction volume and precondition as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012" ], "questions": [ { "id": "eligible-recipient-customer-segment-region-channel-transaction-volume-and-precondition-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish eligible recipient, customer segment, region, channel, transaction volume and precondition?", "kind": "constraint", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "eligible-recipient-customer-segment-region-channel-transaction-volume-and-precondition-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on eligible recipient, customer segment, region, channel, transaction volume and precondition, for which purpose and under what authority?", "kind": "quality", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "eligible-recipient-customer-segment-region-channel-transaction-volume-and-precondition-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify eligible recipient, customer segment, region, channel, transaction volume and precondition?", "kind": "identity", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "eligible-recipient-customer-segment-region-channel-transaction-volume-and-precondition-data", "name": "Eligible recipient, customer segment, region, channel, transaction volume and precondition data", "description": "Typed offer or quotation data for eligible recipient, customer segment, region, channel, transaction volume and precondition, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012" ] } ], "artifacts": [ { "id": "eligible-recipient-customer-segment-region-channel-transaction-volume-and-precondition-record", "name": "Eligible recipient, customer segment, region, channel, transaction volume and precondition record", "description": "Immutable or successor-versioned proposal evidence for eligible recipient, customer segment, region, channel, transaction volume and precondition.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for eligible-recipient-customer-segment-region-channel-transaction-volume-and-precondition; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "pricing-taxes-totals-and-commercial-terms", "name": "Pricing, taxes, totals and commercial terms", "description": "Groups governed offer and quotation context for pricing, taxes, totals and commercial terms.", "rationale": "Make every amount, formula, currency and commercial condition independently interpretable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-014" ], "layers": [ { "id": "price-components-currency-basis-and-calculation", "name": "Price components, currency, basis and calculation", "description": "Groups source-qualified proposal context for price components, currency, basis and calculation.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ], "findings": [ { "id": "unit-list-base-net-fixed-estimated-ranged-tiered-recurring-usage-and-formula-price", "name": "Unit, list, base, net, fixed, estimated, ranged, tiered, recurring, usage and formula price", "description": "Records unit, list, base, net, fixed, estimated, ranged, tiered, recurring, usage and formula price as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ], "questions": [ { "id": "unit-list-base-net-fixed-estimated-ranged-tiered-recurring-usage-and-formula-price-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish unit, list, base, net, fixed, estimated, ranged, tiered, recurring, usage and formula price?", "kind": "measurement", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "unit-list-base-net-fixed-estimated-ranged-tiered-recurring-usage-and-formula-price-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on unit, list, base, net, fixed, estimated, ranged, tiered, recurring, usage and formula price, for which purpose and under what authority?", "kind": "validation", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "unit-list-base-net-fixed-estimated-ranged-tiered-recurring-usage-and-formula-price-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify unit, list, base, net, fixed, estimated, ranged, tiered, recurring, usage and formula price?", "kind": "classification", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "unit-list-base-net-fixed-estimated-ranged-tiered-recurring-usage-and-formula-price-data", "name": "Unit, list, base, net, fixed, estimated, ranged, tiered, recurring, usage and formula price data", "description": "Typed offer or quotation data for unit, list, base, net, fixed, estimated, ranged, tiered, recurring, usage and formula price, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ] } ], "artifacts": [ { "id": "unit-list-base-net-fixed-estimated-ranged-tiered-recurring-usage-and-formula-price-record", "name": "Unit, list, base, net, fixed, estimated, ranged, tiered, recurring, usage and formula price record", "description": "Immutable or successor-versioned proposal evidence for unit, list, base, net, fixed, estimated, ranged, tiered, recurring, usage and formula price.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for unit-list-base-net-fixed-estimated-ranged-tiered-recurring-usage-and-formula-price; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "currency-minor-unit-exchange-rate-rounding-precision-quantity-basis-and-price-validity", "name": "Currency, minor unit, exchange rate, rounding, precision, quantity basis and price validity", "description": "Records currency, minor unit, exchange rate, rounding, precision, quantity basis and price validity as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ], "questions": [ { "id": "currency-minor-unit-exchange-rate-rounding-precision-quantity-basis-and-price-validity-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish currency, minor unit, exchange rate, rounding, precision, quantity basis and price validity?", "kind": "measurement", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "currency-minor-unit-exchange-rate-rounding-precision-quantity-basis-and-price-validity-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on currency, minor unit, exchange rate, rounding, precision, quantity basis and price validity, for which purpose and under what authority?", "kind": "security", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "currency-minor-unit-exchange-rate-rounding-precision-quantity-basis-and-price-validity-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify currency, minor unit, exchange rate, rounding, precision, quantity basis and price validity?", "kind": "composition", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "currency-minor-unit-exchange-rate-rounding-precision-quantity-basis-and-price-validity-data", "name": "Currency, minor unit, exchange rate, rounding, precision, quantity basis and price validity data", "description": "Typed offer or quotation data for currency, minor unit, exchange rate, rounding, precision, quantity basis and price validity, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ] } ], "artifacts": [ { "id": "currency-minor-unit-exchange-rate-rounding-precision-quantity-basis-and-price-validity-record", "name": "Currency, minor unit, exchange rate, rounding, precision, quantity basis and price validity record", "description": "Immutable or successor-versioned proposal evidence for currency, minor unit, exchange rate, rounding, precision, quantity basis and price validity.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for currency-minor-unit-exchange-rate-rounding-precision-quantity-basis-and-price-validity; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "tax-allowance-charge-total-and-payment-terms", "name": "Tax, allowance, charge, total and payment terms", "description": "Groups source-qualified proposal context for tax, allowance, charge, total and payment terms.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-011", "SRC-013" ], "findings": [ { "id": "tax-category-rate-jurisdiction-exemption-inclusion-exclusion-and-evidence", "name": "Tax category, rate, jurisdiction, exemption, inclusion, exclusion and evidence", "description": "Records tax category, rate, jurisdiction, exemption, inclusion, exclusion and evidence as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-011", "SRC-013" ], "questions": [ { "id": "tax-category-rate-jurisdiction-exemption-inclusion-exclusion-and-evidence-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish tax category, rate, jurisdiction, exemption, inclusion, exclusion and evidence?", "kind": "requirement", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "tax-category-rate-jurisdiction-exemption-inclusion-exclusion-and-evidence-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on tax category, rate, jurisdiction, exemption, inclusion, exclusion and evidence, for which purpose and under what authority?", "kind": "privacy", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "tax-category-rate-jurisdiction-exemption-inclusion-exclusion-and-evidence-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify tax category, rate, jurisdiction, exemption, inclusion, exclusion and evidence?", "kind": "relationship", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "tax-category-rate-jurisdiction-exemption-inclusion-exclusion-and-evidence-data", "name": "Tax category, rate, jurisdiction, exemption, inclusion, exclusion and evidence data", "description": "Typed offer or quotation data for tax category, rate, jurisdiction, exemption, inclusion, exclusion and evidence, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "tax-category-rate-jurisdiction-exemption-inclusion-exclusion-and-evidence-record", "name": "Tax category, rate, jurisdiction, exemption, inclusion, exclusion and evidence record", "description": "Immutable or successor-versioned proposal evidence for tax category, rate, jurisdiction, exemption, inclusion, exclusion and evidence.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for tax-category-rate-jurisdiction-exemption-inclusion-exclusion-and-evidence; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "discount-allowance-surcharge-freight-subtotal-tax-total-payable-deposit-and-payment-schedule", "name": "Discount, allowance, surcharge, freight, subtotal, tax total, payable, deposit and payment schedule", "description": "Records discount, allowance, surcharge, freight, subtotal, tax total, payable, deposit and payment schedule as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-011", "SRC-013" ], "questions": [ { "id": "discount-allowance-surcharge-freight-subtotal-tax-total-payable-deposit-and-payment-schedule-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish discount, allowance, surcharge, freight, subtotal, tax total, payable, deposit and payment schedule?", "kind": "composition", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "discount-allowance-surcharge-freight-subtotal-tax-total-payable-deposit-and-payment-schedule-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on discount, allowance, surcharge, freight, subtotal, tax total, payable, deposit and payment schedule, for which purpose and under what authority?", "kind": "retention", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "discount-allowance-surcharge-freight-subtotal-tax-total-payable-deposit-and-payment-schedule-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify discount, allowance, surcharge, freight, subtotal, tax total, payable, deposit and payment schedule?", "kind": "state", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "discount-allowance-surcharge-freight-subtotal-tax-total-payable-deposit-and-payment-schedule-data", "name": "Discount, allowance, surcharge, freight, subtotal, tax total, payable, deposit and payment schedule data", "description": "Typed offer or quotation data for discount, allowance, surcharge, freight, subtotal, tax total, payable, deposit and payment schedule, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "discount-allowance-surcharge-freight-subtotal-tax-total-payable-deposit-and-payment-schedule-record", "name": "Discount, allowance, surcharge, freight, subtotal, tax total, payable, deposit and payment schedule record", "description": "Immutable or successor-versioned proposal evidence for discount, allowance, surcharge, freight, subtotal, tax total, payable, deposit and payment schedule.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for discount-allowance-surcharge-freight-subtotal-tax-total-payable-deposit-and-payment-schedule; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "fulfilment-risk-conditions-and-evidence", "name": "Fulfilment, risk, conditions and evidence", "description": "Groups governed offer and quotation context for fulfilment, risk, conditions and evidence.", "rationale": "Express performance expectations, assumptions and rights without owning downstream fulfilment.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012", "SRC-013" ], "layers": [ { "id": "delivery-performance-quality-warranty-and-returns", "name": "Delivery, performance, quality, warranty and returns", "description": "Groups source-qualified proposal context for delivery, performance, quality, warranty and returns.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ], "findings": [ { "id": "delivery-place-method-window-lead-time-incoterm-shipment-service-location-and-responsibility", "name": "Delivery place, method, window, lead time, Incoterm, shipment, service location and responsibility", "description": "Records delivery place, method, window, lead time, incoterm, shipment, service location and responsibility as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ], "questions": [ { "id": "delivery-place-method-window-lead-time-incoterm-shipment-service-location-and-responsibility-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish delivery place, method, window, lead time, incoterm, shipment, service location and responsibility?", "kind": "process", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "delivery-place-method-window-lead-time-incoterm-shipment-service-location-and-responsibility-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on delivery place, method, window, lead time, incoterm, shipment, service location and responsibility, for which purpose and under what authority?", "kind": "access", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "delivery-place-method-window-lead-time-incoterm-shipment-service-location-and-responsibility-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify delivery place, method, window, lead time, incoterm, shipment, service location and responsibility?", "kind": "lifecycle", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "delivery-place-method-window-lead-time-incoterm-shipment-service-location-and-responsibility-data", "name": "Delivery place, method, window, lead time, Incoterm, shipment, service location and responsibility data", "description": "Typed offer or quotation data for delivery place, method, window, lead time, incoterm, shipment, service location and responsibility, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ] } ], "artifacts": [ { "id": "delivery-place-method-window-lead-time-incoterm-shipment-service-location-and-responsibility-record", "name": "Delivery place, method, window, lead time, Incoterm, shipment, service location and responsibility record", "description": "Immutable or successor-versioned proposal evidence for delivery place, method, window, lead time, incoterm, shipment, service location and responsibility.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for delivery-place-method-window-lead-time-incoterm-shipment-service-location-and-responsibility; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "quality-acceptance-criterion-service-level-warranty-support-return-cancellation-and-remedy", "name": "Quality, acceptance criterion, service level, warranty, support, return, cancellation and remedy", "description": "Records quality, acceptance criterion, service level, warranty, support, return, cancellation and remedy as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ], "questions": [ { "id": "quality-acceptance-criterion-service-level-warranty-support-return-cancellation-and-remedy-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish quality, acceptance criterion, service level, warranty, support, return, cancellation and remedy?", "kind": "requirement", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "quality-acceptance-criterion-service-level-warranty-support-return-cancellation-and-remedy-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on quality, acceptance criterion, service level, warranty, support, return, cancellation and remedy, for which purpose and under what authority?", "kind": "exception", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "quality-acceptance-criterion-service-level-warranty-support-return-cancellation-and-remedy-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify quality, acceptance criterion, service level, warranty, support, return, cancellation and remedy?", "kind": "temporal", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "quality-acceptance-criterion-service-level-warranty-support-return-cancellation-and-remedy-data", "name": "Quality, acceptance criterion, service level, warranty, support, return, cancellation and remedy data", "description": "Typed offer or quotation data for quality, acceptance criterion, service level, warranty, support, return, cancellation and remedy, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ] } ], "artifacts": [ { "id": "quality-acceptance-criterion-service-level-warranty-support-return-cancellation-and-remedy-record", "name": "Quality, acceptance criterion, service level, warranty, support, return, cancellation and remedy record", "description": "Immutable or successor-versioned proposal evidence for quality, acceptance criterion, service level, warranty, support, return, cancellation and remedy.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for quality-acceptance-criterion-service-level-warranty-support-return-cancellation-and-remedy; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-012" ] } ], "inline_only_rationale": null } ] }, { "id": "assumptions-exclusions-contingencies-rights-and-confidentiality", "name": "Assumptions, exclusions, contingencies, rights and confidentiality", "description": "Groups source-qualified proposal context for assumptions, exclusions, contingencies, rights and confidentiality.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-012", "SRC-013" ], "findings": [ { "id": "assumption-exclusion-dependency-customer-input-contingency-risk-change-trigger-and-limitation", "name": "Assumption, exclusion, dependency, customer input, contingency, risk, change trigger and limitation", "description": "Records assumption, exclusion, dependency, customer input, contingency, risk, change trigger and limitation as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-012", "SRC-013" ], "questions": [ { "id": "assumption-exclusion-dependency-customer-input-contingency-risk-change-trigger-and-limitation-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish assumption, exclusion, dependency, customer input, contingency, risk, change trigger and limitation?", "kind": "constraint", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "assumption-exclusion-dependency-customer-input-contingency-risk-change-trigger-and-limitation-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on assumption, exclusion, dependency, customer input, contingency, risk, change trigger and limitation, for which purpose and under what authority?", "kind": "interoperability", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "assumption-exclusion-dependency-customer-input-contingency-risk-change-trigger-and-limitation-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify assumption, exclusion, dependency, customer input, contingency, risk, change trigger and limitation?", "kind": "provenance", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "assumption-exclusion-dependency-customer-input-contingency-risk-change-trigger-and-limitation-data", "name": "Assumption, exclusion, dependency, customer input, contingency, risk, change trigger and limitation data", "description": "Typed offer or quotation data for assumption, exclusion, dependency, customer input, contingency, risk, change trigger and limitation, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "assumption-exclusion-dependency-customer-input-contingency-risk-change-trigger-and-limitation-record", "name": "Assumption, exclusion, dependency, customer input, contingency, risk, change trigger and limitation record", "description": "Immutable or successor-versioned proposal evidence for assumption, exclusion, dependency, customer input, contingency, risk, change trigger and limitation.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for assumption-exclusion-dependency-customer-input-contingency-risk-change-trigger-and-limitation; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "permission-prohibition-duty-license-usage-right-confidentiality-publicity-and-data-term", "name": "Permission, prohibition, duty, license, usage right, confidentiality, publicity and data term", "description": "Records permission, prohibition, duty, license, usage right, confidentiality, publicity and data term as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-012", "SRC-013" ], "questions": [ { "id": "permission-prohibition-duty-license-usage-right-confidentiality-publicity-and-data-term-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish permission, prohibition, duty, license, usage right, confidentiality, publicity and data term?", "kind": "access", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "permission-prohibition-duty-license-usage-right-confidentiality-publicity-and-data-term-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on permission, prohibition, duty, license, usage right, confidentiality, publicity and data term, for which purpose and under what authority?", "kind": "decision", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "permission-prohibition-duty-license-usage-right-confidentiality-publicity-and-data-term-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify permission, prohibition, duty, license, usage right, confidentiality, publicity and data term?", "kind": "ownership", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "permission-prohibition-duty-license-usage-right-confidentiality-publicity-and-data-term-data", "name": "Permission, prohibition, duty, license, usage right, confidentiality, publicity and data term data", "description": "Typed offer or quotation data for permission, prohibition, duty, license, usage right, confidentiality, publicity and data term, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "permission-prohibition-duty-license-usage-right-confidentiality-publicity-and-data-term-record", "name": "Permission, prohibition, duty, license, usage right, confidentiality, publicity and data term record", "description": "Immutable or successor-versioned proposal evidence for permission, prohibition, duty, license, usage right, confidentiality, publicity and data term.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for permission-prohibition-duty-license-usage-right-confidentiality-publicity-and-data-term; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-response-and-time", "name": "Lifecycle, response and time", "description": "Groups governed offer and quotation context for lifecycle, response and time.", "rationale": "Record attributable proposal and response events without deciding contract formation.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-013", "SRC-015" ], "layers": [ { "id": "draft-issue-effectiveness-receipt-validity-and-expiry", "name": "Draft, issue, effectiveness, receipt, validity and expiry", "description": "Groups source-qualified proposal context for draft, issue, effectiveness, receipt, validity and expiry.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-015" ], "findings": [ { "id": "draft-reviewed-approved-issued-sent-delivered-received-effective-open-expired-lapsed-and-closed", "name": "Draft, reviewed, approved, issued, sent, delivered, received, effective, open, expired, lapsed and closed", "description": "Records draft, reviewed, approved, issued, sent, delivered, received, effective, open, expired, lapsed and closed as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-015" ], "questions": [ { "id": "draft-reviewed-approved-issued-sent-delivered-received-effective-open-expired-lapsed-and-closed-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish draft, reviewed, approved, issued, sent, delivered, received, effective, open, expired, lapsed and closed?", "kind": "lifecycle", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "draft-reviewed-approved-issued-sent-delivered-received-effective-open-expired-lapsed-and-closed-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on draft, reviewed, approved, issued, sent, delivered, received, effective, open, expired, lapsed and closed, for which purpose and under what authority?", "kind": "identity", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "draft-reviewed-approved-issued-sent-delivered-received-effective-open-expired-lapsed-and-closed-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify draft, reviewed, approved, issued, sent, delivered, received, effective, open, expired, lapsed and closed?", "kind": "authority", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "draft-reviewed-approved-issued-sent-delivered-received-effective-open-expired-lapsed-and-closed-data", "name": "Draft, reviewed, approved, issued, sent, delivered, received, effective, open, expired, lapsed and closed data", "description": "Typed offer or quotation data for draft, reviewed, approved, issued, sent, delivered, received, effective, open, expired, lapsed and closed, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-015" ] } ], "artifacts": [ { "id": "draft-reviewed-approved-issued-sent-delivered-received-effective-open-expired-lapsed-and-closed-record", "name": "Draft, reviewed, approved, issued, sent, delivered, received, effective, open, expired, lapsed and closed record", "description": "Immutable or successor-versioned proposal evidence for draft, reviewed, approved, issued, sent, delivered, received, effective, open, expired, lapsed and closed.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for draft-reviewed-approved-issued-sent-delivered-received-effective-open-expired-lapsed-and-closed; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "issue-effective-from-valid-until-delivery-window-response-deadline-expiry-observation-ingestion-and-knowledge-time", "name": "Issue, effective-from, valid-until, delivery-window, response deadline, expiry, observation, ingestion and knowledge time", "description": "Records issue, effective-from, valid-until, delivery-window, response deadline, expiry, observation, ingestion and knowledge time as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-015" ], "questions": [ { "id": "issue-effective-from-valid-until-delivery-window-response-deadline-expiry-observation-ingestion-and-knowledge-time-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish issue, effective-from, valid-until, delivery-window, response deadline, expiry, observation, ingestion and knowledge time?", "kind": "temporal", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "issue-effective-from-valid-until-delivery-window-response-deadline-expiry-observation-ingestion-and-knowledge-time-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on issue, effective-from, valid-until, delivery-window, response deadline, expiry, observation, ingestion and knowledge time, for which purpose and under what authority?", "kind": "classification", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "issue-effective-from-valid-until-delivery-window-response-deadline-expiry-observation-ingestion-and-knowledge-time-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify issue, effective-from, valid-until, delivery-window, response deadline, expiry, observation, ingestion and knowledge time?", "kind": "requirement", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "issue-effective-from-valid-until-delivery-window-response-deadline-expiry-observation-ingestion-and-knowledge-time-data", "name": "Issue, effective-from, valid-until, delivery-window, response deadline, expiry, observation, ingestion and knowledge time data", "description": "Typed offer or quotation data for issue, effective-from, valid-until, delivery-window, response deadline, expiry, observation, ingestion and knowledge time, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-015" ] } ], "artifacts": [ { "id": "issue-effective-from-valid-until-delivery-window-response-deadline-expiry-observation-ingestion-and-knowledge-time-record", "name": "Issue, effective-from, valid-until, delivery-window, response deadline, expiry, observation, ingestion and knowledge time record", "description": "Immutable or successor-versioned proposal evidence for issue, effective-from, valid-until, delivery-window, response deadline, expiry, observation, ingestion and knowledge time.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for issue-effective-from-valid-until-delivery-window-response-deadline-expiry-observation-ingestion-and-knowledge-time; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "withdrawal-revocation-rejection-counteroffer-acceptance-and-amendment", "name": "Withdrawal, revocation, rejection, counter-offer, acceptance and amendment", "description": "Groups source-qualified proposal context for withdrawal, revocation, rejection, counter-offer, acceptance and amendment.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013", "SRC-015" ], "findings": [ { "id": "withdrawal-revocation-rejection-counteroffer-acceptance-conduct-silence-and-response-evidence", "name": "Withdrawal, revocation, rejection, counter-offer, acceptance, conduct, silence and response evidence", "description": "Records withdrawal, revocation, rejection, counter-offer, acceptance, conduct, silence and response evidence as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013", "SRC-015" ], "questions": [ { "id": "withdrawal-revocation-rejection-counteroffer-acceptance-conduct-silence-and-response-evidence-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish withdrawal, revocation, rejection, counter-offer, acceptance, conduct, silence and response evidence?", "kind": "event", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "withdrawal-revocation-rejection-counteroffer-acceptance-conduct-silence-and-response-evidence-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on withdrawal, revocation, rejection, counter-offer, acceptance, conduct, silence and response evidence, for which purpose and under what authority?", "kind": "composition", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "withdrawal-revocation-rejection-counteroffer-acceptance-conduct-silence-and-response-evidence-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify withdrawal, revocation, rejection, counter-offer, acceptance, conduct, silence and response evidence?", "kind": "constraint", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "withdrawal-revocation-rejection-counteroffer-acceptance-conduct-silence-and-response-evidence-data", "name": "Withdrawal, revocation, rejection, counter-offer, acceptance, conduct, silence and response evidence data", "description": "Typed offer or quotation data for withdrawal, revocation, rejection, counter-offer, acceptance, conduct, silence and response evidence, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013", "SRC-015" ] } ], "artifacts": [ { "id": "withdrawal-revocation-rejection-counteroffer-acceptance-conduct-silence-and-response-evidence-record", "name": "Withdrawal, revocation, rejection, counter-offer, acceptance, conduct, silence and response evidence record", "description": "Immutable or successor-versioned proposal evidence for withdrawal, revocation, rejection, counter-offer, acceptance, conduct, silence and response evidence.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for withdrawal-revocation-rejection-counteroffer-acceptance-conduct-silence-and-response-evidence; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "amendment-revision-renewal-extension-supersession-correction-version-lineage-and-comparison", "name": "Amendment, revision, renewal, extension, supersession, correction, version lineage and comparison", "description": "Records amendment, revision, renewal, extension, supersession, correction, version lineage and comparison as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013", "SRC-015" ], "questions": [ { "id": "amendment-revision-renewal-extension-supersession-correction-version-lineage-and-comparison-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish amendment, revision, renewal, extension, supersession, correction, version lineage and comparison?", "kind": "lifecycle", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "amendment-revision-renewal-extension-supersession-correction-version-lineage-and-comparison-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on amendment, revision, renewal, extension, supersession, correction, version lineage and comparison, for which purpose and under what authority?", "kind": "relationship", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "amendment-revision-renewal-extension-supersession-correction-version-lineage-and-comparison-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify amendment, revision, renewal, extension, supersession, correction, version lineage and comparison?", "kind": "process", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "amendment-revision-renewal-extension-supersession-correction-version-lineage-and-comparison-data", "name": "Amendment, revision, renewal, extension, supersession, correction, version lineage and comparison data", "description": "Typed offer or quotation data for amendment, revision, renewal, extension, supersession, correction, version lineage and comparison, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013", "SRC-015" ] } ], "artifacts": [ { "id": "amendment-revision-renewal-extension-supersession-correction-version-lineage-and-comparison-record", "name": "Amendment, revision, renewal, extension, supersession, correction, version lineage and comparison record", "description": "Immutable or successor-versioned proposal evidence for amendment, revision, renewal, extension, supersession, correction, version lineage and comparison.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for amendment-revision-renewal-extension-supersession-correction-version-lineage-and-comparison; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-validation-and-interoperability", "name": "Governance, validation and interoperability", "description": "Groups governed offer and quotation context for governance, validation and interoperability.", "rationale": "Preserve provenance, authority, quality and loss-aware representations.", "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" ], "layers": [ { "id": "source-approval-provenance-access-and-retention", "name": "Source, approval, provenance, access and retention", "description": "Groups source-qualified proposal context for source, approval, provenance, access and retention.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-013", "SRC-014", "SRC-015" ], "findings": [ { "id": "catalogue-price-list-cost-input-calculation-rule-approver-source-system-derivation-and-confidence", "name": "Catalogue, price list, cost input, calculation rule, approver, source system, derivation and confidence", "description": "Records catalogue, price list, cost input, calculation rule, approver, source system, derivation and confidence as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-013", "SRC-014", "SRC-015" ], "questions": [ { "id": "catalogue-price-list-cost-input-calculation-rule-approver-source-system-derivation-and-confidence-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish catalogue, price list, cost input, calculation rule, approver, source system, derivation and confidence?", "kind": "provenance", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "catalogue-price-list-cost-input-calculation-rule-approver-source-system-derivation-and-confidence-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on catalogue, price list, cost input, calculation rule, approver, source system, derivation and confidence, for which purpose and under what authority?", "kind": "state", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "catalogue-price-list-cost-input-calculation-rule-approver-source-system-derivation-and-confidence-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify catalogue, price list, cost input, calculation rule, approver, source system, derivation and confidence?", "kind": "event", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "catalogue-price-list-cost-input-calculation-rule-approver-source-system-derivation-and-confidence-data", "name": "Catalogue, price list, cost input, calculation rule, approver, source system, derivation and confidence data", "description": "Typed offer or quotation data for catalogue, price list, cost input, calculation rule, approver, source system, derivation and confidence, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-013", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "catalogue-price-list-cost-input-calculation-rule-approver-source-system-derivation-and-confidence-record", "name": "Catalogue, price list, cost input, calculation rule, approver, source system, derivation and confidence record", "description": "Immutable or successor-versioned proposal evidence for catalogue, price list, cost input, calculation rule, approver, source system, derivation and confidence.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for catalogue-price-list-cost-input-calculation-rule-approver-source-system-derivation-and-confidence; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-013", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "confidentiality-access-purpose-privacy-disclosure-retention-legal-hold-tombstone-and-audit", "name": "Confidentiality, access, purpose, privacy, disclosure, retention, legal hold, tombstone and audit", "description": "Records confidentiality, access, purpose, privacy, disclosure, retention, legal hold, tombstone and audit as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations remain independently identifiable.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-013", "SRC-014", "SRC-015" ], "questions": [ { "id": "confidentiality-access-purpose-privacy-disclosure-retention-legal-hold-tombstone-and-audit-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish confidentiality, access, purpose, privacy, disclosure, retention, legal hold, tombstone and audit?", "kind": "privacy", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "confidentiality-access-purpose-privacy-disclosure-retention-legal-hold-tombstone-and-audit-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on confidentiality, access, purpose, privacy, disclosure, retention, legal hold, tombstone and audit, for which purpose and under what authority?", "kind": "lifecycle", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "confidentiality-access-purpose-privacy-disclosure-retention-legal-hold-tombstone-and-audit-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify confidentiality, access, purpose, privacy, disclosure, retention, legal hold, tombstone and audit?", "kind": "measurement", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "confidentiality-access-purpose-privacy-disclosure-retention-legal-hold-tombstone-and-audit-data", "name": "Confidentiality, access, purpose, privacy, disclosure, retention, legal hold, tombstone and audit data", "description": "Typed offer or quotation data for confidentiality, access, purpose, privacy, disclosure, retention, legal hold, tombstone and audit, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-013", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "confidentiality-access-purpose-privacy-disclosure-retention-legal-hold-tombstone-and-audit-record", "name": "Confidentiality, access, purpose, privacy, disclosure, retention, legal hold, tombstone and audit record", "description": "Immutable or successor-versioned proposal evidence for confidentiality, access, purpose, privacy, disclosure, retention, legal hold, tombstone and audit.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for confidentiality-access-purpose-privacy-disclosure-retention-legal-hold-tombstone-and-audit; title, date, amount, filename or digest never identifies an offer or quote alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-013", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "validation-projection-mapping-and-conformance", "name": "Validation, projection, mapping and conformance", "description": "Groups source-qualified proposal context for validation, projection, mapping and conformance.", "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" ], "findings": [ { "id": "identity-cardinality-arithmetic-total-tax-date-eligibility-authority-and-jurisdiction-validation", "name": "Identity, cardinality, arithmetic, total, tax, date, eligibility, authority and jurisdiction validation", "description": "Records identity, cardinality, arithmetic, total, tax, date, eligibility, authority and jurisdiction validation as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations 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" ], "questions": [ { "id": "identity-cardinality-arithmetic-total-tax-date-eligibility-authority-and-jurisdiction-validation-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish identity, cardinality, arithmetic, total, tax, date, eligibility, authority and jurisdiction validation?", "kind": "validation", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "identity-cardinality-arithmetic-total-tax-date-eligibility-authority-and-jurisdiction-validation-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on identity, cardinality, arithmetic, total, tax, date, eligibility, authority and jurisdiction validation, for which purpose and under what authority?", "kind": "temporal", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "identity-cardinality-arithmetic-total-tax-date-eligibility-authority-and-jurisdiction-validation-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify identity, cardinality, arithmetic, total, tax, date, eligibility, authority and jurisdiction validation?", "kind": "evidence", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "identity-cardinality-arithmetic-total-tax-date-eligibility-authority-and-jurisdiction-validation-data", "name": "Identity, cardinality, arithmetic, total, tax, date, eligibility, authority and jurisdiction validation data", "description": "Typed offer or quotation data for identity, cardinality, arithmetic, total, tax, date, eligibility, authority and jurisdiction validation, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "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" ] } ], "artifacts": [ { "id": "identity-cardinality-arithmetic-total-tax-date-eligibility-authority-and-jurisdiction-validation-record", "name": "Identity, cardinality, arithmetic, total, tax, date, eligibility, authority and jurisdiction validation record", "description": "Immutable or successor-versioned proposal evidence for identity, cardinality, arithmetic, total, tax, date, eligibility, authority and jurisdiction validation.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for identity-cardinality-arithmetic-total-tax-date-eligibility-authority-and-jurisdiction-validation; title, date, amount, filename or digest never identifies an offer or quote 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" ] } ], "inline_only_rationale": null }, { "id": "human-pdf-html-json-yaml-api-ubl-schemaorg-gs1-odrl-prov-and-loss-declaring-projection", "name": "Human, PDF, HTML, JSON, YAML, API, UBL, schema.org, GS1, ODRL, PROV and loss-declaring projection", "description": "Records human, pdf, html, json, yaml, api, ubl, schema.org, gs1, odrl, prov and loss-declaring projection as source-qualified proposal context while parties, product and service masters, negotiation, request, tender, contract, order, invoice, payment, fulfilment, response events and legal formation determinations 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" ], "questions": [ { "id": "human-pdf-html-json-yaml-api-ubl-schemaorg-gs1-odrl-prov-and-loss-declaring-projection-q01", "text": "What stable proposal, version, line, party, subject, term and external-master identities plus explicit profile and unknown state establish human, pdf, html, json, yaml, api, ubl, schema.org, gs1, odrl, prov and loss-declaring projection?", "kind": "interoperability", "answer_data": [ "proposal, version, line, lot, party, subject, term and master identifiers", "offer, quotation, estimate or informational profile, jurisdiction, language and schema version", "unknown, omitted, estimated, conditional, disputed, expired and not-applicable states" ] }, { "id": "human-pdf-html-json-yaml-api-ubl-schemaorg-gs1-odrl-prov-and-loss-declaring-projection-q02", "text": "Who creates, owns, prices, asserts, reviews, approves, communicates, receives, responds to or may rely on human, pdf, html, json, yaml, api, ubl, schema.org, gs1, odrl, prov and loss-declaring projection, for which purpose and under what authority?", "kind": "provenance", "answer_data": [ "issuer, offeror, seller, offeree, buyer, customer, agent, approver, recipient and system", "purpose, mandate, pricing authority, governing rule, access, confidentiality and retention", "conflict, exception, segregation of duties, escalation and accountability" ] }, { "id": "human-pdf-html-json-yaml-api-ubl-schemaorg-gs1-odrl-prov-and-loss-declaring-projection-q03", "text": "Which issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times, sources and evidence qualify human, pdf, html, json, yaml, api, ubl, schema.org, gs1, odrl, prov and loss-declaring projection?", "kind": "quality", "answer_data": [ "distinct proposal, communication, response, fulfilment, observation and knowledge times", "source catalogue, price list, calculation, approval, message, evidence, quality and uncertainty", "amendment, successor, comparison, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "human-pdf-html-json-yaml-api-ubl-schemaorg-gs1-odrl-prov-and-loss-declaring-projection-data", "name": "Human, PDF, HTML, JSON, YAML, API, UBL, schema.org, GS1, ODRL, PROV and loss-declaring projection data", "description": "Typed offer or quotation data for human, pdf, html, json, yaml, api, ubl, schema.org, gs1, odrl, prov and loss-declaring projection, qualified by proposal version, profile, jurisdiction, party authority, time, uncertainty and provenance.", "value_kind": "collection", "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" ] } ], "artifacts": [ { "id": "human-pdf-html-json-yaml-api-ubl-schemaorg-gs1-odrl-prov-and-loss-declaring-projection-record", "name": "Human, PDF, HTML, JSON, YAML, API, UBL, schema.org, GS1, ODRL, PROV and loss-declaring projection record", "description": "Immutable or successor-versioned proposal evidence for human, pdf, html, json, yaml, api, ubl, schema.org, gs1, odrl, prov and loss-declaring projection.", "media_or_form": [ "logical proposal specification assertion", "proposal, line, pricing, terms, communication, response-reference, validation, approval or projection record" ], "serial": true, "identity_strategy": "Proposal ID plus independent version, line or term ID and artifact kind for human-pdf-html-json-yaml-api-ubl-schemaorg-gs1-odrl-prov-and-loss-declaring-projection; title, date, amount, filename or digest never identifies an offer or quote 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" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-proposal", "name": "Register an offer or quotation", "description": "Governed operation to register an offer or quotation without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "owner", "issuer", "purpose", "declared profile" ], "outputs": [ "stable proposal and version head" ], "preconditions": [ "namespace, identity, issuer authority and profile checks pass" ], "effects": [ "a draft proposal exists without legal-effect inference" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013" ] }, { "id": "classify-profile-and-jurisdiction", "name": "Classify profile and jurisdiction", "description": "Governed operation to classify profile and jurisdiction without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "proposal head", "intent and governing-context evidence" ], "outputs": [ "qualified offer, quotation, estimate or informational classification" ], "preconditions": [ "classification criteria, jurisdiction, governing rules and uncertainty are explicit" ], "effects": [ "classification remains revisable and does not determine enforceability" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "compose-subject-lines", "name": "Compose subject lines and dependencies", "description": "Governed operation to compose subject lines and dependencies without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "proposal version", "external product, service or right references", "quantities and constraints" ], "outputs": [ "versioned lines, lots, bundles, options and dependencies" ], "preconditions": [ "subject masters resolve and cardinality, unit, option and dependency checks pass" ], "effects": [ "external subject lifecycles remain authoritative" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-010" ] }, { "id": "calculate-and-bind-pricing", "name": "Calculate and bind pricing", "description": "Governed operation to calculate and bind pricing without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "proposal lines", "price inputs", "currency, quantity, tax, allowance and charge rules" ], "outputs": [ "source-qualified price components and totals" ], "preconditions": [ "formula versions, units, currencies, rounding, tax jurisdiction and approval policy pass" ], "effects": [ "calculation produces evidence and never silently approves or mutates an issued price" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ] }, { "id": "bind-commercial-and-fulfilment-terms", "name": "Bind commercial and fulfilment terms", "description": "Governed operation to bind commercial and fulfilment terms without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "proposal version", "delivery, payment, warranty, service-level and rights terms" ], "outputs": [ "qualified term bindings" ], "preconditions": [ "term sources, dependencies, responsibility, jurisdiction and exceptions are explicit" ], "effects": [ "contract, order and fulfilment remain external" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-012" ] }, { "id": "review-approve-and-issue-version", "name": "Review, approve and issue a version", "description": "Governed operation to review, approve and issue a version without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "proposal candidate", "validation evidence", "authorized decision" ], "outputs": [ "immutable issued version and communication instructions" ], "preconditions": [ "pricing, tax, legal, commercial, access and approval checks pass" ], "effects": [ "the model records but does not autonomously sign, dispatch or publish" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-013" ] }, { "id": "record-communication-and-response", "name": "Record communication and response events", "description": "Governed operation to record communication and response events without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "proposal version", "attributable sent, received, withdrawal, revocation, rejection, counter-offer or acceptance evidence" ], "outputs": [ "immutable event references and observed lifecycle assertions" ], "preconditions": [ "actor, authority, channel, receipt semantics, time, source and uncertainty are explicit" ], "effects": [ "no event or status automatically determines contract formation" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-013", "SRC-015" ] }, { "id": "validate-proposal", "name": "Validate an offer or quotation", "description": "Governed operation to validate an offer or quotation without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "proposal version", "rules and profile" ], "outputs": [ "validation findings and reconciliation evidence" ], "preconditions": [ "identity, totals, taxes, dates, eligibility, authority, lifecycle and projection checks execute" ], "effects": [ "errors are reported without autonomous legal or commercial action" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-014", "SRC-016" ] }, { "id": "amend-correct-or-supersede", "name": "Amend, correct or supersede", "description": "Governed operation to amend, correct or supersede without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "proposal head", "authorized change", "impact and recipient evidence" ], "outputs": [ "successor version, comparison and communication requirements" ], "preconditions": [ "reason, affected lines and terms, prior responses, validity, authority and retention checks pass" ], "effects": [ "prior issued versions remain resolvable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-013" ] }, { "id": "query-project-retain-and-audit", "name": "Query, project, retain and audit", "description": "Governed operation to query, project, retain and audit without autonomous pricing approval, tax determination, contract formation, acceptance, signature, dispatch, publication, access widening or records disposition.", "inputs": [ "proposal", "purpose-bound access", "target profile", "records policy" ], "outputs": [ "filtered view, loss-declaring projection, retention result or audit event" ], "preconditions": [ "purpose, authority, privacy, mapping, digest, lifecycle and legal-hold checks pass" ], "effects": [ "representations never replace the canonical proposal and disposition stays external" ], "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" ] } ], "composition": [ { "target": "WM-OBJ-003", "relation": "REFERENCE", "purpose": "Resolve generic object context without granting ownership, mutation or cascade authority.", "required": false, "source_refs": [ "SRC-004", "SRC-013" ] }, { "target": "Party, Product, Service, Right, Catalogue, Price List, RFQ, Negotiation, Tender, Contract, Order, Invoice, Payment, Fulfilment, Event and Records models", "relation": "REFERENCE", "purpose": "Resolve authoritative external identities, processes, events and evidence without duplicating their lifecycles.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-013" ] }, { "target": "CISG, UNIDROIT Principles, EU Consumer Rights, UBL 2.3, schema.org, GS1 Web Vocabulary, UN Recommendation 20, ISO 4217, ODRL 2.2, PROV-O, DQV, RFC 3339, JSON Schema 2020-12 and OpenAPI 3.1.1", "relation": "ALIGN", "purpose": "Project version-pinned legal, commerce, discovery, policy, provenance, quality, time, validation and API views with declared information 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" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension owner, namespace authority, accountable commercial owner and delegated pricing and legal authorities", "Authoritative Party, Product, Service, Catalogue, Price List, RFQ, Negotiation, Tender, Contract, Order, Invoice, Payment, Fulfilment, Event and Records registries", "Approved jurisdiction, tax, currency, unit, pricing, eligibility, delivery, payment, rights, privacy, retention and interoperability profiles", "Role, delegation, segregation-of-duties, review, approval, issue, communication, response, amendment and agent-operation policies" ], "namespace_guidance": "Mint proposal, version, line, lot, price-component, term, event-reference, validation and projection IDs; preserve all external master identifiers.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative proposal identifier, issuer namespace and version head, never by title, recipient, issue date, total, filename or digest alone.", "Keep offer or quote, party, product, service, catalogue, RFQ, negotiation, tender, contract, order, invoice, payment, fulfilment, response event and records independently identifiable." ], "patch_rules": [ "Extensions declare profile, jurisdiction, identity, party, subject, line, quantity, price, tax, term, lifecycle, access and interoperability effects.", "Issued versions are immutable; changes create linked successors with reason, affected terms, response impact, compatibility, migration and approval.", "Never silently change profile, issuer, recipient, subject, quantity, price, currency, tax, total, term, validity, authority, response or legal-effect qualifier." ], "compatibility_rules": [ "Ignore additive fields only when identity, version, profile, parties, subject, price, currency, taxes, terms, validity, authority, access and provenance survive.", "Every projection pins specification or vocabulary version and declares loss in line, pricing, tax, term, response, lifecycle and authority semantics." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for proposal, version, line, price component, term, event reference or artifact, qualified by issuer namespace and record kind.", "Governed globally resolvable proposal 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 issue, effective, receipt, validity, response, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times whenever they differ.", "serial_naming_rule": "Use {proposal-id}--{version-id}--{line-term-or-event-id}--{artifact-kind}--{revision-id}.", "integrity_rule": "Store digest, media type, record kind, proposal and version IDs, profile, issuer, actor, distinct event and knowledge times, confidentiality marking and provenance." }, "policies": [ "The proposal owns its commercial assertions and versions but not external parties, subjects, negotiations, requests, tenders, contracts, orders, invoices, payments, fulfilment, response events or legal determinations.", "Offer, quotation, estimate and informational proposal are explicit profiles; labels and statuses alone never establish legal effect.", "Issue, delivery, receipt, effectiveness, validity, response, expiry and formation determinations are separate assertions.", "Agents cannot autonomously approve pricing, determine tax or legal effect, accept, sign, dispatch, publish, widen access or dispose records without delegated authority." ], "crud": { "read": [ "Resolve proposal head, versions, profile, parties, subjects, lines, pricing, taxes, totals, terms, validity, events, evidence, access and projection loss under the permitted view." ], "create": [ "Bind identity, issuer, declared profile, purpose, recipient scope, jurisdiction, currency, source authority and initial lifecycle before commercial assertions are accepted." ], "update": [ "Append successor lines, prices, taxes, terms, approvals, communications, responses, corrections and lifecycle assertions with reason, authority, expected revision, event time and knowledge time." ], "delete": [ "Apply legal hold, commercial-record, consumer, tax, privacy and adopting-Dimension retention policy; withdraw or tombstone only the catalogue view without cascading to external masters, and let authoritative systems execute physical disposition." ] }, "roles": [ { "name": "Proposal owner", "responsibilities": [ "Own purpose, scope, profile, lifecycle, compatibility and accountable use." ] }, { "name": "Commercial and pricing owner", "responsibilities": [ "Own subjects, quantities, price inputs, formulas, discounts, charges, totals and approval evidence." ] }, { "name": "Tax and legal authority", "responsibilities": [ "Own jurisdictional tax treatment, legal profile, required disclosures, formation interpretation and limitations." ] }, { "name": "Sales or procurement operator", "responsibilities": [ "Own party, RFQ, communication, delivery, receipt, response and amendment coordination." ] }, { "name": "Reviewer and approving authority", "responsibilities": [ "Own validation, exceptions, segregation of duties and authorization to issue." ] }, { "name": "Access and records authority", "responsibilities": [ "Own confidentiality, privacy, disclosure, retention, legal hold and disposition policy." ] }, { "name": "Interoperability steward", "responsibilities": [ "Own UBL, schema.org, GS1, ODRL, PROV, JSON, API mappings, conformance evidence and declared loss." ] } ], "access": { "default_rule": "Deny draft, non-public, negotiated, personal, confidential, commercially sensitive, cost, margin, discount, tax, approval, recipient-specific or response data unless a purpose-bound policy permits the minimum necessary view.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Declared commercial, legal, tax, audit, dispute, regulatory or subject-rights access must cite authority, scope, purpose and time limit and must be logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, proposal and version, operation, authority, policy, RFC 3339 time, affected lines or terms, source revision and outcome without duplicating restricted commercial data." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension namespace, commercial, pricing, tax, legal, privacy, retention and agent policies.", "Read this proposal and linked party, subject, catalogue, RFQ, negotiation, contract, order, invoice, payment, fulfilment, event and records models before mutation." ] } }, "coverage": { "claim": "WM-ECO-021 covers one governed offer or quotation from identity, version, profile and participants through offered subjects, line composition, eligibility, prices, currencies, taxes, totals, commercial and fulfilment terms, validity, attributable response events, amendments, evidence, access, retention and loss-aware projections. Jurisdiction and sector profiles, legal-effect determinations and independent external review remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "classification and direct properties", "status": "covered", "notes": "Classification and direct properties is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Recognition and observation is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Capabilities and possible actions is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "composition", "status": "covered", "notes": "Composition is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "lifecycle", "status": "covered", "notes": "Lifecycle is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "relationships", "status": "covered", "notes": "Relationships is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "temporal", "status": "covered", "notes": "Temporal is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "spatial", "status": "not-applicable", "notes": "Spatial properties are not intrinsic; eligible region, delivery place, service location and jurisdiction remain referenced context." }, { "dimension": "provenance", "status": "covered", "notes": "Provenance is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Ownership and stewardship is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "validation and quality", "status": "covered", "notes": "Validation and quality is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "access and privacy", "status": "covered", "notes": "Access and privacy is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention and deletion is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "interoperability", "status": "covered", "notes": "Interoperability is explicit; jurisdiction, sector, legal-effect and external-review profiles remain held where applicable." }, { "dimension": "authority and ethics", "status": "covered", "notes": "Authority and ethics is explicit; jurisdiction, sector, legal-effect 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.", "The WM-OBJ-003 parent signal has no frozen approved relation and grants no cascade authority.", "Public procurement, securities, insurance, healthcare, utilities, travel, telecom, software subscription, construction and other sector profiles need separate rules.", "National contract, tax, consumer, electronic-signature, records and privacy rules require jurisdiction profiles and authorized legal review.", "Schema.org is a discovery vocabulary and does not establish legal effect or full transactional conformance." ], "conflicts": [ "Offer, quote, estimate, proposal, invitation, RFQ, tender, counter-offer, order and contract are related but not interchangeable.", "Issue, sending, delivery, receipt, effectiveness, availability, validity, acceptance and contract formation are distinct assertions.", "List, unit, net, estimated, ranged, recurring, usage, tax, charge, subtotal and payable amounts must not be collapsed.", "Silence, acknowledgement, click, conduct or technical status does not universally prove acceptance or enforceability." ], "regional_assumptions": [ "Offer formation, revocability, receipt, acceptance, tax, required disclosure, signature and retention depend on governing law, jurisdiction, party type and channel.", "CISG, UNIDROIT Principles and EU consumer rules are scoped profiles, not universal governing law." ], "adversarial_checks": [ "Reject a proposal that collapses into party, product, service, RFQ, negotiation, tender, contract, order, invoice, payment or fulfilment masters.", "Reject a price without amount or formula, currency, unit or quantity basis, tax and charge treatment, validity, source and approval provenance.", "Reject automatic contract-formation, acceptance, enforceability or tax conclusions from a label, click, acknowledgement or status.", "Reject silent mutation of an issued version or loss of prior recipient-visible terms and response evidence.", "Reject autonomous pricing approval, tax determination, acceptance, signature, dispatch, publication, access widening or records disposition.", "Reject a projection that hides profile, version, line dependencies, pricing components, taxes, terms, lifecycle, authority 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-with-profile-boundary", "rationale": "The root is a versioned pre-contract commercial proposal aggregate with explicit legal-offer, quotation, estimate and informational profiles. Parties, products, services, catalogues, RFQs, negotiations, tenders, contracts, orders, invoices, payments, fulfilment, response events, legal determinations and records remain external masters." }, "decisions": [ { "concept": "Offer, quotation, estimate and informational proposal", "disposition": "accepted-with-explicit-profile", "rationale": "The shared structure is useful, but declared intent, definiteness, governing rules and legal effect differ; no label alone determines an operative legal offer." }, { "concept": "WM-OBJ-003 parent signal", "disposition": "accepted-as-unapproved-reference", "rationale": "The registry parent signal has no frozen canonical relation and grants no ownership, mutation or cascade authority." }, { "concept": "Proposal and neighboring commercial masters", "disposition": "accepted-with-explicit-boundary", "rationale": "Party, subject, catalogue, price list, RFQ, negotiation, tender, contract, order, invoice, payment and fulfilment identities and lifecycles remain external." }, { "concept": "Line, lot, bundle, option and dependency semantics", "disposition": "accepted", "rationale": "Composition preserves stable line and term identities plus alternative, substitution, minimum, partial and all-or-none rules rather than flattening them into text." }, { "concept": "Price and total semantics", "disposition": "accepted", "rationale": "List, unit, base, net, fixed, estimated, ranged, tiered, recurring, usage, tax, allowance, charge, subtotal and payable values stay distinct with currency, unit, quantity basis, formula, validity and provenance." }, { "concept": "Communication, response and contract formation", "disposition": "accepted-with-authority-boundary", "rationale": "Sending, delivery, receipt, acknowledgement, withdrawal, revocation, rejection, counter-offer, acceptance evidence and formation determinations are separately attributable; no status automatically proves legal effect." }, { "concept": "Multiple temporal axes", "disposition": "accepted", "rationale": "Issue, effective, receipt, validity, response, delivery, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge times remain distinct and RFC 3339 timestamps require seconds and offset." }, { "concept": "Jurisdiction and consumer profile", "disposition": "accepted-with-profile-hold", "rationale": "CISG, UNIDROIT Principles and EU consumer requirements provide scoped reference profiles; national contract, tax, signature, privacy and records rules remain jurisdiction-qualified." }, { "concept": "Interoperability projections", "disposition": "accepted-with-loss-declaration", "rationale": "UBL, schema.org, GS1, ODRL, PROV, DQV, JSON Schema and OpenAPI expose different subsets and never replace canonical proposal semantics." }, { "concept": "Single-provider waiver and 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 audits the frozen validated result and comparison locally without tools or new research facts; assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-ECO-021 each timed out after 120 seconds; no external research result was admitted.", "Relation hold: WM-OBJ-003 is only a parent signal and no model relation is canonically approved for this aggregate.", "Boundary hold: offer or quote, party, product, service, catalogue, price list, RFQ, negotiation, tender, contract, order, invoice, payment, fulfilment, response event, legal determination and records must retain separate identities.", "Legal-effect hold: offer, quotation, estimate and informational profiles require explicit intent, governing rules and jurisdiction; no label, click, acknowledgement, conduct or status universally proves acceptance, formation or enforceability.", "Pricing hold: every amount requires type, currency, unit or quantity basis, inclusion and exclusion, tax and charge treatment, formula or source, validity, rounding, approval and uncertainty qualifiers.", "Temporal hold: issue, effective, receipt, validity, response, delivery, withdrawal, revocation, rejection, acceptance, expiry, observation, ingestion and knowledge time must never be silently collapsed; timestamps require seconds and timezone offset.", "Authority hold: pricing approval, tax determination, legal classification, acceptance, signature, dispatch, publication, access widening and disposition require delegated accountable authority.", "Jurisdiction hold: CISG, UNIDROIT Principles and EU consumer requirements are scoped profiles; national contract, tax, signature, privacy, records and sector rules require separate validation.", "Interoperability hold: every UBL, schema.org, GS1, UNECE, ISO 4217, ODRL, PROV, DQV, JSON Schema and OpenAPI projection requires version pins, conformance evidence and information-loss declarations.", "Privacy hold: recipient-specific prices, discounts, cost, margin, tax, negotiation, approval, contact, response and commercially sensitive 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 approve the WM-OBJ-003 relation and register Party, Product, Service, Catalogue, Price List, RFQ, Negotiation, Tender, Contract, Order, Invoice, Payment, Fulfilment, Event and Records edges.", "Create public procurement, securities, insurance, healthcare, utilities, travel, telecom, software subscription, construction and jurisdiction-specific profiles.", "Conformance-test lines, dependencies, quantities, units, prices, taxes, totals, validity, amendments and projections against concrete UBL and commerce examples.", "Validate organization-specific pricing, discount, tax, approval, signing, dispatch, publication, access, retention and disposition policies.", "Obtain authorized legal and tax review before making jurisdiction-specific formation, enforceability, disclosure or tax claims.", "Obtain independent external research review before promoting beyond reviewable-draft assurance." ] }, "statistics": { "sources": 17, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }