ProductsUnderstand
Decisionslive
Product and design documents with versions, reviews and diagrams
Product plans, proposals and decision records, reviewed like code. Decisions is where a team writes down what it wants to build, proposes changes and records why it chose what it chose. Each document keeps its versions, reviews, diagrams and a dated log of what was done, and the pull requests that carry it out are linked to it. We write every design here first: our own RFCs run on it, and the ones we share are on rfcs.inorbit.hr for people with access.
Live today. Accounts open after a 30-minute call.
- Status
- live
- Group
- Understand
- Defined in
- RFC 0035, RFC 0041
01The problem
Decisions get made in chat threads and documents nobody can find later. When the code drifts from what was decided, nobody notices until it breaks.
02How it works
How it works
Where it runs
- On the platform: in the console, through the API and from AI assistants, and as a command (
iohr lab check) on your own repository. What it reads
- The documents you write, their versions and reviews, and the pull requests that implement them, through the GitHub App (on our own repository today; yours is coming).
What you approve
- Named reviewers approve or ask for changes, and a person decides. An AI assistant may only approve where the space's owner allowed it for that kind of document, and its answer is recorded on that person's behalf. Making a document public needs the right to manage it and passes the redaction check.
03What you getlive
What you get
- Three kinds of document, one placelivePRDs for product intent, RFCs for proposals, ADRs for decisions, in spaces with access levels from public to internal. Every save is a version; a save on a stale one is refused.
- Reviews and a status logliveNamed reviewers approve or ask for changes, and a person decides. Each document keeps a dated log of what was done.
- The pull requests that carry it outin partLink a pull request to a document through the API, an AI assistant or
iohr decisions link-pr, and its state, review and checks are read from GitHub through the GitHub App. Listing them on the document's page in the console is coming. - Checked like codeliveThe file name, the header block, the log and the hiding of private details are checked, the same way in the product and in
iohr lab checkon your repository. - Published through redactionliveA public document is shown on its own site and refused if it names an internal server, an address or a secret. A fact we keep back shows as a bar with the reason.
- Linked to the code it governsin developmentAtlas will tie each decision to the services and files it governs, and flag the running system when it goes against one. In development.
04In the consoleExample data
In the console
Platform · ADRs
ADR-0017Retries to the ledger, at most three
Checkout retries a failed ledger call at most three times, with jittered backoff, so a slow ledger cannot charge a payment twice.
Context
Under load the ledger answers in up to 4 s. Checkout retried five times with no backoff, and one slow call became five writes.
Decision1 open thread
At most three retries, 200 ms to 1.6 s apart with jitter, each with the same idempotency key.
max_retries = 3- Supersedes
- ADR-0009
- References
- RFC-0012 · Ledger client
Status log
- Proposed, version 1
- Accepted by Emma Walker, 2 approvals on version 3
- Building: the checkout client retries behind a flag
- Backoff measured on staging, version 4
Example data
Drawn from the console's own layout. The services, times and numbers are made up for the example.
05Proof and links
Proof and links
Documents
Docs
API
- RESTliveSpaces, documents, versions, reviews, comments, diagrams, the status log and linked pull requests.
GET /v1/decisions/spaces/{space_id}/documents - MCPlive
decisions_*tools: read and list documents, save a new version on the one read, comment, link pull requests and read the timeline. Reviewing is refused unless the space's owner allowed it for that kind. - iohrlive
iohr decisionsto list, create, save, comment, review and link a pull request;iohr lab checkruns the checks on a repository with no network.
The evidence rule: a model saying it succeeded is never evidence. What counts is what was measured, by what, and when.
Your data, your call
Each document has an access level. A public one passes the redaction check before it is served, and a classified span reaches only readers cleared for it.
Logs record who did what and the outcome, never content. InOrbit stores only a reference to each credential, such as vault:kv/payments#token, never its value, and never logs it. The platform's own models are self-hosted; a third-party model provider is one you connect with your own key, and it bills you directly, with no line or markup from InOrbit. Separately, our own DPAs with model providers are in progress, none signed yet. InOrbit is not certified: no auditor has attested its controls yet, and the known gaps are listed.
06Questions
Questions, answered plainly
Can we import the RFCs we already have?
Can an AI agent write a document?
iohr decisions, under the caller's rights. It may approve or ask for changes only where the space's owner allowed that for the kind of document, and its answer is then recorded on that person's behalf.Who can use it today?
Next step
See it on your own system
Book 30 minutes with an engineer. We look at your system together and, where it fits, open early access for your team.