Department 5

Engineering

19 documents

• 5.1ArchitectureServices, web and worker roles, queue, leases, storage, diagramOne Node codebase, two production services, and exactly one paid background workerDraft
• 5.2Codebase mapEvery top-level module, what it owns, its testsEvery module on origin/main, with who owns what and what tests itDraft
• 5.3Data modelPostgres tables, doc parts, bucket mirror, what lives whereEverything lives in Postgres rows, with only binaries left in the bucketDraft
• 5.4EnvironmentsProduction, staging, demo, local; who uses each; what moves between themFour places Brew runs, and each brand has exactly one homeDraft
• 5.5The readStages in order, what each reads, healing, versionsA pasted store address becomes a sourced profile in seven stagesDraft
• 5.6Plays engineSpecs, the first ten, rewrites, caps, cadence familiesPlays are written from the brief and ledger, then fact checkedDraft
• 5.7Cards and the feedGeneration, ranking, rings, tuningCards come from seven sources and are fact checked firstDraft
• 5.8The jam and StudioRemix, engines, make, checks, finals, versionsA jam turns a card into finished work, never paying twiceDraft
• 5.9Briefs and hand-offTeam brief, jam brief, hand-off page, recipients, send routesEvery jam ends in a brief someone else can work fromDraft
• 5.10ConnectorsEach account, scopes, refresh, protected connectionsRead only connectors on a fixed cadence, with Arata's protected in codeDraft
• 5.11Learnings and memoryBrand memory, learnings, taste, tuning, Brand BookFive memory layers teach Brew more about each store weeklyDraft
• 5.12Testing and QAThe suite, honesty tests, layout audit, QA roundsOne free test suite guards every deploy, and audits check every brandDraft
• 5.13Release and promoteDeploy, promote, the clean gate, rollbackStaging ships any time, production only through one guarded promote scriptDraft
• 5.14Parallel sessionsWorktrees, staging only your own lines, deploying from a clean treeSessions edit brew in parallel, so each ships only its own linesDraft
• 5.15Decision recordsOne per big technical callBig technical calls written down, so nobody re-decides without new factsDraft
• 5.16Tech debtKnown debt, its risk, the fixKnown debt, ranked by risk, with the riskiest paid firstDraft
• 5.17ChangelogWhat shipped, by date884 changes since 12 October, newest first, straight from gitGenerated
• 5.18Engineering rulesEvery brand, heal saved data, errors never shown as zero, dummies markedThe rules every change follows, each one earned by a past hurtDraft
• 5.19Performance and reliabilityPage speed, load test results, caches, timeouts, what we promise on uptimeFast today, with no written uptime promise to partners yetDraft