chp-server 0.60.2__tar.gz

chp_server-0.60.2/.github/workflows/release.yml

@@ -0,0 +1,96 @@
+name: Release
+
+# Publishes chp-server to PyPI + a GitHub Release. Fires ONLY on bare version tags
+# (v0.60.2, v1.0.0 — never rc tags, which go to staging.yml). Mirrors the chp-core
+# release flow, adapted for this single-package repo (the package is at the repo root).
+#
+# PREREQUISITE — PyPI trusted publishing (one-time, operator-side):
+#   On https://pypi.org/manage/project/chp-server/settings/publishing/ (or, if the project
+#   does not exist yet, add a "pending publisher" at https://pypi.org/manage/account/publishing/)
+#   register:  owner=capabilityhostprotocol  repo=chp-server  workflow=release.yml  environment=release
+#   No API token is stored — publishing uses OIDC (id-token: write below).
+#
+# Flow:  push v<version>-rc.N → staging.yml (green) → push v<version> → this workflow.
+
+on:
+  push:
+    tags:
+      - 'v*.*.*'
+      - '!v*.*.*-rc.*'   # RC tags → staging.yml only
+    branches-ignore:
+      - '**'             # tags only — branch pushes never trigger a release
+
+jobs:
+  verify-staged:
+    name: Verify a matching RC was staged
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository (full history for tags)
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Confirm a matching RC tag exists
+        run: |
+          VERSION="${GITHUB_REF_NAME#v}"
+          MATCHES=$(git tag --list "v${VERSION}-rc.*")
+          if [ -z "$MATCHES" ]; then
+            echo "ERROR: no RC tag found for v${VERSION}." >&2
+            echo "Push v${VERSION}-rc.1 and let staging.yml pass before the production tag." >&2
+            exit 1
+          fi
+          echo "Found RC tags: $MATCHES"
+
+  publish:
+    name: Build + publish chp-server to PyPI
+    needs: [verify-staged]
+    runs-on: ubuntu-latest
+    environment: release
+    permissions:
+      id-token: write     # PyPI trusted publishing (OIDC) — no stored token
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tooling
+        run: python -m pip install build
+
+      - name: Build (single package at repo root)
+        run: python -m build .
+
+      # The exact bytes built here go to BOTH PyPI and the GitHub Release.
+      - name: Upload dist artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist-chp-server
+          path: dist/
+
+      - name: Publish to PyPI (trusted publishing)
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/
+          skip-existing: true
+
+  create-release:
+    name: GitHub Release
+    needs: [publish]
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: Download the published dist
+        uses: actions/download-artifact@v4
+        with:
+          name: dist-chp-server
+          path: dist
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          files: dist/*
+          generate_release_notes: true

chp_server-0.60.2/.github/workflows/staging.yml

@@ -0,0 +1,48 @@
+name: Staging
+
+# Fires on release-candidate tags (v0.60.2-rc.1, v0.60.2-rc.2, …). All jobs must be green
+# before the production tag (v0.60.2) is pushed — release.yml refuses to publish without a
+# matching rc.* tag. Mirrors chp-core's RC→staging→prod discipline for this single-package repo.
+#
+# Flow:  push v<version>-rc.N → this workflow → (green) → push v<version> → release.yml.
+
+on:
+  push:
+    tags:
+      - 'v*.*.*-rc.*'
+    branches-ignore:
+      - '**'
+
+jobs:
+  test-and-smoke:
+    name: Tests + clean-venv build smoke
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      # chp-server's only mandatory dep is chp-core (pulled from PyPI by -e .). The suite
+      # also needs pytest + the schema/crypto libs the wire tests exercise.
+      - name: Install package + test deps
+        run: python -m pip install -e . pytest jsonschema cryptography
+
+      - name: Run test suite
+        run: python -m pytest tests/ -q
+
+      - name: Build the distribution (repo root)
+        run: |
+          python -m pip install build
+          python -m build .
+
+      # Prove the built wheel installs and imports with ONLY its declared deps — the
+      # one-dependency contract (chp-core alone) that a chp-server release must honor.
+      - name: Clean-venv install + import smoke
+        run: |
+          python -m venv /tmp/smoke
+          /tmp/smoke/bin/python -m pip install dist/*.whl
+          /tmp/smoke/bin/python -c "import chp_server; from chp_server import CapabilityServer, Server; print('chp-server import OK')"

chp_server-0.60.2/.gitignore

@@ -0,0 +1,13 @@
+# CHP evidence stores and session DBs must never be tracked or published.
+.chp/
+*.sqlite
+*.sqlite-shm
+*.sqlite-wal
+*.db
+
+# Build / cache
+__pycache__/
+*.egg-info/
+.pytest_cache/
+dist/
+build/

chp_server-0.60.2/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Project Auxo, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

chp_server-0.60.2/NOTICE

@@ -0,0 +1,18 @@
+Capability Host Protocol (CHP)
+Copyright 2026 Project Auxo, Inc.
+
+This product includes software developed by the CHP project contributors.
+
+Source code (packages/, conformance/, examples/, scripts/) is licensed under
+the Apache License, Version 2.0. See LICENSE for the full text.
+
+Specification, schemas, and documentation (spec/, docs/, schemas/) are
+licensed under the Creative Commons Attribution 4.0 International License.
+See LICENSE-DOCS for the full text.
+
+Implementing the specification is additionally covered by a royalty-free
+patent grant. See PATENTS for the full text.
+
+"Capability Host Protocol", "CHP", "CHP-Certified", and the CHP logo are
+trademarks of Project Auxo, Inc. Trademark use is governed by TRADEMARK.md
+and is NOT granted by the code or documentation licenses above.

chp_server-0.60.2/PKG-INFO

@@ -0,0 +1,224 @@
+Metadata-Version: 2.5
+Name: chp-server
+Version: 0.60.2
+Summary: Independently installable reference CHP server: assembles chp-core plus optional attachments behind truthful feature negotiation
+Project-URL: Homepage, https://github.com/capabilityhostprotocol/chp-server
+Project-URL: Issues, https://github.com/capabilityhostprotocol/chp-server/issues
+Author: Project Auxo, Inc.
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: capability-host-protocol,chp,evidence,governance,server
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: System :: Distributed Computing
+Requires-Python: >=3.11
+Requires-Dist: chp-core[schema]>=0.60.2
+Description-Content-Type: text/markdown
+
+# chp-server
+
+**Your node in CHP — a network of governed capabilities. One dependency. Runs anywhere.
+Every call is admission-gated and recorded as signed, replayable evidence.**
+
+[![PyPI](https://img.shields.io/pypi/v/chp-server.svg)](https://pypi.org/project/chp-server/)
+[![Python](https://img.shields.io/pypi/pyversions/chp-server.svg)](https://pypi.org/project/chp-server/)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+Run a **node** that serves capabilities (plain Python functions) over HTTP behind the full CHP
+pipeline — identity, admission, execution, and an append-only evidence chain, plus truthful
+feature negotiation, deadlines, and HA. A node is fully useful alone, and can point outward to
+**discover, compose, and federate** with others — *governed federation* is what makes it a
+network, not just a server ([what that unlocks](docs/the-network.md)).
+
+```bash
+pip install chp-server
+```
+
+One CHP dependency — `chp-core` (with its `schema` extra, so declared input schemas are
+*enforced*, not just described: the whole point of a governed node).
+
+## Quickstart — run a node, serve a capability
+
+```python
+from chp_server import CapabilityServer
+
+app = CapabilityServer("my-host")
+
+@app.capability("greet.hello")
+def hello(name: str = "world") -> dict:
+    "Greet a name."
+    return {"greeting": f"hello, {name}"}
+
+app.run(port=8800)
+```
+
+The **docstring becomes the description**, the **type hints become the input schema** — and
+the pipeline *enforces* it, denying a malformed call before your function runs — and payload
+fields arrive as **keyword arguments**. No descriptor boilerplate, no request parsing, no schema
+by hand.
+
+```console
+$ curl -s localhost:8800/invoke \
+    -H 'Content-Type: application/json' \
+    -d '{"capability_id": "greet.hello", "payload": {"name": "CHP"}}'
+{"outcome": "success",
+ "data": {"greeting": "hello, CHP"},
+ "correlation": {"correlation_id": "corr_b11dc07c…"},
+ "evidence_ids": ["evt_…", "evt_…"]}          # a signed, append-only chain
+
+$ curl -s localhost:8800/replay/corr_b11dc07c…
+{"events": [{"event_type": "execution_started"}, {"event_type": "execution_completed"}]}
+```
+
+That invocation was admission-gated, executed, and **recorded as a hash-chained evidence trail
+you can replay** — without you writing a line of middleware. `CapabilityServer` is thin sugar over
+the explicit host/attachment API you drop to when you need resolution, federation, or the
+distribute path (see the [serving guide](docs/serving-capabilities.md)). Prefer no code?
+
+```bash
+chp-server new mycaps           # scaffold a runnable starter you own, then: python mycaps.py
+chp-server serve --example      # a live node with sample capabilities, curl-able at once
+chp-server adapters             # list installed chp-adapter-* capability sets you can compose()
+chp serve                       # a truthful protocol-only node; attach capabilities when ready
+```
+
+Every `/invoke` prints a `correlation_id`; pipe its evidence through a readable view:
+
+```bash
+curl -s localhost:8800/replay/corr_… | chp-server replay
+#   correlation corr_…  (2 events)
+#     [9]  execution_started    greet.hello
+#     [10] execution_completed  greet.hello  → success
+```
+
+## Join the network
+
+Each rung stands alone — climb only as far as you need: **run your node** (above) → **serve** your
+capabilities → **discover** what others serve (`chp-server adapters`, `GET /host`) → **compose**
+them (`app.compose(...)`) → **resolve & federate** across nodes (`GET /resolve`) → **trust across
+boundaries** with signed evidence. Rungs 1–2 are the whole of many deployments; the rest is the
+outward axis — [the network](docs/the-network.md).
+
+## Set up with your AI agent
+
+Hand the setup to a coding agent. **Claude Code, Cursor, and Cline** can install and verify a node
+from [`llms-install.md`](llms-install.md) — paste this:
+
+```text
+Install and set up chp-server by following its llms-install.md. Steps: pip install chp-server;
+start a node with `chp-server serve --example --port 8800`; prove a governed call with a POST
+/invoke of greet.hello; then replay its evidence chain. Verify each step (health 200, outcome
+"success", execution_started + execution_completed) and report the correlation id. Add no
+dependency beyond chp-server.
+```
+
+Already running a CHP host? Provision the node **through** it so the install itself is evidenced —
+see [`agent/`](agent/install-chp-server.md) for a governed Agentkit skill + profile.
+
+---
+
+## What your node gives you standalone
+
+Everything below is real and exercised end-to-end by [`examples/demo.py`](examples/README.md) —
+with only `chp-core` + `chp-server` installed. This is the solo value: a node earns its keep
+before it ever talks to another one.
+
+| You get | What it means |
+|---|---|
+| **Governed invocation + evidence** | Every `/invoke` runs the full CHP pipeline and emits a signed, replayable chain (`/replay/{correlation}`). Nothing executes un-recorded. |
+| **Truthful feature negotiation** | `GET /server` (Server.Describe) reports each feature's *real* state (`ready` / `unsupported`), computed from live attachment health — never faked from package presence. |
+| **Honest long-running work** | A capability that can't answer yet returns `indeterminate` — not a fabricated success — and stays queryable without holding a connection open. |
+| **Absolute deadlines** | Send a `deadline`; a stale request is denied `deadline_exceeded` *before any effect runs*. |
+| **Tenant-scoped evidence** | Callers can only replay their own correlations; someone else's is `404`, not disclosed. |
+| **Restricted visibility** | A capability's `allowed_actors` policy hides it from discovery for callers outside it. |
+| **Capability resolution** | `GET /resolve` answers *where* a capability is served (endpoints), honoring lease/freshness — the basis for "invocable anywhere." |
+| **Active/standby HA** | Two instances of one logical host contend for an ownership lease; the active admits work, the standby fails closed with `server_not_active`. |
+| **Three discovery surfaces** | `/.well-known/chp` (bootstrap), `/capabilities.txt` (public hint), and authorized live `/host` — each with a distinct, honest purpose. |
+
+### See it all at once
+
+```bash
+python examples/demo.py
+```
+
+One self-contained script stands up real nodes and walks every surface above with a narrated
+trace — needing only `chp-core` + `chp-server`. See [`examples/README.md`](examples/README.md).
+
+---
+
+## The one-dependency principle
+
+The install pulls in **one CHP package — `chp-core`** (with its `schema` extra for input-schema
+enforcement; jsonschema is the only transitive). That is a deliberate contract, not an accident:
+a CHP node must be installable and runnable where every other CHP package is absent. Richer
+behavior — host exposure, local execution, resolution, MCP import/export, federation,
+Platform services — attaches through optional packages that register in the `chp_server.ports`
+entry-point group. **Feature truth is computed from attachment health, never from what happens
+to be installed**, so `GET /server` never overstates what the node can actually do.
+
+```python
+server.attach(ExistingHostPort(host))          # a pre-built governed host
+server.attach(DirectoryResolutionPort([...]))  # answer GET /resolve
+# ...MCP, federation, Platform, artifacts — each behind its own port role
+```
+
+## Profiles — fail-closed by construction
+
+A **profile** declares which port roles a node *requires*; boot fails closed if one is missing,
+so a node never silently comes up under-provisioned.
+
+| Profile | Requires | For |
+|---|---|---|
+| `protocol-only` (default) | — | the pure protocol surface; everything optional reports `unsupported` |
+| `host` | a governed host | serving your own capabilities (the quickstart above) |
+| `local` | host + execution | full local admission→execute→evidence |
+| `standalone` | + catalog/resolution | a self-describing single node |
+| `managed` / `edge` / `gateway` | Platform / federation roles | control-plane-backed and multi-node topologies |
+
+## Endpoints
+
+`GET /health` · `GET /ready` (reports role) · `GET /server` (Describe) · `GET /host` (authorized
+discovery) · `GET /capabilities` · `POST /invoke` · `GET /replay/{correlation}` · `GET /resolve` ·
+`GET /.well-known/chp` · `GET /capabilities.txt`
+
+## Discovery — read layer + act layer
+
+A node ships two well-known files, mirroring how agents already read the web:
+
+| Layer | File | Answers |
+|---|---|---|
+| **Read** | [`llms.txt`](llms.txt) | what's *worth reading* about this node (the llms.txt convention) |
+| **Act** | [`capabilities.txt`](capabilities.txt) | what a node can *do* — CHP's own [capabilities.txt](https://capabilitiestxt.org) convention |
+
+CHP adopts `llms.txt` and **owns the action layer**: `robots.txt` (may access) · `sitemap.xml`
+(exists) · `llms.txt` (worth reading) · **`capabilities.txt` (what a host can do)**. A live node
+serves its own at `GET /capabilities.txt` (a public hint) and bootstraps at `GET /.well-known/chp`;
+authoritative capability truth is the authenticated `GET /host`.
+
+---
+
+## Learn more
+
+- **Why this is a network, not just a server:** [`docs/the-network.md`](docs/the-network.md) —
+  the two axes, what governed federation unlocks, and the honest limits.
+- **Serve capabilities of your own:** [`docs/serving-capabilities.md`](docs/serving-capabilities.md)
+  — capability anatomy, the embed and distribute paths, evidence, policy, auth, deadlines.
+- **For LLMs & agents:** [`docs/agent-integration.md`](docs/agent-integration.md) — a recipe to
+  CHP-enable a codebase (wrap existing functions as governed capabilities).
+- **Expose it safely:** [`docs/public-exposure.md`](docs/public-exposure.md) — ingress auth/mTLS,
+  the governed ingress route, egress governance.
+- **Full walkthrough:** [`examples/demo.py`](examples/demo.py) + [its guide](examples/README.md)
+- **Protocol:** built on [`chp-core`](https://github.com/capabilityhostprotocol/chp-core), the
+  canonical CHP implementation (identity, evidence, signing, the 12-gate pipeline).
+- **Public API:** `CapabilityServer`, `Server`, `ServerConfig`, `ExistingHostPort`,
+  `DirectoryResolutionPort`, `FeatureRegistry`, `PROFILES` — see `chp_server.__all__`.
+
+Licensed Apache-2.0 (see `LICENSE`, `NOTICE`). This repository is a read-only public mirror;
+development happens in the private CHP workspace and syncs here.