Glossary

These entries define product meaning. The typed contract remains authoritative for exact wire fields, and capability status remains authoritative for current support posture.

​

Organization and ownership

Organization — The administrative company or developer organization that contains one or more Tenants and Workspaces. Tenant — The mandatory Checkfu isolation authority below Organization. It normally remains implicit in builder-facing flows. Workspace — The normal resource, policy, and deployment boundary for Agents, Environments, Sessions, capabilities, governance, and Usage. Agent — Reusable mutable authored configuration. An Agent is not a running process, Session, or harness. AgentVersion — An immutable publication of Agent configuration. Session admission freezes one exact Version. Environment — Reusable execution authority selected at Session admission. It constrains the runtime tuple and other prerequisites that may realize work. ExternalInstallation: A Workspace-owned record of one external system tenant, created with a signed pairing proof, identified by exti_. See Installations and placement. AgentPlacement: An optional entry point for one Agent behind an ExternalInstallation, with an autonomous or delegated identity posture, identified by aplace_.

​

Durable execution

Session — The durable execution aggregate and ordered event history. It freezes AgentVersion and Environment authority, then remains the truth for Runs, waits, child lineage, recovery, and settlement. Specialized resources such as ActionApproval and Usage retain their own authority. SessionThread — The internal execution lineage a Session runs on; every Session has exactly one primary thread. It preserves lineage without creating another transcript authority and is not a public resource. Turn — A user-meaningful interaction boundary inside a Session. Run — One durable unit of execution inside a Session. RunAttempt — One fenced attempt to perform a Run. Retrying creates another attempt, not another Session history. Checkpoint — Continuation material bound to Session execution. It does not settle an external effect or make an uncertain effect safe to retry.

​

Resources and trust

File — Explicit retained content that can be attached to Agent work. MemoryStore — The authority for retained memory content and immutable MemoryVersions. Memory is distinct from Session events, Files, traces, and Credentials. MemoryVersion — An immutable publication in MemoryStore history. Skill — Reusable authored capability with immutable SkillVersions. Vault — The custody boundary for secret-bearing Credentials. A Vault grants nothing by itself. Credential — Secret-bearing material resolved only at a trusted effect boundary. Custodied values do not belong in Agent instructions, model context, harness configuration, Session events, or sandbox workloads. Connection — A governed nonsecret link to one external account or provider capability. A Connection is not a Credential or permission grant. PermissionAssignment — A scoped grant allowing a subject to use a governed resource. ActionPolicy — The rule that allows, denies, or requires ActionApproval for an exact action. ActionApproval — A durable human decision over one frozen consequential action. Approval is not execution. CustomTool — An operation declared by the admitted Agent and handled by customer code. Its ActionPolicy governs the call; it has no inherent Connection or PermissionAssignment gate. Audit — The trusted governance record for administrative and consequential actions. It is distinct from Session execution events and authoritative Usage.

​

Composition and delivery

Automation — Durable configured job and firing authority. AutomationRun — The execution record for one Automation firing. AutomationGraph — Versioned authored composition that plans and reconciles specialized resources. It is not another runtime consulted at each firing. Outcome — A recipe, not a resource: an ordinary Automation graph that runs an Agent, evaluates the work, and starts another attempt until the criteria pass or an authored attempt limit is reached. See Outcomes.

​

Metering and retention

Usage — Authoritative metering facts and reservations used for attribution, Budgets, and quotas. Usage is distinct from traces and application analytics. Budget — A limit enforced from authoritative Usage and reservations, not traces, estimates, or model narration. Zero-data retention (ZDR) — A posture that refuses persistence of prohibited execution content. ZDR is not standard retention with a shorter timer and can change recovery, replay, and export behavior.