Skip to content

I0926 — The deployment documentation is generated and reachable

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.

BLOCKED wave 4 · p1 · implementation profile · parallel safe

Part of fly-deployment — A deployment is a projection of the repository model, and a reachable URL is its evidence.

Blocked. This issue cannot start until I0903, I0913, I0924 are done. The status is derived from that, not declared.

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.

Current state

The site is generated from the registry and the documentation index. No deployment page exists and no navigation entry points at one.

Desired state

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.

Scope

  • docs/DEPLOYMENT.md
  • site

Out of scope

  • Deployment values retyped into prose
  • A hand-written navigation entry or landing card
  • Currency prices stated as permanent facts

Dependencies

What waits on this

Acceptance criteria

  • 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.sh
  • majordomus generate --check

Evidence required

  • docs_generated
  • links_resolve
  • landing_registered

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Risk

Troubleshooting written before anything has failed is fiction. It is filled from the failures the implementation actually hits.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I0926.yaml. Read it back with majordomus plan show I0926.