**Verdict.** Conditional accept of the proposed reuse and separations. Reject Renewal as a candidate type. Keep Consumption Entitlement as an identifier-unassigned candidate, not a peer master. Keep the thin cross-model profile correspondence-only. The card is not publication-ready: WM-ECO-020 and WM-ECO-022 are reviewable-drafts with empty relation ledgers; WM-ECO-024 is named by WM-ECO-008 but 404s; no entitlement catalogue entry exists. Do not invent identifiers. Published ≠ independently reviewed.

**Identity / mastership.** EM-COM-03 is a queued subject assembly, not a world-model. It must not mint Order, OrderLine, Subscription, Invoice, Payment, or Usage keys. Seller-side order identity and line quantities (ordered / allocated / delivered / outstanding) stay with WM-ECO-020. Subscription identity, version head, plan binding, suspension and renewal clocks stay with WM-ECO-022. Offer version stays with WM-ECO-021 (the card already requires an order to pin one). Invoice issue and correction stay with WM-ECO-008; allocation and settlement stay with WM-ECO-009 under the EM-FIN-03 contour. Actual usage events stay with WM-FLW-015. Software licence remains out of this card. The profile has no identifier and no mastership. If it stores keys, balances, or state, it is a stealth model and must be rejected.

**Order / line.** Reuse WM-ECO-020. The line is a priced commitment to a pinned offer version, independently addressable for acceptance, despatch linkage, and claims. It is not the subscription and not the entitlement. Goods lines close by quantity-progress. Subscription-originating lines close by creating or activating a WM-ECO-022 version, not by shipment. Partial delivery is already first-class on the line (delivered vs outstanding vs oversupply). WM-ECO-020’s own deferred research says subscription / standing-order / service-order specialisations are only lightly covered; the profile must not pretend otherwise. “020 for line-level fulfilment” means line quantity-progress and despatch *linkage*, not ownership of despatch or receipt events. Those events were pointed at WM-ECO-024, which is unverified.

**Subscription / entitlement / usage.** Reuse WM-ECO-022 for the continuing commercial relationship, immutable predecessor versions, successor versions, pause / suspension / grace / reactivation, and renewal windows. Usage is observed consumption (WM-FLW-015), not the right to consume and not a billing document.

Challenge to independent Entitlement identity. WM-ECO-022’s boundary hold already requires entitlement to remain a separate identity, yet the same model records entitlement, allowance and meter as source-qualified subscription / plan context and has no entitlement artifact of its own. That is an internal contradiction, not a completed master. Many grants *are* reconstructable from subscription-version + WM-ECO-021 item + beneficiary + period + grant-source. An independent key in those cases creates dual mastership and reconcile debt. Stronger later cases exist and should be parked, not assigned: seats / meters / features with different beneficiaries and clocks on one version; prepaid or promo grants with no subscription; remaining-balance that outlives cancellation; transfer, split or pool; a licence-system master distinct from the commercial instrument. Stance: keep Consumption Entitlement identifier-unassigned. Promote only after a fixture shows a grant whose identity is not that projection. Do not collapse it into WM-XCT-017 attestation / credential or into software-licence declaration; those are issued claims, not a commercial right-to-consume. Do not hide usage inside the grant.

**Fulfilment / invoice / payment.** Keep the five-way split: fulfilment, invoice, payment, entitlement, usage. Payment settles an invoice only; it never closes an order line, never grants a right, and never proves use. EM-FIN-03 already states that reconciliation does not confirm delivery. A paid invoice with outstanding quantity is lawful (bill-then-ship / prepay). Partial delivery with an unpaid remainder is lawful (ship-then-bill). WM-ECO-008 is immutable at issue and carries payment instruction, not settlement. WM-ECO-009 holds allocation, residual and exception. Neither writes line residuals.

**Change / renewal / proration.** Mid-cycle plan or price change creates a successor WM-ECO-022 version that pins a (possibly new) WM-ECO-021 offer version. Predecessor facts stay immutable. Renewal is a typed predecessor→successor version-link assertion on WM-ECO-022, not a model and not an EM-COM-03 type. The card lists Renewal as a candidate type; reject that listing. Proration is an economic consequence of the version transition, materialised as WM-ECO-008 credit / debit / new-invoice lines, never as mutation of a prior subscription version and never as profile state. New price lives on the successor’s offer reference.

**Lifecycle.** Do not collapse clocks. Order: draft → committed → (partial) fulfilled → closed | cancelled. Subscription: pending / trial → active ↔ suspended → cancelled | expired. Entitlement, if later asserted: granted → active ↔ suspended → exhausted | revoked | expired. Invoice: issued → (partial) paid → settled | corrected / void. Payment: instructed → settled | failed | returned. Usage: asserted → corrected. Suspension is reversible and distinct from revocation and from cancellation. Cancellation of the instrument is distinct from entitlement revocation, final bill, refund and data disposition.

**Scenario.** Required beats, with no history rewrite. (1) Goods qty 10, fulfil 6: WM-ECO-020 line residual 4; invoice may be 6 or 10 by terms; neither writes the other. (2) Invoice for 10 paid in full via WM-ECO-009: payment closed; fulfilment residual remains 4; payment does not activate a grant and does not mark the line delivered. The card’s negative case — payment means every line is delivered — must fail. (3) Mid-term suspension: current WM-ECO-022 version remains; authorisation stops or is reduced; issued invoices stand; usage is rejected unless an explicit overage policy says otherwise; grant identity, if any, is not deleted. (4) Renewal at a new price: successor version + new WM-ECO-021 reference + renews-link; old version, old price and old invoices untouched; proration only on the new WM-ECO-008 document.

**Invariants.** An order pins an offer version. A subscription can exist without the next payment. An entitlement, if asserted, is limited by subject and period. Line ordered quantity ≥ sum of line fulfilments unless over-fulfilment is explicit. Fulfilment quantity and invoice quantity are independently constrained. Payment references an invoice, never an order or a grant. One effective subscription version per instrument per instant. Version facts are immutable after effective; change is a successor. Renewal and mid-cycle change are links, not types. A suspended subscription cannot authorise usage. Paid ≠ delivered ≠ entitled ≠ used. A usage event does not create a grant. The profile mints no identities and stores no competing master keys.

**Blockers.** Independent Entitlement identity is unproven; assigning it now over-commits. WM-ECO-022 simultaneously holds entitlement separate and composes it as plan context. Usage has a cited home (WM-FLW-015) but no registered edge from 022. WM-ECO-024 is unverified. WM-ECO-020 subscription specialisation is deferred. Relation ledgers for 020 / 022 / 008 / 009 are empty; neighbour IDs are not canonically registered. Party / account — the entitled subject — sits outside this card. All cited world models are reviewable-drafts under waiver. TMF SID / UBL / CRM-OMS crosswalk and the four test fixtures do not exist. The profile must not remaster grants, quantities, version heads or proration.

Challenge to the profile boundary. A thin identifier-unassigned profile is the right *subject* seam only if it is allowed correspondences plus the invariants above — the EM-COM-04 pattern of a declarative profile with no new runtime identity. This card cannot be a profile-over-one-model: it stitches two published aggregates and references several others. Collapse either way fails. If the profile stores line quantities, version heads or grant balances, it competes with 020 and 022. If it is only a reading list, the card stays a documentation wrapper. Split the work products: the profile names joins and forbids identity collapse; the Entitlement candidate, if retained, is a parked hypothesis, not a profile member with implicit identity. Renewal’s home is the 022 version chain. Proration’s home is 008. Do not let “thin profile + candidate” become two new masters by another name.