# Checkfu documentation map

Checkfu is a managed-agent control plane that keeps product truth independent from one model, harness, sandbox, provider, or authoring interface.

## Canonical builder journey

Create or select Workspace
→ create Agent
→ configure Environment and model access
→ add tools, skills, Files, Memory, and Connections
→ start Session
→ stream events and handle approvals
→ add Automation, triggers, channels, or Computer
→ inspect Usage, Budgets, Audit, recovery, and retention

The runnable quickstart may stop after the first successful Session.

## Canonical model

- Organization contains the administrative relationship.
- Tenant is mandatory isolation authority and normally implicit.
- Workspace is the normal resource and policy boundary.
- Agent is reusable mutable configuration, never a running process.
- AgentVersion is immutable and frozen at Session admission.
- AgentBlueprint is a portable versioned package, not an Agent.
- AgentBlueprintApplication is the Workspace-local Blueprint plan/apply/reconcile journal.
- Environment is reusable execution authority selected at admission.
- Session is the durable execution aggregate and ordered event history.
- SessionThread and Turn organize child and user-meaningful work inside Session truth.
- Run is one unit of execution; RunAttempt is one fenced attempt.
- Vault owns Credential custody.
- Connection is a governed nonsecret link to an external account or provider capability.
- File, MemoryStore, MemoryVersion, Skill, and SkillVersion remain distinct resources.
- Automation owns firing; AutomationRun records a firing.
- AutomationGraph owns authored composition, not execution.
- Outcome owns bounded same-Session revision.
- Channel provides ingress and presentation around Session truth.
- Computer is provider-neutral; Screen is durable public observation.
- Usage is authoritative for Budgets and quotas.

## Authority boundaries

Session events are durable execution truth. Model Usage receipts, provider-effect custody, ActionApproval, Connection, MemoryStore, Audit, and other specialized aggregates retain their own authority while projecting relevant evidence into the Session.

Connected/platform action:
PermissionAssignment → ActionPolicy → optional ActionApproval → live Connection, revision, scope, Budget, and revocation re-check → trusted effect → Audit.

CustomTool declared by the admitted Agent:
ActionPolicy → optional ActionApproval → customer handler → user.custom_tool_result → same parked Run continues.

Approval is not execution. Uncertain external outcomes are indeterminate and require reconciliation rather than blind retry. Custodied Credential values never enter Agent instructions, model context, harness configuration, Session events, or sandbox workloads.

## Authoring

UI, HTTP, SDK, CLI, and MCP act through canonical resource operations. YAML and Git are desired-state inputs that compile or plan through those operations. Desired configuration has zero or one active authoring owner. Source forms are not another runtime, scheduler, policy authority, credential broker, transcript, or reconciler.

## Support and retention

A typed route, adapter, or deterministic fixture is not automatically deployed or supported. Capability posture combines typed audience, stability, availability, prerequisites, and qualifying evidence.

Standard retention and ZDR have different persistence, recovery, replay, export, and presentation semantics. Traces are diagnostic and do not enforce Budgets.

## Primary pages

- /getting-started/quickstart
- /getting-started/choose-a-path
- /getting-started/status
- /concepts/product-model
- /concepts/glossary
- /concepts/agents
- /concepts/work-environments
- /concepts/sessions-and-runs
- /concepts/capabilities
- /concepts/action-approvals
- /concepts/automations
- /concepts/channels
- /concepts/computer-and-screens
- /concepts/security
- /concepts/retention-and-zdr
- /concepts/agent-blueprints
- /reference/overview
- /reference/typescript-sdk
- /reference/mcp

## Source routing

- DOMAIN.md: timeless product meaning and invariants.
- packages/contract and generated OpenAPI: served HTTP wire.
- SECURITY.md plus executable controls: current security guarantees and limitations.
- VERIFICATION.md and verification/: shipped behavior and support evidence.
- LANGUAGE.md §0: final vocabulary while Plan 900 is active.
- RUNNING.md, DEPLOY.md, OPERATOR.md: current operational procedures.
- Generated surfaces: edit their named source and regenerate.