Pilot Plan

Glossary

Glossary

Terms and concepts used throughout the Pilot codebase.


Package Naming

Directory vs. npm Name

Directory Pathnpm Package NameDescription
@core/ai@repo/aiAI CLI commands
@core/base@repo/baseDomain modeling
@core/query@repo/queryQuery builder
@core/lint@repo/lintESLint config
@core/typescript@repo/typescripttsconfig presets
@core/ui@repo/uiCore UI components
@packages/chamber-ui@repo/chamber-uiOpenChamber UI
@packages/frontend@repo/frontendRuntimeAPIs adapters
@packages/backend@repo/backendHono app factory
@packages/domain@repo/domainDomain models
@packages/shared@repo/sharedShared contracts
@services/app@pilot/appMain web app
@services/gateway@pilot/gatewayAPI gateway
@services/chamber@pilot/chamberChamber frontend
@services/runtime@pilot/runtimeRuntime orchestrator

Naming Convention

  • @core/* and @packages/* use @repo/ npm scope (internal packages)
  • @services/* and @demos/* use @pilot/ npm scope (deployable artifacts)

Architecture Terms

Planes

TermDefinition
Control Plane@pilot/gateway - handles auth, session, routing decisions
Runtime Plane@pilot/runtime - executes workloads, manages instances
App Plane@pilot/app - hosts browser application

Canonical Package

A package that is the authoritative owner of a specific domain. Other packages should not duplicate its functionality.

Example: @repo/backend is the canonical owner of RuntimeAdapter interface.

Adapter

An implementation that bridges two interfaces. Used for:

  • RuntimeAdapter: Bridges backend to runtime (LocalAdapter, MockAdapter)
  • RuntimeAPIs: Bridges frontend to backend (terminal, files, git adapters)

Tier-1 / Tier-2 Endpoints

TierDefinitionExamples
Tier-1Critical endpoints required for core functionalityterminal, fs, git, session, health
Tier-2Supporting endpoints, can be added incrementallygithub, push, skills, quota, tts

Tier-1 parity gates migration decisions.


Upstream Terms

Upstream

The external source repository that Pilot packages derive from.

UpstreamRepositoryOur packages
OpenChambergithub.com/btriapitsyn/openchamberchamber-ui, frontend, backend
OpenCode@opencode-ai/sdkUsed as dependency

Baseline

The specific upstream version we're tracking. Currently: v1.6.8

Divergence

Any change from upstream. Categories:

  • Integration glue: New files for Pilot integration
  • Bug fix: Fixes that could be upstreamed
  • Feature addition: Pilot-specific features
  • Intentional removal: Upstream features we don't use

Manifest

A document recording a sync event with upstream. Located in @plan/sync/openchamber/manifests/.


Code Annotations

@pilot:divergence

// @pilot:divergence embedded prop for app integration
export function App({ embedded = false }: AppProps) {

Marks code that intentionally differs from upstream. Include reason.

@pilot:note

// @pilot:note this may conflict with upstream 1.6.9 ContextPanel feature

Marks code that needs attention or has context not obvious from code alone.


Service Status Terms

StatusDefinition
ActiveIn production or active development
NewRecently created, being built out
DeprecatedScheduled for removal, should not add features
DecommissionedRemoved, no longer exists

Plan Terms

TermDefinition
PlanAn execution plan for a specific goal
TaskA unit of work within a plan
PhaseA group of related tasks
P0/P1/P2Priority levels (P0 = immediate, P2 = can wait)
SupersededPlan replaced by a newer plan

Runtime Terms

RuntimeAPIs

The interface that chamber-ui uses to communicate with the backend. Defined in @repo/frontend.

interface RuntimeAPIs {
  runtime: RuntimeDescriptor
  terminal: TerminalAPI
  git: GitAPI
  files: FilesAPI
  settings: SettingsAPI
  permissions: PermissionsAPI
  notifications: NotificationsAPI
  github?: GitHubAPI
  push?: PushAPI
  tools: ToolsAPI
}

RuntimeAdapter

The interface that backend uses to communicate with runtime instances. Defined in @repo/backend.

interface RuntimeAdapter {
  identity: RuntimeIdentity
  capabilities(): Promise<RuntimeCapabilities>
  health(): Promise<RuntimeHealth>
  proxy(request: Request, targetPath: string): Promise<Response>
}

Instance

A running OpenCode process in an isolated environment (container, worker, etc.).

Orchestrator

The component that manages instance lifecycle (create, destroy, health check).


Build Terms

Catalog

Centralized dependency versions in pnpm-workspace.yaml. Use catalog:<name> in package.json.

Workspace Reference

Use workspace:* to reference local packages in package.json.


Abbreviations

AbbrevFullContext
FEFrontend@repo/frontend, browser code
BEBackend@repo/backend, server code
CFCloudflareCloudflare Workers deployment
SSEServer-Sent EventsReal-time streaming
SDKSoftware Development Kit@opencode-ai/sdk
ADRArchitecture Decision RecordDocumented decision
POCProof of ConceptDemo/experiment