From 02e229f73e5a2fc61002792fafc7af1fee1e362c Mon Sep 17 00:00:00 2001 From: Alan Szmyt Date: Mon, 24 Aug 2026 18:51:25 -0400 Subject: [PATCH 1/2] docs(roadmap): reconcile the 2026-08-24 execution graph Roadmap-Step: PAC-Q02 --- ROADMAP.md | 172 ++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 171 insertions(+), 1 deletion(-) diff --git a/ROADMAP.md b/ROADMAP.md index be1ac12..ea792c9 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -8,7 +8,7 @@ status: provisional owners: - egohygiene created: 2026-08-19 -updated: 2026-08-21 +updated: 2026-08-24 governed_by: - architecture-roadmap depends_on: @@ -26,6 +26,176 @@ supersedes: [] # Pace Roadmap + + +## 2026-08-24 execution snapshot + +> This evidence-reconciled snapshot is the issue-generation and visual-roadmap handoff. The longer-horizon strategy below remains canonical context; generated HTML, JSON, progress, issue plans, and commit lists are projections. + +**Lifecycle:** seed implementation +**Current gate:** Add observed-state capture and a drift report before attempting the reviewable convergence plan tracked by issue #2. +**North-star outcome:** Reviewable fleet convergence from declared desired state, observed state, and explicit drift. + +### Visual roadmap publication + +**Mode:** `central` +**Route:** `/roadmap/pace/` +**Current publication evidence:** GitHub source and CI only; no Pages or release publication observed. + +Publish the public-safe projection through egohygiene.io at /roadmap/pace/. This repository owns intent and acceptance evidence; it does not add a second site deployment. + +### Quest line + + +#### PAC-Q01 — Lock desired state + +**State:** `complete` +**Depends on:** None + +**Outcome:** Desired fleet state is represented by a deterministic lock artifact. + +**Exit criteria:** + +- [x] The lock is reproducible. +- [x] Validation runs green in CI. + +**Current evidence:** + +- PR #4 merged at 99d479445406. +- Desired-state lock validation was observed green. + + +#### PAC-Q02 — Capture observed state + +**State:** `active` +**Depends on:** `PAC-Q01` + +**Outcome:** Pace can record what is actually deployed without mutating it. + +**Exit criteria:** + +- [ ] An observed-state schema and collector are implemented. +- [ ] Fixtures prove stable normalization of at least one representative fleet. + +**Current evidence:** + +- No observed-state implementation was found. + + +#### PAC-Q03 — Render actionable drift + +**State:** `planned` +**Depends on:** `PAC-Q02` + +**Outcome:** Desired and observed states produce a deterministic, human-reviewable drift report. + +**Exit criteria:** + +- [ ] Additions, removals, and changes are distinguished. +- [ ] Repeated runs on unchanged input are identical. + +**Current evidence:** + +- No drift engine or report was observed. + + +#### PAC-Q04 — Create a reviewable convergence plan + +**State:** `planned` +**Depends on:** `PAC-Q03` + +**Outcome:** Issue #2 yields an ordered plan with explicit risk, ownership, and rollback information. + +**Exit criteria:** + +- [ ] The plan is generated without applying changes. +- [ ] Each action links to the drift that caused it. + +**Current evidence:** + +- Issue #2 is the identified next planning gate. + + +#### PAC-Q05 — Prove a no-write fleet pilot + +**State:** `planned` +**Depends on:** `PAC-Q04` + +**Outcome:** A representative repository fleet can be assessed safely before rollout automation is considered. + +**Exit criteria:** + +- [ ] The pilot runs with read-only credentials. +- [ ] Operators approve the generated plan and documented rollback boundary. + +**Current evidence:** + +- No observed-state, drift, or fleet pilot evidence was found. + + +#### PAC-Q06 — Roll out roadmap adoption safely + +**State:** `planned` +**Depends on:** `PAC-Q05`, `REL-Q05` + +**Outcome:** Pace detects stale roadmap adoption and proposes one bounded, reviewable repository update at a time. + +**Exit criteria:** + +- [ ] Dry-run drift covers contract, renderer, workflow, route, and publication-mode versions. +- [ ] Write authority is separately approved and every proposal has a rollback path. + +**Current evidence:** + +- Only the desired-state lock is implemented today; fleet rollout remains unproven. + +### Roadmap-to-issue handoff + +- A step is complete only when its exit criteria and required evidence are satisfied; commit count never determines progress. +- Ready or planned steps without an issue are candidates for the private, duplicate-aware roadmap.issue-plan.json dry run. +- Issue creation or reconciliation requires human approval or an explicitly authorized Pace operation and returns issue references through a reviewable roadmap pull request. +- Pull requests and commits should include Roadmap-Step: ; historical evidence may be linked through existing issue and pull-request relationships. +- Public rendering uses only allowlisted build-time evidence and never places a GitHub token or private issue plan in the browser artifact. + + + ## Strategic context This roadmap describes capability evolution, not promised dates or an issue queue. Sequence follows architecture dependencies and may change when evidence or risk changes. From cac77716498c2e2a69f4c7e5796c2d82d949ead4 Mon Sep 17 00:00:00 2001 From: Alan Szmyt Date: Mon, 24 Aug 2026 19:00:18 -0400 Subject: [PATCH 2/2] docs(roadmap): constrain issue-plan candidates Roadmap-Step: PAC-Q02 --- ROADMAP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ROADMAP.md b/ROADMAP.md index ea792c9..fc3ebd6 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -189,7 +189,7 @@ issues: [] ### Roadmap-to-issue handoff - A step is complete only when its exit criteria and required evidence are satisfied; commit count never determines progress. -- Ready or planned steps without an issue are candidates for the private, duplicate-aware roadmap.issue-plan.json dry run. +- Ready steps without an issue are candidates for the private, duplicate-aware roadmap.issue-plan.json dry run. Planned steps remain preview-only unless a reviewer explicitly opts them in with issue_policy: propose. - Issue creation or reconciliation requires human approval or an explicitly authorized Pace operation and returns issue references through a reviewable roadmap pull request. - Pull requests and commits should include Roadmap-Step: ; historical evidence may be linked through existing issue and pull-request relationships. - Public rendering uses only allowlisted build-time evidence and never places a GitHub token or private issue plan in the browser artifact.