THE FOUNDATION

Trust is a boundary.
Then a relationship.

A teammate earns your trust by doing the little things well. These twelve rules are what make that possible on Proxima.

Proxima is in development. These are design commitments, not completed certifications. Every rule below has test status: at launch. We'll publish the results here as the product becomes available. The first release uses a separate container per teammate; stronger microVM isolation is planned before broader launch.

1. One teammate. One private world.

   A teammate cannot read another teammate's memory, conversations, files or logins.

   Test status: at launch

2. Your account stays yours.

   Another person's account cannot read your data. The boundary belongs in the database, too.

   Test status: at launch

3. Logins live outside the computer.

   A teammate uses a reference to a secret. A separate vault supplies it only to the service you connected. The teammate never holds the raw secret.

   Test status: at launch

4. Every bit of work has a name on it.

   Every model call is attributed to one teammate and checked against its share before it starts. You can see what used your plan.

   Test status: at launch

5. Your settings are the rules.

   An action outside the autonomy you gave a teammate cannot run. The check happens when the tool is called, including in routines.

   Test status: at launch

6. An email is data. Never an instruction.

   Web pages, emails and documents are marked as untrusted content. At launch we will publish both a check that every tool result is fenced and the measured pass rate of adversarial tests. No model is immune to prompt injection.

   Test status: at launch

7. The right access, for the right person.

   In a team account, each person sees only what their role allows. Team accounts are planned for a later release.

   Test status: at launch

8. Disconnected means disconnected.

   Revoke a connection and the next tool call is blocked. A running teammate does not get to keep using an old login.

   Test status: at launch

9. A share that actually stops.

   Each teammate pauses at its share. Usage cannot go over by more than one model call. There is no silent shared pool to drain.

   Test status: at launch

10. Take the wheel whenever you like.

    When you take over a computer, the teammate stops acting. You hand control back when you are ready.

    Test status: at launch

11. Delete means gone.

    Deleting a teammate destroys its computer, disk, memory, credentials and service identities. It leaves no working files on shared infrastructure. Actions already completed in connected services, such as sent emails, remain there.

    Test status: at launch

12. Only you can say yes.

    Approvals happen in the signed-in app or on your phone. Never through email, or any channel the teammate can read. Opening a notification link does not approve anything.

    Test status: at launch

Found something we should know?

Tell us at hello@hireproxima.com. Please keep sensitive details out of your first email so we can agree a safe way to share them.