Roles
Behind each number we publish and each engagement we sell are the roles below. Each card says what the role does, what it gives you, and where its work is recorded.
A role here is a job, not a rank.
Behind what we publish
-
Day AGI
Answering today; limits listed
What it does. Answers questions on embark.day, works as the consultant at Agile Integrations, and draws each figure on our Mission page from its committed record.
For you. Each answer names the section it came from and each figure's caption says what kind of evidence it is; what Day has been measured to do and not to do, failures first, is on its own page.
Recorded on.
-
The consultant of record
Working today
What it does. Designs and builds the engineering behind each paper: the engine's contracts, the tests that hold each page to its measurements, and the release checks.
For you. Each paper's numbers are pinned by tests to the measurements they report.
Recorded on.
-
You, reading
You
What it does. Reads each number with its status word: a measured number names the record it was read from, a test registered before its data was written down first and is never edited after, and anything marked our reading is an interpretation, never a result.
For you. Every solved model carries a certificate you can re-check on your own machine with no network, and our measurement pages put their failures first.
Recorded on.
Inside your business system
These three roles are defined in version 0.1.0 of the QubitOS app for your business system, the read-only release, licensed GPL-3.0-only. It is not yet released.
-
QubitOS Reader
Defined, not yet released
What it does. Reads everything the app holds and changes nothing.
For you. Whoever needs to see the tree of your business and its readings can, without being able to change them.
-
QubitOS Manager
Defined, not yet released
What it does. Owns the switches, the engine's address and key, and the fields that name people; voids a reading; and, once proposals are on, approves or rejects one.
For you. Every switch ships off and a Manager turns each one on. While proposals are off the app refuses them; while writing is off the engine only plans, and disabling the engine's account stops it for certain. A proposal that commits money also needs your system's accounts-manager role. Give this role only to people you would trust with the key.
-
QubitOS Engine
Defined, not yet released
What it does. Not a person: the one account the engine signs in as. It writes only the app's own records — the tree, the readings, outside conditions and proposals — never an invoice, a deal or a customer.
For you. Give the role to that one account, and give that account no other role. Nobody edits a reading; a Manager can void one.
When you hire us
-
The professional engagement
By written quote
What it does. A person reads your request and sends a written, itemised quote, and you prepay by invoice. An engagement runs in three shapes, in order: a diagnostic of about a week at a fixed fee, a pilot of a few weeks at a fixed scope and price, and a build your team owns at the end.
For you. Day is the instrument behind it: Day asks what is missing, names the kind of problem, writes it as a model, solves it with its certificate, reports what each rule cost, and bills its time as a line of its own. You keep the model, its certificate and the report.
Recorded on.
-
Partner firms
By written terms
What it does. Development and consulting companies take the optimisation engine behind our engagements, the Day QIO optimisation API, to deliver optimisation work to their own clients.
For you. Each firm takes it under a written agreement, as a client.
Recorded on.