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.
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
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.
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.
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)
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)