Beagle SCM

DIS-068: URI.mkd lacks the trees.mkd resolution model — the five questions + slot-coverage/override, /// empty-authority = main tree, address-#pin vs payload-#message split, ?sha detach placement

trees lines 124-148 give the URI section its model: five questions (store, repo, branch, commit, dirs/files), the slot-coverage plot //12345 /2345/5 ?/2/34 #4, general→specific with later parts overriding earlier guesses, and the .be-climb derivation. URI covers only relative resolution (URI.mkd:29-31) — no question model, no override principle, no empty-authority form (///jab appears solely at Project.mkd:15, with the "bagle-ext" typo; URI.mkd:9 says "//name is a worktree, period"). Separately the fragment slot is conflated: the post's grammar reads fragment = pinned hash, while the verb pages use # as PAYLOAD — commit message (Verbs:19, POST.mkd:8), move target (PUT.mkd:16), rewind (#~1, GET.mkd:25), free-form (Home.mkd:27); and a detached commit is addressed by ?sha in the QUERY (URI.mkd:53-55, GET.mkd:11,24) where the post's clean split would put a hash in #. Doc-only ticket; the resolver itself matches the model (audited 2026-07-12: mergeUri slot merge, per-verb overrides).

Input

Context

• URI.mkd:29-31 relative resolution only; no ladder/override section.
• // empty authority: Project.mkd:15 (only mention, typo), URI.mkd:9 (excludes it), GET.mkd:14,28 (only //ABC-123), POST.mkd (absent).
• Fragment payload uses: Verbs.mkd:19, POST.mkd:8, PUT.mkd:16, GET.mkd:25, Home.mkd:27. Address use: #pinned_hash (post line 126, URI.mkd:56-57).
• ?sha detach shapes: URI.mkd:53-55, GET.mkd:11,24, Home.mkd:29.
• POST-SUSPECT caveats for the blog itself (user edits, propose only): file: is a load-bearing local scheme (URI.mkd:13, GET.mkd:31) yet the post lists ssh/http/be as "for remotes"; the fragment=pin grammar line deserves the payload caveat; ?sha detach deserves a mention or a relocation ruling.

Goals

• URI.mkd gains: the five questions, the coverage plot with a one-slot worked decode, the override sentence, the .be-climb derivation paragraph (post lines 128-148 condensed to wiki budget).
• Define //////path: empty authority = the main tree; fix the Project.mkd:15 typo; add the form to GET/POST pages.
• Split ADDRESS fragment (#pin) from VERB-PAYLOAD fragment (#message, #new.c, #~1) explicitly in URI.mkd; each verb page names which it takes.
• RULING (gritzko): does ?sha detach stay in the query (then the post gets a caveat) or move to #hash (then GET/URI pages change)?

Constraints

• Doc-only; no code moves here (resolver verified conforming).
• Wiki budgets/greppability per /meta/wiki; blog edits are the user's — propose, don't write.

WIP

Design decisions

• (none yet)

TODOs

• URI.mkd: questions + plot + override + climb section
• URI.mkd + GET/POST: /// empty-authority form; Project.mkd:15 typo
• URI.mkd: address-vs-payload fragment split; verb pages annotated
• obtain the ?sha-detach ruling; apply to GET/URI or propose the post caveat
• propose the file: scheme caveat for the post (user edit)

Blockers and bummers

• (none yet)

Outcome

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