How to read this page
Fleet runs in two places. The hosted service is what an invited organization connects to from an MCP client. The workstation runtime is what Oracis engineers use every day to build software, this site included; its capabilities are real and in use, but they are not offered to customers remotely yet. Each entry names one of three states and the evidence for it, with the date it was last checked.
- Hosted · private preview
- On the hosted endpoint for invited organizations. The docs status table lists each hosted journey as proven live or implemented but not yet demonstrated.
- In daily use by Oracis · not yet remote
- Runs in Fleet's workstation runtime and is used on Oracis engineering. Not available to a connected client.
- Planned
- Designed, not available.
Build and navigate
Bounded engineering workers in isolated copies of the repository, and a map of the code before anyone writes.
| Capability | What it does | Where it runs | Proof |
|---|---|---|---|
| Bounded engineering workers | A worker takes a written brief, a list of files it may write and a spend ceiling, works in its own git worktree, runs the tests in a sandbox, and hands back a diff. It cannot write outside its scope, and two workers never share a file. | In daily use by Oracis · not yet remote | An engineer job drew four of this site's figures first pass for about 2 cents; a person read its diff before it merged (27 Sep 2026). Checked 2026-09-27. |
| Isolated worktrees and merges | Every job gets its own branch and working copy; the diff is read before it lands, and the copy is removed after. | In daily use by Oracis · not yet remote | Engineer work on this site was reviewed, merged and cleaned up this way (27 Sep 2026). Checked 2026-09-27. |
| Repository intelligence | Find a symbol, who uses it, what a change breaks, and which files matter for a task, before any model is paid to read. | In daily use by Oracis · not yet remote | Part of Fleet's workstation tool set, used on Oracis engineering. Checked 2026-09-27. |
| Hosted jobs | Submit, read and cancel a bounded job from a connected MCP client; it keeps running after you disconnect. | Hosted · private preview | Deployed on the live hosted service; not yet recorded as working end to end (27 Sep 2026). Checked 2026-09-27. |
Research and investigate
Questions answered from the live web with sources quoted, and a council of independent seats for hard calls.
| Capability | What it does | Where it runs | Proof |
|---|---|---|---|
| Web research with quoted sources | A question answered from the live web, every claim tied to a verified quote and its source. | In daily use by Oracis · not yet remote | Oracis's AI-visibility research was produced with it (25 Sep 2026). Checked 2026-09-27. |
| Independent council | Three independent expert seats and an architect's synthesis for a decision that deserves more than one opinion; an incomplete council says so. | In daily use by Oracis · not yet remote | Part of Fleet's workstation tool set, used on Oracis engineering. Checked 2026-09-27. |
Review and repair
An independent second seat reads every change; findings go back for repair with a test that proves them.
| Capability | What it does | Where it runs | Proof |
|---|---|---|---|
| Independent review of every change | A second model, not the author, reviews a diff before it counts as done; a finding must name the line that proves it. | In daily use by Oracis · not yet remote | Field note N-101, "The reviewer was wrong" (oracis.ai/notes/the-reviewer-was-wrong/). Checked 2026-09-27. |
| Repair with a failing test first | When a review finds a real problem, it is reproduced with a failing test, fixed, and the test kept. | In daily use by Oracis · not yet remote | Oracis's engineering practice (oracis.ai/how-we-work/). Checked 2026-09-27. |
| Independent validation of a commit | Run the repository's own verification policy against one exact commit, each lane in a fresh VM that is destroyed afterwards, and get a signed receipt. | Hosted · private preview | On the live hosted tool list (27 Sep 2026); not yet demonstrated end to end for a customer repository. Checked 2026-09-27. |
Browse and inspect
Browser journeys and visual checks against your own running software, and media for the product itself.
| Capability | What it does | Where it runs | Proof |
|---|---|---|---|
| Browser journeys | Up to twenty declared journeys against your own running server in one call, under a matrix of devices and motion settings, with a pass, fail or unproven report. | In daily use by Oracis · not yet remote | Part of Fleet's workstation tool set, used on Oracis engineering. Checked 2026-09-27. |
| Visual inspection | Mechanical checks and a vision seat's findings tied to page selectors, on your own local server and never on pages with patient data. | In daily use by Oracis · not yet remote | Part of Fleet's workstation tool set, used on Oracis engineering. Checked 2026-09-27. |
| Images and film for the product | Generated imagery and film for a product's own pages, labelled as illustration wherever it shows people. | In daily use by Oracis · not yet remote | The editorial photography and film on oracis.ai, labelled as illustration in its footer, were produced with it. Checked 2026-09-27. |
Coordinate and control
Missions split into lanes with exclusive write scopes, hard spend ceilings, data rules and a person on every merge.
| Capability | What it does | Where it runs | Proof |
|---|---|---|---|
| Missions | An outcome split into lanes, each with an exclusive write scope, checked by a plan critic before anything is spent, then staffed, run and integrated. | In daily use by Oracis · not yet remote | Field note N-104: seven lanes for 19.5 cents (oracis.ai/notes/seven-diagrams-seven-lanes/). Checked 2026-09-27. |
| Hard spend ceilings | A daily cap, a per-job budget and a provider key per job capped at that budget, so a ceiling is enforced by the provider rather than checked afterwards. | In daily use by Oracis · not yet remote | Reported by Fleet on every engineering session (27 Sep 2026). Checked 2026-09-27. |
| Data rules per repository | Each repository declares which vendors may read which paths; a repository that has not declared is refused. | In daily use by Oracis · not yet remote | Every repository Oracis works in declares its data classes before any model reads it. Checked 2026-09-27. |
| Organizations, roles and scopes | Every hosted call is tied to one organization; another organization's work answers not found. | Hosted · private preview | Deployed on the live hosted service, with cross-tenant tests; isolation not yet observed on it independently (27 Sep 2026). Checked 2026-09-27. |
Record evidence and learn
Signed receipts, a durable record of every job, and verified corrections that become lessons, guards and evaluations.
| Capability | What it does | Where it runs | Proof |
|---|---|---|---|
| Signed receipts and published checks | A receipt binds the source, the policy, each command and its exit code and output hashes; a separate publisher turns it into a GitHub check with counts and ids only. | Hosted · private preview | On the live hosted tool list (27 Sep 2026); not yet demonstrated for a customer repository. Checked 2026-09-27. |
| A durable record of every job | Every engineer job, mission, review and delegated task is recorded when it ends: what ran, what it cost, what the tests said. | In daily use by Oracis · not yet remote | Fleet's evidence record took in more than 200 records in the 24 hours to 27 Sep 2026 (counted from its ingest log, rounded down). Checked 2026-09-27. |
| Lessons for work like yours | Retrieve the lessons Fleet has recorded for similar work in a repository; confirm whether one held. | Hosted · private preview | Deployed on the live hosted service; not yet recorded as working end to end (27 Sep 2026). Checked 2026-09-27. |
| Verified corrections | A hand repair of Fleet's work is recorded with its reason, so it can become a lesson, a guard or an evaluation. Recording a correction does not by itself change a model. | In daily use by Oracis · not yet remote | Part of Fleet's workstation tool set; hand repairs on this build were recorded (27 Sep 2026). Checked 2026-09-27. |
What this page does not claim
- That any workstation capability is available to a connected client. Only the hosted entries are.
- That recording a correction improves a model. It becomes a lesson, a guard or an evaluation after a person verifies it; nothing here retrains a model.
- That the hosted customer journeys marked implemented have been demonstrated end to end for a customer repository. The docs status table says which have.
- Any certification, uptime figure or customer count.