okf 1.9.0 → 1.11.0

data/lib/okf/skill/SKILL.md

@@ -13,7 +13,7 @@ description: >-
   working in a repo that already carries an OKF bundle — a `.okf/` directory or a
   root `index.md` carrying `okf_version`.
 user-invocable: true
-argument-hint: "[search|produce|migrate|maintain|consume|curate|doctor|<okf-cli-verb>] [dir|@slug] [--flags]"
+argument-hint: "[search|produce|migrate|maintain|refine|consume|curate|doctor|<okf-cli-verb>] [dir|@slug] [--flags]"
 allowed-tools: Read Write Edit Grep Glob Bash
 ---
 
@@ -83,10 +83,10 @@ flags. The division of labour is the whole game:
 
 - **Shell out — never eyeball —** anything a verb computes: conformance (§9), what
   exists, what links where, where a term lives, what's stale, the map. Every read
-  verb takes `--json` and the list views filter by type/area/tag, so ask the narrow
+  verb takes `--json` and the list views filter by type/dir/tag, so ask the narrow
   question instead of paging the bundle.
-- **Skeleton first, bodies last.** `index --no-body`, `search`, `graph --minimal`,
-  and `--fields` projections each answer for a fraction of a dump's bytes; full
+- **Skeleton first, bodies last.** `dirs`, `search`, `graph --minimal`, and
+  `--fields` projections each answer for a fraction of a dump's bytes; full
   bodies are the final step of a retrieval, never the first. <!-- rule:okf-skeleton-first -->
 - **You judge — the CLI can't —** meaning: contradictions, semantic staleness
   (parses fine, no longer true), whether a loose file is terminal-by-design, whether
@@ -102,12 +102,15 @@ shapes, the tag-curation views, the server's trust boundary.
 
 ## Orient before you touch anything
 
