DIS-067: terminology — the shard unit is a REPO; wiki (Store/Title/Keeper/Home/Submodules/URI) and code (`be.find().project`) call it "project"; the post reserves "project" for the metadata root

Now: OPEN

trees lines 47-54 fix four terms: store / project (the top-level thing with wikis, issues, tickets) / repo (a versioned tree, the shard unit) / worktree. The wiki calls the SHARD unit "project" throughout: Store:3,9,23,25 "project shards", .be/<project>/; Title:1,6-9 libabc is a "project"; Keeper.mkd:3; Home.mkd:26; Submodules:5,37; URI.mkd:44-57 ?/project/… shapes. Wiki Project:3 uses the POST's sense — the wiki is internally split. Code double-books it too: be.find().project is the shard title = the post's "repo" (discover.js:52-68,111; store.js reader.project), while the post's "project" exists separately as shared/project.js root() — which anchors on .be-or-.git PLUS a meta/ dir (project.js:17-41), NOT the post's decoder rule "the topmost .be under and excluding $HOME". Boundary letter-mismatch too: the climb probes $HOME/.be INCLUSIVELY (discover.js:136-137) and topWt stops at the hive boundary */work/ (discover.js:173-174, BE-031) — stop rules the post never states.

Input

Context

Full wiki hit list: Store.mkd:3,9,23,25; Title.mkd:1,6,8-9; Keeper.mkd:3; Home.mkd:26; Submodules.mkd:5,37; URI.mkd:44-57.
Code: discover.js:52-68,111 (project = shard title); shared/project.js:17-41 (metadata-root climb, meta/-dir rule); the naming side (navCwd/wtdir) is SRC_ROOT-bounded while the find-climb is $HOME-bounded — that gap is DIS-069/BRO-024:54 territory, not this ticket.
The post itself simplifies "sharded by a repo": the actual shard key is the Title with convergence/clash rules (Title.mkd:6-38) — footnote candidate for the post (user edit).

Goals

RULING (gritzko): rename plan — wiki shard-unit "project"→"repo" (or "title"d repo), and the code field be.find().project→? (title/repo); pick one and sweep.
RULING (gritzko): the project-anchor rule — post's "topmost .be under and excluding $HOME" vs project.js's meta/-dir rule vs the hive stop; one definition, stated in both post and code.
After the rulings: wiki sweep + code field rename (read-compat kept), URI.mkd query shapes re-worded.

Constraints

Pure-rename mechanics only after the ruling; refs-log row shapes (?/<title>/…) are wire/disk format — do NOT touch bytes, only prose and identifiers.
Coordinate the anchor-rule ruling with DIS-069 (nearest-hive) so we don't define "project root" twice.

WIP

Design decisions

(none yet)

TODOs

obtain the two rulings (rename target; anchor rule)
wiki sweep per the hit list
code: rename the discover/store field, keep read-compat
align project.js root() with the ruled anchor
propose the post's "sharded by Title" footnote to the user

Blockers and bummers

Gates on the rulings; the sweep is mechanical after that.

Outcome

FILED 2026-07-12 (trees.mkd audit); nothing landed yet.

DIS-067: terminology — the shard unit is a REPO; wiki (Store/Title/Keeper/Home/Submodules/URI) and code (be.find().project) call it "project"; the post reserves "project" for the metadata root