Angry Letters
Started May 2025
angryletters.us
Problem
Ship a full SaaS (payments, creator programs, admin, AI-assisted content) as a solo founder with limited bandwidth. Need a Cursor-centric operating model that stays maintainable.
Stack
Product: live SaaS stack (payments, email, etc.). OAIS: separate repo (angry-letters-oais), Cursor-centric, its own context and documentation structure.
Operating system used
Cursor-centric workflow; context and docs separate from the matthewheyman.com OAIS. Built and shipped as an experiment in a different operating model.
Documentation structure
OAIS lives in angry-letters-oais (oais/ folder). README, INSTALL, and agent/context docs in that repo.
Lessons learned
Separate OAIS per product keeps context clean. Solo build benefits from a single, opinionated workflow rather than a one-size-fits-all system.
Reusable assets
Clone or download the OAIS repo; drop oais/ into your project. See INSTALL in the repo.
matthewheyman.com
Started February 2026
matthewheyman.com
Problem
Run a credible primary site and a Labs surface with one OAIS that can bootstrap new products and support multi-feature execution with human gates.
Stack
Static site (HTML/CSS). OAIS in repo (oais/); published separately at matthew-heyman-oais for clone/download.
Operating system used
Canonical index, lifecycle workflows, bootstrap mode, Tier A/B/C authority. Emphasizes human-in-the-loop alignment gates and convergence over speed and blind AI trust. Tool-agnostic.
Documentation structure
OAIS in matthew-heyman-oais. Documentation and agents live in the repo; drop oais/ into another product.
Lessons learned
Stage and gate guardrails (validate preceding stage, no implementation before Alignment sign-off, clarification-seeking) reduce agent drift. Portable oais/ folder keeps product and OS separate.
Reusable assets
Clone or download matthew-heyman-oais; copy oais/ into your project root. See oais/INSTALL.md.