# The chain of custody _A plain-text mirror of the page at /process, generated from the same source that page renders from. Where the page resolves a counted fact when it is built, the mirror leaves it out rather than printing the placeholder._ Four stations, in order, and each one leaves something behind. The paper trail is not a report we write about the work afterwards. It is the work. ### Station one: Intake, under seal Before a single substantive question, both sides sign a mutual non-disclosure agreement. Then you are interviewed one question at a time, in a deliberate order. Where an answer is too vague to build from, you are asked a better question there and then, rather than in a follow-up long after it would have helped. - The exact agreement text you accepted, fingerprinted and stored with the moment you accepted it - Your answers, in your own words, encrypted before they are written down - What you could not decide, recorded as undecided rather than quietly assumed ### Station two: The packet, sealed Your answers compile into one document: what the thing is, who uses it, every screen and every state it can be in, the data behind it, the permission rules, and what finished means, stated precisely enough to be argued with. Sealing it fingerprints the exact text. After that, a change is a re-issue with its own record, never a quiet edit. - A sealed document with its own identifier and its own digest - Yours to keep, and yours to take elsewhere, whatever you decide next - Nothing is built until you have read it and approved it ### Station three: The build, witnessed The build runs under a chain of standing checks. They read the work on every change and refuse the ones that break a rule this studio has already paid to learn: a permission gap, an error swallowed in silence, a promise in the copy nobody approved. - Every change runs the whole chain before it is allowed to land - A red check stops the change, which is the only moment stopping it is cheap - The same chain runs on this website, and the sentence you are reading passed it ### Station four: Handover, with the trail At the end you have the product itself, the sealed document it was built from, and the record of what was decided and when. Nothing about this studio is required to keep it running, and nothing about it is a secret from you. - The product, deployed and running, on every platform it was built for - The sealed specification, and every decision on the record - The source, and the chain of checks that keeps it honest afterwards ## What changes hands - the product, running, on its own hosting - the sealed specification, with its digest - the record of every answer, including the undecided ones - the source, and the chain of checks that reads it - the accounts and the keys, in your name ## The first thing we sign protects you The agreement is mutual and it comes before the first substantive question. It covers what you tell us about your concept, and it covers what we show you about how we work. Nothing about your venture is asked before it is in place. ## One build at a time This studio takes one build at a time. That is the entire capacity statement: no countdown, no waiting list, no invented scarcity. When intakes are open you can start one here, and when they are not, this page says so instead of pretending. ## The reversal You see it running before you commit, and the packet is yours either way.