Skip to content

Checkpoint craft: five stops, visual identity, and the direction stop first - #19

Merged
leochenpm merged 1 commit into
sync/gate-user-choicefrom
sync/checkpoint-craft
Aug 12, 2026
Merged

Checkpoint craft: five stops, visual identity, and the direction stop first#19
leochenpm merged 1 commit into
sync/gate-user-choicefrom
sync/checkpoint-craft

Conversation

@leochenpm

Copy link
Copy Markdown
Collaborator

Batch 6/8 of the release_1.6.5 sync (checkpoint craft, prompt-only). Stacked on #18. Re-mapped by hand from the net end-state of the upstream Aug 1-10 gate/orchestration iteration (c4ba98815, 707a8bf1f, 734cfc675, ed5d22684, 2182ad89a, 72e541a87).

What this adds (all prompt-level, all absent from OSS today)

  1. "Show the work; stop only five times." OSS's checkpoint protocol says when to stop but never the anti-over-stopping half — that showing an artifact is not itself an ending. The five stops are now a closed set.
  2. The visual preview stops once per visual identity. Narration/audio-only changes preserve the accepted silent frames; only a change to visible copy/layout/assets/windows/motion re-gates. Without this an OSS agent re-previews after every narration tweak. (Consistent with the PR5 resolver's amendment-aftermath reasons.)
  3. The direction stop comes first, before any plan file exists (orchestration Gate A + video-router). OSS's compose runbook currently starts after Gate B, and nothing stops an agent from authoring the whole plan before the user has picked a direction — upstream measured 11 minutes of thrown-away authoring. An exact brief still stops, with one concept: a misunderstanding costs one message instead of a whole plan.
  4. Turn mechanics that survive summarized transcripts: artifacts ride the message that ENDS the turn (mid-turn frames were never seen); an enumerated-option reply ("2", its wording, or a paraphrase) IS the decision — act on it, don't re-ask.
  5. Presentation copy: progress prose is user-facing; no finding codes/severity words/internal frame roles; a passing preview message = sheet → one sentence → one question; passing checks stay silent.
  6. Repair economics: all independent blocking findings from one QA result get repaired in ONE message (upstream: one-per-message cost ~10 minutes for six findings); a successful write is authoritative — never re-read to confirm it.
  7. AUTO stop economics: an assembled production is ONE video — stop count fixed by the gate table, one whole-video review, an edit invalidates only its own segment.
  8. gate-control: Gate B restates settled direction facts instead of reopening them; a different-language reply is a revise instruction; a recovery is executed, not narrated.

Verification

Prompt-only; the skills content test pins each new clause (stop only five times, once per visual identity, before any plan file exists, Routing ends at the direction stop, …). Full suite 266 pass / 11 skip.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VL7mRpmEphLAbcH7YmABnV

… the direction stop first

Sync of the checkpoint-protocol craft from Orkas release_1.6.5
(c4ba98815 end-state, 707a8bf1f, 734cfc675, ed5d22684, 2182ad89a,
72e541a87, b0514f075, f0e0c348a), prompt-only, re-mapped onto the OSS
orchestration/gate-control/video-router split:

- orchestration: "Show the work; stop only five times" — the stops are
  a closed set and showing an artifact is not an ending in itself; the
  visual preview stops once per VISUAL IDENTITY (narration-only changes
  inherit the accepted frames); artifacts ride the message that ENDS
  the turn; an enumerated-option reply IS the decision; everything
  outside a tool call is user-facing copy (no finding codes or severity
  words; passing checks stay silent); repair every independent finding
  in one message and never re-read to confirm a successful write.
- Gate A: the direction stop comes first, before any plan file exists;
  2-3 genuinely different concepts; an exact brief still stops with ONE
  concept; propose instead of interrogating for creative preferences.
- AUTO: an assembled production is ONE video — the stop count is fixed
  by the gate table, never per segment; an edit invalidates only its
  own segment.
- gate-control: Gate B opens with the locked direction summary and
  restates settled facts instead of reopening them; a different-language
  reply is a revise instruction; amendment aftermath follows the visual
  identity; a recovery is executed, not narrated (the concrete mutation
  precedes the validator retry).
- video-router: routing ends at the direction boundary — no plan file,
  script, narration copy, or art direction before the user picks.

Verified: skills content tests pin each new clause; suite 266 pass.

Prompt audit: every clause above is NEW behavioral guidance absent from
the OSS pack (verified against current SKILL.md text); none duplicates
gate-control's authorization rules — orchestration carries presentation
/stop craft, gate-control carries authorization; the five-stops set
matches the resolver's gate enum; no clause contradicts the PR5
user-fork/waiver contract, and the preview-identity rule is consistent
with the PR5 amendment-aftermath resolver reasons.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VL7mRpmEphLAbcH7YmABnV
@leochenpm
leochenpm merged commit 6afe1df into sync/gate-user-choice Aug 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant