Ultimate boundary

Type: agentic-system-analyses/types/agentic-system-boundary.md

Boundary and evidence

This run analyses Ultimate as the shipped local coding-agent application, not just its memory API or its Pi Durable integration. Its intended use is a project-specialized agent with a browser UI, standing agents, coordinator branches, bounded subagents and extensible tools. The target is in scope because its server opens and resumes a model-driven harness and its shipped callers submit inputs and consume stored conversations. It is an enclosing runtime at the application boundary, even though model execution and durable scheduling use external packages. The boundary kind is whole-system: the supervisor, server, browser client, built-in extensions, prompts, project configuration and maintenance paths are included together. SRC-1: README.md, package.json, bin/ultimate.ts, server/main.ts, server/harness.ts, server/api.ts, web/src/sdk/api.ts.

A coding agent you specialize for the project you work on. Start it in your repository and it is Pi's coding agent in a web UI. --- README.md

The executable entry is ultimate → bin/ultimate.ts; development can enter through server/main.ts. The supervisor forks that server, gates replacement with a type check, releases the old storage owner and activates the new one. The server prepares extensions and API services, opens storage and resumes the harness. The browser's submit endpoint is a shipped consumer, not an excluded host application: it reaches conversation.submit in the same system. SRC-1: package.json, bin/ultimate.ts, server/main.ts, server/api.ts, web/src/sdk/api.ts.

const child = fork(join(ultimateRoot, 'server/main.ts'), [], { --- bin/ultimate.ts

storage = await openNodeSqliteStorage(chapter.database) --- server/harness.ts

The functional boundary includes state production, persistence, admission and later consumption. Initial project memory is instructed through onboarding; remember and landing-triggered distillation maintain root memory. Branch creation consumes a memory index and recent landings instead of the root's full tally when memory exists. The memory tool and recall hook retrieve fuller content later. Compaction, catch-up, memory review and dream/chapter handover are included maintenance paths, not external editorial work. These statements identify paths for later analysis; they do not establish successful recall, faithful summaries or effective self-improvement. SRC-1: agents/ultimate.md, extensions/lineage/server.ts, extensions/lineage/memory.ts, extensions/recall/server.ts, extensions/dream/DREAM.md, extensions/dream/seed.ts.

The model text a branch from root starts from instead of its tally, read inside tx before its first table * write; undefined while the root has no memories. tip is the root's newest entry. --- extensions/lineage/memory.ts

Only @ultimate writes project memory; tell @ultimate what to remember (message, reply: false). --- extensions/lineage/server.ts

Recalled from project memory for the message above. Act on each that applies, and say so in one line when it changes what you do: --- extensions/recall/server.ts

The checkout is frozen at e2b9fa61962f6aecd394dea1c670688fac3ec432. Its HEAD matched acquisition and its working tree was clean on inspection. The applicability cutoff is 2026-11-01, the supplied run date, not a claim about any later upstream state. Overall evidence is code-grounded. Documentation and agent instructions supply doctrine/design; inspected source supplies implementation evidence. Test source supplies intended executable checks, not observed passing runs. No target, tests, examples, model calls or external services were executed.

Shipped coverage

Every top-level tracked entry is classified below. All included entries remain inside the registered commit for later source inspection. “Not yet inspected” means available but not initially read in detail, never an access gap. Whole-system describes the functional scope and traced loop, not a claim that every file has already been audited. All repository path references in this table refer to SRC-1.

External dependencies and limits

Pi Durable, Pi Coding Agent, Pi AI, Chord, codemode/MCP adapters and the Claude Code provider are external dependencies, not additional frozen repositories. Their declared versions and the shipped patches are in scope; their complete upstream implementations are unavailable within this evidence set. The inspected harness demonstrates Ultimate's integration calls, not the internal crash consistency or scheduling correctness of those packages. SRC-1: package.json, pnpm-workspace.yaml, server/harness.ts.

Model providers, Claude Code CLI, Chromium/browser execution, Git, Tailscale and cloud services are environmental dependencies. Local adapter source and UI remain in scope; actual credentials, live installations, remote instances, user/project additions outside this checkout and production databases/traces are not supplied. This prevents conclusions about live service reliability, realized cross-machine behavior, actual user customization, token costs and retention outcomes. The source's own operational claims may be attributed but are not observed runs. SRC-1: README.md, docs/running.md, server/project.ts, server/harness.ts.

No material shipped path was inaccessible during initial inspection. Files explicitly marked not yet inspected are available under the same pin; they must be read before making detailed claims about their behavior. The traced persistence and memory loop supports a whole-system scope without excluding the prompts, maintenance procedures, callers or evaluators that give that loop its purpose.

Source register