You say what you want to build. FLOW builds the team that makes it.
It runs the interview, learns the trade of your field from real sources, proposes the org chart, trains every role, and hands you a desk where you work with your team. The decisions stay yours, one at a time, with the reasoning on the table.
“I want to write a detective novel and I need an editor for my ideas.” one sentence, at the interview
An assistant answers you. A team works for you, with written roles, cited sources, and verification gates that close by themselves when something is wrong.
Before recommending anything, FLOW reads 20 to 30 comparable works or businesses in your field and writes one note per source, cited with the source and the place. No recommendation out of the model's memory. A source it could not find is reported as not found.
What it does, what it is not allowed to do, which model drives it and why that one. Written down, not assumed. A cheap model for mechanical work, a middle one for volume, the most capable where judgement is required.
A rule that nothing defends is a wish. The verification gates run without you, on every write and every handover. What cannot be defended mechanically is told to you plainly.
Nothing is skipped and nothing is decided for you out of assumption. At every station where something is decided, the decision goes to you.
The architect asks until the project charter is done: the goal, the final deliverable defined at the start, the boundaries, the budget, and what stays your responsibility. The deliverable is defined on the first day rather than the last, precisely so that no one builds an entire mechanism with an empty final step. The charter is a proposal until you adopt it explicitly.
out: the project charterThe researcher builds the house's expertise in your field, only from sources of an admitted tier: academic work, innovation centres, the top of the field. One reading note per source, written only from text actually read. Then the comparison: what separates the works that sold from the ones that did not, with the proof for every reason given.
out: the corpus, with cited notesYour team on paper, before a single line of code: which roles, why each one, and who the coordinator is that speaks to you. You adopt it, cut it, or change it. Nothing is generated on top of an org chart you have not adopted.
out: the proposed teamEvery role in the chart receives the corpus of its trade and its own briefing, drawn from the expertise. A role that has read nothing does not join the team. From here on, every recommendation cites notes rather than impressions.
out: the trained teamThe builder writes the pipeline: the directory structure with a single direction of flow, the roles with their double contract, the rules with the mechanism that defends each one, and the verification gates already running. Then the critic attacks it against a list of its own, without seeing the builder's justification. Rejected is a normal verdict, not an accident.
out: the pipeline, after a verdictYou get a web office: the Visual Studio Code editor served in the browser, entry by password, your space on a persistent volume, deliveries kept read-only and your directions left at the door. The team works there, in your language, not in our technical one. You install nothing.
out: your office, with the team in itThe team works, you decide. Every delivery arrives as a considered recommendation, with the alternatives beside it and the reasoning next to them. Whatever gets in your way more than once becomes a proposal for a new rule, with a threshold it has to pass. The workshop learns from your friction, not from assumptions about you.
out: the work, decision by decisionA pipeline handed to someone who is not an engineer has to defend itself. We do not ask you for discipline and we do not hand you a list of good practice to remember. We give you verification gates that run without you.
Blocks the file before it is saved, if it breaks a rule of your project.
Nothing reaches you without the critic's verdict. Handing over without a verdict is mechanically forbidden.
The verification gate written for your trade, the continuity of a plot for instance, run against every new chapter.
And whatever cannot be defended mechanically is not hidden: it is written into the charter, explicitly, on your responsibility. We would rather give you a short list of things you take on than a long list of promises nobody keeps.
The most expensive mistake in a project is plausible advice taken as certain. Here, the two do not look alike.
It has its source and its place. It comes from text that was actually read, not from the model's memory. You can open it and read it yourself.
It is reasoning, not proof. It arrives with what would have to be found for it to become verified, so you know what it weighs.
The same person, the same opening sentence. This is the team that comes out of the interview and the expertise, with the model assigned to each role.
| Generated role | What it does | Model |
|---|---|---|
| Coordinator | The only one who speaks to you. Carries the decisions to you and the work to the team. | judgement |
| Developmental editor | Structure, arcs, pacing. Holds every chapter against the findings of the expertise. | judgement |
| Line editor | The sentence, the voice, the repetitions. The voice stays yours, a boundary written into the charter. | volume |
| Plot researcher | The logic of the clues, the chronology, police procedure. | volume |
| Critic | Attacks the manuscript like a hostile reviewer, before any handover. | judgement |
| Market agent | Positioning, the selling synopsis, the list of publishers and agents worth approaching. | volume |
| Mechanical proofreader | Lexicon, typography, formatting. Runs last, every time. | mechanical |
Three decisions get put to you along the way: the narrative structure, a pen name or your own, a traditional publisher or self-publishing. Each one with a recommendation resting on notes. The choice is yours.
The interview lasts about as long as a serious conversation. At the end of it you hold the project charter, and you know exactly what you are getting, who is making it, and what stays yours.
FLOW and Quanticus are working names. The product is in pilot: the first team it generated was the workshop's own, because a method that does not apply to itself is not a method.