-Picking up a bundle you don't already know — to consume or maintain — run `okf
-index <dir|@slug>` (the §6 map: every directory's index body, rollups, and listings) and
-read `log.md` (the §7 baseline of what changed last) **before** greping or opening
-leaves. It is the cheapest high-signal context, and the only reliable way to catch
-enumeration drift: **grep cannot find an index entry that is missing** — you can't
-search for the word that should be there but isn't. <!-- rule:okf-orient-index -->
+Picking up a bundle you don't already know — to consume or maintain — start with
+`okf dirs <dir|@slug>`: one row per *directory*, so it stays small on a bundle of
+any size and it names the branches every other view narrows to. Then open the one
+you want with `okf index <dir|@slug> --dir <branch>` (the §6 map: that directory's
+index body, rollups, and listing), and read `log.md` (the §7 baseline of what
+changed last) — all of it **before** greping or opening leaves. Reach for `index`
+rather than grep for the one reason that outranks convenience: **grep cannot find
+an index entry that is missing**, so enumeration drift is invisible to it — you
+can't search for the word that should be there but isn't. <!-- rule:okf-orient-index -->
 Per-verb steps are in the
 playbooks (the Commands table below; no `okf` installed? read the root
 `index.md` plus each area's `index.md`).
@@ -123,10 +126,12 @@ when you need chapter and verse.
 
 **No subcommand?** Infer intent: "document this / capture X" → `produce`;
 "convert / migrate / OKFy these existing docs into a bundle" → `migrate`; "the
-code changed, update the docs" → `maintain`; "what do we know about X / where
-is X documented" → `search`; a repo already carrying a bundle plus a task
-needing its knowledge → `consume`; "check / graph / preview it" → run the
-matching CLI verb and interpret the result. When genuinely ambiguous, ask.
+code changed, update the docs" → `maintain`; "restructure / rebalance the
+bundle / is the structure right / get more out of it" → `refine`; "what do we
+know about X / where is X documented" → `search`; a repo already carrying a
+bundle plus a task needing its knowledge → `consume`; "check / graph / preview
+it" → run the matching CLI verb and interpret the result. When genuinely
+ambiguous, ask.
 
 **Which target?** A leading `@` is a *registry ref*, not a path: `@slug` names a
 bundle registered with `okf registry set`, bare `@` the default — route it
@@ -158,15 +163,17 @@ Read the referenced playbook before executing — it *is* the procedure.
 | `produce`  | Author | create or extend a bundle | [playbooks/produce.md](playbooks/produce.md) |
 | `migrate`  | Author | convert existing docs in place: frontmatter + reserved files, bodies verbatim | [playbooks/migrate.md](playbooks/migrate.md) |
 | `maintain` | Author | sync the bundle's content with reality after a change | [playbooks/maintain.md](playbooks/maintain.md) |
+| `refine`   | Author | optimize the bundle's structure: evidence-driven, cohesion-first; proposes, never auto-applies | [playbooks/refine.md](playbooks/refine.md) |
 | `consume`  | Use    | use the bundle as context for a task | [playbooks/consume.md](playbooks/consume.md) |
 | `curate`   | Curate | structural upkeep as it stands: validate + lint + loose | [playbooks/curate.md](playbooks/curate.md) |
 | `doctor`   | Setup  | install and verify the CLI, then doctor the bundle | [playbooks/doctor.md](playbooks/doctor.md) |
-| `<okf-cli-verb>` | Read | validate, lint, loose, index, catalog, files, tags, types, stats, graph, server, render, registry, skill | `okf <verb> --help` + [reference/cli.md](reference/cli.md) |
+| `<okf-cli-verb>` | Read | validate, lint, loose, index, catalog, files, tags, types, stats, graph, server, render, registry, skill — **plus any verb an installed extension adds** (`okf help` is authoritative, this list is not) | `okf <verb> --help` + [reference/cli.md](reference/cli.md) |
 
-Two boundaries worth keeping sharp: `curate` is structural upkeep only — when
-the *content* no longer matches reality, that is `maintain` — and `doctor` is
-the one playbook that does not assume the CLI is installed. In Claude Code with
-the okf plugin, `/okf:gem` routes these same verbs.
+Three boundaries worth keeping sharp: `curate` is structural upkeep only — when
+the *content* no longer matches reality, that is `maintain`, and when the
+content is right but the *shape* underserves retrieval, that is `refine` — and
+`doctor` is the one playbook that does not assume the CLI is installed. In
+Claude Code with the okf plugin, `/okf:gem` routes these same verbs.
 
 ## The lifecycle is a flywheel, not phases
 

data/lib/okf/skill/playbooks/consume.md

@@ -1,8 +1,8 @@
 # Playbook: consume — use a bundle as context
 
-1. **Orient first** (the [SKILL.md](../SKILL.md) reflex): `okf index <dir|@slug>` maps
-   the whole bundle in one pass — every directory's index body, rollups, and listings —
-   and `log.md` gives recent history. Address a registered bundle by `@slug` (bare
+1. **Orient first** (the [SKILL.md](../SKILL.md) reflex): `okf dirs <dir|@slug>`
+   gives the shape, `okf index <dir|@slug> --dir <branch>` opens the branch you
+   want — its index body, rollups and listing — and `log.md` gives recent history. Address a registered bundle by `@slug` (bare
    `@` = the default); if the cwd carries no bundle, `okf registry list` finds one
    instead of a directory hunt. Then follow links only into the concepts the
    task needs. For a *pointed question* rather than broad context, switch to the

data/lib/okf/skill/playbooks/curate.md

@@ -9,7 +9,9 @@ reachability, backlog, completeness, hygiene. It is not `maintain`, the
 skill's workflow for when the project changed and the bundle's *content*
 must catch up with reality; reach for that one when what is written stopped
 being true. Curating can surface semantic staleness, and when it does,
-switch to `maintain` for those concepts.
+switch to `maintain` for those concepts. And it never moves knowledge: when
+the content is right but the shape underserves retrieval — fat areas,
+mis-homed hubs, an uncurated tag layer — that is [refine](refine.md).
 
 1. Locate the bundle: the directory you were given, if any; otherwise a
    `.okf/` directory or a root `index.md` whose frontmatter carries

data/lib/okf/skill/playbooks/maintain.md

@@ -1,11 +1,13 @@
 # Playbook: maintain — keep a bundle in sync with reality
 
 Reach for this when the project changed and the bundle's *content* must catch
-up. The modelling craft behind steps 3 and 7 lives in
-[authoring.md](../reference/authoring.md).
+up. Restructuring the bundle itself — moving concepts, adding areas — is
+[refine](refine.md), not maintain. The modelling craft behind steps 3 and 7
+lives in [authoring.md](../reference/authoring.md).
 
-1. **Orient before hunting.** Run `okf index <dir>` (the §6 map — every directory's
-   index body, rollups, and listings), read `log.md` (the §7 baseline: what changed
+1. **Orient before hunting.** Run `okf dirs <dir>` (the shape), then `okf index
+   <dir> --dir <branch>` on the branch the change touches (the §6 map: its index
+   body, rollups and listing), read `log.md` (the §7 baseline: what changed
    last), and `okf stats <dir>` (size and shape) *before* you grep. It is the
    cheapest context and it primes the hunt — and it is the only reliable way to
    catch enumeration drift, because **grep cannot find an index entry that is
@@ -44,7 +46,7 @@ up. The modelling craft behind steps 3 and 7 lives in
      defect.** Loose ≠ orphan: an index listing makes a file *reachable* (not an
      orphan) but is not a graph edge, so an indexed file can still float here.
 7. **Curate the tag vocabulary** when the pass
-   touched tags, or when `okf tags <dir>` shows a long tail of singletons. Run `okf tags <dir> --by area` and
+   touched tags, or when `okf tags <dir>` shows a long tail of singletons. Run `okf tags <dir> --by dir` and
    `--by type` — the grouped view is the analysis; read each group top-down:
    - **twins** — two tags riding the exact same concepts (equal counts sort them
      adjacent). Merge into one unless each genuinely names a different theme.

data/lib/okf/skill/playbooks/menu.md

@@ -33,6 +33,11 @@ is the lede.
      the working tree has uncommitted changes to the code the bundle describes
      (`git status`), prefer **`maintain`**: that is exactly the drift it exists
      to close.
+   - **clean, but the shape strains** — one area dwarfing the rest in
+     `okf stats`, tags spread thin across dirs in `okf tags --by dir`, hubs
+     whose inbound links are mostly foreign in `okf graph --hubs` → offer
+     **`refine`** (evidence-driven restructuring; it proposes before it
+     touches anything).
 4. **Freshness is off by default.** If the bundle carries timestamps, note that a
    plain `lint` said nothing about staleness and `okf lint <root> --stale-after
    90d` is the check that would.

data/lib/okf/skill/playbooks/refine.md

@@ -0,0 +1,93 @@
+# Playbook: refine — restructure a bundle to get the most from OKF
+
+Reach for this when the bundle's *content* is right but its *shape* may not be:
+areas grown fat by additive passes, hubs homed by history, a tag layer that
+never became the second index. Refine optimizes the projection — the same
+knowledge, arranged to serve progressive disclosure, the emergent graph,
+cross-cutting tags, and capture-once-link-many. It is not [curate](curate.md)
+(upkeep of the structure as it stands) and not [maintain](maintain.md) (content
+catching up with reality): refine changes where knowledge lives, never what it
+says. Its permitted edits are structural — move a concept, extract a duplicated
+fact to one home, section an index, retag, relink, and write the connective
+sentence a link lives in; summarizing, updating, or correcting a body is
+maintain's job, reached by switching verbs, not by stretching this one.
+
+The frame that governs every move: the directory tree is a **lossy projection
+of the link graph**. A tree gives each concept one parent, so the tree encodes
+only the single dominant decomposition; every genuinely many-to-many
+relationship rides links and tags, never new directories. And cohesion outranks
+balance — a move has semantic cost, so balance is a tiebreaker and a fatness
+alarm, never the objective. <!-- rule:okf-cohesion-over-balance -->
+
+1. **Orient.** `okf dirs <dir|@slug>` (directories, fan-out, depth — and
+   `subtree` says where the weight sits), `log.md` (how the bundle grew), `okf
+   stats` (totals). Additive growth
+   optimizes each pass locally, never the whole — that is the drift this
+   playbook corrects.
+2. **Measure — the CLI is the evidence.** Baseline `validate` / `lint
+   --stale-after` / `loose` first: refine assumes a sound bundle, and hard
+   errors are [curate](curate.md)'s job. Then the two structural reads:
+   - `okf tags <dir> --by dir` — each row carries `count/total`, so a tag's
+     **locality** reads directly: a tag wholly inside one area names a *domain*
+     (the directories are right); one spread across areas names a *concern*.
+   - `okf graph <dir> --hubs` — concepts ranked by inbound links, each with
+     the areas those links come from: the **origin test** for every hub.
+3. **Diagnose — you are the judgment.** The measurements are evidence, never
+   verdicts:
+   - **Concerns never become containers.** A directory built around a spread
+     tag ("everything async") prunes nothing — most needs would enter it.
+     The cross-cut stays a tag. <!-- rule:okf-concern-not-container -->
+   - **A directory must prune.** The positive test for any area, existing or
+     proposed: does knowing "it's in there" eliminate a large, even slice? A
+     good node splits its parent into chunks that are nameable, mutually
+     exclusive, and roughly comparable in size. And small is not merge-worthy
+     on its own — a two-concept area that is a genuinely distinct domain
+     stays. <!-- rule:okf-directory-prunes -->
+   - **The hub origin test.** Inbound majority from the hub's own area:
+     well-homed, leave it. A dominant *foreign* area: that area is the better
+     home. Foreign majority with *no* dominant area: a shared primitive — the
+     only admission ticket into a shared-core area (without that test, a
+     `foundation/` rots into a `misc/`). Two comparable strong ties, one of
+     them home: stay and carry the other as a tag — moving trades one
+     imbalance for another. And in a design bundle expect the central
+     decisions to fail this test wholesale: that is centrality, not
+     mis-homing.
+   - **Fatness alarm, not fatness rule.** A fat area (≳20–25 concepts) wants
+     **heading sections inside its `index.md`** first — the same prune as
+     sub-directories, for zero extra hops and no new enumeration to keep
+     sound. Directory nesting pays only at hundreds of concepts, and only
+     where the index's own headings already form separable, nameable
+     sub-groups — fatness alone never justifies depth; the sections that
+     formed are the evidence the split exists.
+   - **Duplication.** Read the area overviews for a fact re-explained in
+     several (drifting tables are the tell); capture-once-link-many says
+     extract it into one concept and link from the rest. Extraction is the one
+     refine move that touches bodies, and it redistributes rather than
+     rewrites: assemble the canonical concept from the copies, keep every
+     copy's unique domain-specific detail (in the extract, or in the one-line
+     note left beside each link), and where the copies *disagree*, which is
+     true is a [maintain](maintain.md) question — verify against reality or
+     flag the conflict in the proposal, never silently pick a winner while
+     merging. <!-- rule:okf-extract-not-rewrite -->
+   - **Vocabulary twins.** The [maintain](maintain.md) tag-curation recipe
+     (twins, echoes, singletons) applies to `type` too — `okf types <dir>`.
+4. **Plan — tier by leverage ÷ churn, free levers first.** Tag curation,
+   index heading-sectioning, and extraction before any file move; a move only
+   when the origin test demands one, and each gated by **do-nothing**: skip it
+   unless its value beats its churn. Record what you *declined* and why — the
+   decline list is what stops the next pass from re-proposing it.
+5. **Propose — never auto-apply.** Refine's output is a short report (the
+   evidence, the tiers, the declines) plus a ready-to-run execution prompt the
+   user can hand back later: a scope line, the governing principles above, the
+   explicit prohibitions, the closeout gate as acceptance. Analysis and
+   execution are separate on purpose — the judgment is spent once, frozen, and
+   then executed without re-derivation. <!-- rule:okf-refine-proposes -->
+6. **Execute only on approval**, then walk the
+   [Closeout gate](../reference/authoring.md#closeout--the-finishing-gate):
+   every touched `index.md` re-enumerated, links absolute bundle-relative so
+   they survived the moves, a dated `log.md` entry carrying the *why*,
+   validate/lint/loose clean, and a before/after of step 2's evidence.
+
+Two traps: never split a cohesive cluster (a deliberately paired mirror flow)
+to hit a size band, and never tag a concept with its own directory's name — a
+group-name echo adds no edge.

data/lib/okf/skill/playbooks/search.md

@@ -12,12 +12,12 @@ reads, and full bodies are read last, and only the winners.
    the root `index.md` then each relevant area's `index.md` by hand. No bundle in
    the cwd? `okf registry list` names the registered ones — address them by
    `@slug`, don't hunt sibling directories.
-2. **Ingest the map and decide where to look.** `okf index <dir|@slug> --no-body` is
-   the skeleton: every directory with its concept count, types, tags, children.
-   *You* do the semantic matching here — the question names a meaning, the map
-   names areas; connect them by judgment, not string equality. When an area
-   looks right, `okf index <dir> --area <name>` buys its authored index body and
-   listing (titles + descriptions) for the price of one directory.
+2. **Ingest the map and decide where to look.** `okf dirs <dir|@slug>` is the
+   skeleton: every directory with what lives under it. *You* do the semantic
+   matching here — the question names a meaning, the map names directories;
+   connect them by judgment, not string equality. When one looks right, `okf
+   index <dir|@slug> --dir <name>` buys its authored index body and listing
+   (titles + descriptions) for the price of one directory.
    <!-- rule:okf-search-map-first -->
 3. **Cut across with the finder when the question is lexical.** An exact
    symbol, an error code, a column name, a phrase — things structure won't
@@ -52,7 +52,7 @@ reads, and full bodies are read last, and only the winners.
    default when you can. <!-- rule:okf-search-fuzzy-is-a-switch -->
 
    Scope any of them with what the map taught you:
-   `--area billing`, `--type Decision`, `--tag idempotency`, `--in body`.
+   `--dir billing`, `--type Decision`, `--tag idempotency`, `--in body`.
    Matches rank by where they hit, and the snippet often *is* the answer.
    When the answer may live in another registered bundle, span them — leading
    @slugs (`okf search @handbook @notes <terms>`) or `@all` for every registered

data/lib/okf/skill/reference/cli.md

@@ -20,6 +20,12 @@ The surface is self-describing — `okf --help` maps every verb, `okf <verb> --h
 its flags. Ask the tool for what exists; this file carries only what `--help`
 cannot: each verb's semantics, its traps, and its JSON shape.
 
