> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Key concepts

> The stable concepts used across Forge, how they relate, and the design principles behind them.

Forge separates who performs work, how it runs, what it may reach, how it is governed, and how it
is operated.

## Workforce

People and agents are workers with identity, organizational placement, relationships, and access.
Agent definitions add models, prompts, skills, and tools. Read [Workforce](https://docs.gloo.com/forge/concepts/workforce.md),
including [Personal agents](https://docs.gloo.com/forge/concepts/workforce.md#personal-agents).

## Workflows and runs

Workflows are versioned graphs; runs are durable executions of a published version. Factories,
schedules, triggers, ingress, files, outcomes, and human tasks build on that lifecycle. Read
[Workflows and runs](https://docs.gloo.com/forge/concepts/workflows-and-runs.md), [Outcomes](https://docs.gloo.com/forge/concepts/outcomes.md), and
[Use the Workflow Architect](https://docs.gloo.com/forge/build/use-workflow-architect.md).

## Capability

Tools expose callable operations. Skills contribute reusable instructions and tool groupings.
Procedures run deterministic code in a sandbox. Capability providers resolve business operations
to integrations without exposing vendor credentials to the worker. When a workflow needs a skill,
agent, or procedure that does not exist yet, [synthesis](https://docs.gloo.com/forge/run/synthesis-budgets-and-curator.md)
can create a provisional one for review. Read [Tools and skills](https://docs.gloo.com/forge/concepts/tool-registry.md),
[Procedures](https://docs.gloo.com/forge/concepts/procedures.md), and [Capabilities](https://docs.gloo.com/forge/concepts/capabilities.md).

## Governance

Roles and grants establish possible authority. Trust Fabric evaluates a concrete action and returns
a decision. Human tasks record approvals and requested input. Judges produce quality or policy
signals; they do not replace authorization. Read [Trust Fabric](https://docs.gloo.com/forge/concepts/trust-fabric.md),
including its [Judges](https://docs.gloo.com/forge/concepts/trust-fabric.md#judges) section.

## Knowledge

Knowledge records and synchronized sources provide governed context. Source access and record scope
continue to apply after ingestion. Read [Knowledge](https://docs.gloo.com/forge/knowledge.md).

## Platform and operations

Convex persists platform state and runs backend orchestration. Sandboxes isolate code execution.
Observability, cost, audit, and emergency controls make running work inspectable and controllable.
Read the [system overview](https://docs.gloo.com/forge/architecture/system-overview.md) and
[Observability](https://docs.gloo.com/forge/run/observability.md).

## Relationship summary

A caller starts a published workflow. Each node resolves a worker and its versioned configuration.
The worker uses assigned tools or procedures; capability bindings reach external systems. Access and
runtime governance decide whether each action proceeds. Runs, files, decisions, usage, and outcomes
become operator evidence.

## Design principles

Forge makes several choices that affect how you build and operate on the platform.

### Persist intent before effects

Durable operations record intent and state around external effects. A timed-out write is still an
unknown outcome: retain its idempotency key and reconcile state before another logical intent.
Read [Idempotency](https://docs.gloo.com/forge/reference/idempotency.md).

### Separate possible authority from runtime decisions

Roles and scoped grants establish possible authority. Token scopes only narrow it. Runtime
governance evaluates the concrete action and can still refuse or hold it. Read
[Credentials and access](https://docs.gloo.com/forge/get-started/credentials-and-access.md).

### Keep secrets behind capability boundaries

Agents and procedures request operations; providers resolve integrations and credentials.
Sandboxes receive short-lived procedure sessions, not vendor secrets. Read [Capabilities](https://docs.gloo.com/forge/concepts/capabilities.md).

### Version executable definitions

Agents, workflows, procedures, skills, and tools have lifecycle and version semantics. Publishing
is deliberate, and editing a draft does not rewrite an in-flight run.

### Treat human interaction as durable work

An approval or request for input has identity, eligibility, state, and history. Design for expiry,
rejection, reassignment, and no response. Read [Approvals](https://docs.gloo.com/forge/run/approvals-and-hitl.md).

### Prefer explicit refusal to partial success

Sensitive operations fail closed when authority or provenance is missing. Bounded reads disclose
paging or truncation. Branch on structured errors and metadata; do not infer completeness.

### Keep interfaces distinct

Console is for people, API v3 for deterministic integrations, and MCP for model-usable tasks and
searchable operations. Read [Choose an interface](https://docs.gloo.com/forge/get-started/choose-an-interface.md).

### Evidence does not remove judgment

Forge can record what ran, who decided, and what it cost. Evidence may still be bounded or
insufficient, and an allowed action may have a bad outcome. Operational review remains necessary.

Use the [glossary](https://docs.gloo.com/forge/concepts/glossary.md) for exact vocabulary and the [architecture overview](https://docs.gloo.com/forge/architecture/system-overview.md)
for system boundaries.

## Related

* [Glossary](https://docs.gloo.com/forge/concepts/glossary.md): one definition per term.
* [System overview](https://docs.gloo.com/forge/architecture/system-overview.md): how the parts run together.
* [Quickstart](https://docs.gloo.com/forge/quickstart.md): create an agent and run a workflow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.