Docs
Learn the hosted capability boundary from concept to conformance.
CHP docs are organized around the protocol primitives independent hosts and callers need to share: capabilities, hosts, adapters, registry, invocation, policy, context, evidence, composition, and conformance.
Documentation IA
Start with meaning, then implement the protocol.
Each documentation path keeps a concrete hosted capability example close to the formal definition.
Introduction
Start with the category, mental model, and protocol boundary.
Concepts
Protocol primitives that every host and caller needs to share.
Guides
Practical implementation paths from capability map to governed invocation.
Examples
Concrete hosted-capability models for operational domains.
Reference
Stable notation, lifecycle, policy, field, outcome, and terminology references.
Failure Modes
Concrete request/outcome examples for first-class protocol failures.
Comparisons
How CHP differs from adjacent protocols and infrastructure categories.
Core path
Read the concepts before the schema.
The concept path gives implementation teams shared language for the parts of the protocol that must stay portable.
Finds an available qualified technician and reserves a service window.
Policy boundary
Approval requiredmanager_approval
A manager must approve technician scheduling before the host returns a confirmed appointment.
Invocation trace
- 01 Actor
Planning Agent
- 02 Capability
schedule_technician
- 03 Host
ServiceOpsHost
- 04 Policy
manager_approval
- 05 Context
job_context
- 06 Result
Confirmed Appointment
Example-first docs
Every major concept includes a concrete capability.
Docs should prove the boundary with a manifest, invocation, policy state, outcome, or evidence example before asking readers to trust abstract protocol language.
{
"id": "service-ops-host",
"version": "0.1.0",
"protocol_version": "0.1",
"kind": "service",
"capabilities": [{
"id": "schedule_technician",
"version": "1.0.0",
"description": "Reserve a qualified technician.",
"status": "experimental",
"modes": ["sync"],
"emits": ["execution_started", "execution_completed", "execution_denied"],
"policy": {
"risk_tier": "high",
"auth_required": true,
"approval_required": true
}
}],
"evidence": {
"store": "local-append-only",
"append_only": true
}
}Comparisons
Place CHP beside adjacent systems without blurring the boundary.
The comparison pages explain when CHP complements APIs, MCP tools, service mesh, and workflow automation.