Repository navigation
Models and runtimes
Model: weights and inference endpoint, for example a local vLLM-served open-weight model. Gateway: approved routing, credentials, budgets and reporting (for example LiteLLM). Harness: Hermes or an independently reviewed runtime, with its own native agent loop. Control plane: ACP's durable identity, policy, conversations, approvals and task ledger. No one of these subsystems replaces the others.
Route by task requirements (latency, context, tool use, code quality, cost, privacy, hardware) and actual available inventory. A fast answer should not consume an H200 merely because it exists. Preserve model ID/revision, runtime, inference route, relevant parameters, task/run IDs, duration and approval evidence. A “deep reasoning” color/status should reflect observed work, not a manually selected fictional state.
Provider keys are optional for a self-hosted supported route. A local model is not a self-hosted copy of a closed OpenAI/Claude service or an entitlement to their proprietary weights. Never silently fall back from private inference to a remote paid provider without consent.
Hermes is the first runtime adapter; Paperclip multi-agent pilots and other harnesses require an explicit sandbox, identity isolation, budgets, timeouts, cancellation, audit trails and human approval for mutations. ACP does not become a second Kubernetes/Slurm scheduler. Run code through typed, constrained resources; never hand unbounded cluster-admin tokens to a prompted model.
Test denial with wrong principal, timeouts, cancelled tool calls, failed model route, excessive token budgets, loss of worker session cache, replay, worker restart and recovery. Validate a second harness using the same canonical conversation, not a fresh chat that merely resembles it.
References: model routing design, harness sandbox model, Paperclip pilot.
ACP
- Home
- Architecture
- Researcher guide
- Clients and integrations
- Models and runtimes
- Operator runbook
- Developer guide
- API and data contracts
- Security and tenancy
- Troubleshooting
- Contributing
- Guide help and support Engineering reference
- Database RLS and migrations
- Memory lifecycle and provenance
- Harness lifecycle and continuity
- ACP release and conformance
- Agent security checklists