Architecture

Preview

How the intelligence, runtime, action, financial and platform layers fit together.

Pimsy is organized into five layers. Each layer depends only on the interfaces of the layer beneath it, so subsystems can evolve independently.

System layers

┌──────────────────────────────────────────────────────────────┐
│  PLATFORM        API · SDKs · Auth · Observability · Deploy  │
├──────────────────────────────────────────────────────────────┤
│  DOMAIN          Markets Intelligence  │  Codebase Engine    │
├──────────────────────────────────────────────────────────────┤
│  ACTIONS         Tools · Connectors · Computer · Builder     │
├──────────────────────────────────────────────────────────────┤
│  AGENT RUNTIME   Planner · Scheduler · State · Checkpoints   │
│                  Verification · Multi-Agent Orchestration    │
├──────────────────────────────────────────────────────────────┤
│  INTELLIGENCE    Reasoning · Multimodal · Research · Memory  │
└──────────────────────────────────────────────────────────────┘
        ▲                                             │
        └──────────── observations / results ─────────┘

Request path#

1
Admission
The API validates the objective, resolves the caller key, intersects capability scopes and creates a task record.
2
Comprehension
The reasoning layer restates the objective, identifies ambiguity and extracts completion criteria. Ambiguity above threshold triggers a clarification event instead of a guess.
3
Planning
The planner emits a step graph with dependencies, tool hints and per-step verification requirements.
4
Scheduling
The scheduler dispatches ready steps, enforces budgets and parallelizes independent branches — including delegation to sub-agents.
5
Execution
Steps run against tools, execution environments, browsers, connectors or chain infrastructure. Every invocation is recorded.
6
Observation
Raw results are normalized into observations and written to working memory with provenance attached.
7
Verification
Checks run according to the step contract: tests, recomputation, source resolution, contradiction detection or verifier agents.
8
Synthesis
The orchestrator assembles artifacts, attaches the trace and confidence assessment, and closes the task.

Component responsibilities#

Component	Responsibility	Failure behaviour
Planner	Decompose objectives, revise plans on new evidence	Falls back to a linear plan; flags low-confidence decomposition
Scheduler	Dispatch, parallelism, budgets, cancellation	Halts dispatch, preserves checkpoint, marks run interrupted
Tool router	Select and invoke tools, normalize errors	Retries idempotent calls, escalates non-retryable errors
Memory service	Write, retrieve, score and consolidate memory	Degrades to conversation context only
Verifier	Apply step-level and task-level checks	Marks result unverified rather than passing silently
Policy engine	Evaluate every effectful action against policy	Denies by default; emits an approval request

Isolation boundaries#

Workspace — data, memory, connectors and artifacts never cross workspaces.
Run sandbox — each run receives an isolated filesystem and network egress profile. See Sandboxing.
Credential broker — connectors receive short-lived, scope-limited tokens; raw secrets are never placed in model context. See Secrets.
Effect gate — every write, purchase, message or transaction passes the policy engine before dispatch.

Last updated 2026-09-14