[pasilastbot]

Canonical process text for slice SLICE-RDD-FLOW. Entry approved: USER:2026-10-14:slice-entry-approve. Design and decisions: design/2026-10-13-slices-gates-uat.md, which stays out of the packaged tree.

What changes

• Slices (REQ-CROSS-562):
  • Work is planned and delivered in slices. "Sprint" is gone, and the code a batch lands is an increment (D4).
  • The new "### Slices" section and file-state/SLICE.md.
  • The build is red-first per connected batch (D1), with one full verification, one code review and one completion per slice.
  • The WORK-SELECTION.md shape is unchanged.
• Stop only at human decisions (REQ-CROSS-586, process side):
  • Agents stop at an open human gate, a question only a human can answer, or a requested stop. An applied entry approval lets the build start.
  • Merging, deploying and releasing wait for a human.
  • Briefs use plain language, with jargon at most a trailing breadcrumb.
• Project gate rules (REQ-CROSS-573):
  • The project's process/rdd-human-gates.md, with default and autopilot presets in presets/ and the shape in file-state/HUMAN-GATES.md.
  • Sign-in, payments, existing data and external contracts stay human in both presets (D2).
  • Light paths are off in the kit default and on in autopilot. An incident counts only when a person declares it.
  • The ten remaining risks are listed.
• Acceptance test step (REQ-CROSS-581, process side):
  • A new step between the delivered-revision check and the completion trace.
  • The new skill skills/rdd-acceptance and the shape file-state/ACCEPTANCE-GUIDE.md.
  • The guide is required per slice. Sign-off follows the project's rules (D3).
• Declared integration path (EPIC-CLI-DELIVERY-PATH):
  • Completion is checked on the project's declared path, from process/integration-path.md with the shape in file-state/INTEGRATION-PATH.md.
  • On merge, the remote default branch must contain each tested commit. On deploy, the deployed commit is named and a deployment run is recorded.
  • The as-built (reverse-engineer) exact-tip check is unchanged, because the CLI still enforces it.

How it ships

The modernpath CLI embeds this text at a pinned commit (rdd-source.txt). The CLI change in ModernPath/modernpath-v1 (branch feat/delivery-path-completion) pins this branch's head for its tests. After this PR merges, it re-pins to the merge commit before it merges itself.

🤖 Generated with Claude Code

[mattias-modernpath]

Reviewed with Astra, xhigh effort, base 25d85d660fe8e8d500c220e36bfc721502d608ad → head efe87476c4342623d3eff96fc28774903c023da4.

Two process-contract findings:

1. [P2] Define entry and RED exceptions for fix-first changes — PROCESS.md:471–476. The incident path permits implementing the fix before its reproduction test and entry records; the defect path also records entry afterwards. But PROCESS.md:985–1000 still prohibits implementation before applied entry except diagnostic tests or uncommitted reversible build-ahead, PROCESS.md:822–825 still requires RED before implementing every clause, and completion review rejects missing required RED. An agent following the enabled path cannot consistently satisfy build and completion. The acknowledged uncertainty about server ordering does not resolve this canonical-process conflict. Add explicit fix-first exceptions to the entry/evidence rules and affected skills, including the required retrospective proof. Grounding: REQ-CROSS-573-AC2 and canonical entry/evidence consistency.

2. [P2] Align autopilot closeout with one full-verification point — PROCESS.md:623. This requires full verification once at the delivered revision. However, skills/rdd-autopilot/SKILL.md:136–145 requires it before independent review of the branch head; that review precedes delivery, after which skills/rdd-completion-review/SKILL.md:39–41 requires full verification again. A normal merge with a new merge commit therefore requires two full runs, or violates one instruction. Identify one full-run point and explicitly state when equivalent evidence may carry across delivery. Grounding: REQ-CROSS-562-AC2.

The PR groups epics/requirements into slices, adds gate presets and acceptance guides, and documents merge/deploy completion. Updated tracked files and skills coordinate the work while retaining each member's records and gates. The intended outcome is supported, but the execution instructions need the corrections above.

Coverage: all 23 changed files plus relevant surrounding rules; REQ-CROSS-562/573/581/586, the delivery-path epic and checked-in design. Citation-auditor tests: 15 passed. Checked 12 relative Markdown paths: none missing. These checks do not establish execution of the companion CLI workflows. REQ-ENG-001–008 are PROPOSED candidates, not governed constraints; their frontend/backend/runtime concerns do not apply to this documentation-only change.

[pasilastbot]

Thanks. Both findings are fixed in ecb97d6:

1. Fix-first paths contradicted the entry and RED rules.
   • The entry rule now lists fix-first on a light path (defect_fix, incident_fix) as its third exception. The autopilot RED rule, rdd-build step 1 and the rdd-completion-review stop list each point to the reproduction proof.
   • New wording for a person to confirm: for an incident, the proof is now the reproduction test failing at the pre-fix revision and passing at the fix, with the gap record citing both runs. The old text only said the test "follows as verification".
2. Full verification was required twice.
   • The one full run is now the slice's closeout run. It carries to the delivered revision through the existing containment rule (§Evidence and completion), and is re-run there only when containment can't be shown (squash or rebase).
   • The same wording is applied in PROCESS.md (both tables, the development loop, the slice completion paragraph and the acceptance step), rdd-autopilot step 2 and rdd-completion-review step 4.
   • As you noted, containment doesn't prove the merged tree passes if the default branch moved. That is the existing rule's choice.

The auditor tests pass (15/15). #890 embeds this revision (a6cd5385e).