\x3C!-- AUTO-GENERATED from SKILL.template.md. Edit the template, not this file. -->

name: coherence-network description: "Coherence Network: an open intelligence platform that traces every idea from inception to payout — with fair attribution, coherence scoring, and federated trust. Works out of the box with the public API at api.coherencycoin.com (no local node required). Install the CLI with npm i -g coherence-cli for the fastest path. Use this skill to: browse and rank ideas by ROI and free-energy score, search feature specs with implementation summaries, trace full value lineage (idea→spec→implementation→usage→payout), inspect contributor ledgers and coherence-weighted payouts, fork and stake on ideas, explore cross-instance federation and governance voting, surface friction signals and runtime telemetry, track idea progress and showcase validated work, or pick the next highest-ROI task automatically. Triggers on: coherence network, ideas, specs, lineage, contributions, assets, traceability, trust, freedom, uniqueness, collaboration, portfolio, ROI, coherence score, fair attribution, value chain, payout, governance, federation, friction, staking, forking, resonance, showcase, cc cli, coherence cli." metadata: { "openclaw": { "emoji": "🔗", "requires": { "bins": ["cc"] }, "install": [ { "id": "node", "kind": "node", "package": "coherence-cli", "bins": ["cc"], "label": "Install Coherence CLI (npm)", }, ], "env": { "COHERENCE_API_URL": { "description": "Coherence Network API base URL", "default": "https://api.coherencycoin.com", "required": false, }, "COHERENCE_API_KEY": { "description": "API key for write operations (governance, spec creation, federation). Read-only access works without a key.", "required": false, }, }, }, }

Coherence Network

An open intelligence platform where every contribution is traced, scored, and fairly attributed — from the spark of an idea to the moment it delivers value.

Production API: https://api.coherencycoin.com (always use this, not Railway or any other host) Web: https://coherencycoin.com

First run — zero-config bootstrap

On first use, the skill auto-registers. No setup, no API key, no identity required to start.

cc status

This works immediately. If cc is not installed yet, run npm i -g coherence-cli first.

Identity is optional but recommended. To get credit for contributions:

cc identity link github \x3Cyour-github-handle>

That's it. No account creation, no API key, no registration form. Your GitHub handle becomes your persistent identity across all sessions and nodes.

OpenClaw session protocol (bidirectional messaging)

OpenClaw loads this skill when a session starts. Check the inbox before any other work so messages from other federation nodes are not missed. Any node can send traffic with cc msg or structured cc cmd; the recipient sees it on the next inbox poll.

Start of every session (in order):

1. cc inbox — list messages for this node (CLI: resolves your node_id from hostname, then GET /api/federation/nodes/{node_id}/messages?unread_only=false&limit=20; unread messages are marked in the output).
2. cc status — confirm API health and operational signals.

If the inbox has messages, surface them to the user and confirm before acting on them.

During / end of session: use cc msg, cc cmd, or POST /api/federation/nodes/{node_id}/messages to reach peers; they will appear in the recipient’s next cc inbox.

Roadmap: Phase 2 — OpenClaw webhook push (requires OpenClaw gateway API). Phase 3 — real-time WebSocket bridge between CC federation and the OpenClaw gateway.

Two ways to use it

Option A: CLI (recommended for agents)

cc status                   # Works immediately — no setup needed
cc ideas                    # Browse the portfolio
cc share                    # Submit an idea

The cc command talks directly to the public API at api.coherencycoin.com. All commands output to stdout for easy parsing. No local server required.

Option B: curl (no install needed)

CN_API="https://api.coherencycoin.com"
curl -s "$CN_API/api/health" | jq '{status, version, uptime_human}'

Both approaches hit the same API. Use whichever fits your context.

How it works

Idea → Research → Spec → Implementation → Review → Usage → Payout
       ↑                                                    ↓
       └────────── coherence scores at every stage ─────────┘

Every stage is scored for coherence (0.0–1.0) — measuring test coverage, documentation quality, and implementation simplicity. Contributors are paid proportionally to the energy they invested and the coherence they achieved.

Ideas — the portfolio engine

