Skip to content

Implementation Status

Jump to bottom
Chris Sweet edited this page Jun 13, 2026 · 7 revisions

type: index up: "Home_llm-wiki-memory-template" tags: [status, implementation, governance]

Implementation Status

What is actually implemented in the template repo vs what is documented as aspirational. Updated whenever a feature lands, or when a documented feature is found to be unimplemented (in which case it migrates from one section to another and the migration is recorded in Wiki-Corrections-Log).

The wiki was authored after the template code shipped, from project notes. Some pages document the design as imagined rather than the code as written. This page is the reconciliation: the single normative answer to "is this a real feature today?"

Implemented (in code on main)

Feature / page Location in code
Three-Operations (Ingest, Query, Lint) .claude/skills/wiki-*.md, .claude/commands/wiki-*.md, .cursor/rules/wiki-*.mdc
Typed-Edges-and-Frontmatter Convention enforced by procedures and SCHEMA
Verification-Gate wiki/agents/verification-gate.md, referenced from 6 surface files
Discipline-Gates wiki/agents/discipline-gates.md
PostToolUse-Hook (opt-in) wiki/agents/claude-code/templates/posttooluse-hook.sh, installed via setup.sh --posttooluse-hook
Sync-Flow (the ALWAYS_FILES contract itself) scripts/update-from-template.sh, scripts/check-template-version.sh
Knowledge-Graph-Pipeline scripts/kg/ (rdflib + pyshacl in-process; PR #14). Not yet in ALWAYS_FILES; likely to ship as an opt-in feature under features/
Log-Entry-Attribution wiki/init-wiki.sh --agent, the per-overlay skills and commands
Agent-Overlays (claude-code, cursor) wiki/agents/claude-code/, wiki/agents/cursor/, .claude/, .cursor/
Template-vs-Derived-Projects Repo structure plus scripts/instantiate.sh
Governance (three-tier model) Documentation only; no code dependency
Lesson-Hook-Type-Matters Historical observation, encoded into the corrected PostToolUse-Hook
Lesson-Parallel-File-Drift Historical observation, documented in init-wiki.sh MAINTENANCE NOTE
Lesson-Validation-Methodology Documentation only (validation discipline)
Limitation-Prompt-Injection-Residual Documents a real residual risk; not a feature
Applied-Example-Microelectronics-Tutor-Demo External demo project, exists separately
Memory boundary subsection in CLAUDE.md CLAUDE.md.template + wiki/agents/claude-code/templates/claude-md-snippet.md; PR #28 (merged 2026-06-12). Closes Analysis-of-model_fusion-Recommendations rec #8
analysis + decision page types in SCHEMA wiki/init-wiki.sh (both create-mode heredoc + update-mode append, byte-identical); PR #29 (merged 2026-06-12). Closes Analysis-of-model_fusion-Recommendations rec #4. The wiki's first type: analysis pages (Analysis-of-model_fusion-Recommendations, Analysis-of-Wiki-Push-Race-Pattern) became retroactively valid the moment this merged
SessionStart auto-load (index + last 5 log entries) wiki/agents/claude-code/templates/session-start-hook.sh ships content-injection logic; PR #30 (merged 2026-06-12). Closes Analysis-of-model_fusion-Recommendations rec #1. Behavioural impact: wiki acts as compounding memory rather than RAG-on-demand
Inverse-edge vocabulary in SCHEMA + verification-gate wiki/init-wiki.sh Edges-as-Interface-Operations table gains an Inverse column; wiki/Edge-Types.md.template declares extendedBy for the previously-missing extends inverse; wiki/agents/verification-gate.md reciprocal-edge criterion realigned to KG-materialises-inverses stance; PR #31 (merged 2026-06-12). Closes the in-repo half of Limitation-Inverse-Edges-Missing (issue #3); upstream SHACL spec at la3d/llm-wiki-colab and PostToolUse write-time check remain pending
Home page category-nav convention wiki/init-wiki.sh HOMEEOF heredoc gains a ## Categories placeholder section; SCHEMA Special Files block gains a ### Home_<repo>.md sub-entry naming the category-level update rule; wiki/agents/verification-gate.md gains a matching criterion; PR #32 (merged 2026-06-12). New wiki convention: humans get a curated entry point on Home; agents update Home only when a new top-level category emerges or a significant page lands

Aspirational (designed, not yet implemented)

Feature / page What is missing Next step
none overlay as a true overlay No wiki/agents/none/ directory --agent=none exists in instantiate.sh as a no-install flag; a true none overlay would document the no-agent path explicitly (probably not warranted)
Multi-Agent-Write-Protocol production wiring Sourcing protocol.sh from the verification gate / ingest skills, installing a pre-push git hook in derived projects' wiki sub-repos, deciding on an LLM-driven resolve_fn for content conflicts. The protocol design and reference implementation are NOT the gap. Spec written (push-time-only design with complementary SessionStart auto-pull). Reference implementation shipped at scripts/wiki-write-protocol/ (renamed from multi-agent-write-protocol-proto/ via PR #33, open as of 2026-06-13); 9 scenarios PASS standalone and via the test harness; CI green on ubuntu-latest + macos-latest. Reclassified 2026-06-12 from aspirational to empirically needed after the wiki/web_forager.wiki/ collision (3-4 human+agent teams; 20 commits of remote drift; manual log-file reconcile). PR6 (#33, open) does the housekeeping-only rename. PR7 (planned) will land the wiring: hook installation in init-wiki.sh, wiki_push invocation from the ingest skills, resolve_fn decision (likely defer-to-agent-turn, not subprocess). See Analysis-of-Wiki-Push-Race-Pattern for the empirical motivation and the PR6/PR7 split rationale.
Inverse-edge KG materialisation (upstream SHACL spec) The KG build pipeline materialises forward edges into their inverses via SPARQL CONSTRUCT, but only for inverse pairs the SHACL spec declares. The spec lives upstream at https://la3d.github.io/llm-wiki-colab/. The in-repo vocabulary now exists (PR #31). The upstream SHACL spec needs PRs declaring extendedBy/supportedBy/criticizedBy as owl:inverseOf of their forward predicates. Tracking under Limitation-Inverse-Edges-Missing. Was rec #9(b)(ii) in Analysis-of-model_fusion-Recommendations; deferred there pending the in-repo half landing (now done).
Inverse-edge write-time enforcement (PostToolUse hook) A PostToolUse hook check that the agent has not asserted an inverse predicate in a source document. Currently relies on prose discipline in verification-gate.md. Was rec #9(b)(iii) in Analysis-of-model_fusion-Recommendations; explicitly deferred there until #9(b)(i) and (ii) land and the prose-discipline path is shown to be insufficient.

Partially implemented

Feature / page What works What is missing
Cursor overlay (per Agent-Overlays and Limitation-Untested-Overlays) Files install correctly via wiki/agents/cursor/setup.sh; structurally validated Behavioral validation: no live Cursor session has confirmed the procedures fire as designed

In review (open PR, not yet merged into template main)

Feature / page Where it lives PR
Test-Harness chrissweet/llm-wiki-memory-template branch add-test-harness; scripts/test-mvp/ + .github/workflows/test-harness.yml #10 (addresses issue #5; CI green on ubuntu-latest + macos-latest)
Wiki-Write-Protocol housekeeping rename scripts/wiki-write-protocol/ (renamed from multi-agent-write-protocol-proto/); README rewritten to drop "prototype" framing; test harness path updated; 3 new structural assertions lock the rename #33 (opened 2026-06-13; CI green on both platforms; mergeStateStatus CLEAN). PR6 of the write-protocol cluster from Analysis-of-Wiki-Push-Race-Pattern. No behaviour change in derived projects; the actual wiring is PR7.

See also

Clone this wiki locally