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

chrissweet committed Jun 26, 2026

lint: reconcile classifications after cluster + PR6 land Five model_fusion-cluster PRs (#28-#32) merged on 2026-06-12 and PR6 (#33, wiki-write-protocol rename) opened with CI green on 2026-06-13. Implementation-Status, Multi-Agent-Write-Protocol, and Limitation- Inverse-Edges-Missing still classified all of this work in its pre-merge form. Bringing them to current state. Implementation-Status: - Five new Implemented rows 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 landed and the Analysis-of-model_fusion-Recommendations rec it closes. - The previously single Aspirational Multi-Agent-Write-Protocol row 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, CI green, mergeStateStatus CLEAN). Multi-Agent-Write-Protocol banner: appended a 2026-06-13 update referencing PR #33 and the PR6/PR7 housekeeping-then-wiring split. Limitation-Inverse-Edges-Missing: substantively rewritten. Title now "(Partially Closed)". The proposed-fix snake-case inverse names (extended-by:, supported-by:, criticized-by:) replaced with the camelCase names that PR #31 actually shipped (extendedBy, supportedBy, criticizedBy) and that match Edge-Types.md.template. The "KG materialises inverses, agents do not author them" stance made explicit. New "What remains" section names the upstream SHACL gap and the optional PostToolUse check. Status: in-repo half closed, upstream half + write-time check still pending. Wiki-Corrections-Log entry appended with the receipt. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

chrissweet committed Jun 13, 2026

ingest: Analysis-of-Wiki-Push-Race-Pattern + reclassify Multi-Agent-Write-Protocol New type: analysis page filed in response to a 2026-06-12 production collision in wiki/web_forager.wiki/ (3-4 human+agent teams; Csweet1 push rejected after Omegaice advanced remote by 20 commits in the interim; conflict on log_web_forager.md from same-date entries from both authors; ~3 minute manual rebase recovery). The Multi-Agent-Write-Protocol prototype at scripts/multi-agent-write-protocol-proto/ (shipped in PR #11; 9/9 CI scenarios green on ubuntu-latest + macos-latest) handles exactly this collision shape automatically via wiki_push's mechanical union-merge for log_* files. The prototype is implemented but not wired into any agent overlay; the only callers are the 9 CI scenarios. Reclassification: the Multi-Agent-Write-Protocol banner is rewritten from "design + prototype only, not yet wired" to "design + prototype shipped, production wiring is the gap." Implementation-Status's row is updated to name the wiring (not the design) as the specific gap and to outline what a wiring PR should contain. Second type: analysis page filed (after Analysis-of-model_fusion- Recommendations earlier today). Both acknowledge the SCHEMA violation that PR #29 closes. Cross-references: Multi-Agent-Write-Protocol gains See-also entry to the new page; Analysis-of-model_fusion-Recommendations and Lesson-Validation-Methodology gain back-refs as sister/related pages. Index updated under Applied examples (after the sister analysis page). Home updated per PR #32's category-level rule: the page is significant enough to warrant a Home entry, not just an Index entry. Wiki-Corrections-Log entry appended for the receipt. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

chrissweet committed Jun 12, 2026

Rewrite Multi-Agent-Write-Protocol as push-time-only + SessionStart Replaces the per-agent-branch design with a transparent push-time-only wrapper. Agents work directly on local main (standard git workflow); the wiki-push wrapper handles conflict resolution only when an optimistic push is rejected. The complementary session_start hook keeps the agent's read view fresh and defers cleanly (no auto-rebase) on divergence. Key spec changes: - "Design at a glance" table separates read freshness, write collision prevention, and mechanical merges as three concerns with one mechanism each. - "The protocol" split into two subsections (session start; write). Session start has four outcomes (up-to-date / fast-forward / ahead / diverged); only fast-forward modifies local main. - "Default behaviour: don't push" section makes explicit that the protocol replaces the *mechanics* of push, not the *policy* (agents don't push by default; user asks or agent asks first; push then means invoke wiki-push). - "Wiki only" scope made explicit (project main repos keep existing conventions). - Six worked examples (added two for session_start outcomes). - Failure modes section gains halt-at-cap recovery: local main has the un-pushed work + any partial merge commits; agent or user decides to keep retrying / abandon / cherry-pick. Implementation-Status updated to reflect the prototype's CI-green status on the template fork at chrissweet/llm-wiki-memory-template branch multi-agent-write-protocol-proto. Log entry follows in a separate commit per Log-Entry-Attribution. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

chrissweet committed Jun 1, 2026

Ingest Multi-Agent-Write-Protocol spec page A new aspirational page documenting an OCC-with-semantic-retry write protocol for wikis with multiple LLM-agent writers. The protocol prevents push-level collisions by construction: each agent writes via its own contribution branch, attempts a merge against current main, and either pushes cleanly or re-plans its writes semantically before retrying. No separate reconciler is needed; the writing agent reconciles its own attempts. The page covers: the protocol's six steps; conflict classification (union-merge for index/log files via .gitattributes, three-way merge for non-overlapping content, semantic resolution for overlapping content); required agent capabilities; failure modes (livelock cap K=3, network faults, stale branches, name collisions); four worked examples spanning the mechanical-merge and semantic-resolution cases; open questions; and cross-references to existing wiki pages (Verification-Gate, Sync-Flow, PostToolUse-Hook, etc). Implementation-Status gains the page under Aspirational, pointing at the deterministic prototype in progress at the Omniscient_2 sister repo. Home and index updated in the Mechanisms section. Log entry follows in a separate commit per Log-Entry-Attribution. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

chrissweet committed May 31, 2026