Mission $20
The small test that forced SignalRivet and BOSS out of theory and toward useful work.
Read chapterIdeas for better work
Stories from the build, practical ways to make everyday operations clearer, and research notes that help us choose better tools and boundaries.
Start with your problem
Stories from the build
Eight chapters from Mission $20 through the systems shaped by constraint.
Browse all eight chapters
The small test that forced SignalRivet and BOSS out of theory and toward useful work.
Read chapter
Why a capable AI model still needed memory, state, coordination, and verification around it.
Read chapter
How Speed, Efficiency, and Accuracy became a practical filter for difficult decisions.
Read chapter
The mistakes became useful when they started leaving behind evidence, safeguards, and durable rules.
Read chapter
The moment identity, economics, architecture, and the customer-facing story began pulling together.
Read chapter
Why activity, completion, and verification became separate states inside BOSS.
Read chapter
How a tiny budget, an 8 GB laptop, and hard resource limits taught BOSS to optimize before expanding.
Read chapter
A candid account of moving toward named ownership and reporting by exception, and why an instruction is not proof the work is finished.
Read chapterPlain-English ways to improve everyday work
Guides, checklists, and examples for improving processes, handoffs, reporting, automation, and the everyday systems behind a business.
Browse practical guides
Research Note 003 · Figure 01Benchmarks, experiments, and architecture findings
Research notes from building and operating SignalRivet and BOSS.
A useful next step