iter cadence.3: skills/fieldtest — Boss-dispatched framing + ordering note

skills/fieldtest/SKILL.md

@@ -34,13 +34,20 @@ rules. This skill file only governs trigger, dispatch, and handoff.
 ## When to Use / Skipping
 
 Triggers:
-- A milestone has just closed `audit` cleanly (or with `ratify`-d
+- Boss-dispatched after audit closes cleanly, when the orchestrator
-  drift only).
+  believes the iteration is correct and wants a Praxistest. The
+  pre-condition is a clean (or `ratify`-d) audit; the trigger is the
+  Boss's judgment-call that the iteration is fertig.
 - A shipped feature is suspected of being LLM-hostile in some way the
   earlier brainstorm could not foresee.
 - A user-facing surface change (Decision 6, schema rev, new
   effect/typeclass mechanic) has just landed.
 
+Findings cluster around two shapes — simple bugs (route via `debug` →
+`implement` mini) or catastrophic architecture problems (route via next
+`brainstorm`). Friction and spec-gap items are also possible; the
+routing table below applies in all cases.
+
 **Skipping is permitted only** for:
 - Bug-fix iterations (use `debug`).
 - Tidy iterations whose scope is purely internal cleanup with zero
@@ -116,6 +123,8 @@ The orchestrator drives downstream:
   Rationalisations table, and the Red Flags list.
 - **Upstream gate:** `skills/audit/SKILL.md` runs first; fieldtest
   comes after a clean (or ratified) audit.
+- **Cadence ordering:** fieldtest runs *before* `skills/docwriter`;
+  docwriter happens at a later, longer stability window.
 - **Downstream targets:**
   - `skills/debug/SKILL.md` — for each `bug` finding
   - `skills/brainstorm/SKILL.md` or `skills/planner/SKILL.md` — for