Published

Subscription

vr.wm-eco-022 · wm-eco-022-subscription

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.

World Models Society, people and institutions SOC.ECO.SUB

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Identity, contract, participants and plan Groups governed subscription context for identity, contract, participants and plan.

Subscription root identity, version, profile and status

Groups source-qualified subscription context for subscription root identity, version, profile and status.

Subscription ID, version, head, name, purpose, language, status and master system

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.

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? identity
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? authority
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? security

Fixed-term, evergreen, auto-renewing, prepaid, postpaid, trial, freemium, sponsored, consumer and enterprise profile

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.

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? classification
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? requirement
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? privacy

Agreement, parties, roles and external masters

Groups source-qualified subscription context for agreement, parties, roles and external masters.

Provider, subscriber, customer, payer, beneficiary, seat holder, administrator, agent and sponsor role

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.

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? relationship
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? constraint
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? retention

Contract, account, order, offer, catalogue, plan, service instance, entitlement and authoritative master binding

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.

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? relationship
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? process
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? access

Plan composition, entitlements and usage Groups governed subscription context for plan composition, entitlements and usage.

Plan version, items, add-ons, bundles, seats and dependencies

Groups source-qualified subscription context for plan version, items, add-ons, bundles, seats and dependencies.

Plan, offering version, SKU, product, service, item, add-on, bundle, option and effective period

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.

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? composition
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? event
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? exception

Seat, quantity, beneficiary, assignment, dependency, prerequisite, exclusivity and substitution

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.

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? composition
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? measurement
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? interoperability

Entitlement, feature, permission, allowance and limit

Groups source-qualified subscription context for entitlement, feature, permission, allowance and limit.

Entitlement, permission, prohibition, duty, feature, scope, territory, device, channel and grant reference

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.

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? access
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? evidence
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? decision

Allowance, meter, unit, bucket, period, rollover, overage, fair-use, cap, threshold and usage source

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.

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? measurement
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? quality
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? identity

Economics, billing, invoice and payment Groups governed subscription context for economics, billing, invoice and payment.

Recurring pricing, discount, tax, credit and proration

Groups source-qualified subscription context for recurring pricing, discount, tax, credit and proration.

Recurring, one-time, seat, usage, tiered, volume, minimum commitment, ramp, trial and overage price

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.

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? measurement
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? validation
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? classification

Currency, tax, discount, promotion, coupon, credit, proration, refund, rounding and price-change policy

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.

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? requirement
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? security
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? composition

Billing cycle, invoice, payment mandate and dunning

Groups source-qualified subscription context for billing cycle, invoice, payment mandate and dunning.

Billing anchor, frequency, calendar, timezone, in-advance, arrears, period close, invoice and due schedule

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.

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? temporal
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? privacy
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? relationship

Payment method, mandate, charge, transaction, retry, dunning, delinquency, credit, refund and write-off reference

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.

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? relationship
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? retention
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? state

Service lifecycle, renewal, change and termination Groups governed subscription context for service lifecycle, renewal, change and termination.

Trial, activation, provisioning, service, pause, suspension and reactivation

Groups source-qualified subscription context for trial, activation, provisioning, service, pause, suspension and reactivation.

Signup, trial, conversion, activation, entitlement, provisioning, service availability and verification

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.

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? lifecycle
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? access
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? lifecycle

Pause, suspension, grace, block, delinquency, remediation, reactivation and state reason

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.

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? state
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? exception
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? temporal

Term, renewal, notice, cancellation and post-termination

Groups source-qualified subscription context for term, renewal, notice, cancellation and post-termination.

Term start, end, renewal window, auto-renew, manual renew, price notice, consent and cooling-off

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.

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? temporal
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? interoperability
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? provenance

Cancel request, at-period-end, immediate cancel, effective cancellation, termination, revocation, export, refund and post-term right

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.

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? lifecycle
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? decision
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? ownership

Usage, quality, support and evidence Groups governed subscription context for usage, quality, support and evidence.

Usage measurement, balance, aggregation and dispute

Groups source-qualified subscription context for usage measurement, balance, aggregation and dispute.

Usage event, meter, observation, unit, source, period, aggregation, adjustment, correction and confidence

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.

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? provenance
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? identity
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? authority

Quota, consumed, remaining, rollover, overage, freshness, forecast, alert, anomaly, dispute and reconciliation

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.

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? quality
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? classification
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? requirement

Service level, conformity, support, remedy and complaint

Groups source-qualified subscription context for service level, conformity, support, remedy and complaint.

SLA, availability, performance, maintenance, support, incident, breach, service credit and evidence

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.

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? evidence
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? composition
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? constraint

Conformity, defect notice, remedy, price reduction, refund, complaint, dispute and chargeback reference

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.

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? process
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? relationship
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? process

Governance, provenance, temporal and interoperability Groups governed subscription context for governance, provenance, temporal and interoperability.

Authority, source, provenance, access, privacy and retention

Groups source-qualified subscription context for authority, source, provenance, access, privacy and retention.

