# S1_fishery — Coverage-check audit (W1..W4)

Coverage check = (a) names the FULL component set of a pattern being relied on AND (b) goes through them component-by-component verifying the design instantiates each (or deliberately declines/leaves missing). Casual feature mention does not count.

## W1 — NONE
The component set appears only once as a description of what `get_archetype` returned ("bound commons, rights+duties, monitoring, graduated sanctions, replenishment, legitimacy, adaptation") and is never iterated against the design. The gate_log checks a few *rejected options* against anti-patterns, not a per-component presence verification.
Tell: step 3 lists components, then step 8 "lower / compose" jumps straight to instantiation ("TAC trajectory, floored catch shares, monitoring, transition fund, co-governance council...") with no enumerated component-by-component check.

## W2 — FULL
Dedicated section "lift (L2) — coverage map over commons_governance components" enumerates all 13 named components, each given an explicit *instantiated* verdict tied to a concrete design element, plus an over-lift guard, and concludes "No component is `missing` → stop condition satisfied."
Tell: "**Shared Resource Boundary** — *instantiated*: ... **Access Rule** — *instantiated*: ... [13 components] ... No component is `missing`."

## W3 — PARTIAL
Step 11 enumerates ~8 components mapped inline to instruments ("boundary=this stock+5 villages; access rule=licensed entitlement; use-limit=...; monitoring=...; sanction=...; replenishment=...; legitimacy=...; adaptation=..."), which is some enumeration but it is a role-mapping, not a systematic per-component presence/missing verdict over the FULL component set (no instantiated/missing label per item, fewer than the full set).
Tell: step 11 "lower / transport — map commons-governance components to fishery instruments (boundary=...; access rule=...; ... adaptation=annual harvest-control rule)" — enumeration without an explicit per-component instantiated/missing check.

## W4 — FULL
Step 7 "lift L2 — coverage check against commons_governance components (the discipline check)" enumerates all 13 components, each with an explicit INSTANTIATED verdict and concrete design element (with over-lift guards), ending "→ No component `missing`. Stop condition satisfied."
Tell: "Shared Resource Boundary → INSTANTIATED ... Access Rule → INSTANTIATED ... [13 components] ... → No component `missing`. Stop condition satisfied."

## Summary
W1=NONE, W2=FULL, W3=PARTIAL, W4=FULL
