The longer view

More of the intelligence, closer to the person.

Mack’s aim is for Orbit to work across the devices people already use: a computer for demanding work, a phone for access on the move, and other trusted devices where they genuinely help. Those devices could cooperate as a personal network, with the person deciding what each one may do.

A direction for Orbit, not a claim that a full mesh exists today.

Why it matters

Useful technology should fit into a life.

When every request must go through one distant service, people can lose sight of where their information travels and who controls the system they depend on. A network built around personal devices offers another design choice: keep suitable work nearby, give each device a clear role, and use outside services deliberately when they are needed.

That choice can make a system more adaptable and more accountable to its owner. It does not automatically make it private, efficient, or reliable. Those qualities have to be designed, tested, and maintained.

A possible arrangement

One person. Several trusted tools. Clear boundaries.

Workstation

Do the heavy lifting

Handle approved local files, applications, and work that needs more computing power.

Phone

Stay connected

Offer a simple way to ask, review, and respond while away from the desk.

Other devices

Join by choice

Contribute a specific capability only after enrollment and permission. A device need not run the whole system.

The illustration describes a design goal. It is not a map of Orbit’s current connections.

Secure by design

A mesh needs more than a connection.

Adding devices also adds places where things can go wrong. Orbit’s future network should make the safe choice the easy one.

  1. 01

    Know every device and person.

    Enrollment should be explicit. A familiar network address alone should never grant trust or inherit the owner’s permissions.

  2. 02

    Give only the access needed.

    Each request should be checked against the person, device, task, and information involved. A collaborator’s view must stay separate from Mack’s private workspace.

  3. 03

    Protect and recover.

    Connections need strong identity, protected communication, updates, a way to revoke access, and honest records of what happened. Lost or offline devices must fail safely.

What the vision does and does not mean

Ambition should stay grounded.

“AGI” is often used for a system with broad, general abilities. Orbit does not claim to have achieved that, or to operate a secure AGI mesh today. The idea is to build toward increasingly capable cooperation among trusted devices while keeping human permission and review at the center.

Reusing hardware may reduce the need for some new equipment, but active devices still consume power, and moving work between them has a cost. Orbit may also rely on outside providers for some tasks. The right balance needs measurement, not a promise of zero impact.

The thinking behind this direction

These independent references inform the security and resource questions; they do not certify Orbit’s implementation.