philotic-slice-closeout

Slice closeout prevents incomplete work from merging by verifying mandatory green build, test, and smoke statuses before allowing updates to docs/task.md and architecture proposal dispositions.

During closeout, you must update docs/task.md with completed work and follow-ups, and record disposition updates for touched architecture proposals to maintain accurate project documentation.

No, you cannot close out a slice with failing smoke tests because mandatory green status clearing requires passing build, test, and smoke statuses before documentation updates and disposition recording proceed.

Capturing reality gaps during closeout identifies discrepancies between expected and actual implementation outcomes, allowing you to document them in docs/task.md and name the next seam for future work.

You update architecture proposal dispositions during closeout when an implementation slice touches those proposals, ensuring project records accurately reflect the completed work status before final commit.