@@ -664,8 +664,8 @@ limit that was exceeded. They are deliberately generous — they exist to stop
 pathological documents, not to constrain reasonable authoring. The content-type
 count is an outstanding exception: its entitlement keys exist, but registration
 does not yet enforce them. The
-[quota accounting proposal](../roadmap/phase-04-cms-media-pages.md#content-type-quota-accounting--proposal-2026-10-19)
-states the pending counting decision and required concurrency proof.
+[accepted quota accounting](../roadmap/phase-04-cms-media-pages.md#content-type-quota-accounting--accepted-2026-10-19)
+states the maintainer's counting decision and required concurrency proof.
 
 | Limit | Value | Why this one |
 |---|---|---|
 
@@ -11132,7 +11132,7 @@ these test corrections.
 ### Additional verification and evidence reconciliation (2026-10-19)
 
 **Status: local corrections and both independent review rounds complete;
-quota accounting choice and renewed source qualification pending.**
+approved quota implementation and renewed source qualification pending.**
 This pass retains existing ADRs, durable-state authority and phase boundaries.
 
 #### Previously qualified source and retained evidence
@@ -11182,7 +11182,7 @@ subsequent corrections.
 | Dependency/comment drift | Remove the unused audit-adapter MediatR reference; align its catalogue/coordinator description, Next patch comment, middleware XML summary and P02b-5 authentication owner. |
 | Moving CI action tags and scanner admission | Pin all 39 uses to seven reviewed upstream commits; future updates require review. Go already uses its checksum database; additionally require exact module and go.mod hashes before scanner installation. Keep aggregate upload identity exact and reject a tag or substituted commit. |
 | ADR comparison silently skips an unresolved base | Require the actual PR base SHA, push predecessor or explicit manual base, and refuse an unresolved base or failed diff. Require the SARIF artifact instead of warning when absent. |
-| Plan-gated content-type count is unenforced | Confirmed pre-existing gap. Correct the absolute enforcement claim; the linked quota proposal makes revision/default/deletion accounting and a tenant-wide concurrency proof explicit before implementing a commercial rule. |
+| Plan-gated content-type count is unenforced | Confirmed pre-existing gap. The maintainer approves distinct nondeleted custom keys, shared revision slots, excluded card default and last-live-revision deletion releasing capacity; the shared writer must serialize count/insert tenant-wide. Approval precedes implementation. |
 | Broken ADR-0038 anchor | Standards 13 already provides the exact `adr-amendments` HTML alias. The accepted record is not edited. |
 | Historical SQL copies or loose-then-tightened policies should be folded | Up/Down snapshots preserve versioned rollout and reversal. Current canonical bodies have parity proofs; no historical migration is folded or made dependent on mutable SQL. |
 | Vendor installer leaves search_path set | Pinned Install.v23.sql ends with RESET search_path. No session-setting change. |
@@ -11209,7 +11209,7 @@ does the actual production-manifest test. The 51 combined shard controls, seven
 ADR lifecycle controls and seven new supply-chain controls pass. The real scanner
 installation verifies both pinned sums and its resulting Go module metadata;
 actionlint accepts the pinned workflow. The quota proposal remains non-runtime
-and awaits the maintainer's accounting choice.
+and was awaiting the maintainer's accounting choice at this source.
 
 **Additional review round 1.** Two fresh independent reviewers examine
 `62ad318c..cd69bbc6` across backend/contract tests and CI/dependency/evidence
@@ -11234,6 +11234,12 @@ SHA admission and its mutation controls remain. Parent verification also passes
 All 512 relative links in the changed documents resolve, including HTML aliases.
 No reviewer claims full hosted qualification for this corrected source.
 
+**Quota acceptance.** The maintainer explicitly selects the proposed accounting
+on 2026-10-19; its
+[accepted rule](phase-04-cms-media-pages.md#content-type-quota-accounting--accepted-2026-10-19)
+precedes the shared-writer change. No new ADR or unapproved counting policy is
+introduced. Runtime implementation and its two independent review rounds follow.
+
 ## Completion Criteria
 
 Each criterion below is observable: a named test can pass or fail on it. Criteria whose
 
@@ -113,24 +113,24 @@ Also in scope:
 - Whether a customization change owes an integration event, per
   [the Customization spec § Integration-event catalogue](../modules/customization/README.md#integration-event-catalogue).
 
-### Content-type quota accounting — proposal (2026-10-19)
+### Content-type quota accounting — accepted (2026-10-19)
 
-**Decision pending.** The existing registration command does not enforce
+**Accepted — 2026-10-19, @cemil.** The maintainer approved the accounting below
+before implementation. The existing registration command does not yet enforce
 `LimitKeys.MaxCustomContentTypes`; the registered key alone is not a write-time
-quota. Resolve this accounting rule before adding enforcement to that command,
-rather than letting an implementation silently choose its commercial meaning.
+quota. The correction implements this rule in that shared writer.
 
-The proposed rule counts distinct, nondeleted, tenant-authored content-type keys.
+The rule counts distinct, nondeleted, tenant-authored content-type keys.
 Schema revisions share one slot; the built-in `card` definition uses none. A soft
 deletion frees a slot only when no nondeleted revision of that custom key remains.
 The unlimited entitlement or a limit of `-1` removes the ceiling; zero permits
 no new custom key. Existing revisions remain writable at the ceiling. A new key's
 count and insert serialize under one tenant-wide transaction advisory lock;
 per-key locks alone cannot prevent two different keys exceeding the quota.
 
-Acceptance must include refusal/allowance controls, revision/default/deletion
+Implementation must include refusal/allowance controls, revision/default/deletion
 accounting, tenant isolation and a real concurrent PostgreSQL count/insert proof.
-This proposal changes no runtime behavior or accepted entitlement decision.
+Approval alone does not claim runtime enforcement or passing qualification.
 
 ### Customization Key Shape and Immutable Schema Versions