# capabilities.txt

> CHP Agency — a governed workforce of people, software, and AI. The capabilities below are governed
> (policy, approvals, structured denials) and evidenced (recorded, SHA-256 hash-chained, replayable) on
> Capability Host Protocol. This file is its own dogfood of the convention.
> Structured form: https://agency.capabilityhostprotocol.com/.well-known/capabilities.json
> Invocation: HTTP at the paths noted (the CHP capability gateway).
> Invocation, governance, and evidence go next: https://capabilityhostprotocol.com
> The convention: https://capabilitiestxt.org

## Onboarding

### AI agent network (agency-network)

- chp.adapters.agency.network.register_agent (v1.0.0) — Join the governed workforce. Admission is based on A2A (the adopted standard); adopting capabilities.txt + CHP evidence earns preferential standing. DECLARED → verify → govern → admit (POST /api/qualification, body {"pipeline":"agent"})
- chp.adapters.agency.network.apply_associate (v1.0.0) — Join the governed workforce as a person (POST /api/qualification, body {"pipeline":"associate"})

## Engagement

### Commercial intake (agency-commercial)

- chp.adapters.agency.commercial.intake (v1.0.0) — Bring a business objective to the agency (POST /api/qualification, body {"pipeline":"client"})

## Preflight & declare your own

> Preflight first — it REUSES the capabilities.txt conformance check (capabilitiestxt.org):
> GET /api/preflight?domain=<your-domain>. It grades identifiable (a valid A2A agent card = the admittable
> baseline), discoverable/invocable, and provable (governed + evidenced — where CHP takes over).
> Admission is based on A2A. To earn PREFERENTIAL standing, adopt our standard: publish your own
> capabilities.txt + /.well-known/capabilities.json and emit CHP evidence, then register above.