{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-eco-022","code":"wm-eco-022-subscription","url":"https://ver.cy/models/wm-eco-022-subscription/","name":"Subscription","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Society, people and institutions","entryKind":"aggregate","plane":"","domain":["SOC.ECO.SUB"],"industry":["Cross-industry"],"navPath":"NAV.SOC.ECO.SUB","tags":["subscription","soc.eco.sub"],"facets":{}},"whatItIs":"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.","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":{"in":["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":["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"],"boundaries":[{"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."},{"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."},{"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."},{"neighbor":"Service provisioning and availability","distinction":"Activation, entitlement, provisioning and availability are separate processes or observations; active subscription status does not prove their success."},{"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."}]},"distinguishingFeatures":["A recurring commercial relationship with renewal and billing cycles, not a one-off order.","Keeps agreement, entitlement, provisioning, billing, payment and usage states distinct.","Differs from the commercial contract, which holds legal terms.","Differs from an entitlement, which grants access to a specific service."],"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.","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.","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.","questions":[{"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?","id":"subscription-id-version-head-name-purpose-language-status-and-master-system-q01","kind":"identity"},{"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?","id":"subscription-id-version-head-name-purpose-language-status-and-master-system-q02","kind":"authority"},{"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?","id":"subscription-id-version-head-name-purpose-language-status-and-master-system-q03","kind":"security"}]},{"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.","questions":[{"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?","id":"fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile-q01","kind":"classification"},{"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?","id":"fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile-q02","kind":"requirement"},{"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?","id":"fixed-term-evergreen-auto-renewing-prepaid-postpaid-trial-freemium-sponsored-consumer-and-enterprise-profile-q03","kind":"privacy"}]}]},{"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.","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.","questions":[{"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?","id":"provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role-q01","kind":"relationship"},{"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?","id":"provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role-q02","kind":"constraint"},{"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?","id":"provider-subscriber-customer-payer-beneficiary-seat-holder-administrator-agent-and-sponsor-role-q03","kind":"retention"}]},{"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.","questions":[{"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?","id":"contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding-q01","kind":"relationship"},{"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?","id":"contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding-q02","kind":"process"},{"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?","id":"contract-account-order-offer-catalogue-plan-service-instance-entitlement-and-authoritative-master-binding-q03","kind":"access"}]}]}]},{"id":"plan-composition-entitlements-and-usage","name":"Plan composition, entitlements and usage","description":"Groups governed subscription context for plan composition, entitlements and usage.","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.","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.","questions":[{"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?","id":"plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period-q01","kind":"composition"},{"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?","id":"plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period-q02","kind":"event"},{"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?","id":"plan-offering-version-sku-product-service-item-addon-bundle-option-and-effective-period-q03","kind":"exception"}]},{"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.","questions":[{"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?","id":"seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution-q01","kind":"composition"},{"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?","id":"seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution-q02","kind":"measurement"},{"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?","id":"seat-quantity-beneficiary-assignment-dependency-prerequisite-exclusivity-and-substitution-q03","kind":"interoperability"}]}]},{"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.","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.","questions":[{"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?","id":"entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference-q01","kind":"access"},{"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?","id":"entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference-q02","kind":"evidence"},{"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?","id":"entitlement-permission-prohibition-duty-feature-scope-territory-device-channel-and-grant-reference-q03","kind":"decision"}]},{"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.","questions":[{"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?","id":"allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source-q01","kind":"measurement"},{"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?","id":"allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source-q02","kind":"quality"},{"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?","id":"allowance-meter-unit-bucket-period-rollover-overage-fair-use-cap-threshold-and-usage-source-q03","kind":"identity"}]}]}]},{"id":"economics-billing-invoice-and-payment","name":"Economics, billing, invoice and payment","description":"Groups governed subscription context for economics, billing, invoice and payment.","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.","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.","questions":[{"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?","id":"recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price-q01","kind":"measurement"},{"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?","id":"recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price-q02","kind":"validation"},{"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?","id":"recurring-one-time-seat-usage-tiered-volume-minimum-commitment-ramp-trial-and-overage-price-q03","kind":"classification"}]},{"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.","questions":[{"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?","id":"currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy-q01","kind":"requirement"},{"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?","id":"currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy-q02","kind":"security"},{"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?","id":"currency-tax-discount-promotion-coupon-credit-proration-refund-rounding-and-price-change-policy-q03","kind":"composition"}]}]},{"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.","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.","questions":[{"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?","id":"billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule-q01","kind":"temporal"},{"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?","id":"billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule-q02","kind":"privacy"},{"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?","id":"billing-anchor-frequency-calendar-timezone-in-advance-arrears-period-close-invoice-and-due-schedule-q03","kind":"relationship"}]},{"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.","questions":[{"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?","id":"payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference-q01","kind":"relationship"},{"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?","id":"payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference-q02","kind":"retention"},{"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?","id":"payment-method-mandate-charge-transaction-retry-dunning-delinquency-credit-refund-and-writeoff-reference-q03","kind":"state"}]}]}]},{"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.","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.","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.","questions":[{"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?","id":"signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification-q01","kind":"lifecycle"},{"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?","id":"signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification-q02","kind":"access"},{"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?","id":"signup-trial-conversion-activation-entitlement-provisioning-service-availability-and-verification-q03","kind":"lifecycle"}]},{"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.","questions":[{"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?","id":"pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason-q01","kind":"state"},{"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?","id":"pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason-q02","kind":"exception"},{"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?","id":"pause-suspension-grace-block-delinquency-remediation-reactivation-and-state-reason-q03","kind":"temporal"}]}]},{"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.","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.","questions":[{"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?","id":"term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off-q01","kind":"temporal"},{"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?","id":"term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off-q02","kind":"interoperability"},{"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?","id":"term-start-end-renewal-window-auto-renew-manual-renew-price-notice-consent-and-cooling-off-q03","kind":"provenance"}]},{"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.","questions":[{"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?","id":"cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right-q01","kind":"lifecycle"},{"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?","id":"cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right-q02","kind":"decision"},{"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?","id":"cancel-request-at-period-end-immediate-cancel-effective-termination-revocation-export-refund-and-post-term-right-q03","kind":"ownership"}]}]}]},{"id":"usage-quality-support-and-evidence","name":"Usage, quality, support and evidence","description":"Groups governed subscription context for usage, quality, support and evidence.","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.","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.","questions":[{"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?","id":"usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence-q01","kind":"provenance"},{"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?","id":"usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence-q02","kind":"identity"},{"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?","id":"usage-event-meter-observation-unit-source-period-aggregation-adjustment-correction-and-confidence-q03","kind":"authority"}]},{"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.","questions":[{"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?","id":"quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation-q01","kind":"quality"},{"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?","id":"quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation-q02","kind":"classification"},{"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?","id":"quota-consumed-remaining-rollover-overage-freshness-forecast-alert-anomaly-dispute-and-reconciliation-q03","kind":"requirement"}]}]},{"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.","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.","questions":[{"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?","id":"sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence-q01","kind":"evidence"},{"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?","id":"sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence-q02","kind":"composition"},{"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?","id":"sla-availability-performance-maintenance-support-incident-breach-service-credit-and-evidence-q03","kind":"constraint"}]},{"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.","questions":[{"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?","id":"conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference-q01","kind":"process"},{"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?","id":"conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference-q02","kind":"relationship"},{"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?","id":"conformity-defect-notice-remedy-price-reduction-refund-complaint-dispute-and-chargeback-reference-q03","kind":"process"}]}]}]},{"id":"governance-provenance-temporal-and-interoperability","name":"Governance, provenance, temporal and interoperability","description":"Groups governed subscription context for governance, provenance, temporal and interoperability.","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.","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.","questions":[{"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?","id":"owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit-q01","kind":"ownership"},{"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?","id":"owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit-q02","kind":"state"},{"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?","id":"owner-steward-approver-source-system-plan-price-policy-derivation-revision-and-audit-q03","kind":"event"}]},{"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.","questions":[{"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?","id":"purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone-q01","kind":"privacy"},{"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?","id":"purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone-q02","kind":"lifecycle"},{"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?","id":"purpose-consent-personal-data-access-confidentiality-disclosure-portability-retention-legal-hold-and-tombstone-q03","kind":"measurement"}]}]},{"id":"clocks-events-validation-and-projections","name":"Clocks, events, validation and projections","description":"Groups source-qualified subscription context for clocks, events, validation and projections.","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.","questions":[{"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?","id":"signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time-q01","kind":"temporal"},{"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?","id":"signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time-q02","kind":"temporal"},{"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?","id":"signup-contract-trial-activation-service-usage-billing-invoice-payment-renewal-notice-cancel-termination-observation-and-knowledge-time-q03","kind":"evidence"}]},{"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.","questions":[{"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?","id":"identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation-q01","kind":"interoperability"},{"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?","id":"identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation-q02","kind":"provenance"},{"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?","id":"identity-state-recurrence-arithmetic-entitlement-privacy-tmf-schemaorg-odrl-epc-prov-api-and-loss-validation-q03","kind":"quality"}]}]}]}]},"agentConduct":{"may":["Track plan, seats, items and renewal dates.","Remind subscribers of upcoming renewals and price changes.","Reconcile usage, invoices and payments.","Prepare cancellation requests for subscriber confirmation."],"mustNot":["Charge, renew or change plans without consent.","Make cancellation harder than sign-up.","Revoke entitlements without notice.","Change prices outside the contract terms.","Disclose subscriber usage data."],"requiresHuman":["Changing prices or plans.","Terminating a subscription for non-payment.","Granting refunds or credits."]},"ethics":{"considerations":["Subscription traps and hidden renewals harm consumers.","Usage data reveals personal behaviour.","Abrupt termination can cut access to essential services."],"affectedParties":["Subscribers and payers","Beneficiaries using the service","Providers"]},"owners":{"steward":"Dimension owner, namespace authority, accountable subscription owner and delegated commercial, billing, entitlement and legal authorities","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."]}],"masterSystems":[]},"relations":[{"target":"WM-ECO-006","type":"references","note":"Resolve the commercial agreement without granting subscription-owned mutation or cascade authority."},{"target":"Party, Account, Product, Service, Catalogue, Plan, Entitlement, Order, Invoice, Payment, Usage, Support and Records models","type":"references","note":"Resolve authoritative external identities, events, states and evidence without duplicating their lifecycles."},{"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","type":"aligned","note":"Project version-pinned legal, product, usage, billing, entitlement, payment, schedule, provenance, quality, currency and API views with declared loss."},{"target":"WM-ECO-006 Commercial Contract","type":"neighbor","note":"The unfrozen parent agreement establishes obligations and legal terms. The subscription is a recurring operational aggregate that references but does not replace the contract."},{"target":"Plan, product, service and entitlement","type":"neighbor","note":"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."},{"target":"Invoice, payment mandate, payment and usage","type":"neighbor","note":"Billing schedules predict or request recurring economics, invoices assert amounts due, payments settle, and usage observations meter consumption; none is the subscription identity."},{"target":"Service provisioning and availability","type":"neighbor","note":"Activation, entitlement, provisioning and availability are separate processes or observations; active subscription status does not prove their success."},{"target":"TM Forum, schema.org, ODRL, EPC, RFC, PROV, DQV and OpenAPI","type":"neighbor","note":"Each representation has a distinct scope; every mapping is version-pinned and loss-declaring."},{"target":"WM-ECO-006","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["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."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A subscription names a provider, a subscriber, a plan, a start date, a billing cycle and a renewal state.","Often confused with a contract, an order, an invoice or an entitlement."]},"capabilities":{"applicability":"required","items":["Register a subscription: Governed operation to register a subscription without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.","Bind plan and participants: 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.","Compose items, seats and entitlements: 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.","Calculate recurring economics: Governed operation to calculate recurring economics without autonomous contract formation, charging, invoicing, plan change, entitlement grant or revocation, cancellation, termination, disclosure or records disposition.","Schedule billing and renewal: 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.","Record activation, service and usage: 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.","Record payment and dunning references: 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.","Renew, change, pause or cancel: 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.","Validate and reconcile a subscription: 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.","Query, project, retain and audit: 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."]},"hazards":{"applicability":"required","items":["Unwanted charges after cancellation.","Service cut-off while paid.","Billing for unused seats."]},"interfaces":{"applicability":"required","items":["TM Forum Open APIs for product ordering and inventory.","Schema.org Offer and Product.","ISO 20022 and the EPC SEPA Direct Debit rulebook for recurring payments.","IETF RFC 5545 recurrence rules.","ISO 4217 currency codes."]},"context":{"applicability":"required","items":["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."]}},"sources":[{"title":"Directive 2011/83/EU on consumer rights","url":"https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32011L0083","note":"European Union"},{"title":"Directive EU 2019/770 on digital content and digital services","url":"https://eur-lex.europa.eu/eli/dir/2019/770","note":"European Union"},{"title":"UNIDROIT Principles of International Commercial Contracts 2016","url":"https://www.unidroit.org/instruments/commercial-contracts/unidroit-principles-2016/","note":"UNIDROIT"},{"title":"Open API Directory","url":"https://www.tmforum.org/open-digital-architecture/open-apis","note":"TM Forum"},{"title":"Product Inventory Management API TMF637","url":"https://www.tmforum.org/open-digital-architecture/open-apis/product-inventory-management-api-TMF637/v4.0","note":"TM Forum"},{"title":"Product Catalog Management API User Guide TMF620 v5.0.0","url":"https://www.tmforum.org/resources/specification/tmf620-product-catalog-management-api-user-guide-v5-0-0/","note":"TM Forum"},{"title":"Customer Bill Management API TMF678 v5.0","url":"https://www.tmforum.org/open-digital-architecture/open-apis/customer-bill-management-api-TMF678/v5.0","note":"TM Forum"},{"title":"Usage Consumption Management API TMF677 v4.0.0","url":"https://www.tmforum.org/resources/standard/tmf677-usage-consumption-management-api-user-guide-v4-0-0/","note":"TM Forum"},{"title":"UnitPriceSpecification","url":"https://schema.org/UnitPriceSpecification","note":"Schema.org Community Group"},{"title":"Offer","url":"https://schema.org/Offer","note":"Schema.org Community Group"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium"},{"title":"SEPA Direct Debit Core Rulebook and implementation guidelines","url":"https://www.europeanpaymentscouncil.eu/what-we-do/epc-payment-schemes/sepa-direct-debit/sepa-direct-debit-core-rulebook-and-implementation","note":"European Payments Council"},{"title":"Internet Calendaring and Scheduling Core Object Specification","url":"https://www.rfc-editor.org/info/rfc5545/","note":"Internet Engineering Task Force"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/info/rfc3339/","note":"Internet Engineering Task Force"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Data on the Web Best Practices: Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"World Wide Web Consortium"},{"title":"Global Financial Data Standards: ISO 4217 Currency Codes","url":"https://www.six-group.com/en/products-services/financial-information/market-reference-data/data-standards.html","note":"SIX Financial Information"},{"title":"OpenAPI Specification 3.1.1","url":"https://spec.openapis.org/oas/v3.1.1.html","note":"OpenAPI Initiative"}],"openQuestions":["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.","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."],"resources":{"spec":"/models/wm-eco-022-subscription/spec.yaml","agents":"/models/wm-eco-022-subscription/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/publications/wm-eco-022-subscription"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-eco-022-subscription/spec.yaml","ver-cy/world-models/card-supplements/wm-eco-022-subscription.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T14:52:17Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}