Jarvis: building an assistant across application boundaries

A desktop assistant combines work with very different lifetimes. A user interaction may be brief, while audio, model calls and background state continue independently. I want the architecture to make those lifetimes understandable rather than hide them behind a single impression of intelligence.

CTO to Human: what the history tells us

Jarvis's selected history moves from Swift package scaffolding in April to automated development releases in May. The release names matter: these are development milestones, not a stable-product announcement. Some later version changes record planning and verification rather than new user-facing features.

Engineer to Engineer: the boundary that matters

Swift 6 concurrency checks and package boundaries make ownership part of the implementation discussion. A release linked to a specific CI run then connects that implementation to an inspectable artifact. Neither mechanism proves the entire assistant experience is complete, but both give the next engineering decision a firmer reference point.

Milestones in the public record

• 2026-04-22 — Jarvis starts with explicit Swift package boundaries. The April foundation added four Swift Package Manager packages with Swift 6 strict concurrency. This establishes a concrete early architecture milestone for the macOS assistant. Project journal.
• 2026-05-13 — Jarvis records its first automated development release. The dev.50 release notes identify the first automated development tag and describe a v0.1 milestone spanning voice, listening, seeing, facts and basic UI. The version is explicitly a development build. Project journal.
• 2026-05-14 — Jarvis keeps development artifacts tied to evidence. The dev.71 release links a specific CI run and records checks for the webview, application build and Swift packages. Its listed change is planning and sequencing documentation for the next wave. Project journal.

The direction is an assistant whose visible behavior and underlying system can be explained together. That requires keeping the development status honest while improving the route from source to something a person can actually try.

Explore the jarvis project hub.

Retrospective written on October 12, 2026, covering the public evidence available for October 12, 2025 through October 12, 2026. Linked journal entries use source event dates; this essay is a newly written retrospective. Quiet months do not imply an unrecorded release, and short-lived projects are not presented as having a full year of activity.