design-increment git:20260918.b9675e5A

Immutable. This exact content never changes and is served at /api/v1/blob/f2d7fdac9c86cb33.

---
name: design-increment
description: Turn a project goal, options and research into one scoped implementable increment and an old-versus-new evaluation plan.
disable-model-invocation: true
---

Use the [shared handoff contract](../../references/design-loop-contract.md). Inputs are request context, baseline, options and research evidence, plus any prior observations; equivalent caller-supplied material is sufficient.

Invoke core `orch-work` for the named assignment `design-increment` with these inputs and resolved Make guidance. Ask it to select one coherent increment, explain the decision and rejected alternatives, and specify changed behavior, boundaries, implementation outline, risks and required dependencies. The first cycle must target a minimum working PoC from the actual baseline.

Return a design that an implementer can follow and an evaluation plan fixed before implementation: acceptance criteria, baseline behaviors to preserve, shared inputs/harness and conditions, expected old-state deficits, improvement measures and required versus optional checks. Mark any unresolved question that blocks implementation. If no change is justified, return that conclusion and its evidence for analysis rather than fabricate scope.