The method, in the open
Most people use AI like a search engine with better manners.
The result is generic output and wasted hours. The fix is not a magic phrase. It is the discipline of making the reasoning explicit before the answer arrives — the same discipline that gets a good result out of a shift.
Eight steps, in order, every time. The same steps plan a project, write an SOP, and build a warehouse operating layer.
- 0Define the tools
Name what will actually be needed before anyone starts typing.
- 1Restate the goal
Say the objective back in your own words. If you can't, you don't have it yet.
- 2Find the missing information
Write down what you still need — the step most people skip, then blame the tool for.
- 3Make assumptions explicit
Every assumption on the table, in the open, so it can be argued with.
- 4Break it into sub-steps
The smallest logical pieces. Not a wish list — an order of operations.
- 5Walk the reasoning
Move through it in the open, so a wrong turn is visible while it is still cheap.
- 6Deliver the answer
The thing you asked for, in a form you can actually use.
- 7Self-critique
Name the weakest part and improve it. This is the step that makes the next one better.
When seven steps aren't enough
- Tree-of-Thoughts — Explore several routes, critique them, then pick or combine the best.
- ReAct — Reason, act, observe, repeat — for work that needs real information.
- Self-Consistency — Several independent answers, then keep what they agree on.
- Meta-Prompting — Have the system critique and rewrite its own instructions first.
When one agent isn't enough
- Researcher + Critic + Synthesizer — Gather, challenge, integrate.
- Planner + Executor + Verifier — Break down, execute, validate.
- Debate — Two sides argue, a judge decides.
- Hierarchical — A manager routes work to specialists, then pulls it back together.
The receipts
Three things you can open right now. Nothing here is a promise about what the method could do.
The Architects Playbook vol. 3: Stop prompting — Start architecting
Matt Lane · ISBN 9798192702451 · published on Amazon and other major retailers worldwide
The full method: the eight steps, the advanced patterns, the multi-agent structures, and how to choose between them. Written for people who have a job to do, not for prompt hobbyists.
A step-by-step breakdown of the method actually running
Not a result with the working erased. The proof engine shows the reasoning end to end — the restatement, the assumptions, the chain walk, the critique — so you can judge the process instead of taking the output on faith. There is no public link for it yet; ask and it comes by email. The same loop runs live inside the demo, on a real count variance.
The workbench that turns the playbook into an execution engine
An interactive decision workbench implementing playbook v3 — the framework as a tool you run instead of a document you read. Pick a decision, work the steps, get a structured result you can hand to someone else.
Where it came from
Ten-plus years managing warehouse and fleet operations is the same problem as getting good work out of an AI system, wearing different boots: you have a goal, incomplete information, unspoken assumptions, and a crew that will do exactly what you actually said instead of what you meant.
Getting a good result out of a shift and getting a good result out of a model both come down to structure, explicit assumptions, and honest feedback. The playbook was written from a supervisor's desk, and Fenyx was built with it.
What the method built
The point of listing these is not a portfolio. It is that the method produced working software, not slideware.
Captures raw tribal floor notes, extracts structured accuracy rules, tracks exceptions against those rules, prices every miss, and drafts the SOP the next shift can run. Built to a mid-market DC's reality: 2-inch carbon steel fittings, heat-treat stamps, slot drift on the grave shift. It sits beside the WMS and never posts an adjustment.
If you want the method installed into something real instead of read about, start with the demo and then send mail. A pilot is two weeks at one site.
Retailer links may earn a small commission at no cost to you. Demo data is fictional and Westline DC is not a real customer. Fenyx is not affiliated with any past employer.