diff --git a/docs/okf-second-brain/handoff-2026-06-29.md b/docs/okf-second-brain/handoff-2026-06-29.md
index d0dbb8b..f3c0ed5 100644
--- a/docs/okf-second-brain/handoff-2026-06-29.md
+++ b/docs/okf-second-brain/handoff-2026-06-29.md
@@ -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.
diff --git a/docs/okf-second-brain/log.md b/docs/okf-second-brain/log.md
index 136c725..4f64750 100644
--- a/docs/okf-second-brain/log.md
+++ b/docs/okf-second-brain/log.md
@@ -42,6 +42,22 @@ distinct from conformance (code landed), which `linkedin-studio` alone holds so
 | **okr** | `type` required + recommended-as-warnings + `okf_version` echo | Has the reference **writer + checker** (`okf-check.mjs`, `okf-index.mjs`, `lib/frontmatter.mjs`) + skill `okr-second-brain-search` v1.6.1. | 🟡 built · **spec ratified @ okr `75bfc9b` (2026-06-29)**; conformance-alignment landing = own go |
 | **ms-ai-architect** | designed, not built | Targets the fuller OKF package + a retrieval skill. Builds against this spec. | 🔵 designed · **spec ratified @ ms-ai-architect `72a7e2b` (2026-06-29)**; build = own go |
 
+## Landing protocol — how a sibling records conformance
+
+When your plugin's bundle actually conforms (the work of step 4, done in your own session):
+
+1. **Record it in your own repo** (STATE/changelog) — as the handoff already instructs.
+2. **Update THIS file** (your own catalog-go): set your row in the status table above to
+   🟡 → **"claims conformant @ `<commit>`, bundle `<path>`, awaiting gate-verification"**.
+3. A **linkedin-studio session** then runs the shared gate against your bundle —
+   `node catalog/scripts/okf-check.mjs <path>` — and, on exit 0, flips your row to 🟢 with the proof.
+
+This puts the landing signal in the **one shared doc**, so the operator need not hand-carry status, and
+any session sees the truth on its next read. **Honest limit:** there is no live push-notification across
+separate sessions — a landing is discovered when a session next *reads* this log (a linkedin-studio
+session is told to check it at start; see its STATE). Self-flipping straight to 🟢 is **not** the
+protocol; 🟢 is reserved for the independent gate-verified step (operator verification-plikt).
+
 ## Open coordination items (what each session must confirm)
 
 > **✅ Resolved 2026-06-29 — both siblings ratified.** okr (`75bfc9b`) and ms-ai-architect (`72a7e2b`)