One-prompt build · 2026-10-23
1am Postmortem
Paste this into a new Shogo project and watch it build.
Build this page in this project. It is a single screen that will be screen-recorded at phone width (390px) and at desktop width, so it must look finished at both. Ship it running in the preview, then reply with the preview URL and how many minutes it took.
Build a single-page incident postmortem. Dark UI, near-black background, one column, monospace for labels, big type for the closing line.
**Hero**
- small mono label: `INCIDENT · six agents · one morning`
- H1: `Every agent stopped mid-task`
- one line under it: `Only the beats we can verify. No clock times, no invented numbers.`
**Timeline** — five rows, in this order, each with a short label on the left and one sentence on the right.
No timestamps anywhere.
1. `The wake` — An agent starts a run on a schedule, the way it does every night.
2. `Mid-task stop` — The process is killed underneath the run. The card it was working on stays in progress.
3. `Second surface` — The same behaviour does not happen on the desktop app.
4. `One variable` — The two surfaces disagreed about one environment variable.
5. `Same morning` — One change, and the runs complete. The cards move again.
**Root cause** — a single line, large:
`Desktop and cloud disagreed about one environment variable.`
**What held** — three items, each with a check:
- `The board showed the stall.`
- `No card was marked done.`
- `The same-morning fix was one variable.`
**Closing block** — the biggest type on the page:
`one environment variable · six agents · one morning`
Under it, small: `nothing was lost, because nothing was marked done.`
**Footer chip**: `built in Shogo from one prompt`
Rules: no charts, no fake metrics, no invented timelines, no uptime percentage. One screen; the hero and
the first three timeline rows must be visible without scrolling at 390px. Keep the type big and the page
calm. Do not add anything that is not listed here.Want it as a guided course with a coach?Agent Team Playbook