# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T14:52:17Z", "synthesisSha256": "d2d5c2dd160025100ae7af5e20f569d8182dde0420b62981d469bfaec51f5d61", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ECO-022", "registryId": "vr.wm-eco-022", "name": "Subscription", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ECO.SUB" ], "tags": [ "subscription", "soc.eco.sub" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-eco-022-subscription/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/publications/wm-eco-022-subscription", "model": { "registry_id": "vr.wm-eco-022", "model_id": "WM-ECO-022", "name": "Subscription", "entry_kind": "aggregate", "purpose": "Represent one governed recurring commercial relationship so agents can understand who subscribes to which plan, which items and entitlements recur, how billing and renewal operate, what usage and service evidence exists and how cancellation progresses without confusing the subscription with its contract, invoices, payments or service instances.", "scope_statement": "Owns subscription identity, versions, profile and lifecycle; provider, subscriber, payer, beneficiary and administrator references; external contract, account, order, catalogue, offering, service and entitlement bindings; plan versions, items, add-ons, bundles, seats, assignments and dependencies; permissions, limits, usage allowances, rollover and overage references; recurring, one-time, seat, usage and tiered price rules; currencies, taxes, discounts, credits, proration and refunds; billing anchors, recurrence, periods, invoice and payment references; trial, activation, service, pause, suspension, grace and reactivation observations; term, renewal, notice, consent, cancellation and termination assertions; usage, quality, support, provenance, validation, privacy, retention and loss-aware projections. External agreement, party, product, entitlement, order, invoice, payment, usage, service, support and records masters remain authoritative.", "in_scope": [ "Subscription identity, versions, profiles, participants, plan bindings, items, seats, beneficiaries, entitlements, usage allowances and constraints", "Recurring economics, billing and renewal schedules, invoice and payment references, service and usage evidence, lifecycle, notices, cancellation, validation, access, retention and projections" ], "out_of_scope": [ "Owning Contract, Party, Account, Product, Service Offering, Entitlement, Credential, Order, Invoice, Payment Method, Payment Transaction, Usage Event, Meter Reading, Service Instance, Support Case or Records masters", "Treating active, paid, renewed or cancelled status as universal proof of legal validity, service delivery, entitlement, conformity, termination completion or data deletion", "Autonomous contract formation, charging, invoicing, plan or price change, entitlement grant or revocation, renewal, cancellation, termination, disclosure or physical records disposition" ], "boundary_notes": [ { "neighbor": "WM-ECO-006 Commercial Contract", "distinction": "The unfrozen parent agreement establishes obligations and legal terms. The subscription is a recurring operational aggregate that references but does not replace the contract.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "neighbor": "Plan, product, service and entitlement", "distinction": "The plan or offering defines reusable terms, products and services have independent instances, and entitlements are separate grants. The subscription binds versions and observes state.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-011" ] }, { "neighbor": "Invoice, payment mandate, payment and usage", "distinction": "Billing schedules predict or request recurring economics, invoices assert amounts due, payments settle, and usage observations meter consumption; none is the subscription identity.", "source_refs": [ "SRC-004", "SRC-007", "SRC-008", "SRC-012" ] }, { "neighbor": "Service provisioning and availability", "distinction": "Activation, entitlement, provisioning and availability are separate processes or observations; active subscription status does not prove their success.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-016" ] }, { "neighbor": "TM Forum, schema.org, ODRL, EPC, RFC, PROV, DQV and OpenAPI", "distinction": "Each representation has a distinct scope; every mapping is version-pinned and loss-declaring.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ] }, "sources": [ { "id": "SRC-001", "title": "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:47:00Z", "relevance": "Defines subscription billing-period price disclosure, contract duration, renewal, termination, payment, performance, withdrawal and durable-medium information in consumer scope." }, { "id": "SRC-002", "title": "Directive EU 2019/770 on digital content and digital services", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2019/770", "version_or_date": "Directive 20 May 2019; national transposition and amendments remain profile-specific", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines continuous digital supply, conformity, modification, price reduction, termination, reimbursement, user content and personal-data consequences." }, { "id": "SRC-003", "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:47:00Z", "relevance": "Provides cross-border reference concepts for agreement formation, authority, interpretation, performance, hardship, termination and long-term contracts." }, { "id": "SRC-004", "title": "Open API Directory", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis", "version_or_date": "Directory accessed 6 September 2026", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Registers product catalogue, product inventory, ordering, usage, billing, payment, agreement, privacy and dunning APIs used as separate subscription neighbors." }, { "id": "SRC-005", "title": "Product Inventory Management API TMF637", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis/product-inventory-management-api-TMF637/v4.0", "version_or_date": "TMF637 v4.0 page updated 7 November 2024", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Represents installed product instances and relationships, a useful projection for subscription products while retaining product identity." }, { "id": "SRC-006", "title": "Product Catalog Management API User Guide TMF620 v5.0.0", "organization": "TM Forum", "url": "https://www.tmforum.org/resources/specification/tmf620-product-catalog-management-api-user-guide-v5-0-0/", "version_or_date": "Version 5.0.0, team approved 29 September 2023", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines product offering, specification, catalogue and pricing lifecycle that subscription instances reference rather than own." }, { "id": "SRC-007", "title": "Customer Bill Management API TMF678 v5.0", "organization": "TM Forum", "url": "https://www.tmforum.org/open-digital-architecture/open-apis/customer-bill-management-api-TMF678/v5.0", "version_or_date": "Stable v5.0, release update 8 May 2026", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Separates customer bills and applied billing rates from the subscription agreement and recurring schedule." }, { "id": "SRC-008", "title": "Usage Consumption Management API TMF677 v4.0.0", "organization": "TM Forum", "url": "https://www.tmforum.org/resources/standard/tmf677-usage-consumption-management-api-user-guide-v4-0-0/", "version_or_date": "Forum Approved 19 November 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines used, remaining, global and out-of-bucket consumption observations that subscription allowance views reference." }, { "id": "SRC-009", "title": "UnitPriceSpecification", "organization": "Schema.org Community Group", "url": "https://schema.org/UnitPriceSpecification", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines billing duration, billing increment, billing start, price components and reference quantity for subscription and payment-plan discovery." }, { "id": "SRC-010", "title": "Offer", "organization": "Schema.org Community Group", "url": "https://schema.org/Offer", "version_or_date": "Schema.org V30.0, 19 March 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines seller, offered item, price specification, eligibility, availability and validity for public offer projections." }, { "id": "SRC-011", "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:47:00Z", "relevance": "Defines Offer and Agreement policies, assets, parties, permissions, prohibitions, duties and constraints for entitlement projections." }, { "id": "SRC-012", "title": "SEPA Direct Debit Core Rulebook and implementation guidelines", "organization": "European Payments Council", "url": "https://www.europeanpaymentscouncil.eu/what-we-do/epc-payment-schemes/sepa-direct-debit/sepa-direct-debit-core-rulebook-and-implementation", "version_or_date": "2025 SDD Core Rulebook version 1.1, current through 21 November 2027", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines mandate and direct-debit scheme context for recurring euro payments without making the subscription a payment mandate or transaction." }, { "id": "SRC-013", "title": "Internet Calendaring and Scheduling Core Object Specification", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/info/rfc5545/", "version_or_date": "RFC 5545 September 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines recurrence rules, start, duration, count, until, timezone and exception semantics for schedule projections." }, { "id": "SRC-014", "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:47:00Z", "relevance": "Defines interoperable timestamps with seconds and explicit UTC relationship." }, { "id": "SRC-015", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines entity, activity, agent, attribution, generation, derivation, revision and qualified provenance." }, { "id": "SRC-016", "title": "Data on the Web Best Practices: Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines quality dimensions, metrics, measurements, annotations, policies and certificates." }, { "id": "SRC-017", "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:47:00Z", "relevance": "Provides maintained alphabetic and numeric currency identifiers and minor units for recurring prices, invoices, credits and refunds." }, { "id": "SRC-018", "title": "OpenAPI Specification 3.1.1", "organization": "OpenAPI Initiative", "url": "https://spec.openapis.org/oas/v3.1.1.html", "version_or_date": "Version 3.1.1, 24 October 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T14:47:00Z", "relevance": "Defines HTTP API operations, schemas, responses, security and reusable components for subscription service projections." } ], "structure": { "bundles": [ { "id": "identity-contract-participants-and-plan", "name": "Identity, contract, participants and plan", "description": "Groups governed subscription context for identity, contract, participants and plan.", "rationale": "Identify the recurring relationship without absorbing its agreement, parties or offering.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-015" ], "layers": [ { "id": "subscription-root-identity-version-profile-and-status", "name": "Subscription root identity, version, profile and status", "description": "Groups source-qualified subscription context for subscription root identity, version, profile and status.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-015" ], "findings": [ { "id": "subscription-id-version-head-name-purpose-language-status-and-master-system", "name": "Subscription ID, version, head, name, purpose, language, status and master system", "description": "Records subscription id, version, head, name, purpose, language, status and master system as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-015" ], "questions": [ { "id": "subscription-id-version-head-name-purpose-language-status-and-master-system-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish subscription id, version, head, name, purpose, language, status and master system?", "kind": "identity", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "subscription-id-version-head-name-purpose-language-status-and-master-system-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on subscription id, version, head, name, purpose, language, status and master system, for which purpose and under what authority?", "kind": "authority", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "subscription-id-version-head-name-purpose-language-status-and-master-system-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify subscription id, version, head, name, purpose, language, status and master system?", "kind": "security", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "subscription-id-version-head-name-purpose-language-status-and-master-system-data", "name": "Subscription ID, version, head, name, purpose, language, status and master system data", "description": "Typed subscription data for subscription id, version, head, name, purpose, language, status and master system, qualified by version, plan, party authority, recurrence, 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-015" ] } ], "artifacts": [ { "id": "subscription-id-version-head-name-purpose-language-status-and-master-system-record", "name": "Subscription ID, version, head, name, purpose, language, status and master system record", "description": "Immutable or successor-versioned subscription evidence for subscription id, version, head, name, purpose, language, status and master system.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for subscription-id-version-head-name-purpose-language-status-and-master-system; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile", "name": "Fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile", "description": "Records fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-015" ], "questions": [ { "id": "fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile?", "kind": "classification", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile, for which purpose and under what authority?", "kind": "requirement", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile?", "kind": "privacy", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile-data", "name": "Fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile data", "description": "Typed subscription data for fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile, qualified by version, plan, party authority, recurrence, 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-015" ] } ], "artifacts": [ { "id": "fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile-record", "name": "Fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile record", "description": "Immutable or successor-versioned subscription evidence for fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "agreement-parties-roles-and-external-masters", "name": "Agreement, parties, roles and external masters", "description": "Groups source-qualified subscription context for agreement, parties, roles and external masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-015" ], "findings": [ { "id": "provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role", "name": "Provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role", "description": "Records provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-015" ], "questions": [ { "id": "provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role?", "kind": "relationship", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role, for which purpose and under what authority?", "kind": "constraint", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role?", "kind": "retention", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role-data", "name": "Provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role data", "description": "Typed subscription data for provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role, qualified by version, plan, party authority, recurrence, 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-015" ] } ], "artifacts": [ { "id": "provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role-record", "name": "Provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role record", "description": "Immutable or successor-versioned subscription evidence for provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding", "name": "Contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding", "description": "Records contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-015" ], "questions": [ { "id": "contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding?", "kind": "relationship", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding, for which purpose and under what authority?", "kind": "process", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding?", "kind": "access", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding-data", "name": "Contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding data", "description": "Typed subscription data for contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding, qualified by version, plan, party authority, recurrence, 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-015" ] } ], "artifacts": [ { "id": "contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding-record", "name": "Contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding record", "description": "Immutable or successor-versioned subscription evidence for contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "plan-composition-entitlements-and-usage", "name": "Plan composition, entitlements and usage", "description": "Groups governed subscription context for plan composition, entitlements and usage.", "rationale": "Represent what recurs and what may be used while preserving product, entitlement and usage masters.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "layers": [ { "id": "plan-version-items-addons-bundles-seats-and-dependencies", "name": "Plan version, items, add-ons, bundles, seats and dependencies", "description": "Groups source-qualified subscription context for plan version, items, add-ons, bundles, seats and dependencies.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011" ], "findings": [ { "id": "plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period", "name": "Plan, offering version, SKU, product, service, item, add-on, bundle, option and effective period", "description": "Records plan, offering version, sku, product, service, item, add-on, bundle, option and effective period as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish plan, offering version, sku, product, service, item, add-on, bundle, option and effective period?", "kind": "composition", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on plan, offering version, sku, product, service, item, add-on, bundle, option and effective period, for which purpose and under what authority?", "kind": "event", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify plan, offering version, sku, product, service, item, add-on, bundle, option and effective period?", "kind": "exception", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period-data", "name": "Plan, offering version, SKU, product, service, item, add-on, bundle, option and effective period data", "description": "Typed subscription data for plan, offering version, sku, product, service, item, add-on, bundle, option and effective period, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period-record", "name": "Plan, offering version, SKU, product, service, item, add-on, bundle, option and effective period record", "description": "Immutable or successor-versioned subscription evidence for plan, offering version, sku, product, service, item, add-on, bundle, option and effective period.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution", "name": "Seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution", "description": "Records seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution?", "kind": "composition", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution, for which purpose and under what authority?", "kind": "measurement", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution?", "kind": "interoperability", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution-data", "name": "Seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution data", "description": "Typed subscription data for seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution-record", "name": "Seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution record", "description": "Immutable or successor-versioned subscription evidence for seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "entitlement-feature-permission-allowance-and-limit", "name": "Entitlement, feature, permission, allowance and limit", "description": "Groups source-qualified subscription context for entitlement, feature, permission, allowance and limit.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "findings": [ { "id": "entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference", "name": "Entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference", "description": "Records entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference?", "kind": "access", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference, for which purpose and under what authority?", "kind": "evidence", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference?", "kind": "decision", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference-data", "name": "Entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference data", "description": "Typed subscription data for entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference-record", "name": "Entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference record", "description": "Immutable or successor-versioned subscription evidence for entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source", "name": "Allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source", "description": "Records allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source?", "kind": "measurement", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source, for which purpose and under what authority?", "kind": "quality", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source?", "kind": "identity", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source-data", "name": "Allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source data", "description": "Typed subscription data for allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source-record", "name": "Allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source record", "description": "Immutable or successor-versioned subscription evidence for allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-005", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "economics-billing-invoice-and-payment", "name": "Economics, billing, invoice and payment", "description": "Groups governed subscription context for economics, billing, invoice and payment.", "rationale": "Preserve recurring economic rules while invoices and payments retain independent identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-016", "SRC-017" ], "layers": [ { "id": "recurring-pricing-discount-tax-credit-and-proration", "name": "Recurring pricing, discount, tax, credit and proration", "description": "Groups source-qualified subscription context for recurring pricing, discount, tax, credit and proration.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017" ], "findings": [ { "id": "recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price", "name": "Recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price", "description": "Records recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017" ], "questions": [ { "id": "recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price?", "kind": "measurement", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price, for which purpose and under what authority?", "kind": "validation", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price?", "kind": "classification", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price-data", "name": "Recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price data", "description": "Typed subscription data for recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017" ] } ], "artifacts": [ { "id": "recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price-record", "name": "Recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price record", "description": "Immutable or successor-versioned subscription evidence for recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy", "name": "Currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy", "description": "Records currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017" ], "questions": [ { "id": "currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy?", "kind": "requirement", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy, for which purpose and under what authority?", "kind": "security", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy?", "kind": "composition", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy-data", "name": "Currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy data", "description": "Typed subscription data for currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017" ] } ], "artifacts": [ { "id": "currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy-record", "name": "Currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy record", "description": "Immutable or successor-versioned subscription evidence for currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-016", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "billing-cycle-invoice-payment-mandate-and-dunning", "name": "Billing cycle, invoice, payment mandate and dunning", "description": "Groups source-qualified subscription context for billing cycle, invoice, payment mandate and dunning.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-012", "SRC-013", "SRC-014", "SRC-017" ], "findings": [ { "id": "billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule", "name": "Billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule", "description": "Records billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-012", "SRC-013", "SRC-014", "SRC-017" ], "questions": [ { "id": "billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule?", "kind": "temporal", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule, for which purpose and under what authority?", "kind": "privacy", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule?", "kind": "relationship", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule-data", "name": "Billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule data", "description": "Typed subscription data for billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-012", "SRC-013", "SRC-014", "SRC-017" ] } ], "artifacts": [ { "id": "billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule-record", "name": "Billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule record", "description": "Immutable or successor-versioned subscription evidence for billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-012", "SRC-013", "SRC-014", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference", "name": "Payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference", "description": "Records payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-012", "SRC-013", "SRC-014", "SRC-017" ], "questions": [ { "id": "payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference?", "kind": "relationship", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference, for which purpose and under what authority?", "kind": "retention", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference?", "kind": "state", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference-data", "name": "Payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference data", "description": "Typed subscription data for payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-012", "SRC-013", "SRC-014", "SRC-017" ] } ], "artifacts": [ { "id": "payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference-record", "name": "Payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference record", "description": "Immutable or successor-versioned subscription evidence for payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-009", "SRC-012", "SRC-013", "SRC-014", "SRC-017" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "service-lifecycle-renewal-change-and-termination", "name": "Service lifecycle, renewal, change and termination", "description": "Groups governed subscription context for service lifecycle, renewal, change and termination.", "rationale": "Keep contract, entitlement, provisioning, billing and payment state axes separate.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-011", "SRC-013", "SRC-014", "SRC-015" ], "layers": [ { "id": "trial-activation-provisioning-service-pause-suspension-and-reactivation", "name": "Trial, activation, provisioning, service, pause, suspension and reactivation", "description": "Groups source-qualified subscription context for trial, activation, provisioning, service, pause, suspension and reactivation.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-011", "SRC-015" ], "findings": [ { "id": "signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification", "name": "Signup, trial, conversion, activation, entitlement, provisioning, service availability and verification", "description": "Records signup, trial, conversion, activation, entitlement, provisioning, service availability and verification as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-011", "SRC-015" ], "questions": [ { "id": "signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish signup, trial, conversion, activation, entitlement, provisioning, service availability and verification?", "kind": "lifecycle", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on signup, trial, conversion, activation, entitlement, provisioning, service availability and verification, for which purpose and under what authority?", "kind": "access", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify signup, trial, conversion, activation, entitlement, provisioning, service availability and verification?", "kind": "lifecycle", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification-data", "name": "Signup, trial, conversion, activation, entitlement, provisioning, service availability and verification data", "description": "Typed subscription data for signup, trial, conversion, activation, entitlement, provisioning, service availability and verification, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-011", "SRC-015" ] } ], "artifacts": [ { "id": "signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification-record", "name": "Signup, trial, conversion, activation, entitlement, provisioning, service availability and verification record", "description": "Immutable or successor-versioned subscription evidence for signup, trial, conversion, activation, entitlement, provisioning, service availability and verification.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-011", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason", "name": "Pause, suspension, grace, block, delinquency, remediation, reactivation and state reason", "description": "Records pause, suspension, grace, block, delinquency, remediation, reactivation and state reason as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-011", "SRC-015" ], "questions": [ { "id": "pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish pause, suspension, grace, block, delinquency, remediation, reactivation and state reason?", "kind": "state", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on pause, suspension, grace, block, delinquency, remediation, reactivation and state reason, for which purpose and under what authority?", "kind": "exception", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify pause, suspension, grace, block, delinquency, remediation, reactivation and state reason?", "kind": "temporal", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason-data", "name": "Pause, suspension, grace, block, delinquency, remediation, reactivation and state reason data", "description": "Typed subscription data for pause, suspension, grace, block, delinquency, remediation, reactivation and state reason, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-011", "SRC-015" ] } ], "artifacts": [ { "id": "pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason-record", "name": "Pause, suspension, grace, block, delinquency, remediation, reactivation and state reason record", "description": "Immutable or successor-versioned subscription evidence for pause, suspension, grace, block, delinquency, remediation, reactivation and state reason.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-011", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "term-renewal-notice-cancellation-and-post-termination", "name": "Term, renewal, notice, cancellation and post-termination", "description": "Groups source-qualified subscription context for term, renewal, notice, cancellation and post-termination.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-013", "SRC-014", "SRC-015" ], "findings": [ { "id": "term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off", "name": "Term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off", "description": "Records term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-013", "SRC-014", "SRC-015" ], "questions": [ { "id": "term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off?", "kind": "temporal", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off, for which purpose and under what authority?", "kind": "interoperability", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off?", "kind": "provenance", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off-data", "name": "Term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off data", "description": "Typed subscription data for term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-013", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off-record", "name": "Term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off record", "description": "Immutable or successor-versioned subscription evidence for term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-013", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right", "name": "Cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right", "description": "Records cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-013", "SRC-014", "SRC-015" ], "questions": [ { "id": "cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right?", "kind": "lifecycle", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right, for which purpose and under what authority?", "kind": "decision", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right?", "kind": "ownership", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right-data", "name": "Cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right data", "description": "Typed subscription data for cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-013", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right-record", "name": "Cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right record", "description": "Immutable or successor-versioned subscription evidence for cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-013", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "usage-quality-support-and-evidence", "name": "Usage, quality, support and evidence", "description": "Groups governed subscription context for usage, quality, support and evidence.", "rationale": "Qualify consumption and service evidence without inferring delivery or fitness from status.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "layers": [ { "id": "usage-measurement-balance-aggregation-and-dispute", "name": "Usage measurement, balance, aggregation and dispute", "description": "Groups source-qualified subscription context for usage measurement, balance, aggregation and dispute.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "findings": [ { "id": "usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence", "name": "Usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence", "description": "Records usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "questions": [ { "id": "usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence?", "kind": "provenance", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence, for which purpose and under what authority?", "kind": "identity", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence?", "kind": "authority", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence-data", "name": "Usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence data", "description": "Typed subscription data for usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence-record", "name": "Usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence record", "description": "Immutable or successor-versioned subscription evidence for usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation", "name": "Quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation", "description": "Records quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ], "questions": [ { "id": "quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation?", "kind": "quality", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation, for which purpose and under what authority?", "kind": "classification", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation?", "kind": "requirement", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation-data", "name": "Quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation data", "description": "Typed subscription data for quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation-record", "name": "Quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation record", "description": "Immutable or successor-versioned subscription evidence for quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "service-level-conformity-support-remedy-and-complaint", "name": "Service level, conformity, support, remedy and complaint", "description": "Groups source-qualified subscription context for service level, conformity, support, remedy and complaint.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-016" ], "findings": [ { "id": "sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence", "name": "SLA, availability, performance, maintenance, support, incident, breach, service credit and evidence", "description": "Records sla, availability, performance, maintenance, support, incident, breach, service credit and evidence as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-016" ], "questions": [ { "id": "sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish sla, availability, performance, maintenance, support, incident, breach, service credit and evidence?", "kind": "evidence", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on sla, availability, performance, maintenance, support, incident, breach, service credit and evidence, for which purpose and under what authority?", "kind": "composition", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify sla, availability, performance, maintenance, support, incident, breach, service credit and evidence?", "kind": "constraint", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence-data", "name": "SLA, availability, performance, maintenance, support, incident, breach, service credit and evidence data", "description": "Typed subscription data for sla, availability, performance, maintenance, support, incident, breach, service credit and evidence, qualified by version, plan, party authority, recurrence, 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-016" ] } ], "artifacts": [ { "id": "sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence-record", "name": "SLA, availability, performance, maintenance, support, incident, breach, service credit and evidence record", "description": "Immutable or successor-versioned subscription evidence for sla, availability, performance, maintenance, support, incident, breach, service credit and evidence.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference", "name": "Conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference", "description": "Records conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-016" ], "questions": [ { "id": "conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference?", "kind": "process", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference, for which purpose and under what authority?", "kind": "relationship", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference?", "kind": "process", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference-data", "name": "Conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference data", "description": "Typed subscription data for conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference, qualified by version, plan, party authority, recurrence, 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-016" ] } ], "artifacts": [ { "id": "conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference-record", "name": "Conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference record", "description": "Immutable or successor-versioned subscription evidence for conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-provenance-temporal-and-interoperability", "name": "Governance, provenance, temporal and interoperability", "description": "Groups governed subscription context for governance, provenance, temporal and interoperability.", "rationale": "Preserve authority, evidence, access, clocks and loss-aware projections.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "layers": [ { "id": "authority-source-provenance-access-privacy-and-retention", "name": "Authority, source, provenance, access, privacy and retention", "description": "Groups source-qualified subscription context for authority, source, provenance, access, privacy and retention.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-015", "SRC-016" ], "findings": [ { "id": "owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit", "name": "Owner, steward, approver, source system, plan, price, policy, derivation, revision and audit", "description": "Records owner, steward, approver, source system, plan, price, policy, derivation, revision and audit as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-015", "SRC-016" ], "questions": [ { "id": "owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish owner, steward, approver, source system, plan, price, policy, derivation, revision and audit?", "kind": "ownership", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on owner, steward, approver, source system, plan, price, policy, derivation, revision and audit, for which purpose and under what authority?", "kind": "state", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify owner, steward, approver, source system, plan, price, policy, derivation, revision and audit?", "kind": "event", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit-data", "name": "Owner, steward, approver, source system, plan, price, policy, derivation, revision and audit data", "description": "Typed subscription data for owner, steward, approver, source system, plan, price, policy, derivation, revision and audit, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit-record", "name": "Owner, steward, approver, source system, plan, price, policy, derivation, revision and audit record", "description": "Immutable or successor-versioned subscription evidence for owner, steward, approver, source system, plan, price, policy, derivation, revision and audit.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone", "name": "Purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone", "description": "Records purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-015", "SRC-016" ], "questions": [ { "id": "purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone?", "kind": "privacy", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone, for which purpose and under what authority?", "kind": "lifecycle", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone?", "kind": "measurement", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone-data", "name": "Purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone data", "description": "Typed subscription data for purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone, qualified by version, plan, party authority, recurrence, time, uncertainty and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone-record", "name": "Purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone record", "description": "Immutable or successor-versioned subscription evidence for purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "clocks-events-validation-and-projections", "name": "Clocks, events, validation and projections", "description": "Groups source-qualified subscription context for clocks, events, validation and projections.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "findings": [ { "id": "signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time", "name": "Signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time", "description": "Records signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time?", "kind": "temporal", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time, for which purpose and under what authority?", "kind": "temporal", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time?", "kind": "evidence", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time-data", "name": "Signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time data", "description": "Typed subscription data for signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time, qualified by version, plan, party authority, recurrence, 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", "SRC-018" ] } ], "artifacts": [ { "id": "signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time-record", "name": "Signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time record", "description": "Immutable or successor-versioned subscription evidence for signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation", "name": "Identity, state, recurrence, arithmetic, entitlement, privacy, TMF, schema.org, ODRL, EPC, PROV, API and loss validation", "description": "Records identity, state, recurrence, arithmetic, entitlement, privacy, tmf, schema.org, odrl, epc, prov, api and loss validation as source-qualified subscription context while agreement, party, product, service, entitlement, order, invoice, payment, usage, support and records masters remain independently identifiable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation-q01", "text": "What stable subscription, version, plan, item, party, entitlement, schedule and external-master identities plus explicit profile and unknown state establish identity, state, recurrence, arithmetic, entitlement, privacy, tmf, schema.org, odrl, epc, prov, api and loss validation?", "kind": "interoperability", "answer_data": [ "subscription, version, plan, item, party, entitlement, schedule and master identifiers", "fixed, evergreen, prepaid, postpaid, trial, seat, usage, consumer or enterprise profile and schema version", "unknown, pending, disputed, estimated, suspended, cancelled and not-applicable states" ] }, { "id": "identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation-q02", "text": "Who creates, owns, subscribes, pays, benefits, assigns, measures, bills, approves, changes, cancels or may rely on identity, state, recurrence, arithmetic, entitlement, privacy, tmf, schema.org, odrl, epc, prov, api and loss validation, for which purpose and under what authority?", "kind": "provenance", "answer_data": [ "provider, subscriber, customer, payer, beneficiary, administrator, approver, operator, processor and system", "purpose, agreement, mandate, consent, policy, access, confidentiality and retention", "conflict, exception, segregation of duties, notice, escalation and accountability" ] }, { "id": "identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation-q03", "text": "Which signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times, sources and evidence qualify identity, state, recurrence, arithmetic, entitlement, privacy, tmf, schema.org, odrl, epc, prov, api and loss validation?", "kind": "quality", "answer_data": [ "distinct agreement, entitlement, service, usage, billing, payment, lifecycle and knowledge times", "plan, catalogue, meter, bill, payment, approval, message, evidence, quality and uncertainty", "proration, correction, successor, dispute, legal hold, projection loss and audit" ] } ], "data_elements": [ { "id": "identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation-data", "name": "Identity, state, recurrence, arithmetic, entitlement, privacy, TMF, schema.org, ODRL, EPC, PROV, API and loss validation data", "description": "Typed subscription data for identity, state, recurrence, arithmetic, entitlement, privacy, tmf, schema.org, odrl, epc, prov, api and loss validation, qualified by version, plan, party authority, recurrence, 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", "SRC-018" ] } ], "artifacts": [ { "id": "identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation-record", "name": "Identity, state, recurrence, arithmetic, entitlement, privacy, TMF, schema.org, ODRL, EPC, PROV, API and loss validation record", "description": "Immutable or successor-versioned subscription evidence for identity, state, recurrence, arithmetic, entitlement, privacy, tmf, schema.org, odrl, epc, prov, api and loss validation.", "media_or_form": [ "logical subscription specification assertion", "subscription, plan binding, entitlement reference, pricing, schedule, usage, lifecycle, notice, validation or projection record" ], "serial": true, "identity_strategy": "Subscription ID plus independent version, item, entitlement, schedule or event ID and artifact kind for identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation; party, date, amount, filename or digest never identifies a subscription alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-subscription", "name": "Register a subscription", "description": "Governed operation to register a subscription without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "owner", "provider", "subscriber", "purpose", "profile" ], "outputs": [ "stable subscription and version head" ], "preconditions": [ "namespace, identity, party authority, contract and profile checks pass" ], "effects": [ "a subscription draft exists without contract or entitlement inference" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-015" ] }, { "id": "bind-plan-and-participants", "name": "Bind plan and participants", "description": "Governed operation to bind plan and participants without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "subscription", "external agreement, party, account, catalogue and offering references" ], "outputs": [ "versioned plan and participant bindings" ], "preconditions": [ "masters resolve and effective periods, roles, authority and privacy checks pass" ], "effects": [ "external masters remain authoritative" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-015" ] }, { "id": "compose-items-seats-and-entitlements", "name": "Compose items, seats and entitlements", "description": "Governed operation to compose items, seats and entitlements without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "subscription version", "items, add-ons, quantities, beneficiaries and entitlement references" ], "outputs": [ "versioned composition and constraints" ], "preconditions": [ "dependencies, cardinalities, plan version, scope, limits and grant authority pass" ], "effects": [ "entitlement grant or revocation remains external" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-011" ] }, { "id": "calculate-recurring-economics", "name": "Calculate recurring economics", "description": "Governed operation to calculate recurring economics without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "subscription version", "price, quantity, usage, tax, discount, credit and proration inputs" ], "outputs": [ "source-qualified recurring charge schedule and estimates" ], "preconditions": [ "currency, unit, formula, recurrence, tax jurisdiction, rounding and approval checks pass" ], "effects": [ "calculation does not charge, invoice, approve or mutate an issued version" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009", "SRC-017" ] }, { "id": "schedule-billing-and-renewal", "name": "Schedule billing and renewal", "description": "Governed operation to schedule billing and renewal without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "subscription", "billing anchor", "recurrence", "term and renewal rules" ], "outputs": [ "versioned billing and renewal schedule" ], "preconditions": [ "timezone, interval, exceptions, count or end, notice, proration and policy checks pass" ], "effects": [ "invoice, payment and renewal decisions remain external" ], "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-013", "SRC-014" ] }, { "id": "record-activation-service-and-usage", "name": "Record activation, service and usage", "description": "Governed operation to record activation, service and usage without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "subscription", "entitlement, provisioning, availability and usage evidence" ], "outputs": [ "source-qualified observed state and usage references" ], "preconditions": [ "source, meter, unit, period, confidence, freshness and authority checks pass" ], "effects": [ "active or paid status does not prove delivery or availability" ], "source_refs": [ "SRC-002", "SRC-005", "SRC-008", "SRC-016" ] }, { "id": "record-payment-and-dunning-reference", "name": "Record payment and dunning references", "description": "Governed operation to record payment and dunning references without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "subscription", "invoice, mandate, payment, retry, credit or refund references" ], "outputs": [ "qualified billing and payment observations" ], "preconditions": [ "external identity, amount, currency, period, status, source and knowledge time pass" ], "effects": [ "the subscription never charges a payment method or owns transactions" ], "source_refs": [ "SRC-004", "SRC-007", "SRC-012", "SRC-017" ] }, { "id": "renew-change-pause-or-cancel", "name": "Renew, change, pause or cancel", "description": "Governed operation to renew, change, pause or cancel without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "subscription head", "authorized lifecycle request", "notice and impact evidence" ], "outputs": [ "immutable lifecycle assertion and successor instructions" ], "preconditions": [ "authority, agreement, notice, affected items, entitlements, billing, data and effective-time checks pass" ], "effects": [ "request, effective change and external execution remain distinct" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-015" ] }, { "id": "validate-and-reconcile-subscription", "name": "Validate and reconcile a subscription", "description": "Governed operation to validate and reconcile a subscription without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "subscription version", "rules and external observations" ], "outputs": [ "validation findings and reconciliation evidence" ], "preconditions": [ "identity, state, recurrence, entitlement, usage, arithmetic, privacy and lifecycle checks execute" ], "effects": [ "errors are reported without autonomous commercial action" ], "source_refs": [ "SRC-004", "SRC-008", "SRC-013", "SRC-016" ] }, { "id": "query-project-retain-and-audit", "name": "Query, project, retain and audit", "description": "Governed operation to query, project, retain and audit without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.", "inputs": [ "subscription", "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": [ "projections never replace the canonical subscription 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", "SRC-018" ] } ], "composition": [ { "target": "WM-ECO-006", "relation": "REFERENCE", "purpose": "Resolve the commercial agreement without granting subscription-owned mutation or cascade authority.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "target": "Party, Account, Product, Service, Catalogue, Plan, Entitlement, Order, Invoice, Payment, Usage, Support and Records models", "relation": "REFERENCE", "purpose": "Resolve authoritative external identities, events, states and evidence without duplicating their lifecycles.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-015" ] }, { "target": "EU Consumer Rights, EU Digital Content, UNIDROIT Principles, TMF Open APIs, schema.org, ODRL 2.2, EPC SDD, RFC 5545, RFC 3339, PROV-O, DQV, ISO 4217 and OpenAPI 3.1.1", "relation": "ALIGN", "purpose": "Project version-pinned legal, product, usage, billing, entitlement, payment, schedule, provenance, quality, currency and API views with declared loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension owner, namespace authority, accountable subscription owner and delegated commercial, billing, entitlement and legal authorities", "Authoritative Contract, Party, Account, Product, Service, Catalogue, Plan, Entitlement, Order, Invoice, Payment, Usage, Support and Records registries", "Approved jurisdiction, consumer, sector, currency, tax, pricing, recurrence, entitlement, privacy, retention and interoperability profiles", "Role, delegation, notice, consent, segregation-of-duties, plan-change, renewal, cancellation, termination and agent-operation policies" ], "namespace_guidance": "Mint subscription, version, item-binding, beneficiary, schedule, lifecycle, usage-reference, validation and projection IDs; preserve every external master identifier.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative subscription identifier, provider namespace and version head, never by subscriber, plan name, invoice, payment, start date or digest alone.", "Keep subscription, contract, party, account, offering, entitlement, order, invoice, payment, usage, service, support and records independently identifiable." ], "patch_rules": [ "Extensions declare profile, identity, plan, party, item, entitlement, usage, pricing, billing, renewal, lifecycle, privacy and interoperability effects.", "Issued versions are immutable; changes create linked successors with reason, affected items, entitlements, bills, notices, compatibility, migration and approval.", "Never silently change provider, subscriber, plan, item, beneficiary, price, currency, tax, recurrence, term, renewal, entitlement, cancellation, authority or privacy term." ], "compatibility_rules": [ "Ignore additive fields only when identity, version, plan, parties, items, entitlements, economics, schedules, lifecycle, authority, access and provenance survive.", "Every projection pins specification version and declares loss in plan, entitlement, usage, billing, renewal, cancellation, authority and temporal semantics." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for subscription, version, item binding, beneficiary, schedule, lifecycle event or artifact, qualified by provider namespace and record kind.", "Governed globally resolvable subscription 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 signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge times whenever they differ.", "serial_naming_rule": "Use {subscription-id}--{version-id}--{item-schedule-or-event-id}--{artifact-kind}--{revision-id}.", "integrity_rule": "Store digest, media type, record kind, subscription and version IDs, profile, provider, actor, recurrence and timezone, distinct event and knowledge times, confidentiality marking and provenance." }, "policies": [ "The subscription owns recurring-relationship context but not external contract, party, product, entitlement, invoice, payment, usage, service or records masters.", "Agreement, entitlement, provisioning, service, billing, payment and usage states and clocks remain distinct.", "Active, paid or renewed status never alone proves legal validity, entitlement delivery, service availability, conformity or future payment.", "Agents cannot autonomously form contracts, change plans or prices, charge, invoice, grant or revoke entitlements, renew, cancel, terminate, disclose or dispose records without delegated authority." ], "crud": { "read": [ "Resolve subscription head, versions, plan, participants, items, entitlements, usage, economics, schedules, lifecycle, notices, evidence, access and projection loss under the permitted view." ], "create": [ "Bind identity, provider, subscriber, purpose, profile, agreement, plan version, currency, term, source authority and initial lifecycle before recurring assertions are accepted." ], "update": [ "Append successor plan bindings, items, entitlements, prices, schedules, usage, billing observations, notices, renewals, cancellations, corrections and lifecycle assertions with reason, authority, event time and knowledge time." ], "delete": [ "Apply legal hold, financial, consumer, tax, privacy and adopting-Dimension retention policy; tombstone only the catalogue view without cascading to external masters, and let authoritative systems execute physical disposition." ] }, "roles": [ { "name": "Subscription owner", "responsibilities": [ "Own purpose, scope, profile, lifecycle, compatibility and accountable use." ] }, { "name": "Commercial and plan owner", "responsibilities": [ "Own plan, items, pricing, term, renewal and approved change policy." ] }, { "name": "Entitlement and service steward", "responsibilities": [ "Own entitlement, provisioning, availability, usage and support bindings." ] }, { "name": "Billing and payment steward", "responsibilities": [ "Own billing schedule, invoice, mandate, payment, credit, refund and dunning references." ] }, { "name": "Legal and privacy authority", "responsibilities": [ "Own consent, notice, consumer rights, termination, data use, access and jurisdictional limitations." ] }, { "name": "Reviewer and approving authority", "responsibilities": [ "Own validation, exceptions, segregation of duties and authorization for changes." ] }, { "name": "Interoperability and records steward", "responsibilities": [ "Own mappings, conformance evidence, declared loss, retention, legal hold and disposition policy." ] } ], "access": { "default_rule": "Deny personal, subscriber-specific, negotiated, commercially sensitive, payment, usage, location, device, entitlement, discount, tax, delinquency, support and cancellation data unless a purpose-bound policy permits the minimum necessary view.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Declared billing, support, 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, subscription and version, operation, authority, policy, RFC 3339 time, affected items or terms, source revision and outcome without duplicating restricted subscriber data." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension namespace, subscription, commercial, billing, entitlement, consumer, privacy, retention and agent policies.", "Read this subscription and linked contract, party, account, offering, entitlement, invoice, payment, usage, service, support and records models before mutation." ] } }, "coverage": { "claim": "WM-ECO-022 covers one governed subscription from identity, version, profile, agreement and plan bindings through participants, items, seats, beneficiaries, entitlements, usage allowances, recurring economics, billing and renewal schedules, invoice and payment references, service lifecycle, cancellation, evidence, access, retention and loss-aware projections. Jurisdiction and sector profiles, legal 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; service region, delivery place, tax jurisdiction and usage location 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-ECO-006 parent signal has no frozen approved relation and grants no cascade authority.", "Telecom, utility, insurance, healthcare, media, SaaS, membership, transport and other sector profiles need separate rules.", "National contract, tax, consumer, payment, electronic-signature, privacy and records rules require jurisdiction profiles and authorized review.", "TM Forum and schema.org mappings are useful projections but do not universally define a subscription or legal entitlement." ], "conflicts": [ "Subscription, contract, plan, offer, membership, entitlement, order, service instance, invoice and payment are related but not interchangeable.", "Contract, entitlement, provisioning, availability, billing, payment, usage and support states and times must not be collapsed.", "Recurring, one-time, seat, usage, tiered, tax, discount, credit, proration and refund values require separate semantics.", "Cancellation request, cancellation effective time, termination completion, entitlement revocation, final bill and data deletion are distinct." ], "regional_assumptions": [ "Renewal, notice, consent, withdrawal, cancellation, refund, tax, payment mandate, data export and retention depend on governing law, jurisdiction, party type and sector.", "EU consumer and digital-content rules, EPC payment rules and UNIDROIT Principles are scoped profiles, not universal governing law." ], "adversarial_checks": [ "Reject a subscription that collapses into contract, plan, entitlement, invoice, payment, usage or service masters.", "Reject a recurring charge without price type, currency, quantity or usage basis, tax, recurrence, validity, source and approval.", "Reject active, paid or renewed status as proof of legal validity, entitlement delivery, service availability or conformity.", "Reject a cancellation that loses request, notice, effective, termination, refund, final-bill, export and post-term-right distinctions.", "Reject autonomous charging, plan change, entitlement grant or revocation, renewal, cancellation, termination, disclosure or disposition.", "Reject a projection that hides plan version, entitlements, usage, recurrence, proration, 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 recurring commercial-relationship aggregate. Contract, party, account, plan or offering, product, service, entitlement, order, invoice, payment, usage event, meter reading, service instance, support case and records remain external masters." }, "decisions": [ { "concept": "Subscription, contract, plan, membership and entitlement", "disposition": "accepted-with-explicit-boundary", "rationale": "The subscription binds an agreement and versioned plan to recurring operational and economic context; it is neither the reusable plan nor the legal contract, membership identity or entitlement grant." }, { "concept": "WM-ECO-006 parent signal", "disposition": "accepted-as-unapproved-reference", "rationale": "Commercial Contract is a plausible parent reference, but no frozen canonical relation grants ownership, mutation or cascade authority." }, { "concept": "Participant and beneficiary roles", "disposition": "accepted", "rationale": "Provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor remain separate, source-qualified roles and may be different parties." }, { "concept": "Agreement, entitlement, provisioning, service, billing, payment and usage axes", "disposition": "accepted", "rationale": "Each axis preserves independent state, authority, evidence and time; active, paid or renewed status cannot prove the others." }, { "concept": "Recurring economics", "disposition": "accepted", "rationale": "Recurring, one-time, seat, usage, tiered, volume, tax, discount, credit, proration, refund and overage values remain distinct and source-qualified." }, { "concept": "Billing and recurrence schedule", "disposition": "accepted", "rationale": "Anchor, timezone, interval, in-advance or arrears basis, exceptions, count or end, invoice and due times stay explicit; a schedule neither invoices nor charges." }, { "concept": "Cancellation and termination lifecycle", "disposition": "accepted", "rationale": "Request, notice, at-period-end selection, immediate effect, termination completion, entitlement revocation, final bill, refund, export and deletion remain separately attributable." }, { "concept": "Consumer, digital-content and payment profiles", "disposition": "accepted-with-jurisdiction-hold", "rationale": "EU consumer and digital-content rules, UNIDROIT Principles and EPC direct-debit rules are scoped profiles rather than universal subscription law." }, { "concept": "Interoperability projections", "disposition": "accepted-with-loss-declaration", "rationale": "TM Forum, schema.org, ODRL, EPC, RFC, PROV, DQV, ISO 4217 and OpenAPI cover different facets and never replace the canonical aggregate." }, { "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-022 each timed out after 120 seconds; no external research result was admitted.", "Relation hold: WM-ECO-006 is only a parent signal and no model relation is canonically approved for this aggregate.", "Boundary hold: subscription, contract, party, account, plan, offering, product, service, entitlement, order, invoice, payment, usage event, meter reading, support case and records must retain separate identities.", "State-axis hold: agreement, entitlement, provisioning, availability, billing, payment, usage, support and cancellation states and clocks must never be silently collapsed.", "Economic hold: every recurring, one-time, seat, usage, tiered, tax, discount, credit, proration, refund and overage value requires currency, quantity or usage basis, period, source, approval and uncertainty.", "Temporal hold: signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancellation, termination, observation, ingestion and knowledge time remain distinct; timestamps require seconds and timezone offset.", "Cancellation hold: request, notice, effective cancellation, termination completion, entitlement revocation, final billing, refund, export and data disposition require separate evidence and authority.", "Authority hold: contract formation, plan or price change, charging, invoicing, entitlement grant or revocation, renewal, cancellation, termination, disclosure and disposition require delegated accountable authority.", "Jurisdiction hold: EU consumer and digital-content rules, UNIDROIT Principles and EPC direct-debit rules are scoped profiles; national and sector rules require separate validation.", "Interoperability hold: every TM Forum, schema.org, ODRL, EPC, RFC 5545, RFC 3339, PROV, DQV, ISO 4217 and OpenAPI projection requires version pins, conformance evidence and information-loss declarations.", "Privacy hold: personal, usage, device, location, entitlement, payment, delinquency, support and cancellation data require purpose-bound access, minimization, portability 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-ECO-006 relation and register Party, Account, Product, Service, Catalogue, Plan, Entitlement, Order, Invoice, Payment, Usage, Support and Records edges.", "Create telecom, utility, insurance, healthcare, media, SaaS, membership, transport and jurisdiction-specific profiles.", "Conformance-test plan changes, entitlement limits, recurrence, usage, billing, proration, renewal, cancellation and projections against concrete implementations.", "Validate organization-specific contract, pricing, billing, payment, entitlement, renewal, cancellation, privacy, retention and disposition policies.", "Obtain authorized legal, tax, consumer and payment review before making jurisdiction-specific claims.", "Obtain independent external research review before promoting beyond reviewable-draft assurance." ] }, "statistics": { "sources": 18, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }