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)
Lesson-Gitignore-Anchor-Propagation — sync-time footgun from PR #39
`.gitignore` leading-slash entries anchor to the repo root of whichever
clone the file lives in. Shipping a template-local block through
`ALWAYS_FILES` moved the anchor into derived repos, where it silently
shadowed their real paths. Mostly latent (tracked files unaffected) but
bites: projects that legitimately track `.claude/hooks/`, paths that are
untracked at sync time, and contributors confused by `git check-ignore`
reporting their own `CLAUDE.md` as ignored.
Root cause classified as "scope-sensitive content shipped through a
scope-preserving channel" — sister to Lesson-Parallel-File-Drift (same
content in two files) but distinct (same file in two scopes).
Pages touched:
- Lesson-Gitignore-Anchor-Propagation.md (new)
- Home_llm-wiki-memory-template.md (Lessons learned entry)
- index_llm-wiki-memory-template.md (Lessons learned entry)
- Sync-Flow.md (See also back-ref)
- Lesson-Parallel-File-Drift.md (See also back-ref)
- Lesson-Template-Contribution-Discipline.md (See also back-ref)
lint: refresh Lessons-Learned-From-model_fusion to HEAD 88f4624
Page declared verification against fc2472a (2026-06-04), an unresolvable
fork-local SHA. Refreshed against actual current HEAD 88f4624
(2026-06-12). Three commits between the original snapshot and HEAD
touch the field report's 12 recommendations:
- PR #14 / 2018186: scripts/kg/ (KG pipeline shipped, rdflib + pyshacl)
- PR #16 / b86c9e4: wiki/Edge-Types.md.template (inverse-edge vocabulary)
- PR #25 / 88f4624: scripts/instantiate.sh --dev-self (recursive
bootstrap fix shipped)
Page updates:
- Headline tally refreshed: 0 fully addressed / 3 partial / 9 missing,
plus recursive-bootstrap RESOLVED.
- Table row 9 refined: inverse vocabulary shipped but not yet wired
into init-wiki.sh page-type list; PostToolUse does not enforce.
- Body #9(a) rewritten to reference the shipped vocabulary and KG
pipeline rather than designed-but-pending.
- "The recursive bootstrap problem" section flipped to "RESOLVED in
PR #25" with --dev-self behavior enumerated.
- Provenance path corrected (/TCF/ -> /CRS_research/, the only real
checkout) and the unresolvable fc2472a flagged as fork-local.
5 bidirectional back-references added on the high-value related: entries
(sister page + three lessons + one limitation). The other 5 (Verification
-Gate, Discipline-Gates, Three-Operations, PostToolUse-Hook, Implementation
-Status) left one-way per the morning's heavily-linked roll-up rule.
Wiki-Corrections-Log appended with the second-pass entry.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
lint: KG aspirational -> implemented; bidirectional back-references; example cleanup
Stale-claim correction: PR #14 shipped scripts/kg/ (rdflib + pyshacl
in-process KG pipeline) to template main, but nine wiki pages still
described the pipeline as aspirational. Reclassified Knowledge-Graph-
Pipeline to implemented; corrected architecture from Fuseki to rdflib +
pyshacl; flagged the distribution gap (scripts/kg/ not yet in
ALWAYS_FILES, likely to ship as features/kg/ under RFC #13). Updated
Implementation-Status, Wiki-LLM-Pattern, Three-Operations, Typed-Edges-
and-Frontmatter, SCHEMA, Limitation-Inverse-Edges-Missing, Sync-Flow,
and the index to match.
Example cleanup: Wiki-LLM-Pattern line 23 used the placeholder example
[Markov-Chain-v5c2](Markov-Chain-v5c2). Replaced with a real wiki page
name so lint and the KG see a valid edge.
Bidirectional back-references added for the high-value concept <-> lesson
/ limitation pairs (Verification-Gate, Discipline-Gates, Lesson-
Validation-Methodology, Lesson-Parallel-File-Drift, Template-vs-Derived-
Projects, PostToolUse-Hook, Agent-Overlays). Index/log roll-ups
(Implementation-Status, Wiki-Corrections-Log) intentionally left one-way.
Wiki-Corrections-Log entry appended with the receipt.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Initialize wiki: scaffold + first ingest of template knowledge
Scaffolded SCHEMA, Home, index, log, and Home.md redirect to match the
canonical create-mode output of wiki/init-wiki.sh. Authored 18 content
pages across five categories (foundation, mechanisms, lessons,
limitations, applied examples) capturing the wiki-llm pattern, the
template's structure, the contents of PR #1 (discipline gates,
verification gate, PostToolUse hook) and PR #4 (log entry
attribution), the parallel-file-drift / hook-type / validation-method
lessons surfaced by PR review, and the three open limitations
(prompt-injection residual, missing edge inverses per issue #3,
untested non-Claude-Code overlays).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>