AIOS 108ALPHA

Part of the ALPHA suite

ALPHA Bit-Bots · Coworkers

Always-on coworkers that stay under command.

Give recurring work a name, a role, and a lane. Each Bit-Bot is a persistent specialist with its own computer, its own saved pages, and its own permission grant — asking before anything consequential, and keeping a readable record of everything it does.

Request access Enter ALPHA Studio
Four Bit-Bots companions in distinct colors gathered around one approval gate

Crew pattern

A small crew, each with a lane.

Bit-Bots are assigned by role, not by personality. Each one carries a narrow grant, a stated approval line, and a readable record — and each keeps its own workspace files across sessions.

  • Role · Investigate

    Scout

    Investigates a topic and returns with sources attached: what was found, where it came from, and what is still uncertain. Never invents origins; never contacts anyone unprompted.

    Typical grants: stated sources and workspace notes. Asks approval before: contacting anyone, publishing findings, expanding the question.

  • Role · Draft

    Scribe

    Turns findings and conversation into saved pages: briefs, drafts, and revisions you can open, edit, and keep. Every saved page links back to the conversation that produced it.

    Typical grants: its saved pages and the conversation that produced them. Asks approval before: sharing a page, publishing, or writing outside its pages.

  • Role · Keep

    Keeper

    Tends the crew's home for working documents: organized pages, nested subpages, and a searchable library. Keeps revisions safe so a stale edit never silently overwrites newer work.

    Typical grants: the crew's page library. Asks approval before: deleting pages, reorganizing shared spaces, changing who can see what.

  • Role · Operate

    Runner

    Works its own computer on declared steps: browsing, filing, staging drafts, preparing notifications. Holds at every approval gate for a person to decide.

    Typical grants: the run's declared tools and fields. Asks approval before: sending, deleting, sharing, spending, or changing the run itself.

How a Bit-Bot works

Ask, browse, approve, save.

You ask in conversation. The Bit-Bot works on its own computer where you can watch — a live view and a human review card appear right in chat — and the approved draft becomes a saved page you can revisit and revise.

  • Ask in conversation, watch the work happen in the open
  • Review card states exactly what is proposed and why
  • Approved work becomes a saved, editable page

Consequential steps

A person confirms what matters.

Sending, publishing, deleting, sharing, granting access, and spending always hold for human confirmation. The request is written to be understood in seconds: what is asked, in which workspace, with what scope, and how to undo it.

Try the discipline

You decide. The log remembers.

A front-end demo of the approval moment. Nothing leaves your browser. Tap a verdict and watch the audit trail grow.

Runner asks: save the approved draft as a page in the crew library

Workspace bit-bots-demo · scope: one page, one library · undo: revert to the previous revision.

Demo only. Real approvals are enforced by the control plane, not by this page.

    Permission model

    Persistent memory, bounded grants.

    Persistence never means latitude. Read the philosophy for the control-first reasoning behind it.

    • Named specialists, narrow toolsEach Bit-Bot receives the minimum files, tools, network, and time its role needs — bounded per assignment, never carried over silently to the next one.
    • Every action attributableActions are logged to the acting Bit-Bot as they occur: who authorized it, what was done, in which workspace, and under which grant.
    • Human confirms consequential stepsAnything that sends, publishes, deletes, shares, or spends waits for explicit approval. Denials are recorded alongside grants.
    • Stoppable and revocablePause or revoke any Bit-Bot from its record. Revocation ends the grant immediately; the saved pages and the record remain for review.

    Control commitments

    No unlogged Bit-Bots, ever.

    This is the suite's standing refusal, applied to every Bit-Bot. Read the philosophy for the full list of what we will not build.

    • 01

      Human in command

      Bit-Bots propose, draft, gather, and organize. A person approves anything consequential — and can redirect or stop the work at any point.

    • 02

      Contained by design

      Single-active workspaces with permission jails. No silent scope expansion: anything outside the grant needs a new approval.

    • 03

      Auditable always

      Grants, actions, approvals, and denials recorded in readable language, so any outcome can be reconstructed and reviewed.

    Begin

    Name the work, keep the authority.

    Request access to ALPHA Bit-Bots, or enter ALPHA Studio today to work inside the same discipline.

    Request access Enter ALPHA Studio