- Why it exists
- General navigation products do not preserve a person's field notes, timing samples, or manually confirmed road observations as an inspectable data layer they control.
- What it does not claim
- It is not navigation, traffic prediction, or a safety-critical system. Attribution remains manual, and signed data proves origin and integrity rather than correctness.
- What is built now
- SwiftUI, MapKit, SwiftData, and CryptoKit source covers road assets, observations, JSON and signed exports, Keychain-backed identity, mock or GPS telemetry, local peer transport, and diagnostics.
- SwiftUI
- MapKit
- SwiftData
- CryptoKit
Evidence attached
- Unit-test sources cover models, export behavior, signing, pairing, and matching logic
- Architecture, risk, setup, and running documents state validation gates and failure modes
- The design requires no account or cloud service and includes signed-record verification support
What remains
The full Mac, Xcode, simulator, and paired-device validation sequence remains unfinished. The OBD source is still a stub, and safe field interaction requires real-world testing.