Developers

Build with Quuipu

Developers is the integration surface. Technology explains how Quuipu exists. Sub-areas are published only when public authority exists.

Integration boundary

Host website

Owns canonical content, routes, and visitor-facing authority.

Public Quuipu boundary

Host-mediated integration. Public contracts publish only when ready — internal packages are not public APIs.

Cognitive experience

Bounded organization and interaction with fallback to the host’s canonical presentation.

Understand vs integrate

Technology: How Quuipu exists — architecture, runtime, context, semantics, security.
Developers: How Quuipu is integrated — when public SDK/API documentation is ready.

Host boundary and progressive enhancement

The host website remains authoritative for canonical content. Quuipu attaches at a public boundary — it does not replace the site, invent facts, or silently redirect visitors.

Integration is progressive: when certified cognitive capability is not claimable, the host’s canonical presentation remains fully usable.

Canonical content stays on the host
Public contracts are published only when ready
Internal packages are not public APIs
Privacy-preserving public experience: no analytics or tracking in the current clean-room surface

Public readiness

Internal packages and contracts are not the same as a public SDK, public API, or supported integration.

SDK — deferred until public contracts exist
API — deferred until public contracts exist
Web Components — deferred
Integrations — deferred
Guides / Reference / Changelog — deferred
GitHub — deferred (no public repository authority)

The Cognisphere Web Protocol specification is available under Research.