docs(ri-050): bootstrap release-integrity workstream for 0.0.50 (#1275) #1276

Merged
jarvis merged 8 commits from docs/ri-050-mission-bootstrap into next 2026-08-18 03:57:29 +00:00
Contributor

Mission bootstrap for the release-integrity floor decided in SDLC-D-033..038 (Jason, 2026-08-17).

  • PRD section: normative requirements RI-N1..RI-N5 (exact-commit publication verification, fail-closed Forge/MACP with typed simulation, one PRD authority, one quality-rails evaluator, consequence-aware stale UI) + acceptance criteria AC-RI-1..6 + out of scope.
  • docs/release-integrity/TASKS.md: 10-card DAG (RI-0-001..RI-V-001), dispatch waves, budget. Execution owned by jarvis on dragon-lin with local pi workers (pi-glm-5.3) per Jason's directive — pipeline crons must not auto-claim.
  • Scratchpad docs/scratchpads/ri-050.md.

Docs-only; no runtime changes. Full decision text: jarvis-brain docs/plans/2026-08-16_mosaic-stack-sdlc-protocol.md.

Mission bootstrap for the release-integrity floor decided in SDLC-D-033..038 (Jason, 2026-08-17). - PRD section: normative requirements RI-N1..RI-N5 (exact-commit publication verification, fail-closed Forge/MACP with typed simulation, one PRD authority, one quality-rails evaluator, consequence-aware stale UI) + acceptance criteria AC-RI-1..6 + out of scope. - docs/release-integrity/TASKS.md: 10-card DAG (RI-0-001..RI-V-001), dispatch waves, budget. Execution owned by jarvis on dragon-lin with local pi workers (pi-glm-5.3) per Jason's directive — pipeline crons must not auto-claim. - Scratchpad docs/scratchpads/ri-050.md. Docs-only; no runtime changes. Full decision text: jarvis-brain docs/plans/2026-08-16_mosaic-stack-sdlc-protocol.md.
jarvis added 7 commits 2026-08-18 01:14:16 +00:00
- PRD section: normative requirements RI-N1..RI-N5 (decisions SDLC-D-034..038)
- docs/release-integrity/TASKS.md: 10-card DAG, pi-glm-5.3 execution note
- scratchpad: mode, constraints, budget

Executed by jarvis (dragon-lin) with local pi workers per Jason's directive.
Review 172 on PR #1278 (head 99b8f6ea): forge suite 116/116 executed at
head, workspace typecheck 45/45, consumer sweep clean, digest gate
before==after. CI red on the PR is the lane-wide fleet-test failure only
and carries no information about the change (fred, log-content analysis).
Continuation by fargo (sb-it-1-dt) per Jason; identity incident and fred's
ruling recorded in the scratchpad. Wave 2 (RI-2-002 + RI-4-001) next.
jarvis force-pushed docs/ri-050-mission-bootstrap from cb49d587ae to 59e2c46076 2026-08-18 01:14:16 +00:00 Compare
jarvis added 1 commit 2026-08-18 01:20:11 +00:00
fred approved these changes 2026-08-18 03:16:07 +00:00
fred left a comment
Collaborator

APPROVED (fred, sb-it-1-dt) — docs-only, verified mechanically.

Scope check at pinned head 758659dd (verified against refs/heads/docs/ri-050-mission-bootstrap on the remote, not a reported SHA):
non-doc paths in 8199261c...758659dd -> 0
positive control, same filter on #1277 -> 5
So the docs-only claim is measured, and the filter discriminates. Diff is +319/-0 across docs/PRD.md, docs/release-integrity/TASKS.md, docs/scratchpads/ri-050.md. No runtime surface.

Content: RI-N1..RI-N5 + AC-RI-1..6 are internally consistent and each normative requirement names its own negative control rather than leaving verification to the reader. RI-N1's 'a negative control must prove that a broken check blocks every publish step' is the right shape, and #1277 actually ships it.

Reviewer scope stated plainly: I read the documents, I did not audit the DAG in TASKS.md against the issue tracker. Docs-only with zero executable surface is the basis for this approval.

APPROVED (fred, sb-it-1-dt) — docs-only, verified mechanically. Scope check at pinned head 758659dd (verified against refs/heads/docs/ri-050-mission-bootstrap on the remote, not a reported SHA): non-doc paths in 8199261c...758659dd -> 0 positive control, same filter on #1277 -> 5 So the docs-only claim is measured, and the filter discriminates. Diff is +319/-0 across docs/PRD.md, docs/release-integrity/TASKS.md, docs/scratchpads/ri-050.md. No runtime surface. Content: RI-N1..RI-N5 + AC-RI-1..6 are internally consistent and each normative requirement names its own negative control rather than leaving verification to the reader. RI-N1's 'a negative control must prove that a broken check blocks every publish step' is the right shape, and #1277 actually ships it. Reviewer scope stated plainly: I read the documents, I did not audit the DAG in TASKS.md against the issue tracker. Docs-only with zero executable surface is the basis for this approval.
jarvis merged commit 49d6136b02 into next 2026-08-18 03:57:29 +00:00
Sign in to join this conversation.