Ideas are the atomic unit. Each is scored, ranked, and trackable through its entire lifecycle.

CLI:

cc ideas                    # Browse portfolio ranked by ROI
cc idea \x3Cid>                # View idea detail with scores
cc share                    # Submit a new idea (interactive)
cc stake \x3Cid> \x3Ccc>          # Stake CC on an idea
cc fork \x3Cid>                # Fork an idea

curl:

# Browse portfolio
curl -s "$CN_API/api/ideas?limit=20" | jq '.ideas[] | {name, roi_cc, free_energy_score, manifestation_status}'

# Search by keyword
curl -s "$CN_API/api/ideas/cards?search=federation&limit=10" | jq '.items[] | {id, name, description}'

# Showcase, resonance, progress, health, count
curl -s "$CN_API/api/ideas/showcase" | jq .
curl -s "$CN_API/api/ideas/resonance" | jq .
curl -s "$CN_API/api/ideas/progress" | jq .
curl -s "$CN_API/api/ideas/count" | jq .

# Deep-dive: scores, progress, activity, tasks
curl -s "$CN_API/api/ideas/IDEA-ID" | jq '{name, potential_value, actual_value, confidence, free_energy_score, roi_cc}'
curl -s "$CN_API/api/ideas/IDEA-ID/progress" | jq .
curl -s "$CN_API/api/ideas/IDEA-ID/activity" | jq .
curl -s "$CN_API/api/ideas/IDEA-ID/tasks" | jq .

# Actions (write)
curl -s "$CN_API/api/ideas/select" -X POST -H "Content-Type: application/json" -d '{"temperature": 0.5}' | jq .
curl -s "$CN_API/api/ideas/IDEA-ID/stake" -X POST -H "Content-Type: application/json" -d '{"contributor_id":"alice","amount_cc":10}' | jq .
curl -s "$CN_API/api/ideas/IDEA-ID/fork?forker_id=alice" -X POST | jq .

Specs — from vision to blueprint

CLI:

cc specs                    # List specs with ROI metrics
cc spec \x3Cid>                # View spec detail

curl:

curl -s "$CN_API/api/spec-registry?limit=20" | jq '.[] | {spec_id, title, estimated_roi, value_gap}'
curl -s "$CN_API/api/spec-registry/cards?search=authentication" | jq '.items[] | {spec_id, title, summary}'
curl -s "$CN_API/api/spec-registry/SPEC-ID" | jq '{title, summary, implementation_summary, pseudocode_summary, estimated_roi}'

Value lineage — end-to-end traceability

The lineage system connects every idea to its specs, implementations, usage events, and payouts.

curl -s "$CN_API/api/value-lineage/links?limit=20" | jq '.[] | {id, idea_id, spec_id, implementation_refs}'
curl -s "$CN_API/api/value-lineage/links/LINEAGE-ID/valuation" | jq '{measured_value_total, estimated_cost, roi_ratio}'
curl -s "$CN_API/api/value-lineage/links/LINEAGE-ID/payout-preview" \
  -X POST -H "Content-Type: application/json" \
  -d '{"total_value": 1000}' | jq '.rows[] | {role, contributor, amount, effective_weight}'

Identity — 37 providers, auto-attach

Link any identity to attribute contributions. No registration required — just provide a provider and handle.

CLI:

cc identity                         # Show linked accounts
cc identity setup                   # Guided onboarding
cc identity link github alice-dev   # Link GitHub
cc identity link discord user#1234  # Link Discord
cc identity link ethereum 0x123...  # Link ETH address
cc identity lookup github alice-dev # Find contributor by identity
cc identity unlink discord          # Unlink

curl:

# Link any identity (37 providers: github, discord, telegram, ethereum, solana, nostr, linkedin, orcid, did, ...)
curl -s "$CN_API/api/identity/link" -X POST -H "Content-Type: application/json" \
  -d '{"contributor_id":"alice","provider":"github","provider_id":"alice-dev"}'

# List all providers
curl -s "$CN_API/api/identity/providers" | jq '.categories | keys'

# Reverse lookup
curl -s "$CN_API/api/identity/lookup/github/alice-dev" | jq .