+**The verb list is open, not closed.** An installed extension gem adds verbs of
+its own, listed under `installed extensions:` in `okf help`. So a verb that
+`--help` shows and this file does not document is **normal, not a documentation
+error** — ask `okf <verb> --help` for it, and expect nothing here about its
+semantics or JSON. Everything below documents the built-ins only.
+
 **`--json` is compact by design.** Every emitting verb prints single-line JSON —
 the token-efficient substrate you consume; `--pretty` (which implies `--json`)
 indents it for a human. The bytes differ, the JSON is identical, so parse either.
@@ -144,7 +150,7 @@ as Ruby regular expressions with `--regexp`/`-e` (an invalid pattern is a usage
 error, exit 2). `--fuzzy` forgives typos; pairing it with `-e` is a usage error,
 since a pattern is matched literally rather than by edit distance.
 `--in a,b` restricts the searched fields (title, id, tags, type, description,
-body); the shared `--type/--area/--tag` filters narrow the candidates *first*,
+body); the shared `--type/--dir/--tag` filters narrow the candidates *first*,
 so a search scoped by what `index` taught you stays surgical.
 
 **The default is exact, so an exact query means what it looks like.** A phrase in
@@ -267,8 +273,30 @@ there, its child directories, and the concept listing. Run it first when picking
 an existing bundle: it is the cheapest high-signal orientation, and it surfaces
 enumeration drift a grep can't (you can't grep for a listing entry that is *missing*).
 
