Repository navigation
docs(plan): AnyEntry claims; the resource-construction campaign converges - #623
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two documentation changes that belong together: the resource-construction campaign's closure, and the
plan for the feature its last phase exposed.
The AnyEntry plan (#616)
docs/plans/any-entry-claims.md— six phases, eleven judgment scenarios, and an audit of all 27announced file-provider methods.
Give the claim surface the permissive option the discovery surface already has. A mutation target's kind
is not the author's business — a move moves whatever is there — but the claim's Go type is the kind
assertion, so a kind-indifferent operation must either name a kind it does not care about or multiply
into one method per kind.
file.AnyEntryasserts existence and nothing else, and resolves to theobserved kind inside the
Pending → Activetransition (Goneleaves it unasserted, because nothing wasobserved) — the moment the model already consults the disk, through the seam
op.RootBinderestablishedand the ledger swap
rebindEntryalready performs.The payoff:
file.movemoves any kind again from a plain authored path,file.move_directoryretires,and a symbolic link can be moved — a capability that regressed when kind-honest activation landed (#611).
The surface audit found three more defects:
file.remove's*Regulartype contradicts its owndocumentation ("file or empty directory");
file.unlinkis the same operation asremoveand retires;file.remove_allis alreadyrm -rfin its body, with the*Directoryclaim the only thing keeping itoff a file or a link. The removal family ends split by blast radius, never by kind — the stdlib's
split (
os.Removedeliberately does not ask the kind;os.RemoveAllopens by callingRemove), whichis why Go never needed an
Unlink. Also ruled:moveloseson_missing(a nil product hands downstreamconsumers a nil promise — the pathology that dropped
Skip), and policy parameters go last.Tasks: #617 – #622.
Resource-construction closure (#587)
The campaign converges.
4-resource-management.status.mdstates it — the design and the tree agree, andthe divergence table has no surviving row — with per-PR completion rows and an Outstanding list carrying
only what outlives the campaign.
4-resource-management.md's header reads implementation complete;3.5.4-file-provider.mdgainsfile.discover/file.resolve,file.move_directory, and thekind-honest-claims paragraph; the transport plan's supersession note is finalized — what replaced
"recreate from slot URIs" is now named, so that plan's Goal holds for every addressing.
Docs only; no code changes. Closes #587. Refs #581, #616.
Gate:
make test103 ok / 0 fail;gofmt -lclean.