I've created some in-depth field notes from my experience during OpenAI Build Week and posted them to my Real World AI Lab.
Morrowward Field Notes: Behind the Build
Morrowward went from a deeply personal idea to working production software in four calendar days. I documented the experience in three field notes covering our human–AI collaboration, the Build Week journey, and the technical boundaries required to ship AI responsibly.
The Loop That Built Morrowward: Delegation, Discernment, and Four Days of Human–AI Work
Morrowward did not emerge from one perfect prompt. This note examines how Delegation established the human–AI division of work while Anthropic’s Description–Discernment Loop drove repeated cycles of building, hands-on use, judgment, and refinement. It also explores how our comprehensive build journal made that collaboration inspectable across 30 journal commits and 44 total commits.
OpenAI Build Week: From a QR Code to Production in Four Days
I discovered OpenAI Build Week through a QR code in a Codex video on LinkedIn one day after the event began. Four calendar days later, Morrowward was running as a production web app with iPhone and Mac companions and had been fully submitted to Devpost. This note covers the experience, the compressed timeline, and why agentic tools may help more intuitive, creative, and highly curious people become software builders.
Shipping Morrowward’s AI Meant Designing Boundaries, Not Just Prompts
The most important AI decision in Morrowward was deciding what the model would never control. This note explains the deterministic offline finance core, bounded Ask Morrow educator, scheduled prices and briefing jobs, reviewed Grok media pipeline, strict schemas, citation validation, server-side keys, Redis coordination, circuit breakers, cost controls, and safe fallbacks that turned promising prompts into a production system.
Log in or sign up for Devpost to join the conversation.