-`--area A` narrows to a directory and is **repeatable** — `--area model --area
-format` shows both; `root` names the bundle root. `--no-body` drops the prose to a
+`--dir PATH` narrows to a directory **and everything below it**, and is
+**repeatable** — `--dir model --dir format` shows both; `root` (or `.`) names the
+bundle root. A `--dir` also brings the **chain from the root down to it**, so a branch is
+never shown adrift of the authored context that says what it is — the root
+`index.md`'s prose first among it. Those rows print with a leading `↑` and carry
+`ancestor: true`; `--no-ancestors` drops them. Ascent and descent are separate
+axes, so `--depth` never bounds the chain: `--dir X --depth 0` is X alone, plus
+how you get to X. A `--dir` that names nothing gains no chain — a lone root row
+would read as a partial answer to a query that matched nothing.
+
+`--depth N` bounds how far below the starting point the map reaches
+(the `--dir` when one is given, else the bundle root), counted **relatively**:
+`--depth 1` is the top of the tree, `--dir X --depth 1` is one branch of it, and
+the pair walks down a level at a time.
+
+**On a bundle of any size the map is unreadable whole** — every directory is a
+section, and even `--no-body` keeps one listing row per *concept* — so narrow
+rather than paging it: `okf dirs` is the orientation, `--dir <branch> --depth 1`
+is the step down into it,
+and `--except body,listing` on top of either is the lean JSON skeleton. Full
+`index` output on a few hundred concepts runs to hundreds of KB; the same map at
+`--depth 1` is a couple of KB.
+
+`--no-body` drops the prose to a
 skeleton (headers, rollups, child pointers). For a directory that has concepts but
 **no `index.md`**, the listing is **synthesized** from the concepts' descriptions
 and tagged `(no index.md)` — §6 explicitly permits synthesizing a map on the fly.
