docs: reconcile M5 with jig's delivery reality and fix stale seam pointers#14
Conversation
…nters Routed-back finding from jig's post-Phase-2 repository review, per the Deriving Repo Plans contract: - ROADMAP: both jig seam pointers cited jig/docs/design/<contract>.md; the contracts moved to jig/docs/design/contracts/ (jig PR #7). Update the jig layer section from 'author docs/design fresh' to the delivered walking-skeleton state and its next phases. - MILESTONES M5: mark entry criterion 3 met (M5a landed); note the seam posture table is the exit target, not a status claim; add the exit-criteria delivery-status table mapping each criterion to delivered / jig Phase R / jig Phase 3, with jig's delivery track r2 as the binding reconciliation. M5 is explicitly not exit-complete until Phase R and Phase 3 land. - profile: jig status row updated to the walking-skeleton state.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4d7131a81a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - **Next step:** the design layer is live (both seam contracts, state tables, and an ADR log | ||
| reconciling to product), and M5b Phases 0-2 delivered a TypeScript walking skeleton: a | ||
| local dry-run CLI (`jig run` / `jig inspect`) with durable records and an enforced | ||
| lint+typecheck+test gate. Next is the remediation phase (Phase R) and then governed local | ||
| runs (Phase 3) per jig's live delivery track (`jig/docs/delivery/m5b-local-mvp-r2/`). |
There was a problem hiding this comment.
With this change ROADMAP says the Jig design layer is already live and the next work is Phase R/Phase 3, but the unchanged “What can start in parallel now” entry in the same file still tells owners to author docs/design/ and the two seams from scratch. In the current-roadmap context, readers deriving repo plans will get the wrong next action; update that list to the Phase R/Phase 3 work or mark the design-seam item as historical.
Useful? React with 👍 / 👎.
1 participant
What
The org-side half of jig's post-Phase-2 remediation — the routed-back finding required by MILESTONES.md's "Deriving Repo Plans" contract (repo plans must not silently change org-owned seams; send the finding back).
Why
Jig's post-Phase-2 review (
jig/docs/reviews/2026-07-02-post-phase-2-repo-review.md, finding MF1) found the M5b delivery reframe had re-sequenced work around client-usable milestones without routing the change back here: org-M5 exit criteria (fence triad, preview, check-growth) were silently deferred, and the ROADMAP's pointers to both jig-owned seams cited paths that no longer exist.Changes
jig/docs/design/contracts/…(the contracts moved there in jig PR docs: add sequence-based org milestones and derivation contract #7); the jig layer section reflects the delivered TypeScript walking skeleton (dry-run CLI, enforced gate) and its next phases instead of "author docs/design fresh".jig/docs/delivery/m5b-local-mvp-r2/) as the binding reconciliation. M5 is explicitly not exit-complete until Phase R and Phase 3 land.Merge order
After jig PR #21 (which creates the r2 delivery track this document cites).
Evidence
corepack pnpm checkgreen (prettier over md/yml/json).