Fleet by Oracis
Request private access

Fleet by Oracis

Sheet
F-000
Set
Product
Status
Issued

Your engineering tools. A coordinated fleet behind them.

An independent engineering runtime for building, researching, reviewing and verifying software.

Fleet brings bounded engineering workers, repository intelligence, research, browser tools and operational evidence into one system. Access is opening in controlled stages, with permissions and availability defined for each capability.

Private preview · Invitation only. Public access coming soon.

Request private access See how Fleet works →

F-000ProductIssued

What it does

Six kinds of engineering work, in one system.

  1. 01

    Build and navigate

    Bounded engineering workers in isolated copies of the repository, and a map of the code before anyone writes.

    • Bounded engineering workers In daily use by Oracis · not yet remote
    • Isolated worktrees and merges In daily use by Oracis · not yet remote
    • Repository intelligence In daily use by Oracis · not yet remote
    • Hosted jobs Hosted · private preview
  2. 02

    Research and investigate

    Questions answered from the live web with sources quoted, and a council of independent seats for hard calls.

    • Web research with quoted sources In daily use by Oracis · not yet remote
    • Independent council In daily use by Oracis · not yet remote
  3. 03

    Review and repair

    An independent second seat reads every change; findings go back for repair with a test that proves them.

    • Independent review of every change In daily use by Oracis · not yet remote
    • Repair with a failing test first In daily use by Oracis · not yet remote
    • Independent validation of a commit Hosted · private preview
  4. 04

    Browse and inspect

    Browser journeys and visual checks against your own running software, and media for the product itself.

    • Browser journeys In daily use by Oracis · not yet remote
    • Visual inspection In daily use by Oracis · not yet remote
    • Images and film for the product In daily use by Oracis · not yet remote
  5. 05

    Coordinate and control

    Missions split into lanes with exclusive write scopes, hard spend ceilings, data rules and a person on every merge.

    • Missions In daily use by Oracis · not yet remote
    • Hard spend ceilings In daily use by Oracis · not yet remote
    • Data rules per repository In daily use by Oracis · not yet remote
    • Organizations, roles and scopes Hosted · private preview
  6. 06

    Record evidence and learn

    Signed receipts, a durable record of every job, and verified corrections that become lessons, guards and evaluations.

    • Signed receipts and published checks Hosted · private preview
    • A durable record of every job In daily use by Oracis · not yet remote
    • Lessons for work like yours Hosted · private preview
    • Verified corrections In daily use by Oracis · not yet remote

Every capability, with where it runs and its proof →

How work moves

Intent in. Authorized, evidenced change out.

This is how Fleet's workstation runtime carries out work on Oracis engineering today; the hosted service offers the jobs, validation and evidence parts of it to invited organizations. Work is scoped before anything runs. Specialists carry it out in parallel, each confined to the files it may change and a spending ceiling. An independent seat reviews and verifies it, and a real problem goes back for repair with a test that proves it. The result is recorded as evidence, and nothing is integrated until a person authorizes it.

How work moves through Fleet An intent becomes scoped work. Specialists execute it in parallel. It is reviewed and verified, and a failed review sends it back for repair. The result is recorded as evidence. A person authorizes it, and only then is it integrated. intent scoped work specialist execution review and verification evidence you authorize authorized integration How work moves through Fleet An intent becomes scoped work. Specialists execute it in parallel. It is reviewed and verified, and a failed review sends it back for repair. The result is recorded as evidence. A person authorizes it, and only then is it integrated. intent scoped work specialist execution review and verification evidence you authorize authorized integration
Fig. 5Work is scoped before it starts, carried out by specialists in parallel, reviewed and verified, recorded as evidence, and integrated only when a person authorizes it.

How it learns

Outcomes become lessons only after someone verifies them.

When Fleet's work is corrected, the correction is recorded with its reason. Once it is verified, it becomes a lesson retrieved for similar work, a guard that stops the same mistake, or an evaluation that measures it. Recording a correction does not by itself change a model.

How Fleet learns from an outcome An observed outcome is checked by a person. Once verified it becomes a verified correction, which is recorded as one of three things: a lesson, a guard, or an evaluation. observed outcome a person verifies verified correction lesson guard evaluation How Fleet learns from an outcome An observed outcome is checked by a person. Once verified it becomes a verified correction, which is recorded as one of three things: a lesson, a guard, or an evaluation. observed outcome a person verifies verified correction lesson guard evaluation
Fig. 6An outcome becomes a verified correction, then a lesson, a guard or an evaluation. Recording a correction does not by itself change a model.

Availability, stated plainly

Not everything Fleet does is remote yet.

Fleet runs in two places. Its workstation runtime is what Oracis engineers use every day; 15 of the capabilities listed here run there and are not offered remotely yet. The hosted service is what an invited organization connects to from an MCP client; 5 capabilities are there today, in private preview. Claude Code sign-in is proven against it; Claude.ai, ChatGPT and Codex are designed for but not yet demonstrated.

Every capability entry says which it is, and what proves it. GitHub stays your system of record: Fleet runs checks on its own runners and posts the result there.

Connect a client → Security, in three states →

Request private access.

Access opens in stages, by invitation. Tell us what your team builds and how it works today; a person reads every request.

Request private access How Fleet works →
Next sheet · F‑100 Capabilities