From 216d8f473cfb6a1a0e54031824b1a4946afdffc8 Mon Sep 17 00:00:00 2001 From: Alan Szmyt Date: Mon, 24 Aug 2026 18:52:21 -0400 Subject: [PATCH 1/2] docs(roadmap): reconcile the 2026-08-24 execution graph Roadmap-Step: MIC-Q02 --- ROADMAP.md | 151 ++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 150 insertions(+), 1 deletion(-) diff --git a/ROADMAP.md b/ROADMAP.md index 9cc4a2f..d4bd937 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -8,7 +8,7 @@ status: draft owners: - egohygiene created: 2026-08-19 -updated: 2026-08-19 +updated: 2026-08-24 governed_by: - architecture-roadmap depends_on: @@ -26,6 +26,155 @@ supersedes: [] # Mindcap 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:** functional capture and vault alpha +**Current gate:** Apply Ruff formatting to the vault catalog and CLI, restore CI, and reconcile stale extraction-era documentation. +**North-star outcome:** A privacy-aware capture and vault layer that normalizes personal sources into durable, portable records. + +### Visual roadmap publication + +**Mode:** `central` +**Route:** `/roadmap/mindcap/` +**Current publication evidence:** Source-only Python library and CLI; no Pages or release publication observed. + +Publish the public-safe projection through egohygiene.io at /roadmap/mindcap/. This repository owns intent and acceptance evidence; it does not add a second site deployment. + +### Quest line + + +#### MIC-Q01 — Build capture and vault foundations + +**State:** `complete` +**Depends on:** None + +**Outcome:** Multiple source adapters, a library and CLI, and a vault implementation exist. + +**Exit criteria:** + +- [x] Representative sources can be captured into the vault. +- [x] Library and CLI entry points are present. + +**Current evidence:** + +- Issues #13, #16, #18, #21, #24, #26, and #28 correspond to implemented source and vault work. +- Architecture PR #29 merged at abce04b0d502504741061ab4c8ea65fe446e5f13 on 2026-08-20. + + +#### MIC-Q02 — Restore CI and standalone documentation + +**State:** `blocked` +**Depends on:** `MIC-Q01` + +**Outcome:** The standalone repository formats, tests, packages, and documents itself correctly. + +**Exit criteria:** + +- [ ] Ruff is green for the vault catalog and CLI. +- [ ] README instructions no longer point to tools/mindcap in the former host repository. + +**Current evidence:** + +- CI was red because Ruff would reformat src/mindcap/vault/catalog.py and src/mindcap_cli/app.py. +- README retained stale tools/mindcap extraction instructions. + + +#### MIC-Q03 — Add redaction and attachment guarantees + +**State:** `ready` +**Depends on:** `MIC-Q02` + +**Outcome:** Sensitive content and binary attachments follow explicit, tested storage and export rules. + +**Exit criteria:** + +- [ ] Redaction policies are configurable and covered by fixtures. +- [ ] Attachment integrity, limits, and failure recovery are tested. + +**Current evidence:** + +- Redaction and attachment guarantees were absent from the observed implementation and backlog. + + +#### MIC-Q04 — Stabilize the source-plugin SDK + +**State:** `planned` +**Depends on:** `MIC-Q03` + +**Outcome:** New capture sources can be added without coupling them to vault internals. + +**Exit criteria:** + +- [ ] A versioned adapter contract and conformance fixtures exist. +- [ ] At least two existing sources migrate without behavioral regression. + +**Current evidence:** + +- Multiple adapters exist, but no stable plugin SDK release was observed. + + +#### MIC-Q05 — Prove vault recovery and Mindgarden ingestion + +**State:** `planned` +**Depends on:** `MIC-Q03`, `MIC-Q04` + +**Outcome:** A backed-up vault restores cleanly and feeds Mindgarden through a versioned privacy boundary. + +**Exit criteria:** + +- [ ] Backup and restore preserve identity and attachment integrity. +- [ ] Mindgarden ingests a sanitized fixture without direct dependence on Mindcap internals. + +**Current evidence:** + +- No release, backup/restore proof, or Mindgarden integration evidence was observed. + +### 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 0904c82b558ea6f48ab785ac4386c3fdca75fe3c Mon Sep 17 00:00:00 2001 From: Alan Szmyt Date: Mon, 24 Aug 2026 19:00:59 -0400 Subject: [PATCH 2/2] docs(roadmap): constrain issue-plan candidates Roadmap-Step: MIC-Q02 --- ROADMAP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ROADMAP.md b/ROADMAP.md index d4bd937..099be53 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -168,7 +168,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.