an-intent-names-the-release-it-must-land-by-and-the-cut-says

Summary

The design record for itd-2609212103572513: the target_release field, its verbs, the cut's report and the move forward.

Scope

1. The field and verbs: intent target and plan --target in internal/core/intent, version-validated through the release package's parser; lint row in record_schema (criterion 1).
2. The report: launch.DryRun and launch.Ship read planned intents with a target and list those not in shipped/ (criterion 2).
3. The move: the ship path rewrites each listed target the cut passes to next (ruling BS1 of 2026-09-29, the intent's decision 4) in the write that rolls the changelog, and the dated section names the move in one line (criterion 3).
4. The board: the status block reads the field (criterion 4).

Out of scope

• Refusal; issues; dates.

Approach

Small: one frontmatter key, two verbs, one read in launch, one write at the cut; the move is part of the receipts commit so a cut is one change.

Footprint

• packages: internal/core/intent, internal/core/launch, internal/core/positioning
• tests: the verbs and refusals; the dry-run list; the move at a fake cut; the board row

How the criteria are satisfied