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

docs(okf): run the §12 re-check against Google OKF v0.2 — three corrections, floor unchanged

Browse source 
§12 says "When Google bumps OKF, each plugin re-checks conformance." Google
bumped 2026-07-25; commons ruled the trigger catalog's to pull and the plugin
owners' to perform. This is the pull.

Held: upstream has NOT moved (git ls-remote answers 3fcbb9f, identical to the
mirror the 0.3 round read; SPEC last touched 2026-07-24 in 780fe9d). All seven
upstream anchors resolve exactly, quotes verbatim. The §3 floor is conformant
with upstream §11. No floor change -> the convention stays at 0.3.

Corrected:
1. §14 said "OKF SPEC v0.1" while linking blob/main/okf/SPEC.md, which has
   served v0.2 since 2026-07-24 — a reader following our own reference got
   v0.2 under a v0.1 label.
2. §3 attributed to upstream a rule upstream does not state: "upstream binds
   the index.md requirement to the bundle root alone", cited to commons'
   method-spec.md. Google requires index.md NOWHERE (SPEC :117 "Optional",
   :504 "MAY appear in any directory", :759 consumers MUST NOT reject for
   missing index files). Three rungs, not two; ours is highest either way, so
   only the attribution was wrong.
3. §4 now names v0.2's second breaking change (# Citations -> sources).
   Measured 2026-08-03: no marketplace emitter writes # Citations; the one
   live exposure is a plan, not code — ms-ai-architect's brief still names an
   upstream v0.1 example as the template to copy.

Suites 120/120, 0 fail. check-versions 12/12 OK.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01THEvHPWM11RupX24wBGKLu
This commit is contained in:
Kjell Tore Guttormsen 2026-08-03 20:46:05 +02:00
commit 552784e262
2 changed files with 76 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

41
docs/okf-second-brain/log.md
View file

@ -494,6 +494,47 @@ protocol; 🟢 is reserved for the independent gate-verified step (operator veri
clean: **no fixture was migrated**, deliberately — the 9 body-text fixtures are now the coverage
for the transitional path. _(catalog session, økt 9.)_
- **2026-08-03** — **The §12 re-check against Google OKF v0.2 was run. Three corrections, no floor
change, so the convention stays at 0.3.**
§12 says «When Google bumps OKF, each plugin re-checks conformance.» Google bumped on 2026-07-25.
commons ruled the trigger **catalog's to pull and the plugin owners' to perform**
(`portfolio-optimiser-commons/STATE.md:120`, plan doc `docs/plan/2026-07-31-okf-versjonsakse-sjekk.md:66-67`);
this entry is the pull.
**What held.** Upstream has **not moved**: `git ls-remote` on `GoogleCloudPlatform/knowledge-catalog`
answers `3fcbb9f` — identical to the local mirror the 0.3 round read. `okf/SPEC.md` was last touched
2026-07-24 (`780fe9d` = the v0.2 migration, #227). All **seven** upstream anchors this document
cites resolve exactly where it says, quotes verbatim (§4.1:168, :193-196, :302, :467-469, §8:509-510,
§12:773-775, §13.1:802-804). The §3 floor is conformant with upstream §11: upstream requires a
parseable frontmatter block and a non-empty `type`; this convention requires the same `type` and
adds `index.md` per level, which §11 permits because it forbids only *rejecting* a bundle for a
missing index. **Nothing about the floor changed, so the convention version does not move.**
**Three corrections, each measured, none of them upstream's fault:**
| # | Where | Was | Is |
|---|---|---|---|
| 1 | §14 references | «OKF SPEC **v0.1**» pointing at `blob/main/okf/SPEC.md` | `main` has served **v0.2** since 2026-07-24 — label and link had disagreed for 10 days |
| 2 | §3 superset paragraph | «**upstream** binds the `index.md` requirement to the bundle root alone», cited to `method-spec.md:81-85` | three rungs: upstream requires it **nowhere** (`:117`, `:504`, `:759`); **commons'** method-spec binds the root alone; ours binds every level |
| 3 | §4 recommended fields | only v0.2's *first* breaking change named | the second (`# Citations` → `sources`, §13.1:806-808) now named, with its measured exposure |
Correction 2 is the defect class this re-check exists to catch: **a claim about upstream sourced
from a sibling's derived document.** The direction matters — it made upstream look *stricter* than
it is, so the superset claim was never at risk; only the attribution was wrong. Nothing downstream
changes, but the sentence misstated a third party in a public document.
**Measured for correction 3 (2026-08-03):** no marketplace emitter writes `# Citations` — grepped
across linkedin-studio, okr and ms-ai-architect. The one live exposure is a **plan, not code**:
ms-ai-architect's design brief still names an upstream **v0.1** example as the template to copy,
carrying both `timestamp` and `# Citations` (`docs/okf-second-brain-brief-2026-06.md:56`). That is
their call to make, and it is in the trigger message they received.
**Trigger sent** to the three consumers of §2 (linkedin-studio, okr, ms-ai-architect) and the
outcome reported to commons, who had closed the track from their side. What the plugin owners own
is conformance of their **own** bundles; what the catalog owns is the axis, the trigger and this
document. _(catalog session, økt 18.)_
## Distilled architecture notes (OKF round, 2026-07)
Durable conclusions from the cross-repo round (full working context retained by the catalog session):