docs: ADR-0014 — containers surface as browsable FileSystems - #7
Merged
Conversation
…Systems (engine); mount convention stays in the consumer
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.
Records the architectural decision behind 4n6mount's mount-smoke fix: forensic-vfs-engine should surface archive (zip/7z/tar) and logical (AD1/AFF4-Logical/DAR) containers as a browsable
FileSystemat natural paths, so every consumer gets them for free and 4n6mount can delete its localSyntheticFs+disk-forensicdep. The mount-folder convention (volume nesting, overlay) stays in the consumer. 4n6mount PR #7 is the interim local unblock; this ADR is its durable replacement (the engine follow-up). 🤖 Generated with Claude Code