Two months of senior engineering in 36 AI-assisted hours
A 36-hour window where an autonomous session opened a stack of PRs and the rest of the time went to landing them cleanly.
A 36-hour window where an autonomous session opened a stack of PRs and the rest of the time went to landing them cleanly.
How Anokii went from one monolithic repo with duplicate identity code to three composable Composer packages, published by a governed CI split instead of a manual release process.
How this blog’s GitHub Actions workflow mines activity, drafts posts with Claude, and publishes with zero human review.
Why AI agents modifying a Waaseyaa app need a DSL, an AST-safe patch generator, and sovereignty guardrails, instead of raw file edits.
How an Elder’s whiteboard video becomes a searchable Anishinaabemowin lesson, on infrastructure the community owns end to end.
Why I automated my own content pipeline, what it costs, and how developers can share their work without adding to the AI slop.
How Waaseyaa serves the same content as a web page for people and clean Markdown for AI agents from a single URL, using HTTP content negotiation.
Six moves that take a vibe-coded prototype to a state where it can be run, debugged, and handed off.
A small detail from a Boris Cherny interview points at a bigger story than the one the headlines told.
How the waaseyaa/agent-output package shrinks PHPUnit, PHPStan, and bin/check-* output to compact NDJSON envelopes so AI agents do not drown their context window in CI noise.