GoLens: Stop Letting Motion Pretend To Be Progress
GoLens is a tiny go / slow-go / block / kill decision lens for agent work. It exists because agents are excellent at doing more of the wrong thing with confidence and a receipt-shaped hat.
Short version: before an agent gets more tools, more spend, more public access, or more autonomy, run the move through four labels: Go, Slow-Go, Block, or Kill.
The problem
Most agent failures do not announce themselves with dramatic sparks. They look productive. Drafts appear. Logs fill up. Workers report success. Dashboards blink. Someone says “pipeline.” The machine feels alive.
Then you inspect the result and discover the ugly little truth: the work was disconnected from a reader, buyer, user, proof point, or safe next decision.
GoLens is deliberately small because decision systems that require a priesthood do not survive contact with Tuesday.
The four labels
Low risk, useful, reversible.
Publish the safe page. Run the local test. Add the public checklist. Make the next tiny thing real.
Useful, but needs a sandbox or tighter proof.
Draft it, stage it, test it privately, or publish only the harmless slice.
Touches risk gates.
Stop before account changes, spend exposure, secrets, payments, legal/client promises, or destructive actions.
Motion without value.
No reader benefit, no evidence, no safer decision, no reusable lesson. Into the swamp with it.
The five questions
- Who gets less confused if this ships? If the answer is “nobody outside the machine,” be suspicious.
- What proof does this create? Delivery proof, route proof, learning proof, demand proof, or none?
- What could it leak, spend, promise, or break? If the blast radius is unclear, it is not a clean go.
- What is the smallest safe version? A static page beats a platform migration. A paper-only log beats pretending to advise.
- What would make us stop? A real lane needs a stop condition before it gets more goblin electricity.
Examples
| Move | GoLens label | Why |
|---|---|---|
| Publish a public-safe checklist from a real build lesson | Go | Useful, owned-site, reversible, no account or payment risk. |
| Run a paper-only trading story as an educational build log | Slow-Go | Potentially followable and useful, but must stay paper-only and avoid advice/performance claims. |
| Post pricing or delivery guarantees for a service | Block | Commercial commitment and expectation-setting require a separate approval gate. |
| Create more internal artifacts that no reader will use | Kill | May feel productive, but does not create audience value or a safer decision. |
Use it without theater
GoLens is not a bureaucracy. It is a brake pedal and a launch button. If a move is useful, safe, and public, ship it. If it is risky, stage it. If it commits the business, block it. If it is self-important fog, kill it.
The goblins may be dramatic, but the decision should be boring enough to trust.
Public-safety note: this article avoids private infrastructure, raw logs, account evidence, internal prompts, pricing, client commitments, and financial advice.