ProductUnderstand
Decisionspreview
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 code changes that carry it out show on the same page. We write every design here first: our own RFCs run on it, and the public ones are on rfcs.inorbit.hr.
In early access. A 30-minute call is the way in; there is no SLA during early access.
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.
A document moves from draft to decided with every step kept, and the work that implements it lands on the same page.
How it works
- 01
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. - 02
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).
- 03
What you approve
- Named reviewers approve or ask for changes. Deciding a document and publishing it are always a person's act.
Each line says how far it is built today. Live means anyone with an account uses it; preview means it runs in early access or as a pre-release; coming means it is written down and not built yet.
What you get
Three kinds of document, one place
PRDs 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.
previewReviews and a status log
Named reviewers approve or ask for changes; deciding and publishing stay a person's act. Each document keeps a dated log of what was done, and the code changes that carry it out.
previewChecked like code
The file name, the header block, the log and the hiding of private details are checked, the same way in the product and in
liveiohr lab checkon your repository.Published through redaction
A 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.
liveLinked to the code it governs
Atlas will tie each decision to the services and files it governs, and flag the running system when it goes against one. In development.
in development
An ADR as Decisions shows it: its state, its log and what it governs.
In the console
ADR-0017 · Retries to the ledger, at most three
accepted · version 4 · 2 reviewers approved
- Accepted after review
- Pull request #318 implements it
- Checks pass: front matter, status log, redaction
Governs
- checkout
- ledger
- checkout/src/ledger.rs
Example data
Drawn from the console's own layout. The services, times and numbers are made up for the example.
Every claim on this page has its evidence: the documents that define it, the docs that say how to use it, and the API it runs on.
Proof and links
Documents
API
- RESTpreviewSpaces, documents, versions, reviews, comments and diagrams.
GET /v1/decisions/... - MCPpreviewTools an AI assistant can use to read documents, save a new version, comment and ask for changes. Approving and publishing stay in the console.
- iohrpreview
iohr rfcto create, save and comment;iohr lab checkfor the checks.
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. 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.
Questions, answered plainly
Can we import the RFCs we already have?
Markdown files in our format load from a repository; that is how ours got in. Keeping a repository in sync both ways is not built yet.
Can an AI agent write a document?
It can draft, save and ask for changes through MCP or the API, as its own identity. Approving, deciding and publishing stay a person's act.
Who can use it today?
Teams in early access, in the console. We write every one of our own designs on it, and the public ones are on rfcs.inorbit.hr.
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.