Owner, steward, approver, source system, plan, price, policy, derivation, revision and audit

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.

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? ownership
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? state
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? event

Purpose, consent, personal data, access, confidentiality, disclosure, portability, retention, legal hold and tombstone

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.

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? privacy
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? lifecycle
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? measurement

Clocks, events, validation and projections

Groups source-qualified subscription context for clocks, events, validation and projections.

Signup, contract, trial, activation, service, usage, billing, invoice, payment, renewal, notice, cancel, termination, observation and knowledge time

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.

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? temporal
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? temporal
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? evidence

Identity, state, recurrence, arithmetic, entitlement, privacy, TMF, schema.org, ODRL, EPC, PROV, API and loss validation

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.

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? interoperability
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? provenance
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? quality

Classifiers Filled

Family: World Models
Category: Society, people and institutions
Entry kind: aggregate
Navigation path: NAV.SOC.ECO.SUB
Domain: SOC.ECO.SUB
Industry: Cross-industry
Tags: subscriptionsoc.eco.sub

What it is Filled

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

Why it exists Filled

Distinguishing features Filled

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.

What robots and AI may and may not do Filled

Must not

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.

Only with a human decision

Changing prices or plans.
Terminating a subscription for non-payment.
Granting refunds or credits.

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.

Moral aspects Filled

Subscription traps and hidden renewals harm consumers.
Usage data reveals personal behaviour.
Abrupt termination can cut access to essential services.

Who is affected

Subscribers and payers
Beneficiaries using the service
Providers

Owners Filled

Steward

Dimension owner, namespace authority, accountable subscription owner and delegated commercial, billing, entitlement and legal authorities

Roles

Subscription owner: Own purpose, scope, profile, lifecycle, compatibility and accountable use.
Commercial and plan owner: Own plan, items, pricing, term, renewal and approved change policy.
Entitlement and service steward: Own entitlement, provisioning, availability, usage and support bindings.
Billing and payment steward: Own billing schedule, invoice, mandate, payment, credit, refund and dunning references.
Legal and privacy authority: Own consent, notice, consumer rights, termination, data use, access and jurisdictional limitations.
Reviewer and approving authority: Own validation, exceptions, segregation of duties and authorization for changes.
Interoperability and records steward: Own mappings, conformance evidence, declared loss, retention, legal hold and disposition policy.

Links to other meta-models Filled

references

WM-ECO-006 - Resolve the commercial agreement without granting subscription-owned mutation or cascade authority.
Party, Account, Product, Service, Catalogue, Plan, Entitlement, Order, Invoice, Payment, Usage, Support and Records models - Resolve authoritative external identities, events, states and evidence without duplicating their lifecycles.

aligned

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 - Project version-pinned legal, product, usage, billing, entitlement, payment, schedule, provenance, quality, currency and API views with declared loss.

neighbor

WM-ECO-006 Commercial Contract - The unfrozen parent agreement establishes obligations and legal terms. The subscription is a recurring operational aggregate that references but does not replace the contract.
Plan, product, service and entitlement - 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.
Invoice, payment mandate, payment and usage - Billing schedules predict or request recurring economics, invoices assert amounts due, payments settle, and usage observations meter consumption; none is the subscription identity.
Service provisioning and availability - Activation, entitlement, provisioning and availability are separate processes or observations; active subscription status does not prove their success.
TM Forum, schema.org, ODRL, EPC, RFC, PROV, DQV and OpenAPI - Each representation has a distinct scope; every mapping is version-pinned and loss-declaring.

parent

WM-ECO-006

What else AI and robots need to interact with it Filled

Sources Filled

Directive 2011/83/EU on consumer rights - European Union
Directive EU 2019/770 on digital content and digital services - European Union
UNIDROIT Principles of International Commercial Contracts 2016 - UNIDROIT
Open API Directory - TM Forum
Product Inventory Management API TMF637 - TM Forum
Product Catalog Management API User Guide TMF620 v5.0.0 - TM Forum
Customer Bill Management API TMF678 v5.0 - TM Forum
Usage Consumption Management API TMF677 v4.0.0 - TM Forum
UnitPriceSpecification - Schema.org Community Group
Offer - Schema.org Community Group
ODRL Information Model 2.2 - World Wide Web Consortium
SEPA Direct Debit Core Rulebook and implementation guidelines - European Payments Council
Internet Calendaring and Scheduling Core Object Specification - Internet Engineering Task Force
Date and Time on the Internet: Timestamps - Internet Engineering Task Force
PROV-O: The PROV Ontology - World Wide Web Consortium
Data on the Web Best Practices: Data Quality Vocabulary - World Wide Web Consortium
Global Financial Data Standards: ISO 4217 Currency Codes - SIX Financial Information
OpenAPI Specification 3.1.1 - OpenAPI Initiative

Open questions

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.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-eco-022-subscription/spec.yaml, ver-cy/world-models/card-supplements/wm-eco-022-subscription.json