# Custos Blueprint _A plain-text mirror of the page at /, 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._ _A sealed design for your application, owned before you build._ CUSTOS BLUEPRINT, noun. A sealed design for your application: every screen, every state, every decision, on the record and owned by you before a line is built. Most software projects fail in the first conversation, not the last sprint. They start with a brief nobody interrogated, and everything after that is repair work. We start somewhere else: with a real interview. ## The deck is not the product. Studios sell you a promise. You pay, and then you find out what you bought. The idea you described in the pitch is now something someone else has heard, and nothing you were shown is yours to take anywhere. Most software projects fail in the first conversation rather than the last sprint. A brief nobody interrogated is a brief that everything after it is repair work for. ## How it starts ### Sign the mutual non-disclosure agreement Before a single substantive question. It runs both ways, and nothing about your venture is asked until it is in place. ### Sit the interview and seal your answers One question at a time, in a deliberate order. Where an answer is too vague to build from, you get a better question there and then. Everything you said is yours to edit until you seal it. ### Receive your Custos Blueprint, then decide Build it with this studio, or take it anywhere. Both were always going to be true, which is what makes the first decision a small one. ## Three things that are structurally true here ### Nothing is asked before the seal The form in front of the agreement takes a name and an address and has no field for your venture. There is nowhere to type your idea, because the agreement that exists to protect it has not been signed yet. ### You own the design either way The edition you receive carries your design and nothing about how this studio works. A scan refuses to release one that would carry the second thing, so this is a rule a machine holds rather than a promise a person makes. ### Every decision is on the record What you could not decide is written down as undecided. It is never quietly assumed on your behalf, and you can read back every fork you were offered and the reasoning you were given for the recommendation. ## The chain of custody We build it before you buy it. Four stations, in order, and each one leaves something behind. The paper trail is not a report written about the work afterwards. It is the work. ### The agreement Mutual, and first. It covers what you tell us about your concept and what we show you about how we work. The exact text you accept is fingerprinted and stored with the moment you accepted it. - The text you agreed to, as it was on the day - Your name, and the moment - Nothing about your venture, because nothing about it has been asked yet ### The interview One question at a time, in a deliberate order, adapting to what you have already said. Where an answer is too vague to build from, you are asked a better one there and then rather than in a follow-up long after it would have helped. - Your answers, in your own words, encrypted before they are written down - Every fork you were offered, with the recommendation and its reasoning - What you could not decide, recorded as undecided ### The seal You read everything back and change anything that is wrong. Sealing fingerprints the exact text. After that a change is a re-issue with its own record, never a quiet edit. - One document with its own identifier and its own digest - A record that cannot be altered behind you - The point after which nothing moves without you ### The packet Your design, sealed and yours: the brief, the screens by state, the data model, the visual language, the build plan and the decision record. It is a specification any developer can be handed. - Six artifacts, and every one of them yours - Nothing about this studio inside it - A dated chapter in the public record saying it was sealed ## What is actually in it ### Every screen, every state Not a list of features. Every screen the application has, and for each one what it looks like loaded, empty, still loading, and when something has gone wrong. The states are where software is actually finished or not. ### Your data, classified Every field the application stores, what it holds, and how sensitive it is. The classification is what decides who may read a row, and deciding it on the page is cheaper than deciding it after the first person has been let in. ### Your app’s own visual law A palette where every colour has a meaning written beside it, a type ramp anchored to the reader’s own text size, spacing, corners, and the list of things this design will not do. Portable to any team. ### Every fork, recorded What you were asked, what you answered, which way each decision went and why, and what was left open. When something turns out wrong later there is a document to argue with instead of two memories. ## What clients say No client has said anything yet. The first chapter that quotes one will be verbatim and named, and until then this space says so rather than borrowing somebody else’s words. ## What has shipped, and when A dated log of real work, drawn from the records that produced it rather than written about them afterwards. Every row is read for what it is allowed to say and approved by a person before it appears here. The log is assembled from records that already exist and is not showing any yet, because no row has been approved for publication. An empty log is the honest state, and filling it with something else would be the first thing on it worth not trusting. ## What we will not tell you here Nothing on this page quotes you, schedules you, or promises you a delivery. None of that can be known before the interview, and a number invented before the work is understood is worth less than no number. You will get real answers, in writing, from a person, once there is something real to answer about. ## The questions a real buyer asks ### What if I already have a developer? Then hand them the packet. It is a specification written to be built from, and it is yours whoever builds it. A developer who is given every screen, every state, the data model and the acceptance conditions is being handed the part of the job that usually goes wrong. ### What if I decide not to build? You keep everything. That is the point of selling the design rather than a deposit on a build. The specification has value standing on its own, and it goes with you whether or not anything is built here. ### Is my idea safe? The agreement is signed before the first substantive question, and it runs both ways. Your answers are encrypted before they are stored, under a key that is not kept with the data. There is no analytics tracker and no session recording on this site, and you can ask for everything to be deleted at any time. ### How long does it take? Not answered on this page, deliberately. It depends on how much application there turns out to be, and that is what the interview is for. You get a real answer in writing, from a person, once there is something real to answer about. ### What does it cost? Also not answered here, and for the same reason. A figure invented before the work is understood is worth less than no figure at all. You get a real one, in writing, after the interview is read. ### Do you host it? No. Running software for other people is a commitment with an availability promise inside it, and this studio is one person, so making that promise would be making one it could not keep. You get the source, the accounts and the keys in your own name, and somewhere to run it that you control. ## Walk in with an idea. Walk out with a sealed design you own. The agreement comes before the first question.