oh-my-pi boundary

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

Boundary and evidence

This run analyses oh-my-pi's shipped coding-agent runtime and its state, context and memory mechanisms. Its intended use is to establish how the system operates from pinned implementation and declared contracts, not to assess deployment quality or recommend Commonplace adoption. The target is in scope as an enclosing runtime: its own CLI constructs sessions and an agent that dispatches model requests. It is not merely a client library embedded in an excluded application.

The package declares its executable directly (SRC-1, packages/coding-agent/package.json):

"bin": { "omp": "src/cli.ts" }, --- packages/coding-agent/package.json

The inspected entry path runs from CLI command routing through the root launch command to runRootCommand, then createAgentSession, AgentSession and the core Agent. The SDK supplies the agent's model, tools, context transforms and streaming function. These are shipped callers, not external hosts (SRC-1, packages/coding-agent/src/cli.ts, packages/coding-agent/src/commands/launch.ts, packages/coding-agent/src/main.ts, packages/coding-agent/src/sdk.ts). The core loop admits prompts to its context before running the model/tool loop (SRC-1, packages/agent/src/agent-loop.ts):

messages: [...context.messages, ...prompts], --- packages/agent/src/agent-loop.ts

await runLoop(currentContext, newMessages, config, signal, stream, streamFn, prompts); --- packages/agent/src/agent-loop.ts

State production and later consumption belong to the target. Initial inspection found session message append, resumed-context reconstruction, CLI resume/fork selection and memory-backend selection. Backend contracts include startup subscriptions, prompt instructions, explicit retention and recall preparation; their implementations remain to be traced, so these contracts do not establish successful memory operation (SRC-1, packages/coding-agent/src/session/session-manager.ts, packages/coding-agent/src/sdk.ts, packages/coding-agent/src/main.ts, packages/coding-agent/src/memory-backend/resolve.ts, packages/coding-agent/src/memory-backend/types.ts).

deobfuscateSessionContext(sessionManager.buildSessionContext(), obfuscator), --- packages/coding-agent/src/sdk.ts:1940-1979

if (id === "hindsight") return (await import("../hindsight/backend")).hindsightBackend; if (id === "mnemopi") return (await import("../mnemopi/backend")).mnemopiBackend; if (id === "sharpshooter") return (await import("../sharpshooter/backend")).sharpshooterBackend; if (id === "local") return localBackend; return offBackend; --- packages/coding-agent/src/memory-backend/resolve.ts

The frozen artifact is the entire registered repository at 2431e8a8716a4da73ae327a412f6d54c22f681e5. HEAD matches the acquisition pin and the checkout reports no tracked or untracked changes. The applicability cutoff is 2026-10-14, the supplied run date, not a claim that the implementation remained unchanged through that date. The overall tier is code-grounded. No target execution, test run, provider request or experiment was performed.

The boundary kind is complete artifact, partial loop, not whole-system. The repository tree and primary entry/caller chain were inspected, but initial inspection has not covered every material shipped state producer and consumer. The following inventory separates included-but-not-yet-inspected material from deliberate exclusions. All included paths at the registered commit remain eligible for subsequent inspection; this is not a path allowlist.

There is no known inaccessible file in the frozen checkout. Uninspected available files are coverage limits, not access gaps. No execution trace or controlled intervention was supplied; therefore the source can establish executable structure and attributed intent, not observed success, comparative efficacy or causality. Later revisions, linked external pages and other repositories are outside this evidence pin.

Source register