BOT-anist

At a glance

Project structure

Source bundle/
├── BOT-anist/
│   ├── BOTanistApp.swift
│   ├── Robot/
│   │   └── RobotData.swift
│   ├── Views/
│   │   ├── RobotView.swift
│   │   ├── SelectorViews.swift
│   │   ├── ContentView.swift
│   │   ├── ExplorationView.swift
│   │   ├── OrnamentView.swift
│   │   └── RobotCustomizationView.swift
│   ├── PlantAnimationProvider.swift
│   ├── Components/
│   │   └── JointPinComponent.swift
│   └── Systems/
│       └── JointPinSystem.swift
└── Packages/
    └── BOTanistAssets/
        └── Sources/
            └── BOTanistAssets/
                └── Components/
                    └── PlantComponent.swift

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 4 project/configuration file(s) and 34 source declaration(s).

Overall architecture

flowchart LR
    N1["BOTanistApp"]
    N2["ContentView"]
    N3["PlantAnimationProvider"]
    N4["RealityKit / SwiftUI APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

BOT-anist/BOTanistApp.swift:15 — architecture anchor

@main
struct BOTanistApp: App {
    @Environment(\.dismissWindow) var dismissWindow
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into visionOS.

Ownership and state

classDiagram
    BOTanistApp *-- Logger : logger
    BOTanistApp *-- AppState : appState
    BOTanistApp *-- Size3D : initialVolumeSize
    BOTanistApp *-- CGSize : initialWindowSize

Ownership evidence

BOT-anist/BOTanistApp.swift:13 — stored dependency or nearest verified ownership anchor

let logger = Logger(subsystem: "com.apple-samplecode.BOTanist", category: "general")

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.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

BOT-anist/AppState+Exploration.swift:74 — representative execution boundary

            Task { @MainActor [entity] in
                entity.components[BlendShapeWeightsComponent.self]!.weightSet[0].weights = BlendShapeWeights([0, 1, 0, 0, 0, 0, 0])
            }

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

BOT-anist/BOTanistApp.swift:16 — representative type boundary

@main
struct BOTanistApp: App {
    @Environment(\.dismissWindow) var dismissWindow
    // ...
}

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

Access control

Reference code

BOT-anist/AppState+Exploration.swift:17 — representative boundary

    public func prepareForExploration() {
        // ...
            let map = try Entity.load(named: "scenes/volume", in: BOTanistAssetsBundle)
        // ...
    }

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

Main application flow

sequenceDiagram
    participant RobotProvider
    participant Entity
    participant rootEntity
    participant animationEntity
    participant entity
    RobotProvider->>RobotProvider: loadEntityFromRCPro()
    RobotProvider->>Entity: Entity()
    RobotProvider->>rootEntity: findEntity()
    RobotProvider->>animationEntity: animationLibraryComponent()
    RobotProvider->>entity: set()

Reference code

BOT-anist/Robot/RobotProvider+Loading.swift:72 — loadRobotParts()

    func loadRobotParts(taskGroup: inout TaskGroup<RobotPartLoadResult>) async {
        RobotPart.allCases.forEach { part in
            for (index, sceneName) in part.sceneNames.enumerated() {
                taskGroup.addTask {
                    do {
                        let partName = part.partNames[index]
                        logger.info("Loading scene \(sceneName), part: \(partName) for part type \(part.rawValue)")
                        if let entity = try await self.loadEntityFromRCPro(named: partName, fromSceneNamed: sceneName) {
                            if part == .body {
                                var libComponent = AnimationLibraryComponent()
                                let animationDirectory = "Assets/Robot/animations/\(partName)/"
                                for animationType in AnimationState.allCases {
                                    if let rootEntity = try? await Entity(named: "\(animationDirectory)\(partName)\(animationType.fileSuffix())",
                                                                          in: BOTanistAssetsBundle) {
                                        if let animationEntity = await rootEntity.findEntity(named: "rig_grp") {
                                            if let animationLibraryComponent = await animationEntity.animationLibraryComponent {
                                                libComponent.animations[animationType.rawValue] = animationLibraryComponent.defaultAnimation
                                            }
                                        }
                                    }
                                }
                                await entity.components.set(libComponent)
                            }
                            return RobotPartLoadResult(entity: entity, type: part, index: index)
                        } else {
                            fatalError("Error loading robot part \(partName) from scene \(sceneName)")
                        }
                    } catch {
                        fatalError("Error loading scene \(sceneName) for part \(part.rawValue)")
                    }
                }
            }
        }
    }

Naming conventions

• Types: App: BOTanistApp; Component: JointPinComponent, PlantComponent; Provider: PlantAnimationProvider; System: JointPinSystem; View: ContentView, ExplorationView, FaceSelectorView, LightColorSelectView, MaterialColorSelectView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: partForMaterialName, color, randomColor, face, hash, handleDrag, adjustRobotToFillCenterOfView, generateGrowAnimationResource.
• Files: BOT-anist/BOTanistApp.swift, Packages/BOTanistAssets/Sources/BOTanistAssets/Components/PlantComponent.swift, BOT-anist/Robot/RobotData.swift, BOT-anist/Views/RobotView.swift, BOT-anist/PlantAnimationProvider.swift, BOT-anist/Components/JointPinComponent.swift.

Architecture takeaways

• BOTanistApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches RealityKit, SwiftUI, BOTanistAssets, Spatial 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