Core Concepts
PreviewThe objects and vocabulary that appear throughout the Pimsy platform.
Nine objects describe almost everything Pimsy does. Learning them makes the rest of this documentation navigable.
Primary objects
Objectivestringrequired- The outcome the user wants. Objectives are stated as goals, not instructions: "find out why checkout fails and fix it" rather than "read this file".
Taskobject- The durable unit of work created from an objective. Holds capabilities, budgets, completion criteria and lifecycle status. See Tasks.
Runobject- One execution attempt of a task. A task may have several runs if it is resumed, retried or forked. See Runs.
Planobject- The decomposition of an objective into ordered or parallelizable steps, revised as evidence arrives. See Planning.
Stepobject- A single bounded action: a reasoning pass, tool call, sub-agent delegation or verification check. See Steps.
Toolobject- A declared capability with a schema, permission scope and execution contract. See Tools.
Memoryobject- Retained, retrievable knowledge separated into conversation, project, episodic, semantic and working stores. See Memory.
Artifactobject- A durable output — file, repository, dataset, report, transaction record — produced by a run. See Artifacts.
Policyobject- A rule constraining what the runtime may do: capability scopes, spend limits, approval requirements, allowlists. See Permission System.
Lifecycle#
queued ──▶ planning ──▶ running ──┬──▶ awaiting_approval ──▶ running
│
├──▶ verifying ──┬──▶ completed
│ └──▶ running (revision)
├──▶ failed
└──▶ cancelledCapability scopes#
Capabilities are requested per task and intersected with the key scope and the workspace policy. The effective set is always the narrowest of the three.
Last updated 2026-09-08