# c02 — Independent Coverage Verification

## Independent pattern identification (catalog, not the design's claims)

Ran `search_by_facets` with 6 domain-stripped facets (finite shared resource drawn
down by many; small group bears upkeep of a free good; cannot compel pay/reciprocity;
rationing scarce attention; the few sustainers exit and collapse it; free-riders
extract without contributing). The fusion + per-facet lists converge on **two**
structurally distinct operative patterns — and this problem instantiates BOTH:

- **commons_governance** (PRIMARY) — the *overuse* side: a rivalrous, non-excludable
  resource (maintainer attention/release capacity) is drawn down by unbounded demand;
  upkeep falls on a small unprotected subset. The archetype's own "Maintenance Commons
  Governance" variant names open-source maintainer burnout as a canonical instance, and
  its failure-modes section names "Maintenance burnout" verbatim. Coercion is
  unavailable, which is exactly the commons (not central-allocation) trigger.
- **public_goods_provision** (SECONDARY, genuinely load-bearing) — the *underprovision*
  side: the contributor pipeline and funding are undersupplied because beneficiaries
  free-ride. The success criterion explicitly forbids collapsing the contributor
  pipeline, so the design MUST also carry provision logic, not only overuse-throttling.
  Anti-signature of commons_governance points here ("underproduction of a non-rival
  shared benefit → public_goods_provision"), confirming it is a second pattern, not noise.

The design names commons_governance as the single operative pattern and folds the
provision/contribution/funding material in as "mechanisms." That folding is defensible,
but I verify against BOTH component sets independently below to ensure the provision
side is actually covered and not lost in the fold.

---

## Coverage map A — commons_governance (13 components)

| Component | Status | Witness / reason (from design alone) |
|---|---|---|
| Shared Resource Boundary | instantiated | SUPPORT/governance doc declares maintainer attention + release/security capacity as the protected resource; states what project is/isn't responsible for. |
| Access Rule | instantiated | Issue tracker becomes triage queue; bug reports require reproducible test case + version before maintainer attention; unpaid "urgent support" is not an access right. |
| Use Quota / Use Limit | instantiated | Declared weekly maintainer time-box; batch triage; explicit no-SLA for unpaid requests. |
| Monitoring Signal | instantiated | Public board showing queue depth, target response by request type, and maintainer load. |
| Sanction Rule | homolog | No coercive sanction exists; discharged by graduated *attention-withdrawal* — one templated boundary reply then thread-lock; loss of scarce attention is the only enforceable consequence. |
| Replenishment Rule | instantiated | Funded stewardship hours / part-paid maintainer + recovered contributors replenish capacity. |
| Legitimacy Basis | instantiated | Published governance doc states expectations *and why* (sustainability, not gatekeeping); legitimacy from openness + visible fairness of limits. |
| Dispute Resolution Path | instantiated | Defined escalation/appeal route + code-of-conduct enforcement path so enforcement is not personal/arbitrary. |
| Adaptation Cadence | instantiated | Quarterly review of queue metrics, funding, maintainer count; revises time-box/tiers/scope — serves the 6-month window. |
| Contribution Rule | instantiated | Contributor ladder, reporter→contributor→committer path, good-first-issues, non-maintainer first responses. |
| Funding Pool | instantiated | Corporate sponsorship tiers, paid-priority SLAs, optional fiscal host buying maintainer time. |
| Exception Process | instantiated | Dedicated private security channel with real response commitment, outside the time-box — the queue that never starves. |
| Transparency Record | instantiated | Public changelog of governance changes + the triage board itself; rules documented and inspectable. |

**A: 12 instantiated, 1 homolog, 0 declined, 0 missing.**

---

## Coverage map B — public_goods_provision (15 components)

| Component | Status | Witness / reason (from design alone) |
|---|---|---|
| Public-Good Boundary | instantiated | Same governance doc names what is owed free (working library, security fixes, best-effort triage) vs. not — defines the shared-benefit boundary and why exclusion is undesirable. |
| Provision Responsibility | instantiated | Maintainers retain stewardship; roadmap/security control stays with them; optional fiscal host as accountable convener. |
| Contribution Rule | instantiated | Contributor ladder + reproducible-repro requirement convert diffuse benefit into concrete labor. |
| Funding Pool | instantiated | Sponsorship tiers + paid SLAs + fiscal host aggregate contributions into usable capacity. |
| Access Policy | instantiated | Tiered access: free best-effort triage vs. paid priority lane; preserves shared value without abuse. |
| Maintenance Obligation | instantiated | Security exception lane + funded stewardship hours treat upkeep as part of provision. |
| Legitimacy & Fairness Review | instantiated | Paid tier explicitly does NOT buy roadmap/security control — anti-capture safeguard; governance doc defends burden. |
| Free-Rider Response | instantiated | Convert takers to funders; high barrier to *consuming free support*; templated boundary + lock on entitled escalation. |
| Provision-Level Target | homolog | No explicit minimum-provision metric, but "load matched to capacity within 6 months" + scope-shrink-if-exceeded serves the same "is the good sufficiently provided" function. |
| Accountability & Reporting | instantiated | Public changelog + triage board + quarterly review keep contributors/beneficiaries informed. |
| Assurance Threshold | homolog | Direct approach to largest dependents framing sponsorship as cheap insurance approximates the pledge/threshold mechanism (overcome each-waits-for-others) without a formal conditional contract. |
| Matching or Leverage Rule | correctly_declined | A minor funding-leverage mechanism among several; provision is solvent via tiered sponsorship/SLAs; forcing a matching scheme over-engineers a 3-maintainer project. |
| Volunteer / In-Kind Contribution Path | instantiated | Good-first-issues, non-maintainer first responses, visible recognition of triage/review (not just feature authors). |
| Benefit Measurement Model | homolog | "Name the risk the library goes unmaintained" / avoided-harm framing to sponsors substitutes for a formal benefit-measurement model. |
| Reserve or Endowment | homolog | No dedicated endowment buffer, but *recurring* sponsorship + SLA revenue (vs. one-time donation) + part-paid maintainer + quarterly review discharge the maintenance-horizon/durability function differently. |

**B: 9 instantiated, 4 homolog, 1 declined, 0 missing.**

---

## Anti-signature gate (this scenario)

- commons_governance — *fully private resource*: NOT tripped (shared by thousands).
  *Central authority can allocate*: NOT tripped (cannot compel pay/labor — the commons
  trigger). *One-time two-party dispute*: NOT tripped (recurring N-party).
  *Underproduction of non-rival good → public_goods_provision*: partially tripped — and
  the design correctly responds by carrying provision logic (map B) rather than ignoring it.
- public_goods_provision — *excludable/rivalrous, ordinary purchase suffices*: NOT
  tripped. *Mainly overuse of existing resource → commons_governance*: partially tripped
  (the load side), handled by map A. *Club-good drift*: guarded — free tier preserved,
  paid tier buys priority not control. No disqualifier on either pattern.

The dual-pattern read is itself the design's reconcile step: throttle unpaid demand on
attention (commons overuse) while *lowering* friction for contributors (provision) — the
two resources must move in opposite directions, which the design states explicitly. This
directly addresses the scarce-maintainer-attention-as-shared-resource protection and the
curb-free-riding-without-collapsing-the-pipeline requirement.

---

## Combined coverage

- commons_governance: 12 instantiated / 1 homolog / 0 declined / 0 missing.
- public_goods_provision: 9 instantiated / 4 homolog / 1 declined / 0 missing.
- **No component left missing on either operative pattern.** Every homolog names a
  concrete substitute mechanism; the single declined component carries a fit reason.

VERDICT: PASS

Missing: none.
