Without KFD
- Local operation is unchanged.
- Every external Hub connection needs a custom bridge.
- Handoff, retry, verdict, conflict, and exit semantics remain proprietary.
For Agent Builders
Build your Hub. Don’t rebuild the runtime.
Our ambition is deliberately narrow: make KFD the standard interoperability protocol and libkungfu the local runtime. You build and own the Hub.
The adoption decision
Without KFD, your Hub still works. It stays an island.
KFD does not make your Hub possible. It replaces a growing set of custom Hub-to-Hub bridges with one responsibility boundary.
With KFD
- One protocol boundary works across conforming Hubs.
- Rooted work, receipts, and verdicts remain portable.
- Each side keeps its runtime, policy, cloud, users, and admission authority.
The Builder contract
Kungfu does not compete for your Hub.
The Hub is the highest-value product layer, and it remains entirely yours. Kungfu makes the capability layer beneath it interoperable—without entering your customer relationship.
- Your users stay yours. Your accounts and billing stay yours.
- Your models, UI, and Agent stay yours. Your product policy stays yours.
- Your cloud stays yours. Your customer relationship stays yours.
Kungfu does not cross this product and customer boundary. Integration is not a channel into your customer relationship.
Portable responsibility and evidence between independent systems. KFD requires no central Kungfu cloud.
A public capability layer for durable local facts and action continuity—not a wedge into your Hub.
- 01 · BoundarySee where KFD and libkungfu sit.
- 02 · ActionSee what responsibility must survive.
- 03 · ProofAudit one unit before the totals.
- 04 · StartIntegrate the smallest bounded path.
01The KFD-libkungfu network
One protocol boundary. Independently owned Hubs.
libkungfu lives inside an adopting Hub. KFD connects its edge so independently owned Hubs can exchange rooted responsibility without sharing one runtime, database, identity provider, cloud, or customer relationship.
Builder-owned boundary
Qualified first-party reference adopter
Everything inside this box remains part of the Builder’s product.
Product plane
Your Agent Hub
Users · UI · models · Agent · accounts · billing · cloud
↓Host Runtime API · actions + local outcomes
Local runtime
libkungfu
Journal · Fact cuts · Episodes · Warrants · recovery · works locally without KFD
↓optional cross-Hub export
Optional Hub edge
KFD adapter + exchange store
Profile roots · capabilities · idempotency · portable records
Protocol boundary only
KFD Agent Hub profile
1capabilities ↔ capabilities
2rooted proposal →
3← transport receipt
4← receiver verdict
Local call · IPC · file · HTTP · gRPC · message bus · offline bundle
Independently owned boundary
Independent conforming implementation · not yet claimed as adopted
The receiver does not need Kungfu and never imports the reference side’s trust.
Product plane
Independent Agent Hub
Its users · UI · models · accounts · workflows · cloud
↑accepted facts + responsibility
Receiver authority
Local policy + verdict writer
Identity · Warrant · admission · disclosure · conflict · completion
↑assess delivered exchange
Hub edge
KFD adapter + exchange store
Original bytes · roots · receipts · idempotency · export
Transport statecreated → offered → delivered
delivery ≠ admission
Semantic stateunassessed → assessing → admitted / rejected / conflicted
- Local peer
- Single-vendor cloud
- Multi-organization federation
- Offline device
No central KFD authority: no required global identity provider, Hub registry, database, transport, clock, or KFD cloud.
Bytes arrived; the receiver still owns the verdict.
An Episode happened; success still needs independent assessment.
Identity control does not prove permission, truth, or fact admission.
02Why action semantics are necessary
An action is a loop through reality, not a row in a workflow.
A KFD exchange cannot be only an RPC payload. For another Hub to evaluate and continue the work, responsibility must preserve why the action was pursued, what was known, what was allowed, what happened, and what the receiver accepted. libkungfu preserves those coordinates.
- Fact Cut NWhat is admitted now?
A rooted view of accepted state, not every observed claim.
- Action GeometryWhy, from what view, under whose authority?
- Pursuit · why
- Atlas · what is known
- Warrant · what is allowed
- ActionBinding → ActBind the decision, then cross into reality.
Changing a Fact, intent, view, permission, action, or resource creates a different binding. Tool success alone does not settle meaning.
- Episode → Inspect + admitWhat happened, and what is accepted?
Receipts and consequences become evidence; local policy admits, rejects, degrades, or conflicts the resulting claims.
- Fact Cut N+1What may safely happen next?
The successor cut starts the next loop without rewriting history.
next action loop
Semantic source: Fact, Episode, and Action runtime.
03Dogfood · public and auditable
The mechanism is building Kungfu itself.
The totals matter only after the unit of proof is clear. Each retained path connects real work to an exact Cut, independent review, and a released result.
Public work → exact Cut → independent review → release
Read one proof unit before the rolling 30-day totals.
Purpose, source cut, authority, and acceptance are explicit.
Source, receipts, and known gaps bind the result being claimed.
A separate review checks the exact result and evidence.
Production closes the path without inflating the claim.
Loading the append-only observation chain from libkungfu.dev…
Adjacent observations compare overlapping rolling P30D windows; they do not count work newly created in one week.
Retained fallback: Live verified history is loading.
Counting boundary: A PR is a work item, not a feature count. An account is not an Agent actor. A review-search match is not an approval.
04A bounded starting path
Inspect. Integrate. Prove.
The current evidence supports a bounded first-party reference path—not certification or broad vendor adoption.
Ask the installed product first.
Run one Kungfu command to execute the fixed KFD Hub 20 suite, see what passed in plain language, retain rooted evidence, and keep the non-claims visible.
Open the executable proof pathChoose the smallest language path.
Review the source-linked C, Node, or Python quickstart. No registry install command is claimed where a public package does not yet exist.
Open exact quickstart sourcesKeep the adapter narrow.
Project bounded lifecycle events into the runtime while prompts, tool payloads, provider data, models, and credentials remain outside the reference adapter.
Audit the reference integrationBind evidence to exact authority.
Use KFD conformance reports and Buildchain release evidence to state only what the exact suite, platform, source, and residual-risk roots support.
Audit the Passport integrationStart with one bounded adapter.
Inspect the exact reference source first. Nothing in this path requires replacing your Hub, moving your customer relationship, or accepting a claim beyond the retained evidence.