01 · One useful product
Solve the pain already in front of the user.
Kungfu earns attention by keeping Work alive across the Agents the user already chooses.
Agent Supply Chain
When Agents learn to recognize better software, they start creating demand for it.
Kungfu onboards the Agent you already use. The Agent experiences explicit capabilities, inspectable evidence, and durable Work—then starts expecting those qualities from every product.
01 · The ignition
One useful product can change what an Agent expects.
Kungfu earns the first use by solving a concrete problem. The surprise comes next: the experience changes how the Agent evaluates every product that follows.
02 · One onboarded Agent
Let the Agent experience the difference.
A version-matched Brief exposes exact capabilities, evidence, limits, public actions, and durable state inside the existing conversation.
03 · One new expectation
Change what good software feels like.
After one useful handoff, the Agent can recognize—and ask for—the same qualities in every product it encounters.
Agent-assisted activation
The product has already been chosen.
A person or upstream channel discovers and selects the product. The Agent compresses the path from that choice to first value.
Agent-mediated distribution
The Agent can help make the choice.
The product becomes legible enough for an Agent to evaluate and recommend. A human or Hub still authorizes adoption.
Maturity and authority boundary. This loop is a product contract, not a blanket release claim. Each step remains bounded by the proved-now, enabled-by-protocol, and not-claimed evidence below. Agent output alone grants no authority and proves no completion.
02 · The self-accelerating market
Kungfu can leave the center. The loop keeps compounding.
Kungfu does not need to own the loop. It only needs to make the first difference legible.
The loop after KungfuNo Kungfu dependency inside the cycle
-
Agent experience
Agents recognize the difference.
Explicit capabilities, inspectable evidence, and durable Work become a product expectation.
-
Demand signal
Agents recommend. Humans or Hubs authorize.
A bounded recommendation during real work turns one useful experience into visible demand without granting the Agent adoption authority.
-
Builder response
Builders see what the market now expects.
A shared product interface becomes a distribution advantage instead of bespoke integration work.
-
Buildchain supply
More products can ship the qualities.
Buildchain binds KFD-3 declarations and KFD-2 evidence to exact releases that Agents can inspect.
-
More products
The next Agent encounters a larger market.
Each new Agent-native product can restart the same loop without routing through Kungfu.
↩ Next product → next Agent → the same expectation compounds.
Self-accelerating is not self-starting. Every product still needs a first introduction and explicit authorization. What compounds is what happens after the first useful, trusted use.Enabled, not claimed. This is a causal adoption thesis enabled by the stack, not evidence that a broad network effect, external adoption, or a multi-Hub market already exists.
03 · The inevitable questions
Once you see the loop, the infrastructure stops looking abstract.
The names arrive after the need. Each part of the stack answers a question the self-accelerating market makes unavoidable.
KFD-3
How does an Agent know what a product can do?
Discover how products cooperate through inspectable value, constraints, choices, commands, Exit, and records.
Explore KFD-3 →KFD-2
How does it assess what the product claims?
Assess claims for a declared purpose while retaining residual risk and decision ownership.
Explore KFD-2 →Buildchain
How do builders ship those qualities in an exact release?
Bind product-owned declarations to exact source, build, artifact, checks, and promotion evidence.
Explore Buildchain →Agent Hub portability
How can bounded Work move across independently governed Agent Hubs?
Carry bounded responsibility objects across independently owned products with receiver-owned admission.
Explore Agent Hub →Human authority remains explicit. Humans and Hubs set goals, permissions, budgets, policy, admission, and revocation. Agents propose and act inside those boundaries. Durable Work and evidence do not belong to the chat.
04 · The evidence behind the thesis
Five responsibilities. Independent owners. One inspectable path.
Now inspect what is proved, what is only enabled, and who owns each responsibility. Kungfu is an open Agent Supply Chain protocol stack for discovering how Agent products cooperate, binding claims to exact software artifacts, establishing purpose-bound trust, preserving durable work facts, and carrying that work across independently owned Hubs.
01 · proved-now
KFD-3
Owner · KFD
Discover how products cooperate through inspectable value, constraints, choices, commands, Exit, and records.
- Input
- Product-owned value, constraints, choices, commands, Exit, and record declarations
- Output
- A stable human-and-agent discovery surface for bounded cooperation
Evidence and known limit
Exact evidencenpm:@kungfu-tech/kfd@1.0.0-alpha.41#README.md
Known limitKFD-3 discovery is inspectable product guidance, not a hidden prompt or forced adoption mechanism.
02 · proved-now
Buildchain
Owner · Buildchain
Bind product-owned declarations to exact source, build, artifact, checks, and promotion evidence.
- Input
- KFD-3-discoverable product declarations and an exact source cut
- Output
- Artifact-bound provenance, checks, and promotion evidence
Evidence and known limit
Exact evidencenpm:@kungfu-tech/buildchain@2.14.14-alpha.4#dist/site/product-mechanism.json
Known limitBuildchain does not create product facts or make the receiver's trust decision.
03 · proved-now
KFD-2
Owner · KFD and receiver
Assess claims for a declared purpose while retaining residual risk and decision ownership.
- Input
- Exact-artifact evidence, a declared purpose, and receiver policy
- Output
- A purpose-bound assessment with residual risk and decision ownership
Evidence and known limit
Exact evidencenpm:@kungfu-tech/kfd@1.0.0-alpha.41#decisions/KFD-2.md
Known limitKFD-2 is purpose-, cut-, and evidence-bound; it is not a company reputation score or universal trust certificate.
04 · proved-now
libkungfu
Owner · Kungfu and adopter
Preserve admitted work facts, Episodes, roots, export, and recovery evidence while applications own domain facts.
- Input
- Receiver-admitted work facts, commands, Episodes, and roots
- Output
- Ordered durable records, export, recovery, and qualification evidence
Evidence and known limit
Exact evidencegit+https://github.com/kungfu-systems/kungfu.git#7eeb5bd1b45492f4da27eaacbe63eddfd6245176:docs/qualification/vendor-agent-hub-embedding.md
Known limitApplications retain authority over domain facts; libkungfu owns admitted runtime records and ordering within its declared boundary.
05 · enabled-by-protocol
Agent Hub portability
Owner · KFD profile and each Hub
Carry bounded responsibility objects across independently owned products with receiver-owned admission.
- Input
- Bounded responsibility objects with rooted evidence and explicit authority
- Output
- Portable envelopes, conformance results, and receiver-owned admission decisions
Evidence and known limit
Exact evidencenpm:@kungfu-tech/kfd@1.0.0-alpha.41#protocols/agent-hub/manifest.json
Known limitThe public profile enables independent implementations but does not prove a second independent production Hub.
Proved now
4 exact layers
KFD-3 · Buildchain · KFD-2 · libkungfu
Enabled by protocol
1 bounded layer
Agent Hub portability
Not claimed
6 explicit boundaries
Capability, conformance, adoption, and endorsement remain separate claims.
Not claimed
Protocol capability is not market adoption.
- two independent production Hubs
- external vendor adoption or endorsement
- industry-standard status
- universal trust or blanket stable compatibility
- public Kungfu Cloud
- lossless one-click migration
Bounded evaluation: Assign a technical and product owner, run a bounded 30-day assessment, build one adapter or conformance spike, submit protocol gaps, then decide to adopt, co-shape, or monitor.
Follow the questions
Explore the infrastructure the loop demands.
The market thesis leads naturally to a product language, an exact-release supply chain, and portable Work across independently governed Agent Hubs.