Why Kungfu?
A name with a recursive promise.
Kungfu began with the Chinese idea of 功夫: capability earned through disciplined practice. The name did not begin as an acronym. Its recursive technical meaning came later.
KUNGFU = KUNGFU UNGFU: Never Guess. Facts Unfold.
The name came first
Kungfu was chosen for its original association with practice, internal capability, and foundations that make visible techniques possible. That history remains real; the project does not rewrite it as a newly discovered acronym.
The recursive definition is a later technical commitment carried by the same name. Kungfu UNGFU™ is the source-identifying signature for that commitment; Kungfu remains the product name.
The recursion
Removing the outer Kungfu name leaves UNGFU, which expands back into itself. The project describes the relationship explicitly:
KUNGFU = KUNGFU + UNGFU + Never + Guess + Facts + Unfold
UNGFU = UNGFU + Never + Guess + Facts + Unfold
UNGFU is not a second product or runtime. It is a compact expression of how Kungfu should behave.
Never Guess
Kungfu does not prohibit hypotheses, estimates, or human judgment. It requires the boundary between them and observed facts to remain visible.
A model claim, inferred state, or optimistic completion report must not silently become a load-bearing fact.
Facts Unfold
Facts do not interpret themselves. They become useful through explicit schemas, provenance, causal context, projections, and observer policy.
Kungfu records local runtime evidence so cost, state, proof, and next actions can be reconstructed instead of guessed.
The project obligation
Read the full definition
The open-source repository carries the canonical technical explanation, including semantic boundaries and its mapping to Facts, Episodes, Projections, Timelines, Proof, Product Layers, and Buildchain.