Building a passthrough file system

At a glance

Project structure

Source bundle/
├── Passthrough/
│   ├── PassthroughApp.swift
│   ├── ContentView.swift
│   └── Passthrough.entitlements
├── PassthroughAppEx/
│   ├── PassthroughAppEx.swift
│   ├── PassthroughFileSystem.swift
│   ├── PassthroughFSItem.swift
│   ├── PassthroughFSVolume+FSVolumeOperations.swift
│   ├── PassthroughFSVolume.swift
│   └── Info.plist
├── Configuration/
│   └── SampleCode.xcconfig
└── Passthrough.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 6 project/configuration file(s) and 8 source declaration(s).

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["Passthrough"]
    V2["PassthroughAppEx"]
    Boundary["FSKit APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary

Reference code

Passthrough/PassthroughApp.swift:10 — architecture anchor

@main
struct PassthroughApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

Interpretation

The branches represent separate entry-bearing project variants in the downloaded bundle, not runtime calls between those variants. Each branch is intentionally collapsed at the documented framework boundary; the detailed target-local flow remains in the cited files. Ownership is claimed only where the next section cites a stored property or assignment.

Ownership and state

classDiagram
    PassthroughFileSystem *-- Logger : passthroughfs
    PassthroughFileSystem o-- FSPathURLResource : resource
    PassthroughFileSystem o-- Containerstatus : containerStatus
    PassthroughFSItem *-- Int32 : fileDescriptor

Ownership evidence

PassthroughAppEx/PassthroughFileSystem.swift:12 — stored dependency or nearest verified ownership anchor

    static let passthroughfs = Logger(subsystem: "com.apple.fskit.PassthroughFS", category: "default")

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Class and protocol design

Passthrough/PassthroughApp.swift:11 — representative type boundary

struct PassthroughApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

PassthroughAppEx/PassthroughFSItem.swift:79 — representative boundary

    private func initInode() throws {
        var statResult = stat()
        _ = try throwErrno { fstat(self.fileDescriptor, &statResult) }
        self.inode = statResult.st_ino
    }

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: App: PassthroughApp; System: PassthroughFileSystem; View: ContentView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: throwErrno, createVolumeNameFromPath, loadResource, unloadResource, probeResource, initInode, openWithMode, upgradeOpenMode.
• Files: Passthrough/PassthroughApp.swift, PassthroughAppEx/PassthroughAppEx.swift, Passthrough/ContentView.swift, PassthroughAppEx/PassthroughFileSystem.swift, PassthroughAppEx/PassthroughFSItem.swift, PassthroughAppEx/PassthroughFSVolume.swift.

Architecture takeaways

• PassthroughApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches FSKit, ExtensionFoundation, SwiftUI through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation