Observe
Read permitted state and source material.
A throwaway experiment should not carry commercial process. Customer money, private data, valuable work and physical safety change the required evidence.
Most of this factory is agents reasoning. MP is the human principal and the final authority, but not the default planner, memory store, specification writer or decision engine. An agent that brings MP a choice between two defensible options has handed back work it should have finished.
What genuinely needs MP is a capability an agent does not have: taste, physical hardware, money, credentials, external accounts, legal judgement, an irreversible action, or a gate this factory has deliberately reserved. Everything else is the agent's work, carried to completion and shown rather than proposed.
The factory can compose software with a payment provider, a printer, a manufacturer, a contractor or a person doing work that software cannot. MAX makes the boundary obvious: a working PWA is not a real walker. The hardware, mounting, microphone, speaker, lights and the person's ability to use FIND still need physical proof.
The same route could take approved artwork to a poster, shirt or book through a fulfilment provider such as Printful. Agents can prepare the files, product details and order workflow. A provider makes and ships the object. The factory records what happened and what still needs a person to check.
An eligible event could ask an AI system to draft artwork, copy, a diagram or a product variant. That output stays a candidate. Check the brief, rights, visual quality, print dimensions and cost, then ask Dean to approve, return or reject it before it becomes a listing.
Before work crosses that boundary, confirm that it is legal, the assets may be used, the provider is authorised, the budget is available, the result is safe and the outcome can be verified. If any of those answers is missing, stop at a proposal.
A milestone, failed check, shipment event or scheduled review can ask an agent to prepare the next change. Production access starts read-only.
Scheduled improvement works the same way. A check can spot an old dependency, stale screenshot, broken journey or drifting document. It creates a proposal or work item. It does not silently edit or deploy production.
Project value sets the amount of process. A throwaway experiment stays cheap to change. Customer money, promises, private data, hard-to-replace work or physical safety add controls when a project earns them. A repository count or an AI-generated market estimate does not make something a company. Record actual customers, revenue, use, replacement cost, creative value and operating risk separately.
A browser redirect cannot settle an order. Payment state comes from the payment provider, then a durable workflow records the fulfilment that follows.
A commercial pipeline can automate orders inside limits Dean approved in advance. A new product, unusual amount, refund, supplier purchase or other exception waits for a decision. The approval is durable and records whether Dean approved it, returned it with notes or rejected it.
Validate events, make handlers idempotent and keep an order ledger. A retry must not charge twice, buy two shirts, send duplicate refunds or tell a customer that an unshipped order shipped. Payment details stay with the payment provider; Woodhouse's order record needs the provider's event and transaction references, not card numbers.
Technical references: Stripe payment events · Stripe idempotency · Printful orders and webhooks · Cloudflare human approval workflows · Cloudflare scheduled agent tasks.
Scope: Woodhouse publishes these rules. This release does not process payments, call Printful, schedule agent work or write to production.
Agents can collect production evidence and prepare a change. Before a consequential action, the change needs a reviewable diff, a reason, qualification and a rollback path. The approval is tied to that exact candidate and cannot be skipped by asking again in chat.
Read permitted state and source material.
Explain what changed and what remains uncertain.
Produce a reviewable change with evidence and rollback.
Bounded work may proceed inside approved limits. New financial, destructive or physical actions wait for a human decision.
Contain the failure. Record it as an incident or tracked defect, attach the evidence, and investigate which control missed it. Link the work item to the changeset, qualification and production follow-up. Then decide whether the factory needs a regression check, release gate, policy, architecture or documentation change.
A recurring failure should become harder to repeat because the factory learned from it. Public claims remain smaller than the evidence supporting them.
Checks accumulate. Some outlive the behaviour they were written to protect, and a factory that treats an outdated gate as a specification will warp a correct product to satisfy a test that no longer describes anything real.
When a gate and current product intent disagree, investigate the gate first. Ask whether the requirement still exists. If it does not, delete or rewrite the gate and record what it used to protect. If it does, the product was wrong. What is not acceptable is deleting the requirement quietly to make the disagreement disappear.
The same bar applies to process work itself. New process, tooling or architecture needs a named observed failure behind it. A control added because a check could not actually run against production, or because one worktree could certify another, has earned its place. A control added because it seemed prudent is a cost with no evidence attached.
Money is the one input in this factory that cannot be un-spent, and the temptation it creates is specific: a capability that could be paid for feels available, and availability is easy to mistake for readiness. The rule is a sequence, not a mood.
Applied honestly, this rules out a whole category of expensive mistake. Capital is not wasted by waiting for a technology that makes a project possible; it is wasted by spending early to find out whether a market exists. A factory that can already build the system has demonstrated one thing: it can build systems. That says nothing about whether strangers will pay for them, and the two claims are routinely confused because both feel like progress.
Technical maturity and commercial validation are separate claims with separate evidence. A deployed product, a passing suite and a growing catalogue are implementation, release and production verification. None of them is a customer. Where the only honest measurement is an empty table — the tables that would hold a rating, a report or a dispute, with no rows — that is a measurement worth publishing rather than a gap to route around.
This also constrains the negative direction. Creative work is allowed to be worth doing without a business attached, and a project with no commercial ambition is not a project awaiting justification. Forcing a revenue thesis onto work that has none produces a worse answer than leaving it alone, and manufacturing the appearance of demand is worse than recording its absence.