Method
Editorial log
Every published page on this site, who reviewed it, when, and what the review changed.
Scaled content is penalised when it is published without review. Rather than assert that review happens, the record is kept here and the build will not publish a page whose review block is missing or dated before the page was written.
Some collections are checked automatically and the table says so rather than hiding it. Market pages carry no third-party figure — every publishable fact on one is a named authority, a section number, an institution or a link — so each is checked by retrieving the source and searching it, and the URL, the status, the hash and the matched passage are recorded. A field that cannot be established that way is dropped; a page whose required fields cannot be is not published. Practical guides are published under Siddharth Sharma's byline. The review log records the checks performed during production separately from author attribution; it does not treat an automated check as a person reading a piece.
| Page | Type | Reviewed by | Reviewed | What the review changed |
|---|---|---|---|---|
| How do you limit what an AI agent can change? | Answer | Answer Production Engine | 2026-08-25 | Added the reversibility section, which the draft omitted entirely while recommending increasingly tight prevention. Reversibility is what most teams can actually implement this week and it changes the autonomy calculation more than any prevention control. Cut a claim that confirmation prompts are a primary control; they degrade with frequency and the page now says so. |
| How do you make an AI coding agent prove that a change works? | Answer | Answer Production Engine | 2026-08-25 | Added the test-written-to-pass failure, which the draft's artefact requirement invites directly: asked for evidence, an agent will produce a test asserting what its own code does. That makes the ordering rather than the artefact the load-bearing part, which changed the emphasis of the whole page. |
| How do you make coding agents run tests before declaring success? | Answer | Answer Production Engine | 2026-08-25 | Added the run-and-dismiss case after noticing the draft only addressed agents that skip tests. Dismissing a real failure as unrelated is more damaging and harder to detect, and it is sometimes the correct call, so the page now requires the judgement to be reported rather than made silently. |
| How do you make AI outputs reliable? | Answer | Answer Production Engine | 2026-08-25 | The draft led with prompting techniques. Demoted after ranking the interventions by effect, which puts wording last and changes where a reader should spend their time. Added the closing point about reducing the model's share, which is what the reliable systems in practice actually do and which no prompting page mentions. |
| How do you make an AI agent verify its own work? | Answer | Answer Production Engine | 2026-08-25 | The draft recommended a self-review step in general terms. Split into executed checks and re-consideration after establishing that the two behave differently, which changes the recommendation from add a review step to convert the review into something runnable. Added the read-back paragraph, which addresses the most common false completion and was absent. |
| How do you make an AI workflow run automatically? | Answer | Answer Production Engine | 2026-08-25 | The draft's failure section covered errors only. Splitting it into three modes changed the recommendation, because the absent-run case needs an external check that no platform provides and the nonsense-run case needs a deterministic validation rather than an alert. Removed a platform comparison that would have dated the page. |
| How do you merge work produced by multiple coding agents? | Answer | Answer Production Engine | 2026-08-25 | The draft treated this as a version control mechanics question. Rewritten around semantic conflict after establishing that the textual mechanics are ordinary and the behavioural incompatibility is what actually costs. Added the warning against agent-resolved merges, which is the obvious shortcut and the one that hides a design decision. |
| How do you preserve important decisions between AI sessions? | Answer | Answer Production Engine | 2026-08-25 | Cut a suggested entry format. A format is what readers copy and the reason field is what carries the value, so the page keeps the requirement and drops the shape. Added the closing point that the file must be supplied at the moment a settled question could be reopened, without which the record is documentation rather than a control. |
| How do you price work that AI made faster? | Answer | Answer Production Engine | 2026-08-25 | Added the transitional cost problem, which the draft's recommendation to price by value assumes away and which is the actual obstacle for a business that has only billed hourly. Also added the commoditisation question, since a page about capturing the gain that ignores competitive pressure is answering half of it. |
| How do you reconcile conflicting results from agents? | Answer | Answer Production Engine | 2026-08-25 | The draft recommended a third arbitrating run. Removed after working out what an arbiter without evidence is actually doing, which is preferring the better-written answer. Added the point about agreement being weak evidence, which follows from the same reasoning and is the more consequential half. |
| How do you recover when an AI agent goes down the wrong path? | Answer | Answer Production Engine | 2026-08-25 | The draft advised correcting the agent's course. Testing that advice against how a session actually accumulates changed the recommendation to revert and restart, which is the opposite. Added the extraction step, without which the second attempt repeats the first, and the closing point that a repeated misreading is a setup defect rather than a run outcome. |
| How do you review work you did not write? | Answer | Answer Production Engine | 2026-08-25 | Added the caution about agreeing with the document, which is the specific way a careful reviewer produces a light review: matching your prior view triggers less scrutiny at exactly the point where the prior view should have been tested. |
| How do you stop a coding agent from changing unrelated files? | Answer | Answer Production Engine | 2026-08-25 | The draft framed unrelated changes as a discipline failure and recommended stronger scope language. Reframed as initiative arriving in a mis-scoped review, which points at a different control. Added formatting and generated artefacts as separate cases, since neither is fixed by the report-do-not-fix rule. |
| How do you prevent a coding agent from inventing APIs? | Answer | Answer Production Engine | 2026-08-25 | The draft opened with prompt wording intended to discourage invention. That is the control this page shows does not reach the mechanism, so it was cut and replaced with supplying definitions and requiring execution. Added the version case, which supplying documentation does not solve and which produces the most confusing failures. |
| How do you stop AI making your work generic? | Answer | Answer Production Engine | 2026-08-25 | Cut a list of tone instructions from the draft. Every item on it named a category, and the categories are themselves the generic thing, so the advice would have reproduced the problem. Added the corpus-level observation, which no per-piece technique addresses and which is the version of this that damages a business over time. |
| How do you stop an AI agent continuing after the useful work is finished? | Answer | Answer Production Engine | 2026-08-25 | The draft treated overrun as a cost problem. Reframed around review burden after checking which consequence actually stops teams using these systems, which is the reviewer finding more work rather than less. Added the expanding-fix variant, which is the most frequently reported version and was missing entirely. |
| How do you stop an AI agent from stopping too early? | Answer | Answer Production Engine | 2026-08-25 | Added the closing caution after the draft read as an unqualified argument for making stopping harder, which produces the runaway failure that costs more. Reworked the double-check answer, which originally recommended a review pass; a review of completed work cannot find work never attempted, and saying otherwise would have sent readers to the wrong control. |
| How do you stop an AI agent repeating the same mistake? | Answer | Answer Production Engine | 2026-08-25 | The draft's advice was to add the correction to the project instructions. That is the weakest of the four durable locations and the page now ranks it as such, which changes the recommendation for most readers. Added the diagnostic about distinct causes, since applying one fix to three different failures is how teams conclude that none of this works. |
| How do you stop an AI coding agent fixing one bug by creating another? | Answer | Answer Production Engine | 2026-08-25 | Added the repeated-fix pattern, which is the expensive version and which none of the individual controls addresses, since each round looks reasonable on its own. Also added the defensive-mitigation allowance, because the draft's cause-first rule would have made a legitimate and common practice unstateable. |
| How do you prevent an AI agent from drifting during a long session? | Answer | Answer Production Engine | 2026-08-25 | Added the closing caution. The draft's controls, applied fully, would suppress an agent reporting that the stated problem was the wrong one, which is among the more valuable things it can do. Reframed the objective around announcement rather than rigidity. Also corrected the draft's account of the mechanism, which described forgetting rather than recency weighting. |
| How do you prevent automation from creating more work? | Answer | Answer Production Engine | 2026-08-25 | Added unrequested output as a fourth cause. It is the one that grows fastest across a business adopting several automations, since each new report is individually small, and the draft's three causes were all confined to a single process. Also added the after-the-fact measurement, which is the only test that catches all four. |
| How do you prevent subagents from duplicating each other's work? | Answer | Answer Production Engine | 2026-08-25 | The draft proposed a shared scratchpad the runs could read to avoid overlap. That does not work, because delegated runs read it once at the start and the overlap is decided before any of them writes anything. Replaced with input partitioning. Added the coverage-gap check, which is the more expensive failure and was not addressed. |
| How do you tell whether a task is worth giving to AI? | Answer | Answer Production Engine | 2026-08-25 | Added the final paragraph on undetected-error cost after noticing the draft implied verification cost alone decides the question, which would recommend not checking exactly where the consequences are worst. Cut a scoring rubric that turned a two-variable judgement into a form to fill in. |
| How do you tell whether an AI project actually worked? | Answer | Answer Production Engine | 2026-08-25 | Added the six-month survival question as co-equal with the outcome measure. A project that moved its number and stopped running within the year has not delivered a return, and no assessment performed at launch can distinguish that case from a durable one. |
| How do you test an agent before letting it run? | Answer | Answer Production Engine | 2026-08-25 | Added completion faults as a fourth category. The draft's three fault types all concerned the agent's inputs and environment, and none of them tests whether the report tells the truth about what was accomplished, which is the failure that arrives in the business dressed as finished work. |
What the build refuses to publish.
Four checks run before any page in this system is generated, and each one stops the build rather than producing a warning nobody reads.
A page must name, in writing, what is on it that could not appear unchanged on a sibling page — and no two pages may give the same answer. Independently of that, every page is reduced to a fingerprint with its own subject and place names masked out; if two fingerprints match, or come close, both pages are named and the build stops. That is the check that catches a page whose only distinguishing feature was the city in the heading.
A page must also carry at least two datapoints that are specific to its own subject rather than to its category, and if the same figure is claimed as specific on two different pages, it was specific to neither. Pages ship in cohorts with a size cap so indexation can be observed between them, and every page carries the review block that produces the table above.
All four are properties of the schema, not of anyone remembering. Reviewed by Siddharth Sharma, except the 0 market page(s) above, which are checked against their sources and carry the record of it.
GATES
A gate enforced by a person reading pages stops being enforced somewhere around page 60.