Developer docs start with the public API boundary.
WCN is not publishing a public API claim before the boundary is ready. This page gives developers the current build surface: public docs, proof workflow concepts, and the waitlist path.
Current developer surface
- API status
- Public API boundary pendingMust not be marketed as an open API.
- Available now
- Wiki, System Atlas, Proof Ledger boundary, System Library
- Agent execution
- Described as a mechanism; public integration surface is unconfirmed
- GitHub / SDK
- Publish only after real URLs are confirmed
Proof workflow mental model
01
02
Submit reviewable evidence
03
Pass review and risk screening
04
Publish only anonymized summaries
05
Keep revocation and dispute boundaries
Where to start
Use the public pages to understand the workflow before asking for private integration material.
01
Understand the loop
Node → Deal → Task → Proof → Decision is the minimum developer path for understanding WCN.
See mechanism02
Understand public fields
Developers need to know what can be public and what must never appear in public interfaces.
View Proof Ledger03
Read the system library
The source system docs define the knowledge boundary for future APIs and agent workflows.
Open systems04
Join developer interest
Describe what you want to build, what boundary you need, and whether private data is involved.
Open contact routing