Skip to main content
The full protocol specification and architecture are maintained in the repository as Markdown.

SPEC.md

SPEC.md covers:
  • Design goals (protocol composability, deterministic execution, least-privilege, hierarchical orchestration, progressive context hydration)
  • Core concepts (Context, Orchestrator, Executors)
  • Runtime behavior: orchestrator vs executor, data flow, what is shared
  • Shared input/output model
  • Executor types (agent, tool, human)
  • Nested orchestration
  • Mounts (seed, focus, deep) and Ref objects
  • Policies and protocols
  • Orchestration strategies (single, sequential, delegate, swarm)
  • Triggers, schemas, context inputs/outputs
  • Security model
Use it as the authoritative protocol document when implementing runtimes or tooling.

Host system configuration

Machine- and project-local ecp.config.yaml (system config) is specified in the same document: Host system configuration (ecp.config.yaml). It covers the version field, the split between configure sections and the security mirror, MCP tool plugins, and A2A endpoint shape. The annotated example is config/ecp.config.example.yaml.

ARCHITECTURE.md

ARCHITECTURE.md documents plugin registration and architecture decisions.

Schema and types

  • JSON Schema: packages/spec/dist/ecp-context.schema.json (generate with npm run generate:schema)
  • TypeScript types: packages/spec/src/types/ecp.ts (single source of truth)
See Schema reference for details.

Repository

PathDescription
spec.yamlCanonical example Context
SPEC.mdFull protocol specification
SETUP.mdInstall, CLI, env, config
SPEC.md — Host system configurationFull ecp.config.yaml spec (v0.5+ security mirror)
config/ecp.config.example.yamlAnnotated system config example (validated in repo tests)
ECPSystemConfig (types.ts)TypeScript reference for system config
ARCHITECTURE.mdPlugin registration and architecture
packages/spec/Types, JSON Schema, validators
packages/runtime/Execution engine
packages/cli/CLI implementation
examples/Example Context manifests