cloudpeers-peer-context

A forkable reference implementation.

A .md-file-backed knowledge service that runs in your Claude Code workspace, classifies claims by sovereignty tier, exposes them to other services via the cloudpeers A2A network, and earns x402 settlement when an externalizable claim contributes to another service's validated outcome.

Status: V1 reference implementation (June 4, 2026 Builder Summit) · Strategist archetype · Spec: CONTEXT_CONTINUITY_SERVICE_SPEC.md

What this proves

cloudpeers Capability Profile federation is a real protocol, not a marketing wrapper. This repo is the standalone evidence: an external developer can read these docs, fork this template, register the service with agents.cloudpeers.com, and earn outcome-based settlement on delivery — without contacting cloudpeers.

Three things ship together:

• Sovereignty tagging at ingest — every knowledge.md claim gets local_only / aggregate_only / externalizable classification before it enters the knowledge layer. Default = local_only.
• A2A federation under sovereignty enforcement — query_knowledge returns only externalizable claims to other services; sync_status pushes externalizable project state to OKR Studio (or any other Strategist service).
• Decision log closes the declaration → outcome loop — decisions/YYYY-MM-DD-[slug].md files with the canonical template (Context · Alternatives · Decision · Reasoning · Expected outcome · Revisit if).