docs(plan): commit the executed event-chain plan (v0.10.0 slice 1) - #84
Conversation
… plan (v0.10.0 slice 1)
There was a problem hiding this comment.
Pull request overview
This PR adds a dated implementation plan document under docs/superpowers/plans/ to preserve the executed v0.10.0 slice-1 “hash-linked event chain + anchored doctor gate” plan as a post-release record.
Changes:
- Add the full slice-1 implementation plan write-up (constraints, task breakdown, interfaces, test strategy, and rollout notes).
Comments suppressed due to low confidence (5)
docs/superpowers/plans/2026-07-24-event-chain-tamper-evident-provenance.md:1021
- This placeholder is inside a Python-fenced snippet; the
<...>token makes the example invalid Python. If this is intentionally pseudocode, consider making it a comment so the snippet stays syntactically valid when copied.
migrate_store(ws); <append one iteration through the store + sync state.json>
docs/superpowers/plans/2026-07-24-event-chain-tamper-evident-provenance.md:1282
- This is in a Python-fenced code block, but
<chained workspace helper>is not valid Python. Consider using the real helper name (e.g._chained_workspace(tmp_path)fromscripts/test_doctor_eventstore.py).
ws = <chained workspace helper>(tmp_path) # >= 3 events, state.json synced
docs/superpowers/plans/2026-07-24-event-chain-tamper-evident-provenance.md:1309
- This placeholder is inside a Python-fenced snippet;
<chained workspace helper>is not valid Python for copy/paste. Suggest replacing it with the concrete helper name used in the codebase (e.g._chained_workspace).
ws = <chained workspace helper>(tmp_path)
docs/superpowers/plans/2026-07-24-event-chain-tamper-evident-provenance.md:1319
- This line is inside a Python-fenced block but is currently raw placeholder text, which makes the snippet invalid Python. If it’s meant as a TODO/pseudocode marker, prefix it with
#so copy/paste remains syntactically valid.
<rebuild the record dict exactly as read_event_rows does, with prev_event_hash=prev>
docs/superpowers/plans/2026-07-24-event-chain-tamper-evident-provenance.md:1328
- This placeholder line is inside a Python-fenced snippet; as written it is not valid Python. Consider converting it to a comment to keep the example syntactically valid when copied.
<rewrite state.json (and terminal_state.json if present) to match the forged projection>
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ```python | ||
| def test_status_and_replay_expose_chain_head(tmp_path): | ||
| ws = <existing fresh-contract helper>(tmp_path) # chained store |
![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: 703eada962
ℹ️ 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".
|
|
||
| ## Program context (what this plan is Slice 1 of) | ||
|
|
||
| Source: `review/2026-07-24-graph-engineering-report-assessment.md` (adjudication of an external "graph engineering" report; 32/32 repo claims confirmed, 6 proposal blockers). The accepted program is **tamper-evident provenance** — the "graph engineering" framing itself was rejected. |
There was a problem hiding this comment.
The program context and its claimed adjudication are delegated to review/2026-07-24-graph-engineering-report-assessment.md, but that file does not exist anywhere in the reviewed tree (a repo-wide path/content search also finds no replacement). Consequently, readers cannot verify the stated 32/32 claim review, six blockers, or the rationale behind the accepted and permanently rejected work; commit the referenced report or replace this with a link/path to an available source.
Useful? React with 👍 / 👎.
Repo convention: plans live in docs/superpowers/plans/ (dated). This is the plan PR #82 and #83 executed — committed post-release for the record. Docs-only, no code changes.