Add ADR-102 and ADR-103 cold-start doctrine

Story 1125Epic None6 files · +607/−0

PR #140 · pramaan-io/pramaan-docs · merged 2026-06-09

Why this matters

Cold start is a factory reset on every container

Why two ADRs, why now

Eager init IS the cold-start problem.

The fix — Lazy at boot, singular at the table.

How it flows

sequenceDiagram
  autonumber
  participant lambda as Lambda
  participant app as App
  participant config as Config
  lambda->>lambda: cold start: kitchen opens, tools ready
  app->>lambda: request: order placed
  lambda->>app: lazy singleton: DB / JWKS / boto3 spin up
  app->>app: per-request: chef preps this order only
  app->>config: 5 waiters → 1 cellar run
  config->>app: canonical menu returns once

Files changed (6)

File±
docs/decisions/adrs/ADR-102-lambda-startup-contract.md ★+207
docs/decisions/adrs/ADR-103-config-screen-bootstrap.md ★+200
docs/decisions/adrs/ADR-REGISTRY.md+2
docs/decisions/adrs/adr-registry.json ★+85
docs/walkthroughs/story-1125-walkthrough.html+56
docs/walkthroughs/story-1126-walkthrough.html+57