twimco.Let’s talk ↗︎
Menu

The TWIMCO notebook

Field notes.

Useful observations from inside the work.
For people building a better way.

Antique workshop with an agent-like apprentice observing a master at a bench behind a thin gauze screen; red thread marking a go/no-go gate on a clipboard success card.

Define shadow-mode success before you promote the agent.

Weeks into shadow mode, the agent is still proposing and people are still doing the work. Someone asks if it's time to let it act, and the answer is a shrug. Shadow mode only helps if you decided at the start what would count as ready.

Read the note ↗︎
Antique workshop with labeled change tickets on a pegboard—prompt, tool, permission—red thread tying each to an approver stamp and a rollback drawer.

Treat agent changes like releases—not like prompt doodles.

Someone edits a system prompt on Friday. On Monday the agent does things the team thought were gated, and nobody knows which edit did it or how to put it back. A change to what an agent may do is a release, even when it doesn't look like one.

Read the note ↗︎
Antique atelier with fabric swatches and a true product specimen beside AI print proofs on a review rail, a fidelity scorecard, an approval stamp, and a red thread from specimen to gate.

Score AI product images on fidelity, not polish.

The color is slightly off, the material is one you don't sell, and the image still looks finished. Image tools are good at plausible. Catalog work needs pictures that tell the truth about what you'll actually ship, and someone named to say so.

Read the note ↗︎
Antique atelier desk with a fillable job-spec form, boundary stamps, an escalation bell, a success-evidence ledger, and a red thread tying the form to a waiting mechanical clerk.

Write the agent a job spec, not a vibe.

Agent projects still start with adjectives like helpful and on brand. An agent that takes actions needs a job instead, written plainly enough that you could hand it to a new hire on one page.

Read the note ↗︎
Hands mark a paper permissions ledger while golden labels distinguish MAY ACT from MUST ASK beside keys and an escalation bell.

Give the agent a permission matrix, not a pep talk.

A warm, careful system prompt won't stop an agent from changing a record it should only have read. Write down what it may read, suggest and change, who signs off on the risky step, and what the audit trail has to show.

Read the note ↗︎
A specialist selects evidence from an archive while an assistant carries a vetted folio to a colleague

Is this workflow ready for AI?

Before adding AI to a process, score it on handoffs, exceptions, visible state, recovery and who may approve changes. A readiness checklist you can use as a worksheet.

Read the note ↗︎
An illustrator compares jacket details on model-image proofs with the original garment using a magnifying glass and correction marks.

How to review AI-generated product imagery before it goes live

A polished image can still misrepresent the product. Build a review process around product fidelity, intended use and a clear approval decision.

Read the note ↗︎
An analog sorting instrument with bounded trays and a human approval lever

What it takes to let AI agents operate a real business system

Natural language is the interface. Useful agent operation also needs bounded actions, permissions, visible state, recovery and a way to judge whether the work succeeded.

Read the note ↗︎
A good place to begin.

A familiar problem? Let’s look closer.

Tell us where you want to go. We’ll find the first thing worth changing.

Tell us about it ↗︎