diff --git a/MILESTONES.md b/MILESTONES.md index 0dcfc97..167f9e6 100644 --- a/MILESTONES.md +++ b/MILESTONES.md @@ -444,7 +444,7 @@ before any design or implementation: ### M7: Real Provider Integration -- State: ready-for-repo-planning +- State: current - Outcome: Enable an operator to turn an approved plan into real landed work — a real agent driver doing real edits, a real execution host with proven confinement, real Forge/GitHub landing, and real work-source intake — recorded in durable, inspectable records under @@ -487,12 +487,29 @@ before any design or implementation: - Real capability-attestation records and the confinement evidence they attest to. - Driver conformance-suite results, including the fail-closed case on a broken adapter. - Tamper-evidence and secret-redaction evidence over the real landing path. +- Closeout checkpoint: + - Jig's local M7 real-provider spine through Phases 6-9 is merged through Jig PR #39 at + commit `3b3d224`. + - The seam-level driver path and records-integrity path are complete for the M7 repo + track: real agent/host, Forge, work-source, and integrity behavior are exercised behind + Jig's existing ports and recorded under policy. + - Remaining tail items are not automatic continuation work. They require replanning before + implementation because they carry product-surface, evidence, policy, or package-boundary + decisions outside the Phases 6-9 spine. - Repo planning handoff: - `jig` derives its repo plan directly from this milestone, decomposing the outcome into its own phases and stories. Org milestones carry no story list; that decomposition lives in Jig's delivery track. - The real run records M7 emits strengthen M6 seeding, but M6 does not block on M7 — M6's entry is already satisfiable by M1 examples or an M5 record. + - Concrete Codex transport evidence or an ADR is a post-M7 validation adjunct unless the + org explicitly decides that shipped transport evidence is required for M7 exit. + - A first-party TUI or dashboard needs product-surface design before implementation. + - A policy analyzer should wait for enough real run-history data to avoid designing against + synthetic or one-off examples. + - v0 contract freeze or package extraction is gated by Phase 9 records-integrity evidence + from Jig PR #39 plus package-boundary and product decisions; if the org requires + concrete transport evidence for M7 exit, that evidence should also precede any freeze. - Risks / kill assumptions: - Fails if a real driver can escalate its substrate — argv, credentials, or egress — past what the attestation authorized. diff --git a/ROADMAP.md b/ROADMAP.md index 63bcbe2..5e847d3 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -42,12 +42,12 @@ coupled only by a small set of **shared contracts (seams)**. Pin down each seam' and every layer can be designed in parallel against the contract, not against another layer's internals. The currently pinned seams are owned by existing layer repos. -| Seam (shared artifact) | Owner | Consumers | Status | -| ----------------------------------------------------------------- | ------------------ | ------------------------------ | ------------------------------------------------------------------------------------------------------------- | -| **Execution-plan contract shape** — Jig's one hard input boundary | `jig` | Planning layer produces to it | v0 shape: `jig/docs/design/contracts/execution-plan-contract-v0.md`; queued for real-driver exercise under M7 | -| **Observability / event records** — durable run output | `jig` | Learning loop consumes | v0 shape: `jig/docs/design/contracts/observability-records-contract-v0.md`; real run records planned under M7 | -| **Technical-design document format** | `technical-design` | Planning layer consumes | v0 handoff: `technical-design/docs/design/technical-design-handoff-contract.md` | -| **PRD / ID'd acceptance-criteria format** | `define-product` | Design + Planning cite the IDs | v0 contract: `define-product/docs/product/prd-contract.md` | +| Seam (shared artifact) | Owner | Consumers | Status | +| ----------------------------------------------------------------- | ------------------ | ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------- | +| **Execution-plan contract shape** — Jig's one hard input boundary | `jig` | Planning layer produces to it | v0 shape: `jig/docs/design/contracts/execution-plan-contract-v0.md`; M7 real-driver spine merged through Jig PR #39 | +| **Observability / event records** — durable run output | `jig` | Learning loop consumes | v0 shape: `jig/docs/design/contracts/observability-records-contract-v0.md`; M7 records-integrity spine merged through Jig PR #39 | +| **Technical-design document format** | `technical-design` | Planning layer consumes | v0 handoff: `technical-design/docs/design/technical-design-handoff-contract.md` | +| **PRD / ID'd acceptance-criteria format** | `define-product` | Design + Planning cite the IDs | v0 contract: `define-product/docs/product/prd-contract.md` | **Sequencing rule of thumb:** the highest-leverage early work is authoring Jig's two seams (execution-plan contract shape, observability records), because two downstream layers wait on their @@ -95,14 +95,13 @@ parallel. The current sequence is tracked in [`MILESTONES.md`](./MILESTONES.md). - **Depends on:** a valid execution plan (its one hard input boundary). Upstream layers are optional strong defaults, not prerequisites. - **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/`). With - the Phase 5 provider ports, composition root, and capability-attestation gate now merged, - jig also derives its real-provider integration plan from - [`M7`](./MILESTONES.md) — promoting the agent, execution-host, forge, and work-source seams - from reference adapters to real drivers behind the same contracts. + reconciling to product), and the local delivery spine now runs from the M5b walking + skeleton through the M7 real-provider track. Jig PR #39 merged the Phase 9 + records-integrity closeout at `3b3d224`, completing the M7 repo-track spine for real + agent/host, Forge, work-source, and records-integrity behavior behind the same contracts. + Tail work now needs replanning before implementation: concrete Codex transport evidence, + TUI/dashboard product-surface design, policy-analyzer timing based on real run history, + and any contract freeze or package extraction decision. - **References (curated):** - Product (own, drafted): `jig/docs/product/jig.md`, `guarantees.md`, `use-cases.md`, `concepts.md`. diff --git a/profile/README.md b/profile/README.md index 7f8e760..5d80578 100644 --- a/profile/README.md +++ b/profile/README.md @@ -22,13 +22,13 @@ repo can stay focused without inventing its own vocabulary. ## Repositories -| Repo | Role | Status | -| ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | -| [`define-product`](https://github.com/agentic-workflow-kit/define-product) | Product layer: PRD authoring and stable, ID'd acceptance criteria upstream of design. | Seeded; M3 contract bootstrap | -| [`technical-design`](https://github.com/agentic-workflow-kit/technical-design) | Design layer: frame, author, review-loop, enforce, and orchestrate technical designs. | Built; planning handoff contract pinned | -| [`jig`](https://github.com/agentic-workflow-kit/jig) | Delivery / execution engine: runs an approved plan under policy into reviewed, landed work, or a deliberate stop. The tool you run (`@agentic-workflow-kit/jig`). | Early; local dry-run walking skeleton (M5b Phases 0-2); M7 real-provider integration queued | -| [`design-to-plan`](https://github.com/agentic-workflow-kit/design-to-plan) | Planning layer: decompose approved designs into the execution-plan shape Jig runs. | Seeded; M4 contract bootstrap | -| Learning loop | Capture run outcomes and feed them back into future work. | Planned | +| Repo | Role | Status | +| ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | +| [`define-product`](https://github.com/agentic-workflow-kit/define-product) | Product layer: PRD authoring and stable, ID'd acceptance criteria upstream of design. | Seeded; M3 contract bootstrap | +| [`technical-design`](https://github.com/agentic-workflow-kit/technical-design) | Design layer: frame, author, review-loop, enforce, and orchestrate technical designs. | Built; planning handoff contract pinned | +| [`jig`](https://github.com/agentic-workflow-kit/jig) | Delivery / execution engine: runs an approved plan under policy into reviewed, landed work, or a deliberate stop. The tool you run (`@agentic-workflow-kit/jig`). | Early; M7 real-provider spine merged through PR #39; tail work gated for replanning | +| [`design-to-plan`](https://github.com/agentic-workflow-kit/design-to-plan) | Planning layer: decompose approved designs into the execution-plan shape Jig runs. | Seeded; M4 contract bootstrap | +| Learning loop | Capture run outcomes and feed them back into future work. | Planned | ## Lifecycle @@ -54,13 +54,14 @@ The shared vocabulary is intentionally small: ## Current Focus -The current org focus is M5: proving a narrow Jig local MVP slice now that Product, Technical -Design, and Planning contract shapes are seeded. M4 seeded `design-to-plan` so approved technical -designs can become Jig-ready execution plans without re-deciding product or design scope. +The current org focus is closing the M7 Jig spine and replanning the remaining tail work now that +Product, Technical Design, and Planning contract shapes are seeded. M4 seeded `design-to-plan` so +approved technical designs can become Jig-ready execution plans without re-deciding product or design +scope. -With Jig's Phase 5 provider ports and capability-attestation gate now merged, M7 (Real Provider -Integration) is ready for repo planning: Jig promotes its agent, execution-host, forge, and -work-source seams from reference adapters to real drivers behind the same contracts. +Jig's M7 real-provider spine is merged through PR #39 at `3b3d224`: real agent/host, Forge, +work-source, and records-integrity behavior are exercised behind the same contracts. Remaining tail +items are gated for replanning before implementation. Start with [`define-product`](https://github.com/agentic-workflow-kit/define-product) for product intent and acceptance-criteria IDs, [`technical-design`](https://github.com/agentic-workflow-kit/technical-design)