Bimaaji: agent-safe mutations for Waaseyaa
Why AI agents modifying a Waaseyaa app need a DSL, an AST-safe patch generator, and sovereignty guardrails, instead of raw file edits.
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.
AI assistants estimate effort using training data from before they existed, then push back when you try to spec faster. Working around it eats hours every week.
A small web game that shows you two short passages — one human, one Claude — and asks you to pick which one is the AI.
Sixty-seven packages, one CI matrix, one PHPStan target. What it takes to actually move the floor.