Question 1

Does it write the documents for me?

Accepted Answer

It writes the drafts. You decide what is true. That distinction is the whole design: an artifact only becomes approved because a person read it and said so, section by section, and the engine keeps the record of who approved what and when.

Question 2

Can I sign up?

Accepted Answer

Not right now, and on purpose — there is no public registration. Accounts are created by hand, one at a time, and every sign-in goes through a second factor sent by email. If you would like to try it, write to me and say a little about what you would point it at.

Question 3

Where does my data go?

Accepted Answer

The application, its database and its backups run on a server in Finland, and transactional email goes through a European provider. The one thing that can leave the EU is the model call itself, and only towards the provider whose key you configured. All of it is set out in the privacy policy.

Question 4

What does it cost?

Accepted Answer

Nothing, because nothing is being sold. There is no pricing page, no plan and no checkout — access is a conversation. You do pay your model provider for the tokens your runs consume, since the key is yours.

Question 5

Is it open source?

Accepted Answer

Not at the moment. The method behind it is a different matter: the reasoning about why the stages are in that order, how the rulebook separates deterministic checks from judgement, and how traceability is modelled is the part I am happiest to talk through.

Question 6

What state is it in, honestly?

Accepted Answer

The engine works: pipeline, gates, revisions, staleness propagation and the rules layer all run. The stages sit at different depths — discovery and the architecture rulebook are the most developed, the later ones are thinner. It is built in evenings and weekends, so it moves in bursts.