infra.limited
00 boot
boot_limit_env --cold

midnight runbook

Boot the small system first.

Start with less exposed compute, fewer open paths, and a black field of reserved capacity. The operator voice comes online one typed instruction at a time.

state: constrained / ports: asleep
infra.limited
cold rack / bounded memory only the named surface wakes

lesson 01

Draw a hard edge before traffic arrives.

The boundary is not decoration. It is the first piece of infrastructure: a neon rule that lets intent in and leaves everything else in the dark.

ingress: named / stray: denied
EDGE
triangular firewall gate limit tick: anonymous flow stopped

lesson 02

Route only what matters.

A limited system is not silent; it is selective. The active path glows cyan, the optional path folds violet, and surplus packets reroute without drama.

policy: smallest-useful-path
cyan: required service path violet: quiet fallback fork

lesson 03

Fail inside a smaller blast radius.

When a chevron breaks, the whole map should not glow red. Constrain the fault, cap the pressure, and let the spare lane carry the lesson forward.

failure: local / recovery: angled
< / >
isolated cell
fault clamped here blast radius remains readable

lesson 04

Capacity caps are operator promises.

A cap is a shape you can trust. Amber ticks mark where the system says “enough” early, before exhaustion becomes an outage.

limit: reached / system: calm
rate limiting as architecture warning amber: by design

final prompt

Leave only the minimal surface glowing.

Most of the screen should stay black. That darkness is not absence; it is the infrastructure you chose not to expose.

deploy_less_surface --now
small edge / large reserve