maybloomstack

A stack for seasonal software

One contract, many paths, and a system you can tend for decades.

The maybloom stack is a schema-first monorepo framework. Protocol Buffers define every boundary, code generation owns the edges, and people write the three layers in the middle. The backend is TypeScript by default and Go when the workload asks for it; the interface is one Expo app; the public surfaces are static Astro sites.

The maybloom skill tree: the contract at the root with two limbs, servers and clients; validated paths lit green — TypeScript (the default), Expo shipping to iOS, Android and web, Astro for static surfaces; Go amber and validating; kotlin, python and swiftui waiting as dashed open pathsRead the docs

The documents

  1. 1OverviewWhat the maybloom stack is and the principles behind it
  2. 2ContractsThe protobuf layer, Buf toolchain, and proto conventions
  3. 3Backend: TypeScriptThe Fastify + Connect-RPC + Drizzle blueprint
  4. 4Backend: GoThe connect-go + sqlc + goose blueprint, as two services walked it
  5. 5InterfaceThe Expo Router + React Query client blueprint
  6. 6SitesAstro for the public, static surfaces
  7. 7Choosing a runtimeWhen Fastify, when Go, when Astro
  8. 8SkillsHow the stack ships as agent skills
  9. 9DelegationHow work on the stack is split between model tiers, and why
  10. 11Adopting the stackBringing an existing service onto the contract without a rewrite
  11. 12Prior artHow the maybloom stack compares to what exists