The architecture journey — one house, one listener, one queue

The architecture journey — one house, one listener, one queue An architecture diagram generated by Archify. Chat rooms · family · ops · self-hosted · Architecture component Chat rooms family · ops · self-hosted Code forge · PRs · nightly gates · issues · Architecture component Code forge PRs · nightly gates · issues Ember · one listener · router · cards · the house — one server in a cupboard, two workstations, one tailnet · the only writer Ember one listener · router · cards the only writer One queue · requires ⊆ capabilities · the house — one server in a cupboard, two workstations, one tailnet One queue requires ⊆ capabilities Workers · a 16 GB desktop · a laptop · the house — one server in a cupboard, two workstations, one tailnet · one name each Workers a 16 GB desktop · a laptop one name each Ledger · packages · deploys · heartbeats · the house — one server in a cupboard, two workstations, one tailnet Ledger packages · deploys · heartbeats Painter module · resident image model · the house — one server in a cupboard, two workstations, one tailnet Painter module resident image model Forge · comic · game · recipe · Director · engine · the house — one server in a cupboard, two workstations, one tailnet Forge · comic · game recipe · Director · engine Admin console · waits on you · pool · GPU · the house — one server in a cupboard, two workstations, one tailnet · merges on a click Admin console waits on you · pool · GPU merges on a click AI wiki · 312 concepts · 52 conventions · the house — one server in a cupboard, two workstations, one tailnet AI wiki 312 concepts · 52 conventions Human vault · 185 reports · 59 decisions · the house — one server in a cupboard, two workstations, one tailnet Human vault 185 reports · 59 decisions Publish gate · default-deny · scans output · Architecture component Publish gate default-deny · scans output Outside box · tailnet control · garden · Architecture component · rebuilt from code Outside box tailnet control · garden rebuilt from code asks · one reaction tasks by kind capability match image task dev task · GPU job packages · heartbeats cards · verdicts merge ⇄ PRs one contract evidence · reports distilled ⇄ frozen status: published static bytes the house — one server in a cupboard, two workstations, one tailnet Legend Frontend Backend Database Cloud Security Message bus External

Kept

  • • Orchestration in code; a painter behind one contract; a template body with painted faces
  • • One listener, one queue, one name per box, modules with health and advertisement
  • • Two vaults with opposite rules; a default-deny gate that scans the rendered output

Dropped

  • • Control flow inside a node graph; a second account nobody read; three GPU locks
  • • A bare git hub as origin; a second forge outside; six copies of one backup
  • • A twenty-day coordinator session; waits longer than the cache; prose as enforcement

Next

  • • Deploy the merged work and verify it from the box, every repository
  • • Gates in code for every named defect before any A/B; a human anchor for faces
  • • An object store, a lighter chat server, a backup server, a sign-in on every door