FIELD NOTE / TIKTOK
Who fixes this after its builder leaves?
The short film, the complete written thought, and the evidence behind it.
The TikTok conversation link will follow its public release.
Who fixes this after its builder leaves?
Video caption
Who fixes this after its builder leaves? The organization inherits the tool, not the prompt session. A tool without an owner is already a liability. Narration uses Eric's authorized AI voice clone. #EricFieldNotes
Full written post / accessibility read
A teammate has made a convincing internal approval app with an AI coding agent. Before launching it, ask who patches a policy change, who supports a new hire, and how customer data leaves the system when you retire it.
If each answer is, we can ask the AI later, there is no owner for behavior now. A future agent can edit files, but it may not know which old exceptions are contractual, which state is authoritative or what cannot be broken.
In a disposable fixture, have somebody other than the builder change one approval rule, recover a failed notification and export a customer's history. Record where they need an undocumented guess. That is a more useful launch test than another happy-path demo.
Require a person accountable for policy, support, recovery and retirement. If that commitment is larger than the value of replacing a maintained SaaS tool, stop the clone. Do that because the company, not the agent, owns the product after the session ends.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Four-beat scene transcript
1. Who fixes this after its builder leaves?
A teammate has made a convincing internal approval app with an AI coding agent. Before launching it, ask who patches a policy change, who supports a new hire, and how customer data leaves the system when you retire it.
Visual: The demo cannot answer an operating question.
2. A vague answer is a real cost.
If each answer is, we can ask the AI later, there is no owner for behavior now. A future agent can edit files, but it may not know which old exceptions are contractual, which state is authoritative or what cannot be broken.
Visual: The organization inherits the tool, not the prompt session.
3. Run a small departure drill.
In a disposable fixture, have somebody other than the builder change one approval rule, recover a failed notification and export a customer's history. Record where they need an undocumented guess. That is a more useful launch test than another happy-path demo.
Visual: Use a protected case and a different operator.
4. Name the maintainer before launch.
Require a person accountable for policy, support, recovery and retirement. If that commitment is larger than the value of replacing a maintained SaaS tool, stop the clone. Do that because the company, not the agent, owns the product after the session ends.
Visual: A tool without an owner is already a liability.
Research and claim limits
- GitHub Copilot Agents application card (S226)
- NIST AI RMF Core (S227)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.