The default branch enables automatic recent daily-summary refresh and catch-up within the tracked period. Current-build checks in an owner-local Apple VM exercised MFA authentication, an automatic seven-day batch, independent import and local queries. Older-history traversal and supported native Docker deployment qualification remain pending. Local queries, protected export and replay remain available.
A single-owner, local Garmin archive. Preserve exact source payloads on your own storage; query daily summaries through REST and a CLI. A separate read-only terminal monitor follows system status and runs.
LOGBOOK 01 / THE OWNERSHIP MODEL
Blackbox reads Garmin’s unofficial private interfaces. Retrieval serves committed local data; a query never calls Garmin.
Each committed observation has its own receipt. Identical payload bytes share one content object. Exact source bytes and their provenance remain under the owner’s control.
Local storage / content deduplicationInstalled importers turn supported archived responses into daily summaries. SQLite is a query projection: supported archives can reconstruct it locally, without another download.
Source acceptance ≠ import successThe daemon owns storage. A scriptable CLI retrieves summaries, coverage, failures and artifacts. A private Chio monitor receives pushed status and run observations, with explicit history browsing.
REST / blackboxctl / read-only monitorLOGBOOK 02 / SYNTHETIC BROWSER ILLUSTRATION
Explore a tiny invented archive. Clear its sample projection, then rebuild it from the same source observations.
This browser illustration uses simplified sample records. It is not an application capture or an implementation of Blackbox’s storage, importer, or API. It connects to no service.
{
"date": "2026-09-19",
"steps": 8420,
"distance_meters": 6100,
"sleep_minutes": null,
"source_observation": "sample-03"
}The newer observation has no sleep value. The earlier value is not carried forward.
Three invented observations; two derived daily records. No Garmin requests.
MISSING STAYS MISSINGThe real daily view uses a whole successfully imported snapshot. Absent measurements do not become zero or inherit an earlier reading.
REBUILD HAS LIMITSArchive reconstruction restores supported source-derived records. It can lose operational run history and invalidate projection cursors; it does not recover every failed attempt.
Exact source, deliberate access
Local reads expose normalized data and public artifact metadata. Exact-byte downloads require a separate artifact-access capability. The CLI verifies downloaded byte counts and SHA-256, then publishes a new file without overwriting an existing one.
LOGBOOK 03 / CAPABILITIES AND EVIDENCE
The usable data scope is daily summaries. This private project is under active development; broader health and workout acquisition remains target behavior.
Project checkpoint / October 18, 2026Date-free archive-v2 setup, authentication with optional MFA and retained tokens, local REST/CLI retrieval, paginated inspection, field selection, protected source export, and explicit local replay are implemented. The daemon owns an independent local importer; a separate read-only monitor consumes pushed status and run updates.
The current checkpoint has recorded macOS and Linux regression and deterministic gates, compiled CLI/REST journeys, and archive-only reconstruction using synthetic data. An optimized arm64 Linux service smoke passed with an Apple-builder release-tar packaging workaround. The current monitor has separate terminal-process verification.
In an owner-local Apple VM, the current build completed MFA authentication and established a fresh archive binding. Ordinary scheduling then acquired seven recent daily summaries without manual sync; independent importing produced seven canonical days without failures. Compiled CLI metadata queries confirmed accepted and imported coverage, canonical days and source references. A compatible restart retained credential presence without new MFA; run results, imported coverage and canonical source references remained identical. Token renewal and rotation remain unverified; this limited check does not qualify supported deployment.
The merged implementation prioritizes the recent seven days, then eligible gaps and unfinished refreshes within retained tracking. Completing a batch does not establish historical completeness. Optional account-export importing is deferred, not a prerequisite. This is not a released or live-qualified deployment.
Older-history traversal, activities and FIT files, remaining Garmin datasets, complete supported host deployment, and backup/verify/restore tools are still pending. Native Docker deployment and an unmodified Dockerfile build remain separate qualification gaps.
LOGBOOK 04 / OPERATING BOUNDARIES
A Swift service with explicit storage ownership and local clients.
Swift 6.4 with strict concurrency. Native development requires macOS 15 or newer. The service image contains the daemon and CLI; the private monitor is built separately.
Use owner-controlled local POSIX storage, restricted credential files, and a named IANA time zone. Current archive-v2 setup takes no historical start date. Earlier archive or SQLite formats are refused without automatic conversion or deletion.
Garmin’s private interfaces are unsupported and can change. Blackbox does not modify Garmin records or bypass challenges or rate limits. The supported API publication is loopback-only; wider access needs a separately reviewed secure boundary.