caerule.
← Selected work

02 / AuthCompanion · Personal / open source

Authentication,
with a way back.

GPG signing and sudo live at different system boundaries. AuthCompanion brings their Touch ID and Apple Watch setup into one coordinated workflow, with explicit ownership and restore behavior.

My roleOriginal coordinator & companion fork maintenance

Swift · macOSApple Silicon & Intel packaging

OpenAI Build Week 2026Project participant

Explore the component boundaries

One workflow.
Clear ownership.

Select a component to inspect its role.
This is a design walkthrough, not a live authentication prompt.

The two companion tools remain independently installable.

Original Swift tool

AuthCompanion

Coordinates the two components through versioned machine-readable contracts, providing setup, restore and diagnostic commands.

Owns
The orchestration and visible suite outcome.
Boundary
Delegates authentication and component state to the tools that own them.
Inspect the source ↗

Make the state understandable

Authentication setup involves configuration files, component versions and different privilege levels. I created the AuthCompanion coordinator and extended the companion GPG/PAM forks so the workflow could be inspected, executed and diagnosed through explicit contracts.

Coordinate instead of duplicating

The coordinator composes the two independent tools. GPG and PAM logic stay with their components. This keeps ownership visible and avoids creating a second implementation of the same authentication behavior.

Inspect before changing the system

A passive plan lets a developer review intended changes before setup. State inspection, restore operations and actionable diagnostics make the lifecycle easier to reason about. In a partial failure, observed state matters: restoring a recorded baseline is a different operation from undoing only the most recent attempt.

01Inspect the planUnderstand intended changes
02Authorize locallyRespect the privilege boundary
03Configure & verifyCheck the resulting state

A release is part of the product

The initial release included CI, stable JSON output and universal archive packaging. Its public validation record reports 39 passing tests, strict-concurrency compilation and archive tamper rejection.

Released software, available to inspect

AuthCompanion v0.1.2 was published in July 2026. The project also participated in OpenAI Build Week 2026.

The coordinator is my original project; the GPG and PAM companions are maintained forks. The quoted validation applies to the initial release record. Current source can include work beyond the linked release.

Next / 03 · AI developer tooling

A workflow beyond the prompt.