Examples

If you only want the supported first steps:

• Docker smoke path: docker/
• Web backend path: hello-openapi-sidecar/, then hello-fastapi/
• Native ARC tool example: hello-tool/

This directory has two layers:

• flagship examples that show ARC as a real control plane in a multi-process or multi-operator setting
• small hello-* examples that isolate one surface at a time and can be understood in a few minutes

For a one-page map of what each example teaches, see EXAMPLE_SURFACE_MATRIX.md.

For web backends, the supported order is:

1. hello-openapi-sidecar/
2. hello-fastapi/

See docs/guides/WEB_BACKEND_QUICKSTART.md for the shared verification flow.

Current Flagship Examples

• agent-commerce-network/: buyer/provider/reviewer topology with approvals, budgets, settlement, federation, and live receipt capture
• internet-of-agents-incident-network/: recursive cross-org incident-response network with a live happy path for OpenAI SDK orchestration, MCP tools, ACP provider jobs, and offline review
• hello-tool/: minimal Rust-native tool example
• docker/: local containerized smoke path
• anthropic-sdk/, openai-compatible/, langchain/: ecosystem-specific slices

Hello Example Contract

The hello-* family follows one shared contract:

1. Expose one safe read path such as GET /hello or a discovery/list call.
2. Expose one governed path such as POST /echo, tool/invoke, or message/send.
3. Show the deny path without a capability token where applicable.
4. Show the allow path with a capability token or authoritative session.
5. Capture or print at least one ARC receipt or receipt id.
6. Ship with one smoke command.

Use the root runner to list or execute the current smoke set:

./run-hello-smokes.sh --list
./run-hello-smokes.sh hello-fastapi hello-fastify
./run-hello-smokes.sh

Implemented Hello Examples

Control Plane Adjuncts

Example	Surface	Runtime	Smoke
hello-trust-control/	Trust service + capability lifecycle + offline evidence verification	./run-trust.sh	./smoke.sh
hello-receipt-verify/	Captured evidence package + offline verification	fixture package only	./smoke.sh

HTTP Framework Surfaces

Example	Surface	Runtime	Smoke
hello-openapi-sidecar/	OpenAPI + arc api protect sidecar	./run.sh	./smoke.sh
hello-fastapi/	FastAPI + arc-asgi	./run.sh	./smoke.sh
hello-django/	Django + arc-django	./run.sh	./smoke.sh
hello-fastify/	Fastify + @arc-protocol/fastify	./run.sh	./smoke.sh
hello-elysia/	Elysia + @arc-protocol/elysia	./run.sh	./smoke.sh
hello-express/	Express + @arc-protocol/express	./run.sh	./smoke.sh
hello-chi/	Go chi + arc-go-http	./run.sh	./smoke.sh
hello-spring-boot/	Spring Boot + arc-spring-boot	./run.sh	./smoke.sh
hello-dotnet/	ASP.NET + ArcMiddleware	./run.sh	./smoke.sh

Protocol And Agent Surfaces

Example	Surface	Runtime	Smoke
hello-mcp/	MCP edge over stdio JSON-RPC	./run-edge.sh serve	./smoke.sh
hello-a2a/	A2A edge with authoritative send + deferred task lifecycle	./run-edge.sh serve	./smoke.sh
hello-acp/	ACP edge with invoke + deferred stream/resume lifecycle	./run-edge.sh serve	./smoke.sh

Build Order That Landed

1. hello-openapi-sidecar
2. hello-fastapi
3. hello-fastify
4. hello-chi
5. hello-express
6. hello-django
7. hello-elysia
8. hello-spring-boot
9. hello-dotnet
10. hello-mcp
11. hello-a2a
12. hello-acp

That sequence gave:

• one Python HTTP path
• one TypeScript HTTP path
• one Go HTTP path
• then the remaining framework wrappers
• then the protocol-native and agent surfaces

Standard Shape

Every hello example converges on roughly this structure:

hello-<surface>/
  README.md
  policy.yaml or config/
  run.sh or run-edge.sh
  smoke.sh
  app/ or src/

Adjunct Candidates

The next small examples should avoid reopening placeholder sprawl. The strongest next adjuncts are federation-aware follow-ons rather than more placeholders.

Relationship To agent-commerce-network

The hello-* examples are the small, surface-specific teaching layer.

The agent-commerce-network example is the “how these surfaces combine in the real world” layer.

The internet-of-agents-incident-network example is the “how recursive delegation, OpenAI SDK orchestration, MCP, ACP, and cross-org authority all compose together” layer.