@aglyn/aglyn 1.0.0-beta.218 → 1.0.0-beta.220

package/src/lib/app-utils/plan-entitlements.js

@@ -19,6 +19,8 @@ import { isOrgOverrideReasonCode } from "./org-override-reason.js";
 import { PLATFORM_BRAND_NAME, PLATFORM_BRANDING_PROFILE } from "./platform-brand.js";
 import { listPluginFeatures, listPluginSeatAddons, pluginSeatAddon } from "../plugin-manager/plugin-entitlements.js";
 import { pluginOrgCapacity } from "../plugin-manager/plugin-org-capacity.js";
+import { declaredMeterReading, pluginCostAxes, pluginCostAxisFields } from "../plugin-manager/plugin-usage-axes.js";
+import { planQuotaOf, pluginPlanFeatureRow, pluginPlanQuotaRow, pluginPlanQuotas } from "../plugin-manager/plugin-plan-entitlements.js";
 /** Sentinel for quotas a plan does not cap; `checkQuota` always allows. */ export const UNLIMITED = Number.POSITIVE_INFINITY;
 /**
  * How many saved form definitions one site may hold, on every plan that can
@@ -159,78 +161,6 @@ import { pluginOrgCapacity } from "../plugin-manager/plugin-org-capacity.js";
  * without moving the figure every other agreement is measured against — the
  * same mechanism every numeric entitlement uses.
  */ export const ENTERPRISE_EMAIL_SENDS_PER_MONTH = 260000;
