Why Codex Should Be a Worker, Not the Scheduler
Explains why Codex and similar AI coding tools should remain bounded workers, not long-running schedulers or release controllers.
github-issues
7 public items tagged github-issues.
Evidence Gate: Why AI Pull Requests Need Evidence Bundles
Explains why AI pull requests should include reviewable evidence bundles, not just code changes and a claim that tests pass.
Use Labels, Branches, and Comments as an AI Engineering State Machine
Shows how GitHub labels, branches, and comments can become an AI engineering state machine that keeps issue repair work observable and controllable.
An Issue Is Not a Todo: It Should Be an Executable Contract for AI
Argues that an issue should be an executable contract for AI work, with scope, context, gates, evidence, and release boundaries instead of a loose todo.
Open-Sourcing an Issue-Driven Agent Workbench
Explains how to safely extract public methodology, templates, and toy examples from private production AI workflow experience.
PR Merged Is Not Done: The Release Boundary in AI Engineering
Explains why a merged PR is not the end of AI engineering work; release verification, rollout checks, and post-merge evidence still define done.
From Triage to Implementation: Why AI Fixes Need Gates
Explains why AI repair work should move through triage, analysis, implementation, evidence, and review gates instead of jumping straight to code.