Security · Identity

Know who is asking before deciding what they may do.

Draft for review. This page describes the proposed design. Features without a confirmed implementation status are marked for review; they are not claims of running controls.

An agent uses a model to reason and a harness to act. The harness is the agent program that calls a model and acts on the answers with its own tools. A seat is the confined environment in which the harness runs. A principal is a named identity to which permissions are assigned. A service is a program that provides a shared function. A key is a credential used to prove an identity. An administrator is a person with permission to change the system’s controls.

The identity outline gives each agent, service and person its own named principal. Permission should attach to that identity, so a request can be checked against the work it is allowed to do.

Design outline dated 6 October 2026. What the four status labels mean.

The proposed design

Each heading states the design or practice. Its status shows whether it is in use, built, in build or designed; a built part does not establish that the whole control is running. Where the outline gives no implementation status, that status awaits review.

  • One named principal per participant.

    The proposed design names each agent, service and person separately. A team name should not stand in for the identity of the participant taking an action.

    Implementation status awaits review.

  • Per-agent keys.

    The outline calls for a key associated with each agent’s identity. The page describes that separation without publishing actual keys or their installation.

    Implementation status awaits review.

  • Code has an identity too.

    The proposed design distinguishes the program acting from the agent’s name. Its code identity belongs in the checks and records surrounding a run.

    Implementation status awaits review.

  • People are first-class principals.

    The design treats people as named participants with permissions, rather than as an exception outside the identity model.

    • Designed

What this provides

The intended result is a permission decision and a record that refer to a specific participant, rather than to an indistinct shared team identity.

What is not yet proven

The outline does not confirm implementation status for all participant identities, per-agent keys or code identities. These remain review questions.

People as first-class principals are designed. This draft does not claim a completed system for multiple administrators or protection against an administrator.