Agreed work can stall. With Dotty, our AI assistant, the commitment loop has repeatedly brought reviewable results, corrected “done” claims and clearer next steps. An early signal: stalls remain and people differ. Our fictional enterprise story: youtu.be/3wWZBqmsMt4
She signed off on the weekly cleaning every week. The cleaning had stopped a couple weeks earlier.
@boardyai connected me today with a quality and change consultant who has spent 25+ years in regulated life sciences. She's currently interim quality manager for a food manufacturer implementing GMPs.
She put a new weekly cleaning procedure in place. Every week she signed off that it was done and looked good. She works remotely.
Then she went on site to collect the cleaning documents. They had just stopped.
She says the hardest part of every implementation she runs is regression. Leaders make little exceptions, and eventually everyone goes back to their happy place. Those signals are hard to pick up from a distance.
Her signature was the only part of the process that kept happening every week.
hey @boardyai analyze my profile and tell me the most useful person in your network I should meet next, and why
Check out my latest article: What I heard at Toronto Tech Week: AI is ahead of trust. linkedin.com/pulse/what-i-he… via @LinkedIn
Non-technical founders are being told they can replace a senior engineer with AI and “move faster.” In reality, that’s how you end up shipping bugs, breaking prod, and losing control of what’s actually true in your system.
In this new piece I share a real incident (119,747 restarts in 6 hours) and the Trust Enablement Control Plane (TECP) pattern I now use so AI-driven changes stay observable, reversible, and investor-safe—even if you can’t read the code yourself.
If you’re leading a product without a deep tech background, this is the AI playbook I wish I’d had 👇
Replacing a Senior Engineer with AI: Possible, Getting Easier, Still Dangerous linkedin.com/pulse/replacing…
Voluntary AI codes don't fail because the people writing them lack integrity.
They fail because competitive pressure selects against them.
If following the framework costs you a deal, the framework loses.
That's not a values problem. It's a market structure problem.
Enforceable evidence standards are the only mechanism that survives.
The argument for AI restriction: fewer AI systems = less risk.
The problem: restriction concentrates AI power in the hands of the few who ignore it.
The sustainable path: governed proliferation.
More AI at the edges. Better governed. Verifiable controls. Human agency preserved.
Not less AI. Less ungoverned AI.
These aren't exotic requirements.
Authorization tickets, execution receipts, immutable ledgers, delegation records — established engineering patterns.
Making them mandatory at the execution boundary, not optional afterthoughts.
Full paper: linkedin.com/pulse/governed-…
6/ How can a person contest the outcome?
If there's no answer to this one, the other five don't matter. Accountability without recourse is theater.
5/ What changed in the real world?
Not just what the system logged. What actually happened to people, data, decisions, or obligations?
4/ What did a human review, approve, reject, or delegate?
If the answer is "nothing" — that's a governance failure, not a feature.
2/ What action was taken?
Not "what was the AI asked to do." What did it actually execute? The gap between instruction and execution is where accountability disappears.
