fix(data): close the Needs×lattice seam — a no_egress Need prunes reference-mount - #32
Merged
Conversation
…erence-mount
The one unfinished coupling from the mount-taxonomy analysis. backend_for now takes needs +
offline_tolerant + store_locality, and prunes the cheap reference-mount BEFORE link availability:
- a `no_egress` Need on a REMOTE store forbids reference-mount (a remote reference-mount IS
egress) -> forced to a local copy;
- offline-tolerance forbids reference-mount even over a reliable link (it has zero offline
capability; cut the link and it fails) -> local cache;
- a `no_egress` Need on a LOCAL store still reference-mounts (a local mount is not egress).
So the signature is intent × link × durability × needs -> backend, and the Needs firewall and the
mount lattice are ONE plane. docs/MOUNT_TAXONOMY.md updated. Tests: +1 = 157 tools tests green.
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
1 participant
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.
The one unfinished coupling from the mount-taxonomy analysis.
backend_fornow takesneeds+offline_tolerant+store_localityand prunes the cheap reference-mount before link availability:no_egresson a remote store → forbidden (a remote reference-mount is egress) → local copy;no_egresson a local store still reference-mounts (a local mount is not egress).Signature is now
intent × link × durability × needs → backend— the Needs firewall and the mount lattice are one plane. 157 tools tests green.