Status: current authority for CloudPoint 1.3.0 source build 8 as of 2026-08-29.
This file records durable product and engineering decisions. Executable source and tests are the final authority. Dated plans, prior release notes, and the Unreleased changelog preserve history but do not reactivate retired behavior.
- Single Image runs Apple SHARP once on one confirmed still, camera frame,
or selected video frame. A published result contains exactly 1,179,648
Gaussians and
single-image-sharp-rawprovenance. It does not claim unseen coverage. - 360 Scan admits 3 through 120 overlapping views of one static subject, solves calibrated RealityKit poses and sparse geometry, and trains one OpenSplat scene on MPS. Image selection may start with 3 through 200 files.
- Coverage labels come from solved geometry, not frame count. Partial output remains Partial. Single Image is never presented as a 360 reconstruction.
- LingBot, MLX point-cloud inference, CPC rendering, and independent-view SHARP fusion are retired. Old manifests remain decodable and read-only.
AppCoordinatorowns routing and exactly one view model per project. Workspace resources close only after the final actualNSWindowcloses; stale callbacks cannot evict a replacement workspace.WorkspaceViewModelretains startup and camera-preflight tasks. Close first delivers controller interruption and camera shutdown, then awaits retained work, so cancellation-insensitive startup cannot deadlock or revive UI state.SessionControlleris the durable state-machine boundary for capture, preparation, training, validation, relocation, cancellation, and terminal publication. Test fixtures must use a runnable current mode, never a retired engine disguised as one.- Pose preparation transfers the original
TemporaryTrainingDirectorytoken insideOwnedTrainerDataset. Never reconstruct ownership from an arbitrary path. Cleanup validates the exact parent and marker and runs on every success, failure, cancellation, relocation, close, or dropped event path. - Keyframe copies, frame persistence, manifest writes, large checkpoint hashes, PLY export, and captured-frame thumbnail decoding stay off the main actor. UI publication alone returns to the main actor.
- A retained security-scope lease covers the selected working directory for the live store lifetime. Stale bookmarks are refreshed; every shorter source or package scope is balanced on its exact lifetime boundary.
- Project manifests are regular, no-follow files capped at 4 MiB before allocation. Native and Python media reject dimensions above 8,192 per side or 64,000,000 decoded pixels before materialization, then validate again after decode.
- PLY parsing rejects headers above 65,536 bytes, more than 64 properties, more than 2,000,000 total elements, list counts above 2,000,000, negative or unrepresentable counts, overflowed sizes, and cancellation.
- Raw SHARP PLY is an exact 56-byte vertex schema with exactly 1,179,648 vertices. Pose-aware OpenSplat PLY is the exact 62-float schema and is capped at 2,000,000 vertices. Provenance, containment, regular-file status, exact body size, finite values, and representative Metal rendering are required before publication.
- The worker opens the checkpoint once with
O_RDONLY | O_NOFOLLOW | O_CLOEXEC, hashes that descriptor, compares the expected digest in constant time, loads through the same descriptor withweights_only=True, and rejects identity or mutation changes. Provenance records the measured digest, not caller-supplied text. - Detailed local paths and reflected failures are private hashed diagnostics. Public logs and UI expose stable categories only.
- The Apple SHARP pin is 2,809,738,232 bytes with SHA-256
94211a75198c47f61fca7d739ba08a215418d8d398d48fddf023baccc24f073d. Its URL, size, digest, source commit, and research license are trust boundaries. - Default and public builds contain no model weights. A private local Release
may opt in through ignored
Config/Local.xcconfig; the verified seed belongs inContents/Resources/Sharp, never Git, test fixtures,WorkerRuntime, or a public archive. - License acceptance still precedes bundled seeding. A present invalid seed fails closed without network fallback. Materialization uses no-follow descriptor traversal, clone or cancellation-aware copy, identity-bound cleanup, digest verification, and atomic publication. Existing valid external installs still win.
- Public ZIPs must use
scripts/package-public-release, which forces the model setting empty and verifies both app and archive. Direct Finder ordittopublic packaging is not an accepted release path. - Swift packages are pinned by root
Package.resolvedand resolved-only verification. Bootstrap always uses the checksum-verified repository-local XcodeGen. Python uses the checked offlineuv.lock. - OpenSplat is AGPL-3.0. Public binaries require the pinned complete source, patches, notices, relocatable dylib closure, path-remapping checks, and MPS host-version gate. There is no silent CPU fallback.
- Independent SHARP predictions do not form a coherent multi-view scene. Plausible single angles can hide folded geometry, mirrored trajectories, duplicate subjects, and scale drift. Solve poses first and optimize once.
- More frames do not repair missing geometry or broken overlap. Quality, calibration, positive depth, motion continuity, and loop closure matter.
- Validate before allocating and bind validation to the bytes actually used. Cached health, pathname reopens, force-unwrapped numeric parsing, and validate-then-materialize flows are insufficient trust boundaries.
- Cancellation is an ownership transition, not only a task flag. Publish the durable terminal state promptly, interrupt external work, and keep exact cleanup tokens until the final consumer releases them.
- Window lifetime, view lifetime, task lifetime, file ownership, and security scope are different concepts. Model each explicitly and test stale callbacks and blocked shutdown paths.
- Deterministic release evidence comes from source-controlled commands and one compiled native test bundle. Global tools, mutable dependency resolution, and hand-built archives are not reproducible gates.
The vendored PLY reader validates an artifact and then reopens it for materialization, leaving a narrow same-user validate-then-reopen replacement window. Imported project artifacts are local user input and receive bounded preflight plus post-read count/finite validation, but a future descriptor-bound reader would remove this residual completely.
Automated gates do not replace private real-media acceptance. Physical camera behavior, a representative 20+ view loop, trajectory quality, seams, and absence of a doubled subject remain owner-operated checks unless the exact fixtures are supplied. Report skipped fixture gates explicitly.
DEVELOPMENT.mdowns current architecture, limits, build, verification, and release commands.README.mdindexes current and historical documentation.../CHANGELOG.md, release notes, notices, vendored patch records, and verification records are immutable history or compliance evidence. Keep them even when behavior is retired.- Compress superseded current guidance here and in
DEVELOPMENT.md. Do not rewrite dated plans to make them appear current.