Make claims auditable.
Paths, links, diffs, tests. If it matters, it should be checkable.
AI workflow design, tooling, and evaluation for teams that ship. Public work, documented methods, and working examples on Projects and GitHub.
Paths, links, diffs, tests. If it matters, it should be checkable.
Sycophancy spirals, generation addiction, phantom capability. New traps need new patterns.
If the spec is vibes, the result is vibes.
Confirmation gates and rollback paths beat good intentions after the fact.
Timeboxes and ship/stop signals beat endless polish loops.
Clear evidence, explicit stop points, and rollback paths where the risk is real.
Pick the surface that matches how you want to evaluate the work: inspect artifacts, learn the rules, read the field notes, or study the failure modes.
A quick scan of what is public today, what kind of claim it supports, and where the evidence lives.
May 24, 2026. Talos, Ship Receipts, and Alcove Mirrulations are public, but each one deserves a narrower claim than a full product launch.
Projects, demos, and public repos stay linked when they are ready to inspect. Private tracks stay labeled as private.
The methods are written as repeatable operating rules, with anti-patterns sitting beside them.
Public repos, linked capabilities documents, and build artifacts stay inspectable instead of hand-waved.
Mechanisms, not magic.