Govern · Products & services
Turn what your product can do into a governed boundary.
Every product already exposes abilities — query inventory, schedule service, generate an invoice. CHP lets you publish them as capabilities with stable identity, versions, permission requirements, and evidence, so agents and applications can call them through a contract that doesn't change quietly underneath them.
How it would work
A capability surface, declared.
A host manifest declares each capability — id, version, modes, the evidence it emits, and its policy. Callers discover what is available and how to call it safely; every invocation leaves a replayable record. The HTTP, OpenAPI, and GraphQL adapters already wrap existing APIs as CHP capabilities.
Demonstrated, not yet shipped: the manifest, invocation, and evidence primitives exist today. The managed product surface and its lifecycle tooling are what we build with a design partner.
{
"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
}
}Exposing capabilities to agents?
If callers depend on what your product can do, a governed boundary keeps that contract stable and provable. Bring the surface and we will map it onto the protocol with you.