Back to Core product mapimplemented-source / staged

C/C++, Python, Node and Rust remain thin surfaces over one native authority.

Each ecosystem package can qualify independently through clean install, capability discovery, the shared semantic fixture and the same .kungfu evidence path.

What this layer supports

Capabilities

C and C++ consume the installed Kungfu::kungfu coordinate.
Python and Rust start at kungfu_get_api and negotiate responsibility tables.
Node exposes the versioned storage contract over its current in-process native adapter.

Claim boundary

Known limits

Source and artifact gates do not themselves prove current public registry publication.
Stable compatibility and external adoption remain separate release claims.

Pinned authority

Inspect the exact upstream sources

semantic-authority docs/guides/libkungfu-abi-consumer.md sha256:67e32143c7e69bb3960d2d8be1f76699e5734df8dc9a178e2a302a51117adf5f
product-framing framework/storage/README.md sha256:187ca5846ef808eb41ab15e9b04f78c2c9db65840732a5db0e1d7868e02ba054
product-framing crates/kungfu-sdk/README.md sha256:c77c80fb73486026ea1bf4ea1b88adfb49cf60f57feec3da10e2fd67be1e2a5f
release-policy docs/qualification/layer-product-release-qualification.md sha256:ac656c090a11498284c49c348ebef3ae8bb40ecbb7759f3244e89d013d07acea