Public work example
A planning record that makes AI challenge and human judgment visible
This public library makes sanitized planning easier to browse: proposals, deliberate AI counterproposals, roadmaps, wireframes, and implementation checkpoints remain connected to the decisions that shaped them.
It includes a hypothetical client portal and governed automation planning. These are decision-making artifacts, not client work or claims of business results. AI can challenge a proposal; Todd retains final decision authority.
What the record demonstrates
A useful challenge still needs accountable decisions.
- 01
Initial proposal
The record begins with a plan for a hypothetical client portal. It makes assumptions and tradeoffs visible before anyone treats them as a build commitment.
- 02
AI counterproposal
An AI-generated counterproposal deliberately challenges the initial direction. Its value is in surfacing questions and alternatives, not in deciding what should happen.
- 03
Human evaluation and revision
Todd's follow-up questions and decisions lead to a revised direction: Vercel and Supabase, Stripe for payments, an external signature service, and a JSON:API integration boundary.
Decision history, not a finished product
Keep the reasoning available when the direction changes.
The repository preserves superseded plans as decision history. That lets a reviewer see what changed, why alternatives were considered, and where a person made the call.
It includes public information only. The record does not describe a completed client engagement, a finalized cost estimate, or a product ready for implementation.
Have a workflow worth exploring?
Bring one real process, and we can discuss whether AI is a reasonable fit and what a sensible first step could be.