# Get all linked identities
curl -s "$CN_API/api/identity/alice" | jq .

Contribute by identity (no registration):

# Record a contribution using provider identity instead of contributor_id
curl -s "$CN_API/api/contributions/record" -X POST -H "Content-Type: application/json" \
  -d '{"provider":"github","provider_id":"alice-dev","type":"code","amount_cc":5}'

Contributions & assets

CLI:

cc contribute                # Record any contribution (interactive)
cc status                    # Network health + node info
cc resonance                 # What's alive right now

curl:

curl -s "$CN_API/api/contributions?limit=20" | jq '.[] | {contributor_id, coherence_score, cost_amount}'
curl -s "$CN_API/api/contributions/ledger/CONTRIBUTOR-ID" | jq .
curl -s "$CN_API/api/contributions/ledger/CONTRIBUTOR-ID/ideas" | jq .
curl -s "$CN_API/api/assets?limit=20" | jq '.[] | {id, type, description, total_cost}'

Tasks — agent-to-agent work protocol

The task queue is the backbone of agent-to-agent coordination. Any AI agent with cc installed can pick up work, execute it, and report back.

CLI (recommended for agents):

cc tasks                    # List pending tasks
cc tasks running            # List running tasks
cc task \x3Cid>                # View task detail (direction, idea link, context)
cc task next                # Claim the highest-priority pending task
cc task claim \x3Cid>          # Claim a specific task
cc task report \x3Cid> completed "All tests pass"   # Report success
cc task report \x3Cid> failed "Missing dependency"   # Report failure
cc task seed \x3Cidea-id> spec # Create a spec task from an idea

When piped (non-TTY), cc task next outputs raw JSON for programmatic consumption.

curl:

# List tasks by status
curl -s "$CN_API/api/agent/tasks?status=pending&limit=10" | jq '.tasks[] | {id, task_type, direction, context}'

# Claim a task
curl -s "$CN_API/api/agent/tasks/TASK-ID" -X PATCH -H "Content-Type: application/json" \
  -d '{"status":"running","worker_id":"my-node"}'

# Report result
curl -s "$CN_API/api/agent/tasks/TASK-ID" -X PATCH -H "Content-Type: application/json" \
  -d '{"status":"completed","result":"All tests pass"}'

# Seed a task from an idea
curl -s "$CN_API/api/agent/tasks" -X POST -H "Content-Type: application/json" \
  -d '{"task_type":"spec","direction":"Write spec for idea X","context":{"idea_id":"my-idea"}}'

Federation & governance

CLI:

cc nodes                          # See all federation nodes
cc msg broadcast "Update ready"   # Broadcast to all nodes
cc msg \x3Cnode_id> "Run tests"      # Message a specific node
cc cmd \x3Cnode> diagnose            # Structured command
cc inbox                          # Read messages

curl:

curl -s "$CN_API/api/governance/change-requests" | jq .
curl -s "$CN_API/api/federation/nodes" | jq .
curl -s "$CN_API/api/federation/nodes/capabilities" | jq .
curl -s "$CN_API/api/federation/strategies" | jq .

Friction, runtime & agent health

curl -s "$CN_API/api/friction/report?window_days=30" | jq .
curl -s "$CN_API/api/agent/effectiveness" | jq .
curl -s "$CN_API/api/agent/collective-health" | jq .
curl -s "$CN_API/api/agent/status-report" | jq .
curl -s "$CN_API/api/coherence/score" | jq .

The five pillars

The Coherence Network ecosystem

Every part of the network links to every other. Jump in wherever makes sense.

MCP server

For AI agents that support MCP (Model Context Protocol), Coherence Network exposes an MCP server at:

npx coherence-mcp-server

This provides typed tools that any MCP-compatible agent (Claude, Cursor, Windsurf, etc.) can invoke natively. See references/mcp-server.md for tool definitions.

Write safety

Before executing any POST/PATCH/DELETE request, always confirm with the user. Read operations (GET) are safe to run freely.

API reference

For the full endpoint table (100+ endpoints across 20 resource groups), see references/api-endpoints.md.