Skip to content
Cockpit0.29.0
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

I0926

The deployment documentation is generated and reachable

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
fly-deployment
Milestone status
ACTIVE
Wave
4
Waiting on
I0913I0924
Holds back
I0932
Behind it in all
1
Evidence
0 of 3
In the waySubjectDetail
issueI0913I0913 is not DONE
issueI0924I0924 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0926

majordomus plan verify I0926

majordomus plan done I0926

What it is

Objective
Produce the deployment documentation from the canonical object and the implementation — architecture, container, resources, workflow, CI, security, cost, troubleshooting and scaling — and make it reachable from the surfaces that are already generated.
Why
Deployment values retyped into prose are wrong the first time the region or the memory changes. The repository already generates its references from data; this is the same mechanism applied to one more subsystem.
Now
The site is generated from the registry and the documentation index. No deployment page exists and no navigation entry points at one.
Wanted
The tables and reference sections come from the canonical object and the registry, the prose explains what data cannot, and the page is reachable from the landing surface and the navigation without anyone editing a list.
Done when
unknown: the record declares no `completion`
Risk
Troubleshooting written before anything has failed is fiction. It is filled from the failures the implementation actually hits.

Acceptance

  • Every deployment value shown — region, port, resources, machine count, autostop, budgets, base image — is derived from the canonical object or the recorded measurements
  • The page covers the architecture and why this provider, the container and its runtime, the resources, the developer workflow with real commands, CI and rollback, security, cost, troubleshooting drawn from failures actually met, and how to scale by changing one file
  • Any price or provider fact that changes over time is marked with the date it was observed and is not stated as a guarantee
  • The page is reachable from the landing surface and the navigation through the existing generated mechanism, with no hand-written entry
  • Internal links resolve in the built site
Validation
bash test/run.shmajordomus generate --check
Evidence required
docs_generatedlinks_resolvelanding_registered
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docs/DEPLOYMENT.mdsite
Not
Deployment values retyped into proseA hand-written navigation entry or landing cardCurrency prices stated as permanent facts
Depends on
I0903I0913I0924
Priority
p1
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-06
Updated
2026-09-06
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

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

Findings

Nothing is wrong with these records.