// receipts

Receipts from the lab. The methodology gets tested on our own production work first. Everything below is real, shipped, and verifiable end-to-end. Read what you want. Audit the trail. Decide for yourself.

// featured

// portfolio

Solo cross-domain builds the methodology was forged through

Builds across multiple problem spaces, each one tested the methodology under different conditions. Listed below by domain. The methodology evolved through these; the most recent ones express it most fully.

Builds

  • Asphalt detection (computer vision)
  • Paint defect system (computer vision)
  • Autonomous meme coin trader (finance / automation)
  • Autonomous Discords (social automation)
  • Autonomous Twitter (social automation)
  • Smart contracts (Solana)
  • Web scrapers and siteops
  • Rock Bottom (game design, economy systems)
  • vibekoded.com (this site)

// methodology evolution

How SpecMesh emerged through practice

The methodology was learned through practice, across builds, over time. Early builds informed it before it had a name; the friction in those builds is what it was later built to remove. Mid builds are where the patterns coalesced into something repeatable. Recent builds are the full expression. Operator fills in the chronology.