The owner's direction (2026-08-02, recorded in B-031, verbatim): «не логичней ли самому корневому пакету vibevm в vibe.toml дать нормальное fully-qualified имя как у всех остальных пакетов, и дальше чтобы все ссылки работали по обычным правилам, без исключений? Резолвер при этом должен начать учитывать … адресацию внутри vibe.toml ВЕЗДЕ, включая корневой пакет. Таким образом мы теряем короткую нотацию spec://org.vibevm.core/vibevm/..., но получаем универсальность. Я бы назвал корневой пакет spec://org.vibevm.core».

**The census reshapes the filing's numbers** (all figures: the E5 evidence, commands cited there). The filing's «1 384 цитаты» was the crates-only figure; the whole living tree carries **2 351** occurrences of `spec://org.vibevm.core/vibevm`: crates/ 1 375, campaigns/ 607 (of which **500 are historical evidence JSON**), packages/ 322 (**314 in canonical package sources** — the cross-boundary half), spec/ 33, root md 12, xtask 2. Of the crates figure, ≈343 are **synthetic test fixtures** (`spec://org.vibevm.core/vibevm/x/y#a` and kin) and 95 cite the real root doc `VIBEVM-SPEC` (registered via `specmap.toml`'s `root_spec_docs`). And the «exceptions» turn out narrower than filed: the contract carve-out is **exactly one line** (PROP-029:43 `##SCOPE-HOST`; PROP-035 carries no host language at all), while the code's special-case is one resolver arm (`spec_root`, resolver.rs:66-77), one enum variant (`Authority::Host`, 6 sites), two `HOST_NAMESPACE = "vibevm"` constants, and `specmap.toml:14 namespace = "vibevm"`.

**The «second half of the exceptions» dissolves on evidence.** Doc-id truncation (`PROP-000` → `PROP-000….md`) was filed as a host exception; the sweep shows `resolve_doc` is **authority-agnostic** (resolver.rs:60-63 — the same prefix-scan for host and packages) and package citations already use it (190 occurrences, 165 of them the real `org.vibevm.ai-native → PROP-014`). Truncation is not host-special and B-031 does not touch it; whether the *flow* publishes the rule is B-028's question and stays there.

The root project gains a package identity — **group `org.vibevm.core`, name `vibevm`** (the owner's ruling, 2026-08-04), address prefix `spec://org.vibevm.core/vibevm/…` (the joiner is `/` never `.`, PROP-035 §6; the manifest's `name = "vibevm"` does not change — only `group` is added). The resolver's host mapping dies: `spec_root` maps the **self coordinate** — the workspace's own `[project]` identity — to `ws_root/spec` exactly where it today maps the `vibevm` token, and every other authority resolves as a package slot; nothing else in resolution changes. The `spec://org.vibevm.core/vibevm/…` notation stops resolving: an address whose authority is not a known coordinate fails **loudly with the rename hint** («the host is `org.vibevm.core/vibevm` since B-031») — the B-011 fail-with-candidates posture, never a silent alias. One scripted, reviewed migration rewrites the living surfaces in one commit; historical machine records stay as written; the affected registry anchors re-judge through the standing seal path. Universality is the whole point: after this, §1 of PROP-029 binds *everything*, and the sentence «the root project is not a package with a group» is retired rather than exempted.

**Identity carrier.** `vibe.toml` `[project]` gains `group = "org.vibevm.core"`; its `name = "vibevm"` **does not change** — the identity IS the coordinate (PROP-008: identity = (group, name)), and the ruled form keeps the manifest name intact, so nothing renames anywhere (the owner's ruling, 2026-08-04). The lockfile today carries no root identity block (evidence §7b) and does not need one — the resolver reads the self coordinate from the manifest it already has.

**Resolver shape.** `FileResolver::new(ws_root, host_namespace)` becomes `FileResolver::new(ws_root, self_coordinate)` — the constructor takes the root's (group, name) instead of the undotted token; `spec_root` matches `Authority::Package{group, name, ..}` **against the self coordinate first** (→ `ws_root/spec`), then falls to the vibedeps slot lookup. The `Authority::Host` **parse variant survives** — an undotted authority is grammatically legal (PROP-029:44 keeps illustrative fixtures like `spec://demo/…` as written, and legacy addresses must fail *legibly*) — but **no undotted authority resolves**: the resolver's Host arm becomes one unconditional error carrying the migration hint. The two `HOST_NAMESPACE` constants die with their call sites. `VIBEVM-SPEC` keeps resolving through `specmap.toml`'s `root_spec_docs` under the new namespace value.

**`specmap.toml:14`** — `namespace = "vibevm"` becomes the self coordinate (`"org.vibevm.core/vibevm"`). The build verifies the specmap engine treats the value as an opaque prefix (expected — it mints `spec://{namespace}/…` strings); if anything parses it, that surfaces in the slice as a named finding, not a silent fix. The specmap engine is vendored ×6, so any *engine* change (none expected) vendors forward the same pass.

**Migration.** A python script under the campaign zone (reviewable, idempotent, dry-run first) rewrites `spec://org.vibevm.core/vibevm/` → `spec://org.vibevm.core/vibevm/` and bare `spec://org.vibevm.core/vibevm` (grammar tests) accordingly, across the **living surfaces**: `*.rs` (fixtures included — `spec://org.vibevm.core/vibevm/x/y#a` becomes `spec://org.vibevm.core/vibevm/x/y#a`, exercising the self-coordinate path; the handful of tests that *assert the Host mapping itself* are rewritten to assert the new error), `*.md` (spec/, campaigns/ docs, packages/ canonical, root), `*.toml`, xtask. **Historical machine records are not rewritten:** the 500 campaign evidence/baseline JSONs are dated records of what the tree said at their HEAD (the campaign's own-corpus law), and the registry keys anchors by file-path, never by these literals — so nothing downstream re-keys. The 314 canonical-package occurrences are in-slot edits accumulating to the pre-publication boundary per the release ruling (no version bumps now); `cargo xtask sync-engines` carries the crate-side ones forward.

**Re-judgements riding the landing.** The two deferred ledger rows this build was named for — F-169 (2 anchors) and F-147 (3 anchors, its planning-granularity half B-032's) — re-judge after the migration per `#close-2026-08-03`; host-zone anchors whose fact texts carry migrated literals re-seal through mirror → merge-verdicts → seal, never chained. The B-011 lane preamble sentence («full `spec://` addresses resolve against package sources under `vibedeps/`») gains the self-coordinate clause in the same generated-text edit.

Doc-id truncation (already universal; flow legalization = B-028). The flow-published grammar (B-028's ruling). `SCOPE-FIXTURES` — illustrative addresses stay as written. Disk layout — `spec/` stays where it is; no file moves, no renames. The specmap engine (a config value changes, not the engine). Historical campaign JSON. Publication and version numbers (the release ruling stands).

**Two resolvers, one grammar.** `FileResolver` (vibe-spec) and the specmap engine both resolve host addresses; the design changes one code path and one config value, and the build's acceptance must exercise **both** (a `vibe check`-class pass + a specmap re-mint over the migrated tree).

**A ~1 800-occurrence rewrite is a mass edit.** Mitigations: scripted with a dry-run diff the boss reads; the panel and both gates green before commit; the lane regenerated and byte-compared (only expected lines move); anchors re-judged verdict-first rather than assumed.

**Muscle memory and stale citations.** Every future hand-typed `spec://org.vibevm.core/vibevm/…` fails loudly with the hint — that is the designed behaviour, not a regression; the PROP-029 changelog carries the rename record (the addressable-specs tombstone law applied to an authority).

Three forks, the boss's recommendation first. **RULED 2026-08-04:** (K) → the owner's own form — group `org.vibevm.core`, name `vibevm` (neither K1 nor K2 as presented: the group carries his full spelling, the manifest name never changes); (L) → L1; (P) → P1. The fork texts below stay as presented, the record of what was asked:

PROP-029: `##SCOPE-HOST` is retired-with-tombstone (the changelog records the authority rename and the self-coordinate rule: «the root project is a package at `org.vibevm.core/vibevm`; its docs resolve to the workspace's own `spec/`»); §1's binding sentence loses its host exemption. PROP-035 §6: one sentence — the router's self-coordinate mapping (the root's coordinate resolves to the authored `spec/` tree, not a `vibedeps/` slot). PROP-008: no edit (identity semantics already cover the root once it has a group). `specmap.toml` and the root `vibe.toml` change as §3. The B-031 backlog acceptance restates as: zero `spec://org.vibevm.core/vibevm` occurrences on living surfaces; both resolvers answer `spec://org.vibevm.core/vibevm/…`; the F-169/F-147 rows re-judged; panel green.

Sequenced, one lane (the perimeters chain through the same crates): **(W1)** resolver + identity — `vibe-core` manifest `[project].group`, `FileResolver` self-coordinate, the Host-arm error with hint, the two constants retired, unit tests incl. the erroring legacy form (self-verify: check + targeted tests + clippy + `wc -l ≤ 600`); **(W2)** the migration script (dry-run mode, per-surface counts printed, idempotent) — boss reviews the dry-run diff, runs the wet pass, regenerates the lane and both indexes; **(W3, boss)** the §7 PROP edits, `specmap.toml`/`vibe.toml` identity, **the §5.1 metadata pass — `vibe progress mirror --campaign`, the mechanical-diff spot-check, the mass re-seal of touched files** — the re-judgements proper (F-169/F-147 through mirror → merge → seal, never chained), commits per topic, sync-engines for the vendored crate edits, panel, mirrors. The census's §3 site list is the perimeter map for W1; §1's per-area counts are W2's expected-diff oracle.