Back to libkungfu.devComplete Kungfu product map
Start here · Kungfu adopters and runtime builders
Which Kungfu layer solves the continuity problem I have now?
Start with the complete product map, adopt only the layer you need, and inspect every maturity and authority boundary.
Kungfu product promise
Keep the work when the chat ends.
Kungfu helps a fresh agent continue the same real-world work without asking you to explain it all again.
One core, many complete products. Higher layers add convenience, never authority.
Status: The portable Spec and site bundles are qualified at 4.0.0-alpha.1; the complete product, public CLI and stable compatibility remain separate release claims.
Adopt only what you need
Six independently bounded product layers
libkungfu
Python, npm and Cargo SDKs
Standalone CLI and TUI
GUI
Assembled Kungfu App
Human and agent navigation
Open the layer, boundary, or evidence you need
.kungfu
Fact, Episode and Action Geometry
Runtime
Native ABI
SDKs
KFX and Domain Profiles
CLI, TUI, GUI and App
Qualification and release
ADR map
Domain horizons
Qualification before promotion