The model in one page#

What are the pieces, and how do they fit?

Two ideas run through all of it. Use credentials without reading them: a credential lives in the vault, the vault makes the call or hands a program a placeholder, and the credential goes only where a human said it may go. A machine never does more than the person or team that owns it.

The pieces#

• An account is one human: their passkeys, recovery codes and sessions. It belongs to any number of workspaces.
• A workspace is where everything else lives, isolated from every other workspace:
  • People: members with a role (owner, admin, member, guest), and teams of members.
  • Credentials: each one an item with a destination (its binding), rules (its policy) and a home (the workspace, one project, or one member privately).
  • Machines: enrolled devices, each owned by a member or a team, each with a scope that can only narrow what its owner may do.
  • Projects: coding projects with environments and variables, shared with people or teams at a level.
  • Asks and approvals: the links a human opens, and the decisions they sign with a passkey.
  • The audit chain: a hash-linked record of what happened.
• mehen is the command line on each machine, with mehen mcp for agents that speak MCP and mehen run for project variables.

A request from an agent goes through the same steps every time: the machine signs it with its own key, the vault checks the machine's owner and scope, the credential's binding and policy, and the environment's protection, then either makes the call, asks a human, or refuses with the next step.

The concept pages#

• Workspaces and people: what is a workspace, and who is in it?
• Machines: what is a machine, and what may it do?
• Credentials: what is a credential, and where may it go?
• Policy: what decides whether a request goes through?
• Intakes and connections: how does a credential get into the vault?
• Approvals: who approves what, and how?
• Needs you and asks: what is an ask, and where does it show up?
• Projects, environments and runs: how do projects, environments, variables and mehen run work?
• Audit, review and freeze: what is recorded, and how do I stop things?

The rules#

Ten rules shape every page here; What Mehen protects, and what it does not lists them.