Skip to main content
Jarvisby TheSEO
EN
Language · same pageNLNederlands/jarvis/documentatie/ENEnglish (UK)/en/jarvis/documentation/ESEspañolnot translated yetWe do not remember your choice and never redirect you automatically.
DOC.J00 A product register readable by people and by machines
JarvisDocumentation
DOC.J01 · one source registerdocument id · status · owner · version in force

Find what applies. And what does not yet.

Every core promise gets a document ID, a status, an owner and the version in force. Preview, draft and active are not mixed up with each other.

See Jarvis To the trust centresix gates have to open together · paying on the site is still switched off
FIG.D01: The six gates that have to open togetherDOC.J00 · release gates

A front end that works properly is the first gate, not the last

This page names six areas that have to pass the release gates together, and the paragraph before it lists what is not connected yet. Here those two lists lie on top of each other: per gate what is missing, and at the bottom the single field in prices.json that keeps the payment route shut today.

~/jarvis/documentation · release-gates[note] six gates shut
the six gates that have to open togetherrelease gates
Producttwelve routes and the core interactions are builtfront end done
Dataproduction tenant isolationnot connected yet
Securityreal authenticationnot connected yet
PaymentStripe Checkout and webhooksnot connected yet
Legal documentstrust centre TRUST.J01review
Operationstenant provisioning and production observabilitynot connected yet
and this one fieldin prices.json, checkout_enabled is set to false; only the non-binding waiting list is available
for as long as the six are not open at the same time, selling stays shut and only the non-binding waiting list is available
# per gate you can see what is done today and what is still missing; the field at the bottom is the switch that keeps the payment route shut
REL.J01 · production boundaries

What has been built?

The React interface holds twelve routes and working core interactions: instructions, approvals, memory proposals, knowledge reviews, inbox, task statuses, subscription changes and a five step onboarding. Desktop and mobile have been checked visually.

What is not connected yet?

Real authentication, production tenant isolation, OAuth connectors, Stripe Checkout, webhooks, tenant provisioning and production observability. As long as those six gates are not green at the same time, paying online stays shut and the product layer carries the status preview.

So can you order Jarvis?

No. Jarvis is not available to order while checkout, contract, tax, provisioning and revocation remain behind release gates. On get started you can only choose a preferred trial plan and join the non-binding waiting list. That expression of interest is not an order and creates no agreement or payment obligation. It does not create an account, send a payment instruction or charge anything.

Country-specific tax treatment remains pending and will be confirmed for your country only if the sales route is released.

When may Jarvis go live?

Only when product, data, security, payment, legal documents and operations pass the release gates together. A front end that works properly is necessary, but it is not enough.

Section · Next stepreachable 24/7
Book a call