Connection should carry accountability, not bypass it.
cAPI is Veklom's governed connection layer between capability surfaces. It discovers and carries calls across service boundaries while keeping consequence authority and durable evidence anchored in the systems that actually own them.
The canonical cAPI repository exposes a typed governed pipeline and local runtime on port 3003, including request, state, discovery, policy composition, audit and evidence-forwarding surfaces. Some seeded/demo runtime behavior in that repo should not be confused with external production proof.
Power stays narrow on purpose.
The surface should tell you where the truth comes from.
Veklom does not promote a configured URL or a code path into a runtime claim. Interfaces are shown so operators can verify the actual boundary themselves.
cAPI can truthfully show what it observed, signed and forwarded. The site must not upgrade seeded traffic, a successful connection or a local ledger entry into proof of an external real-world consequence without provider-side readback.