-/**
- * Aglyn Assist credits an Enterprise agreement includes per month, before the
- * contract says otherwise.
- *
- * ## Never `UNLIMITED`, and the reason is not stylistic
- *
- * `UNLIMITED` is `Number.POSITIVE_INFINITY`, `JSON.stringify(Infinity)` is
- * `null`, and `Number(null)` is `0`. An unbounded assist band therefore
- * serialises to a band of ZERO through every route that does not also send
- * the explicit flag `restoreQuotaLimit` rebuilds from — which would hand the
- * only customers with a signed contract the one budget that refuses
- * everything. A finite number crosses the wire as itself.
- *
- * The band is also a real liability rather than a capacity we already own.
- * Storage and page views are infrastructure metered into the deal; assist is
- * a per-token charge from a third party, and generative building spends it in
- * units two orders of magnitude apart.
- *
- * ## Why this number
- *
- * Enterprise carries no list price, so the band cannot be sized the way every
- * self-serve tier's is — against what that tier's other cost terms leave out
- * of a known price. It is anchored to the top of the ladder instead: 116,000
- * credits is twice Agency's band, the rule every Enterprise fallback follows
- * since the 2026-09-07 pricing decision (see the `enterprise` row of
- * `PLAN_ENTITLEMENTS`). In cost that is $116 of provider spend a month, or
- * under 9% of any deal priced at or above the self-serve top. A deal below
- * that is sold as Agency, not written as an Enterprise agreement.
- *
- * ## It is a DEFAULT, and a contract raises it
- *
- * `resolveOrgEntitlements` applies a per-org `entitlements.assistCreditsPerMonth`
- * override ahead of this, so a deal that buys more assist buys it on that org
- * without moving the figure every other agreement is measured against — the
- * same mechanism the other contracted bands use.
- */ export const ENTERPRISE_ASSIST_CREDITS_PER_MONTH = 116000;
-/**
- * The Free AI taste (AGL-2925): the assist credits a Free workspace draws
- * on each month, behind a hard wall.
- *
- * ## Why it exists
- *
- * So the AI landing pages can say "generate your first page free" and mean
- * it. Three hundred credits is one or two generated sections or a handful
- * of copy rewrites — enough to see what the assistant does, not enough to
- * build a site on. The band is a WALL: `PLAN_PRICING.free
- * .extraAssistCreditsUsdPer1k` stays `null`, so `assistBandRefuses` answers
- * true and the reservation refuses at 100% with no overage, no switch and no
- * invoice. Nothing about a Free workspace can produce a charge.
- *
- * ## What it costs, and why that is the number
- *
- * A credit is `ASSIST_CREDIT_COST_USD` of provider spend, so the band costs
- * at most **$0.30 per Free workspace per month** — asserted by
- * `apps/console/specs/tier-margin-floor.spec.ts`. It is the one AI band with
- * no invoice behind it, which is why the same issue closes every multiplier
- * a script could use before the flag flips:
- *
- *  - it is metered per ACCOUNT as well as per workspace, so the three free
- *    workspaces an account may hold (AGL-2265) share one 300-credit
- *    allowance rather than tripling it (`reserveAssistMessage`);
- *  - a fresh account waits `AI_FREE_MIN_ACCOUNT_AGE_HOURS` before it can
- *    spend, and every free request is bounded per IP, per uid and per
- *    account per day;
- *  - a platform-wide daily ceiling on free spend pauses the taste for
- *    everyone until the UTC day rolls, paid workspaces untouched.
- *
- * The account allowance reads THIS constant rather than the workspace's
- * resolved band, because a staff override that widens one workspace's band
- * is a decision about that workspace, not about how much one person may
- * draw across all of theirs.
- */ export const FREE_AI_TASTE_CREDITS_PER_MONTH = 300;
 export const PLAN_ENTITLEMENTS = {
     free: {
         hostLimit: 1,
@@ -243,7 +173,6 @@ export const PLAN_ENTITLEMENTS = {
         maxManagersPerOrg: 1,
         maxMembersPerHost: 1,
         bandwidthGb: 2,
-        formSubmissionsPerMonth: 20,
         // No saved-form CATALOG on Free: the form entity rides
         // `reusableComponents`, which is Starter-and-above, so
         // `/api/hosts/resources` refuses the create on the entitlement before it
@@ -260,22 +189,11 @@ export const PLAN_ENTITLEMENTS = {
         variablesPerHost: 3,
         functionsPerHost: 1,
         workflowsPerHost: 0,
-        workflowRunsPerMonth: 0,
         servicesPerHost: 0,
         redirectsPerHost: 0,
         contactsPerHost: 100,
-        // No one-to-one email on Free, which has no CRM (below): the send lives
-        // on a record's page, and Free opens no record. Zero here is what
-        // `checkCrmEmailQuota` refuses
-        // against, so a per-org grant of `features.crm` alone still sends
-        // nothing until the band is raised with it.
-        crmEmailsPerDay: 0,
         emailSendsPerMonth: 0,
         actionRunsPerMonth: 0,
-        // The Free AI taste (AGL-2925): a real band, and a wall. See the
-        // constant for what it buys, what it costs and the precautions that
-        // keep one person from drawing it three times over.
-        assistCreditsPerMonth: FREE_AI_TASTE_CREDITS_PER_MONTH,
         apiRequestsPerMonth: 0,
         datasetsPerOrg: 0,
         maxDatasetsPerOrg: 0,
@@ -286,11 +204,6 @@ export const PLAN_ENTITLEMENTS = {
         posRegisters: 0,
         transactionFeePhysicalPct: 0,
         transactionFeeDigitalPct: 0,
-        // Marketplace take rate (AGL-46/1543): free-plan sellers pay a higher
-        // share. `marketplaceSelling` is false here, so this rate only prices
-        // an org GRANTED selling via a per-org feature override — and any org
-        // whose dead subscription resolved it down to free.
-        marketplaceFeePct: 30,
         features: {
             abTesting: false,
             versioning: false,
@@ -308,10 +221,9 @@ export const PLAN_ENTITLEMENTS = {
             dedicatedSendingDomain: false,
             removeBranding: false,
             scheduledPublishing: false,
-            marketplaceSelling: false,
             // The two AI flags point opposite ways on Free, on purpose (AGL-2925).
             // `aiAssist` is the guided rung of the console assistant — page-aware
-            // level-2 answers and the copy assistant — and stays Pro and up; Free
+            // level-2 answers and the copy assistant — and starts at Starter; Free
             // keeps the docs-grounded level-1 chat it always had. `aiGenerative`
             // is the generative door the taste is FOR: a Free workspace may
             // generate against its 300-credit band, behind the wall and every
@@ -364,13 +276,10 @@ export const PLAN_ENTITLEMENTS = {
             marketingOverlays: false,
             commerce: false,
             pos: false,
-            storefrontSubscriptions: false,
             contentGating: false,
-            giftCards: false,
             productReviews: false,
             abandonedCart: false,
             dropshipRouting: false,
-            commerceAnalytics: false,
             whiteLabel: false,
             ssoEnabled: false
         }
@@ -385,24 +294,15 @@ export const PLAN_ENTITLEMENTS = {
         managersPerOrg: 2,
         maxManagersPerOrg: 5,
         maxMembersPerHost: 10,
-        bandwidthGb: 50,
-        formSubmissionsPerMonth: 200,
+        // Sized by the same annual-price invariant as Pro's — see that band.
+        bandwidthGb: 20,
         formsPerHost: FORMS_PER_HOST_CEILING,
         variablesPerHost: 25,
         functionsPerHost: 10,
         workflowsPerHost: 3,
-        workflowRunsPerMonth: 500,
         servicesPerHost: 1,
         redirectsPerHost: 25,
         contactsPerHost: 1000,
-        // One-to-one email from a CRM record, per UTC day (AGL-2611). A hard
-        // daily pace rather than a monthly meter — see `crmEmailsPerDay` on
-        // `OrgEntitlements` — sized so the whole day spent at $0.0009 a message
-        // leaves the tier's CRM axis inside the 20% cost share the Drive
-        // pricing decision of 2026-09-05 sets. 50 a day is $1.35 a month against
-        // a $16 annual price. Every send still lands on the `emailSends` cost
-        // meter beside the transactional mail this tier already sends.
-        crmEmailsPerDay: 50,
         // Campaign email starts at Pro. A site that may send campaigns needs its
         // own verified provider sending domain, and provisioning one is a real
         // per-site operational cost that a campaign allowance commits the platform
@@ -424,50 +324,6 @@ export const PLAN_ENTITLEMENTS = {
         // to it, and the CRM is what a Starter site builds before it upgrades.
         emailSendsPerMonth: 0,
         actionRunsPerMonth: 0,
-        // The first paid rung of the assist ladder (AGL-3203). Starter banded at
-        // 0 until 2026-09-20, which put a PAYING workspace below the Free taste's
-        // 300 on the one axis a visitor compares straight down the column — the
-        // `/pricing` row read `300 / mo` for Free and `—` for Starter. A paid
-        // plan that includes less of something than the free plan is not a
-        // packaging subtlety; it is the comparison table arguing against the
-        // upgrade.
-        //
-        // 750 is deliberately small: 2.5x the taste, enough that the assistant is
-        // a thing the tier HAS rather than a thing it is shown, and $0.75 of
-        // provider spend a month at `ASSIST_CREDIT_COST_USD` against a $16 annual
-        // price — a twentieth of the $8.81 the tier's other metered bands already
-        // cost, and the widest margin on the ladder absorbs it with room left
-        // (`tier-margin-floor.spec.ts` carries the arithmetic).
-        //
-        // It is NOT a wall, unlike Free's: `PLAN_PRICING.starter
-        // .extraAssistCreditsUsdPer1k` is $3.00, so past 750 the tier meters and
-        // bills like every paid plan above it. The two fields move together by
-        // rule — a positive band with no rate beside it is usage past a bound
-        // that is silently free, which `plan-entitlements.spec.ts` forbids.
-        //
-        // `features.aiAssist` is TRUE, and AGL-3203 shipping it false was the
-        // defect AGL-3207 closes. The reasoning then was "the band is credits,
-        // not the guided rung, exactly as on Free" — but on Free the band IS
-        // spendable, through `aiGenerative`, which is the door the taste exists
-        // for. Starter carried neither flag, so it was the only row on the
-        // ladder sold a band with nothing to spend it through: 750 credits
-        // reachable only by buying the $9 add-on that was also the only thing
-        // that made them usable. "No plan bands at zero any more" was true of
-        // the number and false of the capability.
-        //
-        // It opens `aiAssist` rather than `aiGenerative` because that is the
-        // shape of every paid rung above it — the included band funds the guided
-        // assistant and generation is the add-on. Opening the generative door
-        // here instead would hand the FIRST paid rung a door Pro through Agency
-        // have to buy.
-        //
-        // No cost moves: `tier-margin-floor.spec.ts` already prices this tier's
-        // assist term at 100% burn of the 750 credits, 75¢/mo. A door does not
-        // widen a band; it only makes spend that was already modeled reachable.
-        //
-        // The AI add-on adds `AI_ADDON_CREDITS_PER_MONTH.starter` on top and
-        // switches `aiGenerative` on as well.
-        assistCreditsPerMonth: 750,
         apiRequestsPerMonth: 0,
         datasetsPerOrg: 3,
         maxDatasetsPerOrg: 10,
@@ -482,7 +338,6 @@ export const PLAN_ENTITLEMENTS = {
         // norm (Wix/BigCommerce/Squarespace-Core = 0% platform fee). See the
         // Pricing Decision Log + Competitive Benchmark.
         transactionFeeDigitalPct: 5,
-        marketplaceFeePct: 20,
         features: {
             abTesting: false,
             versioning: false,
@@ -500,7 +355,6 @@ export const PLAN_ENTITLEMENTS = {
             dedicatedSendingDomain: false,
             removeBranding: true,
             scheduledPublishing: false,
-            marketplaceSelling: false,
             aiAssist: true,
             aiGenerative: false,
             workflows: true,
@@ -527,13 +381,10 @@ export const PLAN_ENTITLEMENTS = {
             marketingOverlays: true,
             commerce: true,
             pos: false,
-            storefrontSubscriptions: false,
             contentGating: false,
-            giftCards: false,
             productReviews: false,
             abandonedCart: false,
             dropshipRouting: false,
-            commerceAnalytics: false,
             whiteLabel: false,
             ssoEnabled: false
         }
@@ -548,36 +399,35 @@ export const PLAN_ENTITLEMENTS = {
         managersPerOrg: 5,
         maxManagersPerOrg: 20,
         maxMembersPerHost: 25,
-        // Page views are the largest term of this tier's modeled COGS — one GB
-        // is 1,035 views at `ESTIMATED_PAGE_TRANSFER_BYTES`, or $0.167 of
-        // measured cost — so the bandwidth band is what decides whether the tier
-        // survives a customer spending the whole allowance it was sold.
+        // Page views are the largest term of this tier's modeled COGS. One GB is
+        // 1,035 views at `ESTIMATED_PAGE_TRANSFER_BYTES`, priced where the CDN is
+        // dearest because it bills in the region that serves a visitor: $0.367 of
+        // weight (`perPageView`, transfer at $0.35 a GB) and $0.190 of CDN
+        // requests once the hosting plan's monthly allowance is spent
+        // (`PAGE_VIEW_CDN_REQUEST_COST_USD`, $3.20 per million). So a GB of
+        // included bandwidth costs $0.557, and the bandwidth band is what decides
+        // whether the tier survives a customer spending the whole allowance it
+        // was sold.
         //
         // The invariant the band is sized against is the ANNUAL price ($39 a
         // month) net of Stripe's fee, with every band at 100% and the CRM seat
-        // and one-to-one email terms counted — the 2026-09-07 pricing decision.
-        // At 225 GB that price was 44% under water; 125 GB is what it carries.
+        // and one-to-one email terms counted — the 2026-09-07 pricing decision —
+        // at that all-in gigabyte (AGL-3444). 35 GB is what it carries; every
+        // paid band on the ladder is sized the same way.
         // `tier-margin-floor.spec.ts` holds the model and pins the figure.
         //
         // `meteredInfraPassThrough` is true here, so traffic past the band BILLS
         // at the page-view pass-through rather than being refused or absorbed.
-        bandwidthGb: 125,
-        formSubmissionsPerMonth: 1000,
+        bandwidthGb: 35,
         formsPerHost: FORMS_PER_HOST_CEILING,
         variablesPerHost: 100,
         functionsPerHost: 50,
         workflowsPerHost: 25,
-        workflowRunsPerMonth: 5000,
         servicesPerHost: UNLIMITED,
         redirectsPerHost: 100,
         contactsPerHost: 10000,
-        crmEmailsPerDay: 150,
         emailSendsPerMonth: 5000,
         actionRunsPerMonth: 5000,
-        // $2.75 of provider spend, against the $8.35 the tier's other seven cost
-        // terms leave out of $56. See `OrgEntitlements.assistCreditsPerMonth` for
-        // why the remainder and not the price is what sizes this.
-        assistCreditsPerMonth: 2750,
         apiRequestsPerMonth: 0,
         datasetsPerOrg: 15,
         maxDatasetsPerOrg: 50,
@@ -590,7 +440,6 @@ export const PLAN_ENTITLEMENTS = {
         // Pricing v3 (2026-07): softened 5→3 to smooth the digital fee ladder
         // (Starter 5 → Pro 3 → Business 2 → Scale 1 → Advanced/Agency 0).
         transactionFeeDigitalPct: 3,
-        marketplaceFeePct: 20,
         features: {
             abTesting: false,
             versioning: true,
@@ -621,7 +470,6 @@ export const PLAN_ENTITLEMENTS = {
             dedicatedSendingDomain: true,
             removeBranding: true,
             scheduledPublishing: false,
-            marketplaceSelling: true,
             aiAssist: true,
             aiGenerative: false,
             workflows: true,
@@ -643,13 +491,10 @@ export const PLAN_ENTITLEMENTS = {
             marketingOverlays: true,
             commerce: true,
             pos: true,
-            storefrontSubscriptions: false,
             contentGating: false,
-            giftCards: false,
             productReviews: true,
             abandonedCart: true,
             dropshipRouting: true,
-            commerceAnalytics: true,
             whiteLabel: false,
             ssoEnabled: false
         }
@@ -665,21 +510,16 @@ export const PLAN_ENTITLEMENTS = {
         maxManagersPerOrg: 100,
         maxMembersPerHost: 100,
         // Sized by the same annual-price invariant as Pro's — see that band.
-        bandwidthGb: 185,
-        formSubmissionsPerMonth: 8000,
+        bandwidthGb: 55,
         formsPerHost: FORMS_PER_HOST_CEILING,
         variablesPerHost: 1000,
         functionsPerHost: 250,
         workflowsPerHost: 100,
-        workflowRunsPerMonth: 50000,
         servicesPerHost: UNLIMITED,
         redirectsPerHost: UNLIMITED,
         contactsPerHost: 50000,
-        crmEmailsPerDay: 200,
         emailSendsPerMonth: 25000,
         actionRunsPerMonth: 50000,
-        // $7.50, against the $22.69 the other seven terms leave out of $139.
-        assistCreditsPerMonth: 7500,
         apiRequestsPerMonth: 100000,
         datasetsPerOrg: 100,
         maxDatasetsPerOrg: 250,
@@ -690,7 +530,6 @@ export const PLAN_ENTITLEMENTS = {
         posRegisters: 2,
         transactionFeePhysicalPct: 0,
         transactionFeeDigitalPct: 2,
-        marketplaceFeePct: 20,
         features: {
             abTesting: true,
             versioning: true,
@@ -700,7 +539,6 @@ export const PLAN_ENTITLEMENTS = {
             dedicatedSendingDomain: true,
             removeBranding: true,
             scheduledPublishing: true,
-            marketplaceSelling: true,
             aiAssist: true,
             aiGenerative: false,
             workflows: true,
@@ -722,13 +560,10 @@ export const PLAN_ENTITLEMENTS = {
             marketingOverlays: true,
             commerce: true,
             pos: true,
-            storefrontSubscriptions: true,
             contentGating: true,
-            giftCards: true,
             productReviews: true,
             abandonedCart: true,
             dropshipRouting: true,
-            commerceAnalytics: true,
             whiteLabel: false,
             ssoEnabled: false
         }
@@ -746,21 +581,17 @@ export const PLAN_ENTITLEMENTS = {
         managersPerOrg: 25,
         maxManagersPerOrg: 150,
         maxMembersPerHost: 150,
-        bandwidthGb: 290,
-        formSubmissionsPerMonth: 25000,
+        // Sized by the same annual-price invariant as Pro's — see that band.
+        bandwidthGb: 90,
         formsPerHost: FORMS_PER_HOST_CEILING,
         variablesPerHost: 5000,
         functionsPerHost: 500,
         workflowsPerHost: 250,
-        workflowRunsPerMonth: 150000,
         servicesPerHost: UNLIMITED,
         redirectsPerHost: UNLIMITED,
         contactsPerHost: 100000,
-        crmEmailsPerDay: 300,
         emailSendsPerMonth: 40000,
         actionRunsPerMonth: 100000,
-        // $10.00, against the $30.62 the other seven terms leave out of $249.
-        assistCreditsPerMonth: 10000,
         apiRequestsPerMonth: 300000,
         datasetsPerOrg: 250,
         maxDatasetsPerOrg: 500,
@@ -771,7 +602,6 @@ export const PLAN_ENTITLEMENTS = {
         posRegisters: 3,
         transactionFeePhysicalPct: 0,
         transactionFeeDigitalPct: 1,
-        marketplaceFeePct: 20,
         features: {
             abTesting: true,
             versioning: true,
@@ -781,7 +611,6 @@ export const PLAN_ENTITLEMENTS = {
             dedicatedSendingDomain: true,
             removeBranding: true,
             scheduledPublishing: true,
-            marketplaceSelling: true,
             aiAssist: true,
             aiGenerative: false,
             workflows: true,
@@ -803,13 +632,10 @@ export const PLAN_ENTITLEMENTS = {
             marketingOverlays: true,
             commerce: true,
             pos: true,
-            storefrontSubscriptions: true,
             contentGating: true,
-            giftCards: true,
             productReviews: true,
             abandonedCart: true,
             dropshipRouting: true,
-            commerceAnalytics: true,
             whiteLabel: false,
             ssoEnabled: false
         }
@@ -824,23 +650,17 @@ export const PLAN_ENTITLEMENTS = {
         managersPerOrg: 50,
         maxManagersPerOrg: 250,
         maxMembersPerHost: 250,
-        bandwidthGb: 345,
-        formSubmissionsPerMonth: 40000,
+        // Sized by the same annual-price invariant as Pro's — see that band.
+        bandwidthGb: 105,
         formsPerHost: FORMS_PER_HOST_CEILING,
         variablesPerHost: UNLIMITED,
         functionsPerHost: 1000,
         workflowsPerHost: 500,
-        workflowRunsPerMonth: 500000,
         servicesPerHost: UNLIMITED,
         redirectsPerHost: UNLIMITED,
         contactsPerHost: 150000,
-        crmEmailsPerDay: 500,
         emailSendsPerMonth: 65000,
         actionRunsPerMonth: 250000,
-        // $13.00, against the $39.74 the other seven terms leave out of $399 —
-        // the thinnest remainder on the ladder, and the tier that binds the
-        // whole assist ladder's share of it.
-        assistCreditsPerMonth: 13000,
         apiRequestsPerMonth: 1000000,
         datasetsPerOrg: 500,
         maxDatasetsPerOrg: 1000,
@@ -851,7 +671,6 @@ export const PLAN_ENTITLEMENTS = {
         posRegisters: 5,
         transactionFeePhysicalPct: 0,
         transactionFeeDigitalPct: 0,
-        marketplaceFeePct: 20,
         features: {
             abTesting: true,
             versioning: true,
@@ -861,7 +680,6 @@ export const PLAN_ENTITLEMENTS = {
             dedicatedSendingDomain: true,
             removeBranding: true,
             scheduledPublishing: true,
-            marketplaceSelling: true,
             aiAssist: true,
             aiGenerative: false,
             workflows: true,
@@ -883,13 +701,10 @@ export const PLAN_ENTITLEMENTS = {
             marketingOverlays: true,
             commerce: true,
             pos: true,
-            storefrontSubscriptions: true,
             contentGating: true,
-            giftCards: true,
             productReviews: true,
             abandonedCart: true,
             dropshipRouting: true,
-            commerceAnalytics: true,
             whiteLabel: false,
             ssoEnabled: false
         }
@@ -908,33 +723,17 @@ export const PLAN_ENTITLEMENTS = {
         managersPerOrg: 100,
         maxManagersPerOrg: 500,
         maxMembersPerHost: 1000,
-        bandwidthGb: 1540,
-        // FINITE, where every other capacity row on this tier is unbounded.
-        // `formSubmissionsPerMonth` is multiplied by `hostLimit` to get the
-        // org-wide band, so at 100 hosts an unbounded figure was not merely
-        // large — it made this tier's cost model unbounded, and an unbounded
-        // term reads as ZERO in any analysis that scores an absent band as
-        // nothing. That is how it stayed invisible: the biggest line item on the
-        // most expensive self-serve plan, contributing 0 to every total.
-        //
-        // Metering makes it safe to bound. `meteredInfraPassThrough` is true
-        // here, so submissions past the band BILL at the pass-through rate
-        // rather than being refused — a merchant's lead form does not stop
-        // working at 25,000.
-        formSubmissionsPerMonth: 25000,
+        // Sized by the same annual-price invariant as Pro's — see that band.
+        bandwidthGb: 485,
         formsPerHost: FORMS_PER_HOST_CEILING,
         variablesPerHost: UNLIMITED,
         functionsPerHost: UNLIMITED,
         workflowsPerHost: UNLIMITED,
-        workflowRunsPerMonth: 2000000,
         servicesPerHost: UNLIMITED,
         redirectsPerHost: UNLIMITED,
         contactsPerHost: 500000,
-        crmEmailsPerDay: 1000,
         emailSendsPerMonth: 130000,
         actionRunsPerMonth: 1000000,
-        // $58.00, against the $176.71 the other seven terms leave out of $1,299.
-        assistCreditsPerMonth: 58000,
         apiRequestsPerMonth: 5000000,
         datasetsPerOrg: 2000,
         maxDatasetsPerOrg: 5000,
@@ -945,7 +744,6 @@ export const PLAN_ENTITLEMENTS = {
         posRegisters: 20,
         transactionFeePhysicalPct: 0,
         transactionFeeDigitalPct: 0,
-        marketplaceFeePct: 20,
         features: {
             abTesting: true,
             versioning: true,
@@ -955,7 +753,6 @@ export const PLAN_ENTITLEMENTS = {
             dedicatedSendingDomain: true,
             removeBranding: true,
             scheduledPublishing: true,
-            marketplaceSelling: true,
             aiAssist: true,
             aiGenerative: false,
             workflows: true,
@@ -977,13 +774,10 @@ export const PLAN_ENTITLEMENTS = {
             marketingOverlays: true,
             commerce: true,
             pos: true,
-            storefrontSubscriptions: true,
             contentGating: true,
-            giftCards: true,
             productReviews: true,
             abandonedCart: true,
             dropshipRouting: true,
-            commerceAnalytics: true,
             // White-Label Phase 1: the Agency-tier ($1,299) differentiator. Only
             // this tier and Enterprise ship white-label by default.
             whiteLabel: true,
@@ -1039,25 +833,16 @@ export const PLAN_ENTITLEMENTS = {
         managersPerOrg: 200,
         maxManagersPerOrg: 1000,
         maxMembersPerHost: 2000,
-        bandwidthGb: 3080,
-        formSubmissionsPerMonth: 50000,
+        bandwidthGb: 970,
         formsPerHost: FORMS_PER_HOST_CEILING,
         variablesPerHost: UNLIMITED,
         functionsPerHost: UNLIMITED,
         workflowsPerHost: UNLIMITED,
-        workflowRunsPerMonth: 4000000,
         servicesPerHost: UNLIMITED,
         redirectsPerHost: UNLIMITED,
         contactsPerHost: 1000000,
-        // Finite like the campaign allowance beside it, and for the same reason
-        // one-to-one mail is capped on every other tier: a rep with a template
-        // and a list can put thousands of messages onto the platform's sending
-        // reputation in an afternoon. A negotiated agreement whose reps need more
-        // than 2,000 a day says so, and the override is what carries it.
-        crmEmailsPerDay: 2000,
         emailSendsPerMonth: ENTERPRISE_EMAIL_SENDS_PER_MONTH,
         actionRunsPerMonth: 2000000,
-        assistCreditsPerMonth: ENTERPRISE_ASSIST_CREDITS_PER_MONTH,
         apiRequestsPerMonth: 10000000,
         datasetsPerOrg: 4000,
         maxDatasetsPerOrg: 10000,
@@ -1068,7 +853,6 @@ export const PLAN_ENTITLEMENTS = {
         posRegisters: 40,
         transactionFeePhysicalPct: 0,
         transactionFeeDigitalPct: 0,
-        marketplaceFeePct: 20,
         features: {
             abTesting: true,
             versioning: true,
@@ -1078,7 +862,6 @@ export const PLAN_ENTITLEMENTS = {
             dedicatedSendingDomain: true,
             removeBranding: true,
             scheduledPublishing: true,
-            marketplaceSelling: true,
             aiAssist: true,
             aiGenerative: true,
             workflows: true,
@@ -1101,13 +884,10 @@ export const PLAN_ENTITLEMENTS = {
             marketingOverlays: true,
             commerce: true,
             pos: true,
-            storefrontSubscriptions: true,
             contentGating: true,
-            giftCards: true,
             productReviews: true,
             abandonedCart: true,
             dropshipRouting: true,
-            commerceAnalytics: true,
             whiteLabel: true,
             // SSO (AGL-1101) is the Enterprise differentiator — the only plan that
             // carries it by default. Lower tiers still need a per-org override.
@@ -1115,6 +895,32 @@ export const PLAN_ENTITLEMENTS = {
         }
     }
 };
+/**
+ * Each plan row gains what the plugins declared for that plan (AGL-3080):
+ * a plugin's own band or gate — the AI credits, the CRM's one-to-one email
+ * pace, the marketplace's take rate — is written beside the reasoning that
+ * sized it, in that plugin's `plan-entitlements` module, and compiled into
+ * `first-party-plugins.generated.ts`. Filled here, once, as the module
+ * loads, so every reader of `PLAN_ENTITLEMENTS` — the pricing tables, the
+ * plan comparison, `resolveOrgEntitlements` — reads one table and cannot tell
+ * which half of a row a figure came from.
+ *
+ * Core's keys keep their order and a plugin's follow them. A key both declare
+ * keeps CORE's figure, so a declaration can never shadow what the platform
+ * already charges; `plan-entitlements.spec.ts` refuses the collision outright.
+ */ function fillPluginPlanEntitlements(rows) {
+    for (const plan of Object.keys(rows)){
+        const quotas = rows[plan];
+        for (const [key, value] of Object.entries(pluginPlanQuotaRow(plan))){
+            if (!(key in quotas)) quotas[key] = value;
+        }
+        const features = rows[plan].features;
+        for (const [key, value] of Object.entries(pluginPlanFeatureRow(plan))){
+            if (!(key in features)) features[key] = value;
+        }
+    }
+}
+fillPluginPlanEntitlements(PLAN_ENTITLEMENTS);
 /**
  * The tiers a customer can buy themselves — every plan EXCEPT `enterprise`
  * (AGL-1118), which is priced per deal and provisioned by staff (AGL-1110).
@@ -1962,6 +1768,74 @@ export const STRIPE_PROCESSOR_FEE_FIXED_USD = 0.3;
  *
  * The console keeps importing it from `usage-metering` unchanged.
  */ export const METERED_MARKUP = 1.3;
+/**
+ * What the CDN requests behind ONE page view cost once the platform is past
+ * its hosting plan's included request allowance, at the DEAREST region the
+ * CDN bills, in USD per view (AGL-1879, AGL-3444). A page view billed past a
+ * plan's band is priced at `(perPageView + this) × METERED_MARKUP` — $0.70
+ * per 1,000 — and every `bandwidthGb` band is sized with it counted.
+ *
+ * ## Why a page view needs a second cost term
+ *
+ * `perPageView` prices what a view WEIGHS: the bytes it transfers at the
+ * CDN's per-GB rate, plus the Firestore reads behind the render. The CDN also
+ * charges per REQUEST once the team's monthly allowance is spent — Vercel Pro
+ * includes 10,000,000 a month, then bills $2.00 to $3.20 per million by
+ * region. A cold load of `aglyn.com/` makes 57 first-party requests to settle
+ * (`tools/tenant-page-budget.json`, `wireCalibration.measuredAgainst`), so the
+ * allowance is about 175,000 views of that page a month, platform-wide —
+ * about 169 GB of included bandwidth — where the 1 TB transfer allowance
+ * lasts about 1.4 million. The request allowance runs out first.
+ *
+ * ## Why the dearest region
+ *
+ * The CDN bills a request, and the bytes it transfers, in the region that
+ * SERVES it — the one nearest the visitor — so a site whose audience is in
+ * São Paulo or Cape Town costs what those regions cost, and nothing about a
+ * plan can choose otherwise. The platform's rule is that no plan is under
+ * water at any utilization and that "at cost + 30%" is true of every billed
+ * unit, so both terms of a page view are priced where the CDN is dearest:
+ * transfer at $0.35 per GB (in `perPageView`) and requests at $3.20 per
+ * million (here). Past the allowance a view then costs:
+ *
+ * |                                   | weight     | requests  | cost / 1k | margin at $0.70 |
+ * |-----------------------------------|------------|-----------|-----------|-----------------|
+ * | the page as measured (748.5 KB)   | $0.262148  | $0.182400 | $0.4445   | +36.5%          |
+ * | the priced basis (1012.8 KB)      | $0.354715  | $0.182400 | $0.5371   | +23.3%          |
+ *
+ * — at least 30% over cost in every region, which is the claim `/pricing`
+ * makes.
+ *
+ * ## The figure
+ *
+ * $0.00018374681 is 57.42 requests at $3.20 per million — the measured 57,
+ * with the basis set ABOVE the measurement as the weight basis is — pinned so
+ * the billed price lands on a whole cent: ($0.354715 + $0.1824) × 1.3 is
+ * $0.6982 per 1,000, rounded up to $0.70, and ($0.354715 + $0.183747) × 1.3
+ * is exactly $0.70. Published as "Our cost $0.538462 / You pay $0.70", the
+ * "at cost + 30%" claim stays true of the cost a billed view incurs in the
+ * dearest region, and so in every other.
+ *
+ * ## ⛔ Not in {@link ORG_COGS_UNIT_RATES_USD}, deliberately
+ *
+ * `perPageView` is half of a pair with `ESTIMATED_PAGE_TRANSFER_BYTES` — one
+ * page weight in dollars and in bytes — and `npm run check:page-view-rate`
+ * recovers that weight from the rate. A per-request charge is not
+ * proportional to weight, so folding it into `perPageView` would make the
+ * gate read a page nobody serves.
+ *
+ * ## The INCLUDED bands carry it too
+ *
+ * A view inside a plan's band makes the same requests as one past it, and
+ * once the platform is past the allowance the CDN bills them either way, so
+ * the `bandwidthGb` bands are sized with this term counted: $0.190 per
+ * included GB on top of $0.367 of weight. `tier-margin-floor.spec.ts`
+ * multiplies it in and pins every tier at 100% of every band.
+ *
+ * Lives HERE, beside the markup, for the reason the markup does: the
+ * `/pricing` generator publishes the cost column from it and cannot import
+ * anything under `apps/console`.
+ */ export const PAGE_VIEW_CDN_REQUEST_COST_USD = 0.00018374681;
 /**
  * Monthly unit costs for the meters the rollup already records (AGL-1134).
  *
@@ -1985,6 +1859,23 @@ export const STRIPE_PROCESSOR_FEE_FIXED_USD = 0.3;
  * infrastructure pass-through, and the customer is charged those figures
  * times `METERED_MARKUP`. They therefore appear in `METERED_UNIT_RATES_USD`
  * as well, with identical values, and must be changed in both places at once.
+ * A page view billed past its band also carries
+ * {@link PAGE_VIEW_CDN_REQUEST_COST_USD}, which neither table holds: it is
+ * the per-request CDN charge past the hosting plan's allowance, and this
+ * table's `perPageView` is the weight-proportional half of what a band is
+ * sized against — the request term is the other.
+ *
+ * ## Every Vercel-billed input is priced at Vercel's dearest region
+ *
+ * The CDN and functions bill by region, from $0.15 to $0.35 per GB of
+ * transfer, $2.00 to $3.20 per million requests, and $0.128 to $0.221 per
+ * hour of active CPU (memory $0.0106 to $0.0183 per GB-hour), and a plan
+ * cannot choose where its visitors are. So the Vercel share of every rate
+ * here is priced at the dearest region (AGL-3444): the transfer inside
+ * `perPageView`, the function invocation inside `perFormSubmission`, and the
+ * compute inside `perRun`. The GCP shares — object and Firestore storage, and
+ * the Firestore reads and writes behind a render, a submission or a run —
+ * are priced as they were.
  *
  * Everything else here is a cost-model input ONLY. `dataStoragePerGbMonth`,
  * `perApiRequest`, `perContactMonth` and `perEmailSend` price what an org
@@ -1994,9 +1885,11 @@ export const STRIPE_PROCESSOR_FEE_FIXED_USD = 0.3;
  * "at cost + 30%" claim, which is true of exactly three meters.
  *
  * The first three were corrected 2026-08-09 (AGL-1280) — storage $0.03 →
- * $0.026 and form submissions $0.0005 → $0.00005 — and `perPageView` was
- * re-pegged 2026-09-09 (AGL-2711), from $0.0001 to $0.00016153846. All three
- * MUST be changed here and in `METERED_UNIT_RATES_USD` together. See that
+ * $0.026 and form submissions $0.0005 → $0.00005 — `perPageView` was
+ * re-pegged 2026-09-09 (AGL-2711), from $0.0001 to $0.00016153846, and the
+ * last two were re-priced at Vercel's dearest region on 2026-10-01
+ * (AGL-3444): page views $0.00035471473, form submissions $0.000053846154.
+ * All three MUST be changed here and in `METERED_UNIT_RATES_USD` together. See that
  * table for each figure's basis; it is the one a customer is billed against,
  * so it is the one that carries the working.
  *
@@ -2016,10 +1909,10 @@ export const STRIPE_PROCESSOR_FEE_FIXED_USD = 0.3;
    * ⛔ HALF OF A PAIR — see ESTIMATED_PAGE_TRANSFER_BYTES, which states the
    * same page in bytes as this states it in dollars. Both are calibrated
    * against a 1012.8 KB page and neither may move alone: their quotient is
-   * the cost of a gigabyte, and that is what every bandwidthGb band on the
-   * ladder was sized against.
-   */ perPageView: 0.00016153846,
-    perFormSubmission: 0.00005,
+   * the cost of a gigabyte's weight, and that — with the request term — is
+   * what every bandwidthGb band on the ladder is sized against.
+   */ perPageView: 0.00035471473,
+    perFormSubmission: 0.000053846154,
     /** Firestore-backed dataset bytes — an order pricier than object storage. */ dataStoragePerGbMonth: 0.18,
     perApiRequest: 0.000002,
     perContactMonth: 0.0002,
@@ -2038,7 +1931,7 @@ export const STRIPE_PROCESSOR_FEE_FIXED_USD = 0.3;
    * both concern a smaller quantity; this is the whole bill.
    */ perEmailSend: 0.0009,
     /**
-   * One workflow or action run — $12 per million.
+   * One workflow or action run — $13 per million.
    *
    * Derived from the run paths at list prices (2026-09-07), because nothing
    * measurable exists yet: runs execute inside the Vercel request that fired
@@ -2057,9 +1950,11 @@ export const STRIPE_PROCESSOR_FEE_FIXED_USD = 0.3;
    *   - writes: the activity row and the counter increment — 2, at $0.18 per
    *     100,000 = $0.0000036
    *   - compute: a few milliseconds of active CPU and memory on Fluid compute
-   *     for the expression evaluation, about $0.000001
+   *     for the expression evaluation, about $0.000001 in the cheapest
+   *     region and $0.0000017 in the dearest ($0.221 against $0.128 an
+   *     hour of active CPU), which is where it is priced
    *
-   * $0.0000118, carried as $0.000012. It scales with the catalog a site holds
+   * $0.0000125, carried as $0.000013. It scales with the catalog a site holds
    * — every `limit(100)` read above is a query that costs one read per
    * document returned — and a step that writes a dataset record or calls a
    * webhook adds to it, so this is the typical figure, not the ceiling.
@@ -2068,8 +1963,24 @@ export const STRIPE_PROCESSOR_FEE_FIXED_USD = 0.3;
    * band on a metered plan. It exists so a tier's run bands reach
    * `orgMonthlyCogsUsd` and `tier-margin-floor.spec.ts` — Agency's 3,000,000
    * runs are $36 a month that read as nothing while this was absent.
-   */ perRun: 0.000012
+   */ perRun: 0.000013
 };
+/**
+ * The unit rate a declared cost axis names, or 1 where it names none (the
+ * rollup already records dollars).
+ *
+ * ⚑ A rate key core does not carry THROWS. Pricing an unknown axis at zero
+ * would make an org cost less than it does, which is the direction that
+ * approves a discount; `plugin-usage-axes.spec.ts` holds every declared key
+ * to a rate that exists, so this is reached only by a tree that skipped it.
+ */ function cogsRateOf(axis) {
+    if (axis.rate === undefined) return 1;
+    const rate = ORG_COGS_UNIT_RATES_USD[axis.rate];
+    if (typeof rate !== 'number' || !Number.isFinite(rate)) {
+        throw new Error(`cost axis "${axis.id}" names the rate "${axis.rate}", which ORG_COGS_UNIT_RATES_USD does not carry`);
+    }
+    return rate;
+}
 /**
  * One org's monthly infrastructure COGS — the single cost model (AGL-1134).
  *
@@ -2094,50 +2005,62 @@ export const STRIPE_PROCESSOR_FEE_FIXED_USD = 0.3;
  * today, and will not until there is real traffic — which is the honest
  * reason to build it now, while nothing depends on the answer.
  */ export function orgMonthlyCogsUsd(rollup, siteCount) {
-    var _ref;
     const num = (value)=>{
         const parsed = Number(value != null ? value : 0);
         return Number.isFinite(parsed) && parsed > 0 ? parsed : 0;
     };
     const rates = ORG_COGS_UNIT_RATES_USD;
-    const breakdown = {
-        storage: num(rollup == null ? void 0 : rollup.storageGb) * rates.storagePerGbMonth,
-        pageViews: num(rollup == null ? void 0 : rollup.pageViews) * rates.perPageView,
-        formSubmissions: num(rollup == null ? void 0 : rollup.formSubmissions) * rates.perFormSubmission,
+    // The platform's own axes, at the positions the plugins' declared axes
+    // interleave with (`order`, a multiple of 10 here). The generator refuses a
+    // declaration that takes one of these ids or positions.
+    const core = [
+        {
+            id: 'storage',
+            order: 10,
+            usd: num(rollup == null ? void 0 : rollup.storageGb) * rates.storagePerGbMonth
+        },
+        {
+            id: 'pageViews',
+            order: 20,
+            usd: num(rollup == null ? void 0 : rollup.pageViews) * rates.perPageView
+        },
         // Megabytes on the doc, gigabytes in the rate — the unit mismatch is in
         // the stored field name, so convert here rather than in each caller.
-        dataStorage: num(rollup == null ? void 0 : rollup.dataStorageMb) / 1024 * rates.dataStoragePerGbMonth,
-        apiRequests: num(rollup == null ? void 0 : rollup.apiRequests) * rates.perApiRequest,
-        // The records band (AGL-2611), under the axis name every breakdown reader
-        // already keys on. `??` and not `||`: a rollup that measured ZERO records
-        // has answered, and must not fall back to a contacts figure from a month
-        // written under the narrower basis.
-        contacts: num((_ref = rollup == null ? void 0 : rollup.crmRecordsCount) != null ? _ref : rollup == null ? void 0 : rollup.contactsCount) * rates.perContactMonth,
+        {
+            id: 'dataStorage',
+            order: 40,
+            usd: num(rollup == null ? void 0 : rollup.dataStorageMb) / 1024 * rates.dataStoragePerGbMonth
+        },
+        {
+            id: 'apiRequests',
+            order: 50,
+            usd: num(rollup == null ? void 0 : rollup.apiRequests) * rates.perApiRequest
+        },
         // Every send, not the overage — the provider bills the first message of
-        // the month as much as the last, so a cost model that started counting at
-        // the plan's included band would report an org that stayed inside its
+        // the month as much as the last, so a cost model that started counting
+        // at the plan's included band would report an org that stayed inside its
         // allowance as free.
-        emailSends: num(rollup == null ? void 0 : rollup.emailSends) * rates.perEmailSend,
-        /*==========================================
-     * AGLYN ASSIST PROVIDER SPEND (AGL-2280).
-     *
-     * Already dollars, so ×1 — see `OrgUsageRollupInput.assistCostUsd`.
-     *
-     * This is the ONE meter on the platform whose unit cost is not a fraction
-     * margin model read it: the discount guardrail priced six meters that
-     * together measured $0.0000054 for the largest real org, and ignored the
-     * only line item that can plausibly clear the $2/site floor on its own.
-     * A 93%-off coupon on an org burning $40/month of tokens rated green.
-     *
-     * It is deliberately NOT in `billedCents` — what an org is charged is a
-     * separate decision with a price sheet behind it. This is what the org
-     * COSTS US, which is the only question the guardrail asks.
-     *=========================================*/ assist: num(rollup == null ? void 0 : rollup.assistCostUsd),
-        // Both run counters on one line: one rate, one cost, whichever builder
-        // produced the run. Unpriced until 2026-09-07 — the two bands were
-        // recorded on every rollup and read as nothing.
-        runs: (num(rollup == null ? void 0 : rollup.workflowRuns) + num(rollup == null ? void 0 : rollup.actionRuns)) * rates.perRun
-    };
+        {
+            id: 'emailSends',
+            order: 70,
+            usd: num(rollup == null ? void 0 : rollup.emailSends) * rates.perEmailSend
+        }
+    ];
+    // Each plugin's meter, priced at the core rate its declaration names — or
+    // at ×1 where the rollup already records dollars, as the AI plugin's
+    // provider spend does.
+    const declared = pluginCostAxes().map((axis)=>({
+            id: axis.id,
+            order: axis.order,
+            usd: declaredMeterReading(rollup, axis) * cogsRateOf(axis)
+        }));
+    const breakdown = Object.fromEntries([
+        ...core,
+        ...declared
+    ].sort((a, b)=>a.order - b.order).map((axis)=>[
+            axis.id,
+            axis.usd
+        ]));
     const measuredUsd = Object.values(breakdown).reduce((sum, x)=>sum + x, 0);
     const floorUsd = Math.max(0, siteCount) * INFRA_COGS_PER_SITE_USD;
     return {
@@ -2165,39 +2088,27 @@ export const STRIPE_PROCESSOR_FEE_FIXED_USD = 0.3;
  * UNITS, because the field names do not all say: `storageGb` and
  * `dataStorageMb` are gigabytes and MEGABYTES respectively (the conversion
  * lives in `orgMonthlyCogsUsd`, with its own test); `pageViews`,
- * `formSubmissions`, `apiRequests` and `emailSends` are counts FOR THE MONTH;
- * `contactsCount` and `crmRecordsCount` are point-in-time levels, not monthly
- * flows.
+ * `apiRequests` and `emailSends` are counts FOR THE MONTH. A plugin's fields
+ * carry the unit its cost-axis declaration states — a monthly count, a
+ * point-in-time level, or dollars.
  */ export function orgCogsInputFrom(source) {
     const read = (field)=>{
         const value = source == null ? void 0 : source[field];
         return value == null ? undefined : value;
     };
-    return {
+    const input = {
         hostCount: read('hostCount'),
         storageGb: read('storageGb'),
         pageViews: read('pageViews'),
-        formSubmissions: read('formSubmissions'),
         dataStorageMb: read('dataStorageMb'),
         apiRequests: read('apiRequests'),
-        contactsCount: read('contactsCount'),
-        // AGL-2611. The band's own figure, forwarded for the reason `assistCostUsd`
-        // is: a projection that drops it prices the CRM at its contacts alone,
-        // which is the direction that approves a discount.
-        crmRecordsCount: read('crmRecordsCount'),
-        companiesCount: read('companiesCount'),
-        dealsCount: read('dealsCount'),
-        emailSends: read('emailSends'),
-        // AGL-2280. Dollars, not a meter — the projection still has to forward it
-        // or the model prices Assist at nothing, which is the direction that
-        // approves a discount.
-        assistCostUsd: read('assistCostUsd'),
-        // Priced since 2026-09-07 (`perRun`); a projection that drops them prices
-        // the org's automations at nothing, the same direction as every other
-        // omission on this list.
-        workflowRuns: read('workflowRuns'),
-        actionRuns: read('actionRuns')
+        emailSends: read('emailSends')
     };
+    // Every field a plugin's cost axis reads or records — forwarded for the
+    // reason the six above are: a projection that drops a priced field prices
+    // the meter at nothing, which is the direction that approves a discount.
+    for (const field of pluginCostAxisFields())input[field] = read(field);
+    return input;
 }
 /**
  * `orgMonthlyCogsUsd` behind an explicit readiness flag (AGL-1134).
@@ -2467,7 +2378,8 @@ function resolvePlan(org) {
  */ export const PRICE_ENTITLEMENT_KEYS = new Set([
     'transactionFeePhysicalPct',
     'transactionFeeDigitalPct',
-    'marketplaceFeePct'
+    // A plugin's percentage of a sale says so in its declaration.
+    ...pluginPlanQuotas().filter((declared)=>declared.price).map((declared)=>declared.key)
 ]);
 /**
  * The entitlements with every band lifted (AGL-3049): `UNLIMITED` on each
@@ -2960,10 +2872,10 @@ function resolvePlan(org) {
     return 0;
 }
 /**
- * Stripe's processing cost on ONE storefront destination charge, in cents
- * (AGL-2152) — the dearest enabled method's percentage plus the fixed 30¢,
- * rounded UP on the percentage so the answer is never a cent short of what
- * Stripe actually debits.
+ * Stripe's processing cost on ONE destination-charge sale, in cents
+ * (AGL-2152) — a storefront order, a booking deposit — the dearest enabled
+ * method's percentage plus the fixed 30¢, rounded UP on the percentage so the
+ * answer is never a cent short of what Stripe actually debits.
  *
  * WHO PAYS THIS. Every storefront charge is a DESTINATION charge:
  * `payment_intent_data[transfer_data][destination]` names the merchant's
@@ -2989,23 +2901,23 @@ function resolvePlan(org) {
  * decides the set — and per AGL-2343 that configuration has `klarna` and
  * `affirm` on beside the card family. Pricing this at the card rate would be
  * wrong exactly on the orders where it cost the most, which is the same
- * reasoning `marketplaceBreakEvenUsd` already applies to the listing floor;
- * these are deliberately the SAME two constants so the two cannot drift.
+ * reasoning the marketplace listing floor applies; both are defined from the
+ * SAME processing constants so the two cannot drift.
  *
  * THE ONE-LINE LEVER. On a card-family order this over-recovers by the spread
  * between the two rates. Pinning `payment_method_types` on the storefront
  * sessions to the card family would make 2.9% the true binding rate, and
- * `STOREFRONT_PROCESSING_PERCENT` below is then the single identifier to
+ * `SALE_PROCESSING_PERCENT` below is then the single identifier to
  * repoint. That is a product decision about which payment methods a storefront
  * offers, not this one; it is recorded on AGL-2152 and in the Pricing Decision
  * Log so it can be taken deliberately.
- */ // `STOREFRONT_PROCESSING_PERCENT` and `STOREFRONT_PROCESSING_FIXED_CENTS` are
-// declared beside the marketplace processing constants they are defined from,
-// further down this file — a `const` cannot be read before its declaration is
-// evaluated, and this function is only ever CALLED, never evaluated at import.
-export function storefrontProcessingCostCents(chargeCents) {
+ */ // `SALE_PROCESSING_PERCENT` and `SALE_PROCESSING_FIXED_CENTS` are declared
+// beside the processing constants they are defined from, further down this
+// file — a `const` cannot be read before its declaration is evaluated, and
+// this function is only ever CALLED, never evaluated at import.
+export function saleProcessingCostCents(chargeCents) {
     if (!Number.isFinite(chargeCents) || chargeCents <= 0) return 0;
-    return Math.ceil(chargeCents * STOREFRONT_PROCESSING_PERCENT / 100) + STOREFRONT_PROCESSING_FIXED_CENTS;
+    return Math.ceil(chargeCents * SALE_PROCESSING_PERCENT / 100) + SALE_PROCESSING_FIXED_CENTS;
 }
 /**
  * The Stripe Connect `application_fee_amount` for ONE storefront sale
@@ -3039,7 +2951,7 @@ export function storefrontProcessingCostCents(chargeCents) {
     // The `Math.max(1, …)` every door already applied: a rate above zero on
     // goods the shopper pays for is a fee however small it rounds to.
     const take = pct > 0 && base > 0 ? Math.max(1, Math.round(base * pct / 100)) : 0;
-    return Math.min(charge, take + storefrontProcessingCostCents(charge));
+    return Math.min(charge, take + saleProcessingCostCents(charge));
 }
 /**
  * Stripe's processing cost on a RECURRING charge of `amountCents`, as the
@@ -3047,7 +2959,7 @@ export function storefrontProcessingCostCents(chargeCents) {
  *
  * A Stripe Subscription accepts no `application_fee_amount` — only
  * `application_fee_percent`, a rate with at most two decimal places — so the
- * fixed 30¢ that `storefrontProcessingCostCents` adds in cents has to be
+ * fixed 30¢ that `saleProcessingCostCents` adds in cents has to be
  * folded into the rate. `(rate × amount + fixed) ÷ amount` is, with the
  * amount cancelled,
  *
@@ -3064,15 +2976,15 @@ export function storefrontProcessingCostCents(chargeCents) {
  * decimal outright, so the only honest direction is over. Integers, because
  * `0.09 * 100` is not `9` in floating point and a percent one ulp above a
  * whole hundredth would round up to the next one. The same two constants as
- * the one-time path, so repointing `STOREFRONT_PROCESSING_PERCENT` moves
+ * the one-time path, so repointing `SALE_PROCESSING_PERCENT` moves
  * both surfaces together. Zero for a charge that is not a charge.
- */ export function storefrontProcessingPassThroughPercent(amountCents) {
+ */ export function saleProcessingPassThroughPercent(amountCents) {
     const amount = Number.isFinite(amountCents) && amountCents > 0 ? Math.round(amountCents) : 0;
     if (amount <= 0) return 0;
-    const rateHundredths = Math.round(STOREFRONT_PROCESSING_PERCENT * 100);
+    const rateHundredths = Math.round(SALE_PROCESSING_PERCENT * 100);
     // 30¢ ÷ amount is a fraction; × 100 makes it a percent, × 100 again makes
     // it hundredths of one.
-    const fixedHundredths = STOREFRONT_PROCESSING_FIXED_CENTS * 10000 / amount;
+    const fixedHundredths = SALE_PROCESSING_FIXED_CENTS * 10000 / amount;
     return Math.min(100, Math.ceil(rateHundredths + fixedHundredths) / 100);
 }
 /**
@@ -3097,7 +3009,7 @@ export function storefrontProcessingCostCents(chargeCents) {
     const amount = Number.isFinite(amountCents) && amountCents > 0 ? Math.round(amountCents) : 0;
     if (amount <= 0) return 0;
     const take = resolveTransactionFeePct(org, productType);
-    const passThrough = storefrontProcessingPassThroughPercent(amount);
+    const passThrough = saleProcessingPassThroughPercent(amount);
     return Math.min(100, (Math.round(take * 100) + Math.round(passThrough * 100)) / 100);
 }
 /**
@@ -3112,8 +3024,23 @@ export function storefrontProcessingCostCents(chargeCents) {
  * conservative direction. A malformed override must never zero the
  * platform's cut.
  */ export function resolveMarketplaceFeePct(org) {
-    const pct = resolveOrgEntitlements(org).marketplaceFeePct;
-    return Number.isFinite(pct) && pct >= 0 && pct <= 100 ? pct : PLAN_ENTITLEMENTS.free.marketplaceFeePct;
+    const pct = takeRatePctOf(resolveOrgEntitlements(org));
+    if (pct !== null) return pct;
+    const fallback = takeRatePctOf(PLAN_ENTITLEMENTS.free);
+    if (fallback !== null) return fallback;
+    // No plan carries a take rate at all: the marketplace plugin's declaration
+    // did not compile in. Pricing a sale at 0% would hand the whole charge to
+    // the seller, so the sale is refused instead.
+    throw new Error(`no plan declares "${TAKE_RATE_KEY}" — the marketplace take rate ` + 'is declared by the marketplace plugin (plugins.config.json)');
+}
+/**
+ * The marketplace take rate's key. Declared by the marketplace plugin
+ * (AGL-3080); read here by key because the storefront and the revenue report
+ * price a marketplace sale from core.
+ */ const TAKE_RATE_KEY = 'marketplaceFeePct';
+/** A row's take rate when it is a usable percentage, else `null`. */ function takeRatePctOf(entitlements) {
+    const pct = entitlements[TAKE_RATE_KEY];
+    return typeof pct === 'number' && Number.isFinite(pct) && pct >= 0 && pct <= 100 ? pct : null;
 }
 /**
  * The marketplace take rate that breaks even LATEST, derived from the plan
@@ -3126,183 +3053,46 @@ export function storefrontProcessingCostCents(chargeCents) {
  * decays into wrong money copy shown to a publisher — the same reason
  * `planGrantingFeature` reads the table instead of a map.
  */ export function bindingMarketplaceFeePct() {
-    return Math.min(...Object.values(PLAN_ENTITLEMENTS).map((plan)=>plan.marketplaceFeePct).filter((pct)=>Number.isFinite(pct) && pct > 0));
+    return Math.min(...Object.values(PLAN_ENTITLEMENTS).map((plan)=>{
+        var _takeRatePctOf;
+        return (_takeRatePctOf = takeRatePctOf(plan)) != null ? _takeRatePctOf : 0;
+    }).filter((pct)=>Number.isFinite(pct) && pct > 0));
 }
 /**
- * What one marketplace sale costs the PLATFORM to process (AGL-2343).
- *
- * NONE OF THESE IS AN AGLYN PRICE. They are Stripe's published US rates and
- * the Texas rate the platform remits, and they exist only as inputs to a
- * figure shown to a publisher while they type. Nothing is billed from them —
- * the charged amounts are `resolveMarketplaceFeePct` and Stripe's own
- * invoicing — so changing one changes a sentence, never a bill.
+ * What one destination-charge sale costs the PLATFORM to process (AGL-2343):
+ * a storefront order, a booking deposit, a marketplace listing. On a
+ * destination charge Stripe debits its fee from the PLATFORM's balance, so
+ * every surface that sells through the platform's account prices its take
+ * against these.
  *
- * WHY THE PLATFORM PAYS THE PROCESSING FEE AT ALL. Marketplace checkout is a
- * DESTINATION charge with a fixed `transfer_data[amount]` and deliberately no
- * `application_fee_amount`, so that the sales tax stays with the platform that
- * owes it (AGL-1544). On a destination charge Stripe debits its fee from the
- * PLATFORM's balance, and it is charged on `amount_total` — the listing price
- * plus the tax added on top of it.
- *
- * So a $1 listing at a 20% take rate is a loss: the buyer pays $1.08, the
- * seller is transferred $0.80, $0.08 is owed to the state, Aglyn keeps $0.20
- * and pays Stripe about $0.33. Net −$0.13.
+ * NONE OF THESE IS AN AGLYN PRICE. They are Stripe's published US rates, and
+ * they exist only as inputs to a platform take and to figures a seller reads;
+ * changing one never changes a price list.
  *
  * THE BNPL RATE IS THE ONE THAT BINDS, and it is not hypothetical: the live
  * default payment method configuration has `klarna` and `affirm` enabled
- * alongside `card`, `cashapp`, `link`, `amazon_pay` and `apple_pay`, and the
- * marketplace session pins no `payment_method_types`, so a buyer may pay by
- * either. Break-even is computed from the dearest enabled method, because a
- * figure computed from the cheapest would be wrong exactly when it mattered.
- * IF BNPL IS EVER TURNED OFF FOR MARKETPLACE SESSIONS, this constant is what
- * has to move with it.
- */ export const MARKETPLACE_PROCESSING_PERCENT_CARD = 2.9;
-/** Klarna/Affirm, roughly. See the note above — this is the binding one. */ export const MARKETPLACE_PROCESSING_PERCENT_BNPL = 6;
-/** Stripe's per-transaction fixed component, in cents. */ export const MARKETPLACE_PROCESSING_FIXED_CENTS = 30;
-/**
- * The tax rate the break-even figure assumes. Tax is added ON TOP of the
- * listing price and enlarges the base Stripe charges its percentage against,
- * so it makes the platform's cost slightly worse; the real rate is whatever
- * `automatic_tax` computes for the buyer's address, and this is the
- * platform's own Texas rate as a representative figure.
- */ export const MARKETPLACE_ASSUMED_TAX_PERCENT = 8.25;
-/**
- * The processing rate a STOREFRONT destination charge is priced against
- * (AGL-2152), and the one identifier to repoint if the storefront's payment
- * method set changes.
- *
- * Deliberately its OWN name rather than a direct use of the marketplace
- * constants, while being defined as one of them: the two surfaces share
- * Stripe's published rates and today share the platform's payment method
- * configuration, but they are separate product decisions. A future choice to
- * pin `payment_method_types` on storefront sessions to the card family — and
- * so to recover at `MARKETPLACE_PROCESSING_PERCENT_CARD` — must not silently
- * lower the marketplace listing floor, which is derived from the same figure
- * for a different flow.
- */ export const STOREFRONT_PROCESSING_PERCENT = MARKETPLACE_PROCESSING_PERCENT_BNPL;
-/** Stripe's per-transaction fixed component, in cents. Not rate-dependent. */ export const STOREFRONT_PROCESSING_FIXED_CENTS = MARKETPLACE_PROCESSING_FIXED_CENTS;
-/**
- * The funds flow for one sale, mirroring what `checkout.ts` actually builds
- * (AGL-2343): tax exclusive and on top, a fixed transfer of the seller's share
- * of the PRE-tax price, and Stripe's fee charged on the buyer's total.
- */ export function marketplaceSaleEconomics(priceUsd, feePercent, processingPercent = MARKETPLACE_PROCESSING_PERCENT_BNPL) {
-    const priceCents = Math.max(0, Math.round(priceUsd * 100));
-    const taxCents = Math.round(priceCents * MARKETPLACE_ASSUMED_TAX_PERCENT / 100);
-    const buyerPaysCents = priceCents + taxCents;
-    const platformFeeCents = Math.round(priceCents * feePercent / 100);
-    const sellerReceivesCents = priceCents - platformFeeCents;
-    // A zero-price listing takes no payment at all, so there is no fee to pay.
-    const processingCents = priceCents === 0 ? 0 : Math.round(buyerPaysCents * processingPercent / 100 + MARKETPLACE_PROCESSING_FIXED_CENTS);
-    return {
-        priceCents,
-        taxCents,
-        buyerPaysCents,
-        sellerReceivesCents,
-        platformFeeCents,
-        processingCents,
-        platformNetCents: platformFeeCents - processingCents
-    };
-}
-/**
- * The cheapest WHOLE-DOLLAR price at which the platform does not lose money on
- * a sale (AGL-2343).
- *
- * Whole dollars because every publish route rounds `priceUsd` to one, so a
- * fractional break-even is not a price anyone can actually set. Searched
- * rather than solved algebraically so that it can never disagree with
- * `marketplaceSaleEconomics` — the rounding in there is what decides the
- * answer at these amounts, and a closed form would drift from it silently.
- *
- * THIS IS THE ENFORCED FLOOR: `marketplaceMinPriceUsd` returns this figure
- * and every publish door refuses a paid listing under it. Recorded in the Pricing
- * Decision Log and on AGL-2343.
- */ export function marketplaceBreakEvenUsd(feePercent = bindingMarketplaceFeePct(), processingPercent = MARKETPLACE_PROCESSING_PERCENT_BNPL) {
-    // The listing price ceiling is the marketplace plugin's
-    // `MARKETPLACE_MAX_PRICE_USD`, which this library may not import (an app-tier
-    // lib cannot depend on an addon). The loop only needs SOME bound, and the
-    // answer is single digits at every rate the table holds, so a generous local
-    // one costs nothing and cannot drift into a wrong figure.
-    const searchCeilingUsd = 1000;
-    for(let priceUsd = 1; priceUsd <= searchCeilingUsd; priceUsd += 1){
-        if (marketplaceSaleEconomics(priceUsd, feePercent, processingPercent).platformNetCents >= 0) {
-            return priceUsd;
-        }
-    }
-    return searchCeilingUsd;
-}
-/**
- * THE MINIMUM PRICE a paid marketplace listing may carry (AGL-2343).
- *
- * The floor is not a chosen round number — it is the break-even price itself,
- * the
- * cheapest whole dollar at which `marketplaceSaleEconomics` stops returning a
- * negative platform net, computed at the take rate that breaks even LATEST and
- * the dearest payment method the live configuration enables. Today that is $3.
- *
- * DERIVED, NEVER RESTATED. A second hand-written copy of this number in a
- * publish route or a form is the artifact that decays into a route refusing a
- * price a form invited, so both the server-side validator
- * (`MARKETPLACE_MIN_PRICE_USD` in the marketplace model) and every price field
- * read this. If the payment method set changes, or the plan table's lowest
- * take rate moves, the floor moves with them on the next call.
- *
- * ZERO IS NOT BELOW THE FLOOR. A free listing takes no payment at all, so it
- * costs nothing to process; the floor is a minimum on PAID listings only.
- */ export function marketplaceMinPriceUsd() {
-    return marketplaceBreakEvenUsd();
-}
-/**
- * Whether a price is a PAID price that the floor refuses (AGL-2343) — the one
- * predicate a form uses to mark its price field in error and hold its publish
- * button, so that the button and the server agree about what is publishable.
- *
- * Rounds first because every publish route does, and a form's value is a
- * string mid-type: `'2.6'` is stored as $3 and must read as allowed here, or
- * the button would refuse a price the route accepts.
- */ export function isBelowMarketplacePriceFloor(priceUsd) {
-    const price = Math.round(Number(priceUsd) || 0);
-    return price > 0 && price < marketplaceMinPriceUsd();
-}
-/**
- * The sentence a publish form shows under its price field when the price is
- * below the floor (AGL-2343), or `undefined` when there is nothing to say.
- *
- * NOT ADVISORY ANY MORE. The same figure is enforced by every publish route
- * through `publishPreconditionRefusal`, so this text has to read as a
- * requirement rather than a warning — a publisher who is told "consider
- * raising it" and then refused has been lied to by the form. It still explains
- * WHY, because a bare minimum with no arithmetic behind it reads as an
- * arbitrary tax on cheap listings.
- *
- * Shared by every publish form rather than written into each, because the
- * figure has to be the same one in all of them and the wording is the only
- * place a publisher ever sees it.
- *
- * Quoted at the take rate that breaks even LATEST, so the sentence holds for a
- * free-plan publisher too.
- */ export function marketplacePriceCostNote(priceUsd) {
-    const price = Math.round(Number(priceUsd) || 0);
-    const minimum = marketplaceMinPriceUsd();
-    // A free listing takes no payment, so it costs nothing to process and has
-    // nothing to warn about — silence there is the point, not an oversight.
-    if (!isBelowMarketplacePriceFloor(price)) return undefined;
-    const { processingCents, platformFeeCents } = marketplaceSaleEconomics(price, bindingMarketplaceFeePct());
-    const usd = (cents)=>`$${(cents / 100).toFixed(2)}`;
-    return `Too low to publish. Processing a $${price} payment costs about ` + `${usd(processingCents)}, more than the ${usd(platformFeeCents)} platform ` + `fee — the sale would lose money. The minimum paid price is ` + `$${minimum}, and a free listing ($0) takes no payment at all.`;
-}
-/**
- * The standing helper sentence a price field shows when there is nothing wrong
- * (AGL-2343): the minimum stated up front, so a publisher meets it while
- * typing instead of discovering it as a refusal.
- *
- * A capability that is not surfaced in the console does not count as shipped,
- * and that applies to a REFUSAL as much as to a feature: a floor only a route
- * knows about is a trap.
- *
- * @param suffix whatever else that particular form needs to say, appended.
- */ export function marketplacePriceFloorHint(suffix) {
-    return `0 for free, or $${marketplaceMinPriceUsd()} and up for a paid listing.` + (suffix ? ` ${suffix}` : '');
-}
+ * alongside `card`, `cashapp`, `link`, `amazon_pay` and `apple_pay`, and no
+ * checkout session pins `payment_method_types`, so a buyer may pay by either.
+ * A cost computed from the cheapest method would be wrong exactly when it
+ * mattered.
+ */ export const CARD_PROCESSING_PERCENT = 2.9;
+/** Klarna/Affirm, roughly. See the note above — this is the binding one. */ export const BNPL_PROCESSING_PERCENT = 6;
+/** Stripe's per-transaction fixed component, in cents. */ export const PROCESSING_FIXED_CENTS = 30;
+/**
+ * The processing rate a storefront or booking destination charge is priced
+ * against (AGL-2152), and the one identifier to repoint if those sessions'
+ * payment method set changes.
+ *
+ * Deliberately its OWN name rather than a direct use of the binding rate,
+ * while being defined as it: every seller shares Stripe's published rates and
+ * today shares the platform's payment method configuration, but each surface
+ * is a separate product decision. A future choice to pin
+ * `payment_method_types` on storefront sessions to the card family — and so
+ * to recover at `CARD_PROCESSING_PERCENT` — must not silently lower the
+ * marketplace listing floor, which is derived from the binding rate for a
+ * different flow.
+ */ export const SALE_PROCESSING_PERCENT = BNPL_PROCESSING_PERCENT;
+/** Stripe's per-transaction fixed component, in cents. Not rate-dependent. */ export const SALE_PROCESSING_FIXED_CENTS = PROCESSING_FIXED_CENTS;
 /**
  * The cheapest plan whose BASE features include `feature`, in ladder order —
  * the answer to "which plan do I need for this?", which is the one thing an
@@ -3362,10 +3152,22 @@ export { PLATFORM_BRANDING_PROFILE } from "./platform-brand.js";
  * entitlement the stored profile is ignored entirely and the full Aglyn
  * brand is returned — so an org that white-labeled and then downgraded
  * reverts cleanly.
+ *
+ * An org WITH the entitlement that has stored no brand value at all gets the
+ * full Aglyn brand too (AGL-3440). The entitlement is the right to a brand,
+ * not a brand: until the org sets one, every name it shows is the platform's
+ * anyway, so the white-label profile's blanks — no logo, no support link, no
+ * home — conceal nothing and only strip the platform's own header and footer
+ * from mail whose every line already names the platform. Every Enterprise
+ * org carries the entitlement, Aglyn's own included. One field set, and the
+ * rules below apply.
  */ export function resolveBrandingProfile(org) {
     var _ref, _cleanBrandString, _cleanBrandString1, _cleanBrandString2, _cleanBrandString3, _cleanBrandString4, _cleanBrandString5, _cleanBrandString6, _cleanBrandString7, _cleanBrandString8, _cleanBrandString9, _cleanBrandString10;
     if (!checkEntitlement(org, 'whiteLabel')) return PLATFORM_BRANDING_PROFILE;
     const profile = (_ref = org == null ? void 0 : org.brandingProfile) != null ? _ref : {};
+    if (!Object.values(profile).some((value)=>cleanBrandString(value) !== undefined)) {
+        return PLATFORM_BRANDING_PROFILE;
+    }
     return {
         productName: (_cleanBrandString = cleanBrandString(profile.productName)) != null ? _cleanBrandString : PLATFORM_BRANDING_PROFILE.productName,
         // NO FALLBACK — and this became load-bearing the moment
@@ -3778,7 +3580,7 @@ export function checkQuota(org, quota, currentUsage) {
  * billing page reads the same document, member-readable, so a rep is never
  * told their limit by being refused.
  */ export function checkCrmEmailQuota(org, usedToday, now = new Date()) {
-    const included = resolveOrgEntitlements(org).crmEmailsPerDay;
+    const included = planQuotaOf(resolveOrgEntitlements(org), 'crmEmailsPerDay');
     const used = Math.max(0, Math.floor(Number(usedToday) || 0));
     const resetsAt = new Date(Date.UTC(now.getUTCFullYear(), now.getUTCMonth(), now.getUTCDate() + 1));
     return {
@@ -3875,7 +3677,7 @@ export function checkQuota(org, quota, currentUsage) {
  * counter lives (`hosts/{id}/counters/formSubmissions`). Callers gating a
  * single submission pass that site's month count.
  */ export function checkFormSubmissionQuota(org, usedThisMonth) {
-    const included = resolveOrgEntitlements(org).formSubmissionsPerMonth;
+    const included = planQuotaOf(resolveOrgEntitlements(org), 'formSubmissionsPerMonth');
     const metered = planMetersInfraOverage(org);
     const used = Math.max(0, usedThisMonth);
     return {
@@ -3930,7 +3732,7 @@ export function checkQuota(org, quota, currentUsage) {
  * `cloud/firebase-firestore.rules`), so the count behind the ceiling cannot
  * be lowered to launder past it.
  */ export function checkFormSubmissionAbuseCeiling(org, usedThisMonth) {
-    const included = resolveOrgEntitlements(org).formSubmissionsPerMonth;
+    const included = planQuotaOf(resolveOrgEntitlements(org), 'formSubmissionsPerMonth');
     const ceiling = Number.isFinite(included) ? Math.max(FORM_ABUSE_CEILING_FLOOR, included * FORM_ABUSE_CEILING_MULTIPLE) : FORM_ABUSE_CEILING_UNLIMITED;
     const used = Math.max(0, usedThisMonth);
     return {
@@ -3950,7 +3752,9 @@ export function checkQuota(org, quota, currentUsage) {
  * view costs. They are one physical measurement written in two units, and
  * what every `bandwidthGb` band is actually sized against is neither of them
  * alone but their quotient — `(1 GB ÷ this) × perPageView`, the cost of a
- * gigabyte. That quotient is stable even while the page's weight is not,
+ * gigabyte's WEIGHT, to which the band sizing adds the CDN requests the same
+ * views make ({@link PAGE_VIEW_CDN_REQUEST_COST_USD}). That quotient is
+ * stable even while the page's weight is not,
  * which is precisely why moving one half re-prices every band on the ladder
  * without touching a band: a heavier page costs more per view and buys fewer
  * views per gigabyte, and the two cancel.
@@ -3999,11 +3803,13 @@ export function checkQuota(org, quota, currentUsage) {
  * It is a CAP, not a price, and it is lower than {@link
  * FORM_ABUSE_CEILING_MULTIPLE} because bandwidth is the largest cost line the
  * platform carries and the one a stranger can spend on the customer's behalf.
- * Past the band every 1,000 views bills $0.21 against about $0.16 of real
- * cost, so the tail is no longer a loss — but a scraper, a hotlinked asset or
- * a botnet still bills the account holder for traffic they did not ask for,
- * and the ceiling is what bounds that before staff look at it. At 10× the
- * band that tail was open-ended on Agency; at 3× it is bounded.
+ * Past the band every 1,000 views bills $0.70 against at most $0.54 of real
+ * cost — the dearest region's — once the CDN's request allowance is spent
+ * ({@link PAGE_VIEW_CDN_REQUEST_COST_USD}), so the tail is not a loss — but a
+ * scraper, a hotlinked asset or a botnet still bills the account holder for
+ * traffic they did not ask for, and the ceiling is what bounds that before
+ * staff look at it. At 10× the band that tail was open-ended on Agency; at 3×
+ * it is bounded.
  */ export const BANDWIDTH_ABUSE_CEILING_MULTIPLE = 3;
 /**
  * Absolute floor for the bandwidth ceiling, in PAGE VIEWS per month, so the
@@ -4013,9 +3819,10 @@ export function checkQuota(org, quota, currentUsage) {
  * Free includes 2 GB ≈ 2,071 views; 3× would be ~6,212, which a genuinely
  * successful hobby site (a post that lands on Hacker News) reaches in an
  * afternoon and would be a miserable first experience of the platform.
- * 100,000 views/month ≈ 96.6 GB ≈ **$16 of real COGS** at
- * `METERED_UNIT_RATES_USD.perPageView` — well above the free band, and an
- * order of magnitude below the $162 a million views costs. It is the number
+ * 100,000 views/month ≈ 96.6 GB ≈ **$54 of real COGS** at the dearest
+ * region (`METERED_UNIT_RATES_USD.perPageView` plus
+ * `PAGE_VIEW_CDN_REQUEST_COST_USD`) — well above the free band, and an order
+ * of magnitude below the $538 a million views costs. It is the number
  * that makes "free stays free" true without making it stingy.
  */ export const BANDWIDTH_ABUSE_CEILING_FLOOR = 100000;
 /**
@@ -4128,15 +3935,25 @@ export function checkQuota(org, quota, currentUsage) {
 /**
  * Is the render path required to serve the capped notice instead of the page?
  *
- * Both halves must hold: the flag is for THIS month, and the trip was
- * recorded as one that degrades. `degraded` is written by the evaluator from
- * {@link bandwidthCeilingDegradesRender} at trip time rather than re-derived
- * here, so a host that upgrades mid-month is not still being degraded by a
- * flag written while it was free — and, in the other direction, a flag from a
- * paying host can never take that host down.
- */ export function bandwidthCeilingDegradesHost(host, month) {
+ * Three things must hold: the flag is for THIS month, the trip was recorded
+ * as one that degrades, and the org's CURRENT plan still degrades.
+ *
+ * The stored `degraded` alone cannot answer the last one. It is written once,
+ * at trip time, and nothing rewrites it: the beacon stops evaluating a host
+ * once it has tripped this month, and a contained site serves no pages to
+ * beacon from. So a host that upgraded mid-month stayed on the notice until
+ * the 1st, while the owner notice and the visitor notice both promised an
+ * upgrade would bring it back. Re-deriving from `org` on every read releases
+ * it on the next org-doc TTL with no write, the same asymmetry
+ * `bandwidthCapEngaged` keeps for the plan band.
+ *
+ * Both halves still hold in the other direction: a flag written for a paying
+ * host (`degraded: false`) can never take that host down, whatever its plan
+ * becomes later. An unknown org (`null`) resolves as unmetered, so a lookup
+ * failure keeps the containment rather than lifting it.
+ */ export function bandwidthCeilingDegradesHost(host, month, org) {
     var _normalizeHostBandwidthCeiling;
-    return ((_normalizeHostBandwidthCeiling = normalizeHostBandwidthCeiling(host, month)) == null ? void 0 : _normalizeHostBandwidthCeiling.degraded) === true;
+    return ((_normalizeHostBandwidthCeiling = normalizeHostBandwidthCeiling(host, month)) == null ? void 0 : _normalizeHostBandwidthCeiling.degraded) === true && bandwidthCeilingDegradesRender(org);
 }
 /** UTC `YYYY-MM`, the key both the beacon and the render path agree on. */ export function bandwidthCeilingMonthKey(now = new Date()) {
     return now.toISOString().slice(0, 7);