Human-led software use
Attention comes before operation.
Software must first reach a person, who then evaluates it, learns it, and operates it directly.
Marketing→Human awareness→Install→Learn→Use
Agent Supply Chain
The next software user is an Agent.
Software use is shifting from humans directly choosing and operating every tool to Agents discovering, evaluating, selecting, and invoking tools within delegated authority.
01 · The transition
Software distribution is becoming Agent-mediated.
The important shift is not that Agents remove human authority. It is that more tool choice happens after a human or Hub defines the operating boundary.
Agent-mediated software use
Authority comes before selection.
A person or Hub sets the boundary; the Agent can then inspect and select tools while work is underway.
Human sets boundary→Agent discovers→Evaluates→Selects→Invokes→Records
02 · The selection advantage
Agent-first software can earn distribution through use.
Agent-first software can be discovered, evaluated, invoked, and continued with less bespoke interpretation, creating a new selection and distribution advantage. An Agent cannot choose what it cannot understand.
Discoverable
Value, constraints, choices, commands, Exit, and records are inspectable rather than hidden in marketing pages or prompts.
Evaluable
The Agent can compare a tool with the current goal, permissions, policy, and evidence before use.
Invocable
Documented machine interfaces reduce bespoke interpretation between product discovery and action.
Continuable
Durable work facts let a later Agent continue useful work without reconstructing it from chat history.
KFD-3 is the collaboration surface. It makes product-owned value, constraints, choices, commands, Exit, and record declarations inspectable to humans and Agents. It does not manufacture product value or force adoption.
03 · The bootstrap
Kungfu gives the first Agent a way to understand the stack.
Agent-first distribution does not require the first Agent to arrive with prior knowledge of KFD or Buildchain. It requires one useful product to provide a trustworthy way in.
First adoption
One real problem starts the loop.
A user first chooses Kungfu for concrete utility: continuity across long-running Agent work.
Managed discovery
The envelope points. The Agent inspects.
When Kungfu launches an Agent, a compact, versioned Skill envelope points to the exact installed context, capability catalog, and KFD-3 collaboration interface. From those local entrypoints the Agent can inspect the KFD-2 evidence and Buildchain-bound release provenance available for that artifact.
User chooses Kungfu for durable Agent workKungfu manages the AgentSkill envelope points to local discoveryAgent inspects the exact installed factsInformed use can reinforce demand
One seed, not two miracles. Kungfu must still solve a real problem well enough to earn the first adoption. The envelope does not create demand or assume prior KFD knowledge; it turns one initial product proof into a repeatable learning and distribution loop.
04 · The conditional flywheel
Useful Agent-first software can create its own demand signal.
The inner loop turns concrete utility into informed Agent use. The outer loop turns successful use into demand for a shared collaboration interface and a repeatable release supply chain.
The strategic consequence: demand can move from one useful product, to a shared Agent-first interface, to an exact-release supply chain that other developers can adopt without rebuilding the underlying trust machinery.
- A user chooses Kungfu because continuity for durable Agent work solves a concrete problem.
- A Kungfu-managed Agent receives a compact Skill envelope and discovers the exact installed collaboration surface and evidence.
- Successful Agent-mediated use can increase demand for KFD-3-compatible software.
- Buildchain binds KFD-3 declarations and KFD-2 evidence to an exact release.
- More developers can ship Agent-ready software with assessable provenance.
Enabled, not claimed. This is an adoption mechanism enabled by the stack, not evidence that a broad network effect, external adoption, or a multi-Hub market already exists.
05 · The complete mechanism
Five responsibilities. Independent owners. One inspectable path.
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
KFD-3
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
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
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
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 and receiver
KFD-2
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
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 · Kungfu and adopter
libkungfu
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
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 · KFD profile and each Hub
Agent Hub portability
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
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
Make one exact decision, not a platform bet.
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.
Open the builder path