Skip to content

/dream: file HTDAG loop-discipline learning + wiki health-check #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dominno merged 1 commit into from
Jul 28, 2026
Merged

/dream: file HTDAG loop-discipline learning + wiki health-check #14

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions .claude/memory/log.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,3 +195,37 @@ change), `rotate` (archived old entries). Format: `## [YYYY-MM-DD] <op> | <summa
- Lesson: a deterministic gate is only as trustworthy as the input it reads — derive the
checked paths from the artifact that is actually applied (the diff), never from a
parallel self-report. The maker/checker "real artifact" rule extends to code gates.

## [2026-07-28] ingest | HTDAG loop discipline (persistent plan/DAG, re-plan node, no action without a node)
- Applied the three HTDAG planning disciplines to the loop meta-layer (not the 2-story
product backlog — that's a deliberate workflow test-stub; the machinery is the real DAG):
(1) a durable plan `.claude/memory/loop-plan.md` (typed nodes, `after:` edges, `ready`
rule) the loop reads at iteration start and rewrites; (2) **re-plan as a first-class
step run BEFORE dispatch** (loop.md step 9) so the loop consults the fresh DAG each
iteration; (3) **no action without a node** — every L2/L3 dispatch is a ready plan node,
node creation the only exempt bootstrap. Layered on top of the denylist + trust levels,
never replacing them. No `.js` engine touched. Filed the discipline in topics/workflow.md.
- Maker/checker: `/improve-skills` (24 agents) confirmed **0 blockers** (no gate weakened)
+ 14 important real+safe, all applied. It caught genuine DAG-contract holes in the first
draft — `in-progress` not excluded from the ready rule (crash-orphan → duplicate
dispatch), and no cascade when an `after:` dep is `dropped`/`escalated` (dependents
strand silently `blocked`). Filed the general "classify every persisted status + resolve
every non-`done` terminal dep-state" lesson in topics/workflow.md.
- Shipped as PR #13 (merged). Wired loop-plan.md into CLAUDE.md, index.md, skills-index.md,
loop-checklist.md §5, and the run-log format (`node:`/`re-plan:` lines).

## [2026-07-28] lint | Post-3-PR health-check — wiki clean, one flag left as-is
- Wiki in sync: 7/7 topic pages resolve from index.md, no orphans, no broken cross-links,
no contradictions (all surfaces consistently name loop-plan.md after the HTDAG change).
- Skills index complete: 12/12 commands have a `description` and a routing row; no dead
rows, no near-duplicates.
- Diagram drift check (`docs/workflow-graphs.md` vs `.claude/workflows/*.js`): node counts
match — critic-panel 10 critics, improve-skills 6 lenses, gap-analysis 7 dimensions,
e2e-design 5 categories; model tiers (🟢 fan-out / 🔵 gate) match FANOUT_MODEL/JUDGE_MODEL.
- Product/tooling topic pages (tooling, build-and-verify, testing, client-react,
code-organization, remote-env) reviewed — all evergreen, nothing stale.
- log.md 215 lines (< 500) — no rotation.
- **Flagged, not fixed (append-only history):** several recent entries carry `[2026-06-29]`
while later work merged ~2026-07-27/28. Left intact — the 06-29 cluster is 7 entries
mostly from genuine prior sessions, so rewriting dates risked corrupting correct history
more than it fixed. Reported for the record; no rewrite without a clear per-entry basis.
6 changes: 5 additions & 1 deletion .claude/memory/topics/workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,11 @@
plan node, and node creation is the *only* action exempt (the sanctioned bootstrap, so
an empty plan populates rather than deadlocks). Readiness never bypasses the denylist
or trust level — those gates stay on top. `loop-plan.md` = current mutable plan;
`loop-run-log.md` = append-only history — keep them distinct.
`loop-run-log.md` = append-only history — keep them distinct. **DAG-contract lesson**
(from the checker round): a deterministic readiness rule must classify *every* persisted
status (exclude `in-progress`, or a crash-orphaned node re-reads as ready → duplicate
dispatch) and resolve *every* non-`done` terminal dep-state (a `dropped`/`escalated`
dependency must cascade-resolve, else its dependents strand silently `blocked`).
- Custom commands live in `.claude/commands/` (each with a `description` for
routing); the grouped "when to use" catalog is `.claude/skills-index.md`. A
catalog file must NOT live in `.claude/commands/` — anything there auto-registers
Expand Down
Loading