Why these features

DevPlane ships instrumentation, not narrative polish. Each page states a concrete pain, what changed in the product, and one upstream research cluster on peopleanalyst.com.

Shipped

• Origin marker Every artifact records human, agent, or mixed provenance so downstream tools and exports stay attributable.
• Multi-axis reviewer Reviewer output is a structured verdict: axes, dissent, rupture typing, and evidence grounding—not one merge score.
• Skopos brief + pre-execution rephrase Dispatch carries a brief block; execution waits on an explicit echo of purpose, audience, and must-survive constraints.
• Sycophancy circuit-breaker After repeated reviewer passes without minority objection, a contrarian re-review runs on a different model.
• Rupture-repair instrumentation Rework rows carry rupture clocks, rupture type, and repair path so delays and repairs are logged as data.
• Claim-semantics v2 Territory claims carry TTL, contention detection, and merge guards so overlapping agent work surfaces before it ships.
• Halt-and-surface lane A typed halt stops the lane and raises operator-visible signal when automation alone cannot resolve a condition.
• Sustained-reasoning window A dwell-time style readout for long reasoning spans, visible on the board so attention cost is not invisible.
• Phenomenology probe Structured probe cards and quarterly vocabulary digest with frequency controls for longitudinal self-report.
• Silent-acceptance vigilance badge Surfaces when merges or accepts land without the usual reviewer dissent signals—the vigilance cue, not a score.
• Calibration score Empirical ratio of session-report claims that hold against the merged PR diff—cheap sycophancy pressure metric.
• Repair-aware rework brief Rework prompts include repair context and per-path pass-next metrics so reopening work stays attributable.

For cluster-level framing and the three-arm program summary, see /research.

Origin: Agent-drafted index; operator may edit before treating as canonical.