open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Releases Activity

docs(catalog): OKF — add landing protocol (siblings record conformance in the shared log)

Browse source 
So a sibling's conformance landing reaches the convergence without the operator
hand-carrying status: when a plugin's bundle conforms, it writes the claim directly
into log.md (its own catalog-go) as 🟡 "claims conformant @ <commit>, awaiting
gate-verification"; a linkedin-studio session runs the shared gate and flips it to
🟢 on exit 0 (independent verification, not self-assertion). Honest limit recorded:
no live push across separate sessions — discovery is pull-at-session-read. Pointer
added to the handoff §5.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012GqEHp4uDiivfrAUjw4BdE
This commit is contained in:
Kjell Tore Guttormsen 2026-06-29 14:38:02 +02:00
commit 062d6336af
2 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/okf-second-brain/handoff-2026-06-29.md
View file

@ -66,3 +66,9 @@ Each plugin acknowledges in its own repo → operator relays → linkedin-studio
table (🔵/🟡 → ratified/conformant) and closes that plugin's open coordination item. That keeps three
independent sessions converged with the operator as the single relay, and no writing crossing repo
boundaries.
**When you later land conformance** (step 4 — your bundle actually conforms), follow the **Landing
protocol** in `log.md`: record your claim **directly in `log.md`** (set your row to 🟡 "claims conformant
@ `<commit>`, bundle `<path>`, awaiting gate-verification") using your own catalog-go. A linkedin-studio
session then runs the shared gate `node catalog/scripts/okf-check.mjs <path>` and, on exit 0, flips you to
🟢 with the proof. This way the landing lives in the shared doc — the operator need not hand-carry it.