A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0931

The application exists, one machine runs it, and the URL answers

Where it stands

Objective: Create or resolve the production application, deploy the cheap profile without accidental redundancy, verify the machine inventory and the resources against the declared policy, run the route-derived smoke suite against the public URL, and write the deployment report.
Why: Everything before this is preparation. A deployment that has never run is a hypothesis, and an exit code from a deploy command is not evidence that anything is being served.
Now: No application exists at any provider.
Wanted: One application, one machine, the declared resources, the declared region, a public HTTPS URL that answers, a smoke suite that passes against it, and a machine-readable report of what was deployed.
Done when: Cancelled 2026-10-14 on master e28daccd9b: its outcome, the Fly application exists, one Machine runs it and its URL answers, is the Fly deployment itself. The owner disconnected Fly.io on 2026-10-12; this repository deploys release binaries, the GHCR image and GitHub Pages (commit 9af3fa65a4 removed fly.toml).
Risk: This is the issue that spends money and touches a real account. It runs once the container evidence is in, and the inventory assertion is what keeps a mistake from billing indefinitely.

The authenticated identity and organisation are inspected before anything is created, and an existing intended application is reused rather than duplicated
The application name is deterministic, and a global collision produces a stable derived name rather than an interactive dead end
The first deployment does not create redundant machines, and the inventory is inspected from machine-readable output rather than assumed
The machine count, CPU class, memory, region, autostart, autostop and minimum running are asserted against the declared cheap profile after the deployment
The public URL answers over HTTPS, redirects behave as intended, and static assets load
The route-derived smoke suite passes against the public URL, including the websocket, MCP and API surfaces that are served
A machine-readable deployment report records the application, the URL, the revision, the image, the region, the resources, the measured sizes and the smoke result, following the repository's artifact conventions

Validation: majordomus deploymajordomus deploy statusmajordomus deploy doctor
Evidence required: app_createdsingle_machineremote_smokedeployment_report
Evidence present: unknown: the record carries no `evidence` entries

Touches: .ai/repo/deployments
Not: Creating a new application on any subsequent deployMutating or deleting any unrelated applicationAccepting a deploy command's exit code as verification
Depends on: I0913 I0914 I0916 I0917 I0918 I0922 I0930
Priority: p0
Profile: deep-work
Parallel safe: false
Owner: unknown: the record declares no `owner`

Adapter: scripts/github-sync
Repository: unknown: the derived plan's header carries no repository
External issue: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Nothing is wrong with these records.