@@ -277,7 +305,49 @@ It is a **read view**: advisory, always exit 0. A synthesized directory is a
 *signal* (a map worth writing), never a defect — `index` emits no lint findings and
 never fails a bundle. JSON: `{ bundle, count, directories: [{ dir, index_path,
 present, synthesized, count, types, tags, subdirs, body, listing: [{ id, title,
-description, type, tags }] }] }`.
+description, type, tags }] }] }` — `ancestor` marks a row that is there to place
+the branch rather than to answer about it.
+
+## dirs — the bundle's clusters and their sizes
+
+`okf dirs <dir>` lists every directory the bundle has — the ones holding
+concepts, the ones carrying an `index.md`, and the empty intermediates that only
+exist to connect the tree — with the number of concepts living **directly** in
+each and the number in its **subtree**. A cluster *is* a directory here, so this
+is the view that tells you what `--dir` can be pointed at and how much sits
+behind each choice.
+
+Two numbers, because one cannot answer the question. `count` is direct, so the
+column sums to the bundle's concept total and a dir holding only sub-directories
+reads `0` rather than a hidden rollup. `subtree` is defined as *exactly what
+`--dir <that row>` returns*, so the row and the flag can never disagree — which
+is also why the root's subtree is its own direct count (`.` is a prefix of
+nothing). Without it a truncated listing is all zeroes at the top of a deep tree,
+which is where you most need to know where the mass is. The human table shows the
+second column only where some dir actually nests.
+
+`--dir PATH` (repeatable) narrows to a directory and its subtree, and brings the
+**chain up to the root** with it so the branch is placed rather than shown
+adrift — those rows are marked `↑`, carry `ancestor: true`, and stay out of
+`total` (`--no-ancestors` drops them). `--depth N` keeps only N levels below the
+starting point — the `--dir` when one is given,
+the bundle root otherwise. Relative, not absolute, so `--dir a/b --depth 1`
+reads "a/b and one level under it" without your first working out how deep `a/b`
+is. `--depth 0` is the starting point alone. A `--depth` that is not a whole
+number is a usage error (exit 2).
+
+**This is the first command to run on a bundle you do not know** — the same first
+move [SKILL.md](../SKILL.md) prescribes. `okf dirs <dir>` is one row per
+directory, so its size tracks the tree rather than the concept count: it tells
+you the shape and where the weight sits, `--depth 1` trims it further on a deep
+bundle, and you then descend with `okf index --dir`, one level at a time.
+
+The root prints `(root)` and stores `.` — the split every grouped view keeps, so
+a table and its `--json` never disagree about which spelling is the data. JSON:
+`{ bundle, total, count, dirs: [{ dir, ancestor, count, subtree, subdirs }] }`,
+root first. `count` is rows printed, chain included; `total` sums the direct
+counts of the rows you actually asked for, which is what keeps a row's `subtree`
+equal to the `total` that `--dir` on that row returns.
 
 ## catalog / files / tags / types / stats — the server views, as text
 
@@ -287,7 +357,8 @@ All are advisory reads (exit 0) sharing one data source (per-concept metadata pl
 in/out link degree). Add `--json` to any for a machine substrate.
 
 - **`catalog`** — every concept with its metadata (type, status, tags, timestamp,
-  in/out link degree, description), grouped by top-level area. The "what's here, in
+  in/out link degree, description), grouped by top-level area (`dir` on every row
+  carries the full path). The "what's here, in
   detail" view. JSON: `{ bundle, count, concepts: [{ id, title, type, description,
   tags, timestamp, status, backlog_ref, dir, area, links_out, links_in }] }`.
 - **`files`** — the folder tree: each concept's filename + title, grouped by
@@ -295,26 +366,44 @@ in/out link degree). Add `--json` to any for a machine substrate.
   id, dir, type, title, description }] }`.
 - **`tags`** — every tag with the concepts that carry it, ordered by count
   descending. The "what themes dominate" view. JSON: `{ bundle, count, tags: [{ tag,
-  count, concepts: [id, …] }] }`. `--by type|area` regroups the list per concept
-  dimension with **within-group** counts (a tag spanning groups appears in each) —
-  the substrate for tag curation; the judgment recipe lives in the
-  [maintain playbook](../playbooks/maintain.md). JSON: `{ bundle, count, by,
-  groups: [{ <dim>, count, tags: […] }] }`.
+  count, concepts: [id, …] }] }`. `--by type|dir` regroups the list per concept
+  dimension with **within-group** counts (a tag spanning groups appears in each);
+  each row also carries the tag's **total** across the narrowed set, printed
+  `count/total` when they differ — so a tag's locality reads per row (a plain
+  count = wholly local; `2/7` = a cross-cutting spread). The substrate for tag
+  curation and for [refine](../playbooks/refine.md)'s domain-vs-concern read;
+  the judgment recipes live in the [maintain playbook](../playbooks/maintain.md)
+  and the [refine playbook](../playbooks/refine.md). JSON: `{ bundle, count, by,
+  groups: [{ <dim>, count, tags: [{ tag, count, total, concepts }] }] }`.
 - **`types`** — every type with the concepts that carry it, ordered by count
   descending. The "what kinds of knowledge" view. JSON: `{ bundle, count, types:
   [{ type, count, concepts: [id, …] }] }`.
-- **`stats`** — bundle rollups: concept / area / type / cross-link / distinct-tag
-  totals plus per-type and per-area breakdowns. The "shape at a glance" view. JSON:
-  `{ bundle, concepts, areas, concept_types, cross_links, distinct_tags, by_type, by_area }`.
+- **`stats`** — bundle rollups: concept / dir / type / cross-link / distinct-tag
+  totals plus per-type and per-dir breakdowns. The "shape at a glance" view. JSON:
+  `{ bundle, concepts, dirs, areas, concept_types, cross_links, distinct_tags,
+  by_type, by_dir, by_area }` (`areas`/`by_area` are the deprecated first-segment
+  cut, kept for one release). `dirs`/`by_dir` cover every directory `okf dirs`
+  lists — counts are direct, so a directory holding nothing itself is present at
+  `0` rather than missing, and `by_dir.keys` is a complete list of what `--dir`
+  can address.
 
 The four list views narrow with the same filters the browser panels offer —
-`--type TYPE`, `--area AREA`, `--tag TAG`; each takes the ones orthogonal to
-itself (`tags` can't filter by tag). Matching is case-insensitive and exact; a
-concept at the bundle root lives in the `(root)` area, which `--area` also accepts
-as plain `root` (no shell quoting). A filter that matches nothing is an empty view,
-not an error: `okf tags <dir> --area billing --json` answers "which tags does the
-billing area use?", `okf catalog <dir> --tag auth` answers "what carries the auth
-tag?".
+`--type TYPE`, `--dir PATH`, `--tag TAG`; each takes the ones orthogonal to
+itself (`tags` can't filter by tag). Matching is case-insensitive; `--type` and
+`--tag` are exact, `--dir` takes the named directory **and everything below it**
+(`--dir platform` reaches `platform/services/api`). A concept at the bundle root
+lives in `.`, which `--dir` also accepts as plain `root` (no shell quoting). A
+filter that matches nothing is an empty view, not an error: `okf tags <dir> --dir
+billing --json` answers "which tags does the billing cluster use?",
+`okf catalog <dir> --tag auth` answers "what carries the auth tag?".
+
+**`--area` is deprecated.** It still works — matching the *first path segment*
+only, its old behavior unchanged — and prints `warning: --area is deprecated, use
+--dir` on stderr (stdout stays clean, so a `--json` consumer is unaffected). Same
+for `tags --by area`. Both go in a later release; write `--dir` in anything new.
+On `index` it combines with neither `--depth` nor `--dir` — exit 2, because it is
+*exact* and both of those select a range, so the pair used to return the area
+plus whatever the other flag selected: an answer to neither question.
 
 Reach for `stats` first to size a bundle, `catalog`/`files` to enumerate it, `tags`
 to find thematic clusters — all without standing up the server.
@@ -330,10 +419,13 @@ in a body render as diagrams, and a click (or tap) opens the diagram full
 screen with drag-to-pan and wheel/pinch zoom. Concepts render as nodes
 coloured by `type` and sized by degree, links as edges, with a detail panel
 (rendered markdown, "Links to" / "Linked from" backlinks), layout switching,
-type/area/tag filters on every view, and search. The authored layer is in the
+type/dir/tag filters on every view (the dir chips take a directory *and* its
+subtree, the same rule `--dir` uses), and search. Cluster mode groups the
+concepts into one box per directory, nested to a depth picked beside the layout
+select — depth 1 is the flat view, and a flat bundle is offered no control. The authored layer is in the
 UI too: the Files view carries **Files | Indexes** tabs — the Indexes tab
 lists the log first (the chronological index), then every `index.md` — and
-folder nodes in file-tree mode and area boxes in cluster mode open a
+folder nodes in file-tree mode and directory boxes in cluster mode open a
 directory's §6 map in the inspector (authored, or synthesized when none
 exists). Links to an `index.md`, `log.md`, or bare directory navigate instead
 of dead-ending, and the log is fetched fresh on every read, so a
@@ -427,3 +519,11 @@ drops each node's body, and `--minimal` ships only `id`/`title` plus the type/ta
 indexes — the lean shape the `server` page boots from. Reach for the full dump
 only when the task truly consumes every body; for one question, the
 [search verb](#search--ranked-text-retrieval-metadata--body) is orders cheaper.
+
+`--hubs` swaps the dump for the **inbound ranking**: every concept with at
+least one inbound link, ranked by inbound degree, each with its links grouped
+by *source area* (`core/status  ×3   flows 2, billing 1`) — the evidence for
+[refine](../playbooks/refine.md)'s hub origin test ("is this hub well-homed?").
+A source at the bundle root counts under `(root)`. JSON: `{ bundle, count,
+hubs: [{ id, area, inbound, by_area: { <area>: n } }] }`. Advisory read, exit 0;
+`--minimal`/`--no-body` shape node payloads and change nothing here.

data/lib/okf/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module OKF
-  VERSION = "1.9.0"
+  VERSION = "1.11.0"
 end

data/lib/okf.rb

@@ -25,6 +25,15 @@ module OKF
     value.respond_to?(:empty?) ? value.empty? : false
   end
 
+  # The directory a concept lives in, derived from its §2 id: the id *is* the
+  # path minus `.md`, so putting the suffix back and taking the dirname is the
+  # definition rather than a parse of it. One home for it because three views
+  # answer with a `dir` — the catalog, the search rows, the linter's per-directory
+  # checks — and a rule spelled three times is three things to keep in step.
+  def self.dir_of(id)
+    File.dirname("#{id}.md")
+  end
+
   require "okf/version"
 
   # ── kernel: cross-cutting primitives ──

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: okf
 version: !ruby/object:Gem::Version
-  version: 1.9.0
+  version: 1.11.0
 platform: ruby
 authors:
 - Rodrigo Serradura
@@ -54,11 +54,22 @@ dependencies:
 description: |
   OKF (Open Knowledge Format) is portable knowledge: Markdown files with YAML
   frontmatter that both humans and agents read from one source. This gem is the
-  Ruby-native way to work with it. Its companion agent skill authors and curates
-  a bundle; the `okf` command-line tool validates the result for v0.1 (§9)
-  conformance, lints its curation quality, and serves it as an interactive graph
-  (a mountable Rack app). The same validate, lint, and graph run in-process
-  through a library API (OKF::Bundle and friends).
+  Ruby-native way to work with it.
+
+  Its companion agent skill authors and curates a bundle. The `okf` command-line
+  tool validates the result for v0.1 (§9) conformance, lints its curation
+  quality, and answers questions about it: ranked full-text search, and a
+  progressive-disclosure map that reads a large bundle a directory at a time
+  rather than loading it whole. `okf server` opens it as an interactive
+  knowledge graph and `okf render` bakes that same page into one self-contained
+  HTML file you can host anywhere. A per-user registry names your bundles, so
+  every verb reaches them by @slug from any directory and one search can span
+  them all.
+
+  Everything the CLI does also runs in-process through a library API
+  (OKF::Bundle and friends), and the graph server is a mountable Rack app. It
+  adds no service to your stack: rack, webrick and minifts are the only runtime
+  dependencies, and it runs on every Ruby since 2.4.
 email:
 - rodrigo.serradura@gmail.com
 executables:
@@ -86,6 +97,23 @@ files:
 - lib/okf/bundle/validator/result.rb
 - lib/okf/bundle/writer.rb
 - lib/okf/cli.rb
+- lib/okf/cli/catalog.rb
+- lib/okf/cli/command.rb
+- lib/okf/cli/dirs.rb
+- lib/okf/cli/files.rb
+- lib/okf/cli/graph.rb
+- lib/okf/cli/index.rb
+- lib/okf/cli/lint.rb
+- lib/okf/cli/loose.rb
+- lib/okf/cli/registry.rb
+- lib/okf/cli/render.rb
+- lib/okf/cli/search.rb
+- lib/okf/cli/server.rb
+- lib/okf/cli/skill.rb
+- lib/okf/cli/stats.rb
+- lib/okf/cli/tags.rb
+- lib/okf/cli/types.rb
+- lib/okf/cli/validate.rb
 - lib/okf/concept.rb
 - lib/okf/concept/file.rb
 - lib/okf/markdown/citations.rb
@@ -97,6 +125,7 @@ files:
 - lib/okf/render/graph/template.html.erb
 - lib/okf/server/app.rb
 - lib/okf/server/hub.rb
+- lib/okf/server/hub/not_found.rb
 - lib/okf/server/runner.rb
 - lib/okf/skill.rb
 - lib/okf/skill/SKILL.md
@@ -107,6 +136,7 @@ files:
 - lib/okf/skill/playbooks/menu.md
 - lib/okf/skill/playbooks/migrate.md
 - lib/okf/skill/playbooks/produce.md
+- lib/okf/skill/playbooks/refine.md
 - lib/okf/skill/playbooks/search.md
 - lib/okf/skill/reference/APACHE-2.0.txt
 - lib/okf/skill/reference/SPEC.md
@@ -142,6 +172,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 rubygems_version: 4.0.16
 specification_version: 4
-summary: 'The complete toolkit for the Open Knowledge Format: an agent skill, a CLI
-  and library, and a live knowledge graph. 100% local.'
+summary: 'The complete Open Knowledge Format toolkit: an agent skill, a CLI and library,
+  ranked search, and a live knowledge graph. 100% local.'
 test_files: []