Concepts

Resource hierarchy

Workspace
└── Project
    ├── identity and users
    ├── memory namespaces
    ├── capabilities and credentials
    ├── connections
    ├── policy ceiling
    ├── Agents
    └── releases, runs, approvals, usage, and audit

A Workspace is the team, billing, and trust boundary. A Project is one app. Project resources are connected once; each Agent selects exact subsets.

Desired state

The server-versioned Project head is authoritative. genaug-agent.yaml is its synchronized local working copy and uses apiVersion: genaug/v3.

Every governed change produces a semantic plan and, by default, one immutable Candidate release. Operational changes such as credential values, user memory corrections, and job execution are audited directly without pretending to be release source.

Agent

An Agent has a stable identity for runs and references. Its purpose, SOUL, skills, capability grants, memory grants, model, limits, guardrails, connections, and delegation are compiled from the exact release. Different Agents can use different SOUL and SKILL assets.

Hermes receives only that Agent’s compiled resources. It cannot discover another Agent’s ungranted OpenAPI, MCP, or direct-app operations.

Candidate and Live

Candidate and Live are pointers to immutable Project releases. Candidate is where reconciliation and hosted evidence happen. Live moves only after exact human review.

Developers can create and test Candidates. Workspace owners/admins can promote or roll back with a fresh interactive session and exact fingerprint confirmation.

Identity and memory

The host app remains the user identity authority. General Augment verifies its issuer/JWKS and maps a stable user claim to Project-isolated user and memory records. Agent memory grants select namespaces; they never collapse to Project-wide memory access.

Capability and connection

Capabilities are Project-owned operations from built-ins, OpenAPI, MCP, or signed direct-app callbacks. Connection declarations are release source; credentials and provider IDs are observed bindings. Shared resources remain installed while any Agent, Candidate, or Live release references them.

Continue with architecture or the quickstart.