We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
log: lint Sync-Flow de-counting
lint: de-count Sync-Flow array descriptions (counts rot; manifest is the authoritative list)
Configure union merge for index/log files
log: lint manifest-consolidation drift across Sync-Flow, Template-vs-Derived, Adopt-Design, Lesson-Gitignore
lint: retire ALWAYS_FILES-era claims from contract pages (manifest consolidation PR #60, doc fixes PR #67)
log: correction | retract 'rhetorical prior snapshot' observation from Cursor-Overlay-Validation
Cursor-Overlay-Validation: retract observation #2, add Verification-Gate scope follow-up The original filing flagged Cursor's narration of a 'prior 2026-06-29 snapshot' as rhetorical framing without a real prior on disk. Verified after the fact via git log on the host's wiki sub-repo: commit 02d4bfc from 2026-06-29 14:35:44 -0400 IS the real prior snapshot Cursor was referencing. The observation was a projection (assumed without checking) rather than an empirical finding. Edits: - Section renamed 'Two minor observations' to 'One minor observation' - Added 'Correction logged 2026-06-30 (retraction)' subsection documenting what was wrong and how it was verified — kept in the page rather than silently removed so future readers see the correction trail - Conclusion caveat updated to point at the Correction subsection - Open follow-up #1 ('tighten cursor rules') removed — no defect to fix - New follow-up #4 added: tighten Verification-Gate's 'no projections' clause to cover claims about agent behaviour, not only numerical claims in the page body. The current gate would not have caught this class of error; extending its scope is the durable lesson.
log: ingest Cursor-Overlay-Validation analysis (2026-06-30)
Add Cursor-Overlay-Validation analysis page (first live validation, 2026-06-30) Filed as fourth type: analysis page. Closes the README Status gap that read 'Cursor overlay is shipped but unvalidated in a live session' with empirical evidence from a real adopting host: rules load automatically (wiki-as-memory.mdc + CLAUDE.md always-applied), link discipline applied without explicit reminder, @wiki-experiment write produces page + index + log with two-commit rule honoured, honest reporting validated against gh pr view. Two non-blocking observations recorded: 1. Commit-without-asking is the designed behaviour per lw:wiki-maintenance (stop-and-confirm gates live at PUSH, not COMMIT). 2. Rhetorical 'prior snapshot' framing without an actual prior on disk is worth tightening in .cursor/rules/wiki-experiment.mdc spec. Bearing on related work: empirical evidence narrows issue #65 to 'adopt entry-point only — overlay itself validated'; comment posted on #65 with concrete 3-part fix sketch. Index + Home updated under Applied examples category.
Adopt-Existing-Repo-Design: resolve manifest drift Open Question scripts/lib/template-manifest.sh is now the single source of truth sourced by update-from-template.sh, check-template-version.sh, and adopt.sh; the Open Question in Adopt-Existing-Repo-Design that called this out as deferred is replaced with a resolution note pointing at the manifest, the two new test fixtures (manifest-shape unit, manifest-convergence smoke), and the behaviour delta (+17 files reach future adopters, .gitignore becomes HOST_OWNED). Log entry summarises the change and the verification gate. Refs: feature/template-manifest-consolidation, chunk 6 of 6.
wiki: record --github-wiki design + empirical sweep (PR #59) Adds 'Decision: --github-wiki flag' section to Adopt-Existing-Repo- Design. Six-row behavior matrix, inline non-github host check, dry-run preview semantics, agent-orthogonality reasoning. Empirical sweep across 9 real repos with concrete would-skip / would-apply outcomes. End-to-end Linux + macOS bash 3.2.57 verification recorded. Two new fixtures from PR #59 review-resolution round noted: - adopt-apply-github-wiki-agent-none (agent-orthogonality case) - adopt-dryrun-github-wiki (dry-run preview coverage) Co-authored-by: Priscila Saboia Moreira <pmoreira@nd.edu>
log: macOS bash 3.2.57 Test C confirms item #1 cp-failure path on FHI360_Lite Last gap: item #1's FAILED_ADDS code path under actual cp failures had been covered by a synthetic fixture and CI but not against the real host Chris used for his review. Test C: fresh FHI360_Lite, pre-create scripts/lib and wiki/agents/claude-code as regular files (blockers); 13 ADD entries under those paths must fail; adopt captures all 13 in FAILED_ADDS, manifest shows the dedicated ADD FAILED block, summary stdout says 'Applied: 14 file(s) created, 13 FAILED', blockers and blocked paths intact, unblocked paths created normally. All 5 of Chris's PR #51 review items now confirmed end-to-end against real hosts on both Linux and macOS bash 3.2.57. Co-authored-by: Priscila Saboia Moreira <pmoreira@nd.edu>
log: macOS bash 3.2.57 verifies PR #51 review-resolution end-to-end against FHI360_Lite Test A (all 3 grants absent) and Test B (all 3 pre-authored) both green on Priscila's macOS bash 3.2.57 against HEAD 8c3a579. 17 of 17 verification points pass: 'created from canonical' status strings on Test A, 'applied' on Test B, host content preserved in all three files in Test B (FHI360 title, *.npz, theme=host, allow=Bash). PR #51 review fixes (items 1, 2, 3+4+5) confirmed across both OSes. Co-authored-by: Priscila Saboia Moreira <pmoreira@nd.edu>
wiki: re-sync Adopt-Existing-Repo-Design with PR #51 review fixes Four sections updated to reflect adopt.sh HEAD 8c3a579 after Chris Sweet's end-to-end review introduced new ADDs (slash commands + skills), the FAILED_ADDS block, the create-from-canonical semantics for absent grants, and the new TOUCH status strings. 1. ADD allowlist: 21 -> 27 entries; new 'CLAUDE-CODE SLASH COMMANDS + SKILLS (6)' sub-block; deferred list pruned; apply-time honesty paragraph for FAILED_ADDS. 2. TOUCH grants: 'absent targets create from canonical' paragraph; per-type apply path described. 3. Dry-run report example: virgin/all-absent verbatim shape, new '[absent; will create from canonical]' marker on TOUCH rows, GRANT WARNINGS now only TOUCH_INVALID, prose updated. 4. Manifest example: 27-file entry, new status strings, TOUCH status vocabulary paragraph, ADD FAILED block placement noted. 5. Empirical table: added chrissweet/FHI360_Lite (Chris's original review host); ADD count 21 -> 27; re-validated 10 prior entries unchanged; Test A and Test B FHI360_Lite e2e results added to the apply-coverage paragraph. All numbers from real terminal runs against HEAD 8c3a579 on 2026-06-27. Co-authored-by: Priscila Saboia Moreira <pmoreira@nd.edu>
log: 2026-06-26 ingest | Knowledge-Bundles-Framing
Knowledge-Bundles-Framing — paper-brief synthesis (OKF + discipline) Filed for handoff to the agent writing the llm-wiki-paper. Reframes the template as an agentic knowledge-bundle system, using OKF v0.1 terminology as the formalisation anchor and naming the discipline layer (typed edges, verification gate, write protocol, KG, federation) as the contribution on top of the bundle format. Structure: TL;DR; OKF-anchored terminology; agentic stance; five-step bundle lifecycle (create/adopt/maintain/federate/ compose); where we extend OKF; cross-cutting properties; honest limits; naming and positioning for the paper; current implementation status footer separating shipped vs forward as of 2026-06-26. Assumes OKF-Alignment-Ideas recommendations are resolved (frontmatter superset, OKF-canonical reserved filenames, [[wikilinks]] body links, posture (c) companion spec for typed edges). The implementation-status footer makes the forward- state assumption auditable. Pages touched: - Knowledge-Bundles-Framing.md (new, type: synthesis) - index_llm-wiki-memory-template.md (Applied examples entry) - Home_llm-wiki-memory-template.md (Applied examples entry) - 9 See-also back-refs across substrate pages
wiki: reconcile Adopt-Existing-Repo-Design with feature/adopt-sh code (5 drifts) Audit against scripts/adopt.sh and real dry-run output found five drifts in the design page; four corrected here, one corrected in the code (commit 829ba64). 1. ADD allowlist: page listed ~30 paths in six categories; real ADD_ALLOWLIST has 21 entries. Rewrote to list the literal array grouped into four real categories. Added 'Deferred surface' subsection naming the four design-sketch paths that never landed. 2. Sentinel 'lw:wiki-section' for CLAUDE.md: does not exist. Real overlay injects 'lw:memory-boundary' AND 'lw:wiki-maintenance'. Both wiki sections corrected. 3. Dry-run report example: replaced with verbatim shape (six fixed sections, banner line, six-line header, basename-only Resolved). 4. Manifest fields: page claimed 'template version pinned'; it does not. Replaced with verbatim manifest entry and explicit note. 5. --agent=cursor: confirmed correct, no change. Co-authored-by: Priscila Saboia Moreira <pmoreira@nd.edu>
log: 2026-06-25 update | OKF-Alignment-Ideas typed-edges posture (c)
OKF-Alignment-Ideas: add typed-edges posture (c) companion spec Prior draft had only (a) documented local extension and (b) upstream proposal. Posture (c) names the artifact path: repackage Edge-Types.md as a self-contained 'OKF Typed Edges Extension v0.1' that any OKF tool can opt into without OKF v0.1 changes. Mirrors how RDFa / microdata / Schema.org evolved as layered HTML extensions rather than HTML spec changes. Concrete artifacts the posture proposes: a spec document built on the existing Edge-Types content, the KG pipeline's existing SHACL shapes file as the machine-checkable form, a conformance section covering inverse-edge materialisation. Also strengthens the ontology framing to name the full vocabulary (forward predicates, inverses from PR #29, page-type vocabulary) and point at wiki/Edge-Types.md.template as the de-facto companion spec we just don't currently label.
wiki: expand empirical table to 10 verified repos, append lint log Original table listed 6 repos; one (FUNSD) was inherited from the design doc without being run this session. Audit pushed by Priscila revealed the gap. - Cloned crcresearch/FUNSD into scratch and ran dry-run: 0/3 virgin, 21 ADDs (verified, not projected). - Added 3 previously-skipped local repos: CSE-60868 (virgin), llm-wiki-branch-test (3/3 derived-drifted), llm-wiki-memory-template itself (rejected by self-target guard). - Added a paragraph naming the two real-shell --apply runs that back the verified path on both OSes. Co-authored-by: Priscila Saboia Moreira <pmoreira@nd.edu>
wiki: record advisory-abort redesign and bash 3.2 hazard from feature/adopt-sh Two ingest entries from the Tier-1 fixture pass on 2026-06-25 (branch feature/adopt-sh HEAD 57457db): - Adopt-Existing-Repo-Design.md: new 'Decision: advisory abort when host is already adopted' section. Composite detector (Signals A/B/C, 2-of-3 threshold), --force escape hatch, empirical classifications against 6 real repos. - Lesson-Bash32-Empty-Array-Hazard.md: new page. macOS bash 3.2 + set -u + empty array hazard, the asymmetric TOUCH_MISSING fixture that surfaced it, bash -x trace pinpointing scripts/adopt.sh:434, single-site fix in commit 57457db, audit of 5 sibling scripts. Index updated with one-line hooks for both pages. Log entry filed. Co-authored-by: Priscila Saboia Moreira <pmoreira@nd.edu>
log: 2026-06-25 update | OKF-Alignment-Ideas vector 5
OKF-Alignment-Ideas: add vector 5 (ask.sh + OKF-bundle query) The user pointed at the agent-comms feature (PR #44) and its ask.sh clone-and-invoke primitive. The pattern generalises to OKF bundles: any cloneable directory of markdown + frontmatter is queryable by claude -p, given a federation index entry and optionally a self-describing preamble. Vector 5 frames query as complementary to import (vector 4): vector 4: absorb the bundle's knowledge once (adopt-and-evolve) vector 5: read but don't absorb, recurring (federate-and-query) One new conclusion paragraph (federation surface widens by a few lines of rebuild-Action code), two new open follow-ups (federation index projection rules for pure OKF bundles; OKF- aware preamble injection in ask.sh). Cross-wiki See-also entries point at the agent-comms wiki via full URL since wikilinks don't resolve across wikis. Back-refs in the agent-comms wiki are deliberately not added — that's a separate write to a separate repo.
log: 2026-06-25 update | OKF-Alignment-Ideas vector 4
OKF-Alignment-Ideas: add vector 4 (adopt.sh + OKF-bundle import) After Priscila flagged that adopt.sh will support adopting OKF memory bundles, the page needed an import-direction section (prior draft covered compatibility and export only). Vector 4 sketches the plausible adopt.sh --seed-from-okf flow, names why it strengthens vectors 2 (reserved filenames) and 3 (link syntax), and explicitly bounds what it does not justify (coupling source-of-truth to OKF wire format, standing reverse export, bypassing the adoption manifest). Three new open follow-ups: link-syntax translation target on import, frontmatter back-fill inference policy, citation reconciliation across OKF's # Citations body section vs our source: frontmatter edge. Pages touched: - OKF-Alignment-Ideas.md (vector 4, conclusion item, three open follow-ups, adopt-sh tag, See-also) - Adopt-Existing-Repo-Design.md (Related-work back-ref)
log: 2026-06-25 ingest | OKF-Alignment-Ideas
OKF-Alignment-Ideas — working analysis vs Google's Open Knowledge Format v0.1 Reads the actual SPEC.md (not just the blog post) and folds in empirical GitHub Wiki link-rendering test results from a temporary push-then-revert probe. Recommends three changes (frontmatter superset; drop reserved-filename namespacing once Obsidian aggregation moves to subdirectory-per-wiki; migrate body links to [[wikilinks]]) and defers/rejects five others, with the gate decision pinned to the user's call on the Obsidian-vault layout. Pages touched: - OKF-Alignment-Ideas.md (new, type: analysis, third in the wiki) - index_llm-wiki-memory-template.md (Applied examples entry) - Home_llm-wiki-memory-template.md (Applied examples entry) - Typed-Edges-and-Frontmatter.md (See also back-ref) - Wiki-LLM-Pattern.md (See also back-ref) - Sync-Flow.md (See also back-ref) - Knowledge-Graph-Pipeline.md (See also back-ref) - Lesson-Parallel-File-Drift.md (See also back-ref)
revert: drop OKF link-form + reserved-filename test pages
test: OKF link-form + reserved-filename probe (temporary, will revert)
ingest: record deferred manifest-consolidation follow-up Adopt's ADD_ALLOWLIST and update-from-template's ALWAYS_FILES are parallel arrays for the same conceptual surface; already diverging on the wiki-write-protocol/ tree and agents READMEs. Documents the agreed direction (single source of truth in scripts/lib/template- manifest.sh, two categories) and explicitly defers the work to a follow-up PR after feature/adopt-sh matures.