open/okr
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

docs(okr): rett CLAUDE.md-beskrivelsen av to-rot-retrieval

Browse source 
CLAUDE.md:67 komprimerte retrieval-aksen til "(project preferred, else
home)", som leses som et oppslags-kortslutt. Det er feil: retrieval er en
UNION over begge røtter (SKILL.md:35,95 "always search both" / "Glob both
roots"), og prosjekt-presedensen gjelder kun ved konflikt (SKILL.md:46).
Kun org-PROFILEN kortslutter (inject-okr-context.mjs:54-56).

SKILL.md er den autoritative prosedyren og var allerede korrekt; kun den
komprimerte oppsummeringen i CLAUDE.md var usann. Funnet rapportert av
catalog, som siterer SKILL.md:94 i spec §8 og trengte å vite hvilken av
våre to filer som gjelder.

Suite: 179/179.
This commit is contained in:
Kjell Tore Guttormsen 2026-07-25 20:24:03 +02:00
commit 52129b566f
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
CLAUDE.md
View file

@ -64,7 +64,7 @@ Cycle archival: `/okr:oppsett arkiver` — moves `syklus/` to `historikk/`, gene
Context files carry OKF v0.1 Documents-style frontmatter (conforms to the OKF v0.1 minimal contract, canonized in `catalog/docs/okf-second-brain/spec.md`): a Title-Case `type` (`Organisasjonsprofil`, `Tildelingsbrev`, `Virksomhetsplan`, `Overordnede OKR`, `OKR`, `Retrospektiv`, `Status`) plus recommended `resource`/`title`/`description`/`tags`/`timestamp`. Only `type` is de-facto required. The flat frontmatter parser reads only single-line keys (`type`, profile/config fields); tree files may carry multi-line `tags` lists without breaking it. Files written by inbox ingestion additionally carry the provenance extension key `kilde: innboks`.
**Two bundle roots** with distinct lifecycles: project `.claude/okr/` (cwd-bound cycle/work) and home `~/.claude/okr/org/` (reinstall-surviving org identity). Each root carries its own `index.md` (no frontmatter; `# H1` + `* [title](link) - description`) and, on the root index, two distinct markers (OKF spec §12): `okf_version` (the upstream OKF version targeted, currently `0.1`) and `okf_layout` (this plugin's own layout revision, currently `kb-layout-2026-06`). `okf-index`/`okf-check` run per root; retrieval Globs both (project preferred, else home).
**Two bundle roots** with distinct lifecycles: project `.claude/okr/` (cwd-bound cycle/work) and home `~/.claude/okr/org/` (reinstall-surviving org identity). Each root carries its own `index.md` (no frontmatter; `# H1` + `* [title](link) - description`) and, on the root index, two distinct markers (OKF spec §12): `okf_version` (the upstream OKF version targeted, currently `0.1`) and `okf_layout` (this plugin's own layout revision, currently `kb-layout-2026-06`). `okf-index`/`okf-check` run per root; retrieval Globs both roots as a union — never a short-circuit — with project content winning on conflict (`skills/okr-second-brain-search/SKILL.md:35,46,95` is the authoritative procedure). Only the org *profile* resolves by precedence (`hooks/scripts/inject-okr-context.mjs:54-56` short-circuits on the project hit).
- `lib/frontmatter.mjs` — shared frontmatter parser/writer; both hooks route through it (strips trailing ` #…` only from unquoted values).
- `scripts/okf-index.mjs` — regenerate a root's per-level `index.md` (verbatim OKF index format).