Skip to content

Wiki Corrections Log

Chris Sweet edited this page Jun 13, 2026 · 6 revisions

type: log up: "Home_llm-wiki-memory-template" tags: [corrections, governance, log]

Wiki Corrections Log

Chronological record of corrections made to wiki pages where they did not match the template code on main. Append-only: each entry is the receipt for one drift fix. See Implementation-Status for the current real vs aspirational classification.

The wiki was authored from project notes after the code shipped, so some pages describe the design as imagined rather than the code as written. This log records the receipts as those gaps are closed.

2026-05-31

Audit triggered by an MVP-planning exercise that needed accurate references to template wiki pages. Cross-checking the wiki against crcresearch/llm-wiki-memory-template main surfaced three substantive drifts. All corrected in a single commit; this log entry is the receipt.

  • by: Chris Sweet via claude-code

  • Knowledge-Graph-Pipeline: was presented as an implemented feature (scripts/kg/build-graph.sh, Fuseki at localhost:3030/wiki/sparql). Reality: no scripts/kg/ directory exists in the template repo. Now flagged status: aspirational in frontmatter with a "NOT YET IMPLEMENTED" banner; the design content is preserved as a target. Citations on 7 other pages (Home_llm-wiki-memory-template, index_llm-wiki-memory-template, SCHEMA_llm-wiki-memory-template, Wiki-LLM-Pattern, Three-Operations, Typed-Edges-and-Frontmatter, Limitation-Inverse-Edges-Missing) softened to make the aspirational status visible at every mention.

  • Limitation-Untested-Overlays: claimed wiki/agents/none/ overlay exists. Reality: --agent=none in instantiate.sh is a no-install flag; there is no wiki/agents/none/ directory. Page now describes the minimal-mode flag accurately. Also fixed: the claim that the README uses the phrase "untested-live"; the actual README uses "Shipped but not yet validated" and "Likewise unvalidated".

  • Agent-Overlays: the "Current overlays" table listed none alongside claude-code and cursor as if it were a third overlay. Restructured: true overlays now in one table; minimal mode (--agent=none) described in a separate subsection that names what it actually is.

  • Sync-Flow: the "contract: ALWAYS_FILES" section mixed contents from four separate arrays (ALWAYS_FILES, CLAUDE_FILES, CURSOR_FILES, ONE_SHOT_FILES) and listed scripts/kg/*.sh (nonexistent). Section rewritten to accurately describe all four arrays plus SUBSTITUTE_FILES, with the actual file lists from the sync scripts.

This entry coincides with the creation of Implementation-Status and this log itself.

Verification debts noted but not corrected this round

  • Applied-Example-Microelectronics-Tutor-Demo: status section is from before the 2026-05-19 conference talk; today is 2026-05-31. Likely stale; requires a check against the demo project's current state.
  • Limitation-Prompt-Injection-Residual: describes the permission model in .claude/settings.json.template; the specific claims were not audited against the file this round.
  • Governance: references chrissweet/llm-wiki-tutor-template as an existing variant; the repo's existence was not verified this round.

2026-06-12

Lint pass after the KG pipeline shipped in PR #14 (template commit 2018186, "scripts/kg/: KG build pipeline (rdflib + pyshacl) + harness coverage"). The wiki still described the pipeline as aspirational across nine pages. Reclassified to implemented, technical details corrected (rdflib + pyshacl in-process, not Fuseki at localhost:3030), and a distribution caveat added: scripts/kg/ is in the template but not yet in ALWAYS_FILES, so derived projects do not receive it on update.

  • by: Chris Sweet via claude-code

  • Knowledge-Graph-Pipeline: rewritten. Banner removed; status: aspirationalstatus: implemented; architecture section now describes rdflib + pyshacl in-process with optional Fuseki, matching scripts/kg/README.md. New "Distribution to derived projects" section flags the ALWAYS_FILES gap.

  • Implementation-Status: row for Knowledge-Graph-Pipeline moved from Aspirational to Implemented; the new row records the ALWAYS_FILES caveat and the likely path via features/.

  • Softened "(not yet implemented)" parentheticals across Wiki-LLM-Pattern, Three-Operations, Typed-Edges-and-Frontmatter, SCHEMA_llm-wiki-memory-template (three locations), Limitation-Inverse-Edges-Missing, and index_llm-wiki-memory-template. Each now references the pipeline as an existing feature rather than a designed-but-pending one.

  • Sync-Flow: "Not on any list" subsection rewritten. Old framing ("scripts/kg/ does not exist on main") is now incorrect; the pipeline exists but is not in ALWAYS_FILES, with the features/ framework named as the planned distribution path.

  • Wiki-LLM-Pattern line 23: replaced the placeholder example [Markov-Chain-v5c2](Markov-Chain-v5c2) (dead link, only an illustration) with a real wiki page name to keep the example from showing up as a dead link to the lint pass and the KG.

Bidirectional back-references added (same pass)

Lint surfaced 70 asymmetric link pairs. Most are intentional (index/log roll-ups). The high-value subset for concept ↔ lesson/limitation pairs was patched in the same commit so the back-references match the forward edges' semantics rather than appearing only in the log:

  • Verification-Gate, Discipline-Gates → backlink Limitation-Prompt-Injection-Residual
  • Lesson-Validation-Methodology → backlink Limitation-Inverse-Edges-Missing, Template-vs-Derived-Projects, Agent-Overlays
  • Lesson-Parallel-File-Drift → backlink Governance, Agent-Overlays
  • Template-vs-Derived-Projects → backlink Wiki-LLM-Pattern, Governance
  • PostToolUse-Hook → backlink Lesson-Validation-Methodology
  • Agent-Overlays → backlink Lesson-Validation-Methodology, Lesson-Parallel-File-Drift
  • Sync-Flow See-also section refreshed with Knowledge-Graph-Pipeline, Governance

Verification debts noted but not corrected this round

  • [[Applied-Example-Microelectronics-Tutor-Demo]] staleness flagged on 2026-05-31 is still open; today is 2026-06-12.
  • [[Limitation-Prompt-Injection-Residual]] permission-model claims still not audited against .claude/settings.json.template.
  • [[Governance]] mention of chrissweet/llm-wiki-tutor-template still not verified.

2026-06-12 (second pass, same day)

Continued lint after the user requested a content review of Lessons-Learned-From-model_fusion. The page declared "verified against HEAD fc2472a (2026-06-04)" but fc2472a does not resolve in the current crcresearch/llm-wiki-memory-template history (likely a fork-local SHA). Today's HEAD is 88f4624 (2026-06-12). Three commits between the original snapshot and HEAD touch the field report's recommendations.

  • by: Chris Sweet via claude-code

  • Lessons-Learned-From-model_fusion: refreshed verification snapshot to HEAD 88f4624. Headline tally updated from "0 / 2 / 10" to "0 fully addressed / 3 partial / 9 missing", and the separate recursive-bootstrap finding moved from "open proposal" to "RESOLVED in PR #25". Row 9 (reciprocal-edge discipline) refined: the inverse-edge vocabulary shipped in wiki/Edge-Types.md.template via PR #16 (commit b86c9e4), so the gap narrowed from "vocabulary itself unimplemented" to "vocabulary shipped, not yet wired into init-wiki.sh page-type list, PostToolUse hook does not enforce". The body of #9(a) rewritten to reflect the shipped vocabulary and to reference the Knowledge-Graph-Pipeline as shipped (PR #14) rather than designed. Provenance section path corrected from /Users/csweet1/Documents/projects/TCF/llm-wiki-memory-template/ (does not exist) to the actual checkout at /Users/csweet1/Documents/projects/CRS_research/llm-wiki-memory-template/, and the unresolvable fc2472a SHA flagged as fork-local.

  • The recursive bootstrap problem section: rewritten from "Proposed fix" to "RESOLVED in PR #25", with the specific behavior of scripts/instantiate.sh --dev-self enumerated (wiki clone expectation, real CLAUDE.md render, SessionStart + PostToolUse hook install, gitignored artifacts).

  • Bidirectional back-references added (5 of 10 entries in the field report's related: frontmatter). All 10 were one-way at filing time. Patched the high-value subset on Applied-Example-Microelectronics-Tutor-Demo (sister page, second empirical test), Lesson-Hook-Type-Matters (command-type hook requirement), Lesson-Parallel-File-Drift (drift caveat invoked for #4 and #10), Lesson-Validation-Methodology (filesystem-verification methodology), Limitation-Inverse-Edges-Missing (#9 builds on it). The other 5 entries (Verification-Gate, Discipline-Gates, Three-Operations, PostToolUse-Hook, Implementation-Status) left one-way consistent with the morning's rule for heavily-linked foundational and roll-up pages.

Verification debts still open

2026-06-12 (third pass, same day — Home sync)

Lint pass after Analysis-of-model_fusion-Recommendations was filed and PR #32 (Home category-nav convention) was opened. Two drifts found on Home_llm-wiki-memory-template: the morning's KG-aspirational → implemented correction missed Home (line 29 still said "designed, not yet implemented"), and the two model_fusion pages filed today were added to the Index Applied-examples section but not to Home. Both fixed in one commit. Dogfoods PR #32's category-level rule: pages significant enough to be a representative link for their category get a Home entry.

  • by: Chris Sweet via claude-code

  • Home_llm-wiki-memory-template line 29: KG-Pipeline parenthetical updated from "(designed, not yet implemented): scripts/kg/, Fuseki, SPARQL over wiki frontmatter" to "(PR #14): scripts/kg/, rdflib + pyshacl in-process; SPARQL over wiki frontmatter, optional Fuseki" — matches the same line in index_llm-wiki-memory-template.md after the morning's correction.

  • Home_llm-wiki-memory-template Applied examples section: added entries for Lessons-Learned-From-model_fusion and Analysis-of-model_fusion-Recommendations with one-line descriptions matching the Index entries' framing. Both were already in Index (the morning's two ingests); Home was missed.

Verification debts still open

2026-06-12 (fourth pass, same day — Multi-Agent-Write-Protocol reclassification)

User provided empirical data showing the web_forager derived project has 3-4 human+agent teams writing concurrently to the wiki sub-repo, with a 2026-06-12 production collision (Csweet1 push rejected after Omegaice advanced remote by 20 commits; conflict on log_web_forager.md from same-date entries by both authors; ~3 minute manual rebase recovery). This contradicts an assumption I had been making earlier in the session about wikis being "single-writer most of the time," and the wiki's classification of Multi-Agent-Write-Protocol as "aspirational" was incomplete. The protocol's reference implementation was shipped in PR #11 with 9/9 CI scenarios green; the gap is production wiring, not design.

  • by: Chris Sweet via claude-code

  • Multi-Agent-Write-Protocol banner: rewritten from "design + prototype only, not yet wired into any agent overlay or shipped in the template" to "design + prototype shipped, production wiring is the gap." Adds the empirical motivation (web_forager collision) and removes the misleading "aspirational" framing that conflated "designed" with "not implemented."

  • Implementation-Status row for Multi-Agent-Write-Protocol: rewritten. The "What is missing" column now says "Production wiring into the agent overlay. The protocol and reference implementation are not the gap." The Next-step column names the specific wiring tasks (source protocol.sh from skills, install pre-push hook, rename proto dir, add LLM-driven resolve_fn).

  • New page: Analysis-of-Wiki-Push-Race-Pattern (type: analysis, second page filed under this type; both pages acknowledge SCHEMA violation that PR #29 closes). Documents the empirical evidence, the gap analysis, and the wiring outline. Cross-references the source incident details, the proto's location, and the sister analysis page.

  • Bidirectional back-refs: added See-also entries to this new page on Analysis-of-model_fusion-Recommendations (sister analysis page) and Lesson-Validation-Methodology (the structural + behavioral discipline argument).

  • Index and Home updated per the just-shipped PR #32 category-level rule: the new page is significant enough to warrant a Home entry, not just an Index entry.

Verification debts still open

2026-06-13 — Cluster landed + PR6 open: reconcile classifications

The five model_fusion-cluster PRs (#28-#32) and the Home category-nav PR all merged to crcresearch/llm-wiki-memory-template main on 2026-06-12. PR6 (#33, wiki-write-protocol rename) opened 2026-06-13 with CI green. Implementation-Status still classified all of the cluster work and the wiring rename in their pre-merge buckets. Reconciled today.

  • by: Chris Sweet via claude-code

  • Implementation-Status: five new rows added to the Implemented table for PRs #28-#32 (Memory boundary, analysis+decision page types, SessionStart auto-load, inverse-edge vocabulary, Home category-nav). Each row names the specific files that changed and the Analysis-of-model_fusion-Recommendations recommendation it closes. The previously single Aspirational row for Multi-Agent-Write-Protocol split into three: production wiring (PR7, planned), inverse-edge upstream SHACL spec (deferred), inverse-edge PostToolUse write-time check (deferred). New In review row for PR #33 (PR6 rename).

  • Multi-Agent-Write-Protocol banner: appended a 2026-06-13 update line referencing PR #33 and the PR6/PR7 housekeeping-then-wiring split.

  • Limitation-Inverse-Edges-Missing: substantively rewritten. Title now reads "(Partially Closed)". The proposed-fix section replaced with what PR #31 actually shipped: the camelCase inverse names (extendedBy, supportedBy, criticizedBy) that match Edge-Types.md.template, with the KG-materialises-not-authored stance made explicit. The earlier snake-case proposal (extended-by: etc.) was outdated. New "What remains" section names the upstream SHACL gap and the optional PostToolUse check. Status: in-repo half closed, upstream + write-time pending.

Verification debts still open

See also

Clone this wiki locally