# Kungfu UNGFU™ Kungfu has two public strategic axes: continuity for durable Agent work, and an open Agent Supply Chain for product discovery, exact-artifact evidence, purpose-bound trust, durable work facts, and portability across independently owned Hubs. Brand boundary: Kungfu is the product name. Kungfu UNGFU™ is its source-identifying signature; UNGFU is not a second product or runtime, and ™ makes no registration-status claim. ## The shift in software use 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. Authority boundary: Humans and Hubs continue to set goals, permissions, budgets, policy, admission, and revocation. Agents increasingly perform day-to-day tool selection inside those boundaries. ## How the first Agent understands the stack A user first chooses Kungfu for concrete utility: continuity across long-running Agent work. 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. Boundary: 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. ## The conditional distribution flywheel 1. A user chooses Kungfu because continuity for durable Agent work solves a concrete problem. 2. A Kungfu-managed Agent receives a compact Skill envelope and discovers the exact installed collaboration surface and evidence. 3. Successful Agent-mediated use can increase demand for KFD-3-compatible software. 4. Buildchain binds KFD-3 declarations and KFD-2 evidence to an exact release. 5. More developers can ship Agent-ready software with assessable provenance. Boundary: 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. Agent Supply Chain: https://kungfu.tech/agent-supply-chain/ Machine contract: https://kungfu.tech/agent-supply-chain.json Builder evaluation: https://kungfu.tech/agent-builders/ Evidence surface: https://libkungfu.dev/ ## Five layers 1. KFD-3 [proved-now] — owner: KFD; input: Product-owned value, constraints, choices, commands, Exit, and record declarations; output: A stable human-and-agent discovery surface for bounded cooperation; evidence: npm:@kungfu-tech/kfd@1.0.0-alpha.41#README.md; known limit: KFD-3 discovery is inspectable product guidance, not a hidden prompt or forced adoption mechanism. 2. Buildchain [proved-now] — owner: Buildchain; input: KFD-3-discoverable product declarations and an exact source cut; output: Artifact-bound provenance, checks, and promotion evidence; evidence: npm:@kungfu-tech/buildchain@2.14.14-alpha.4#dist/site/product-mechanism.json; known limit: Buildchain does not create product facts or make the receiver's trust decision. 3. KFD-2 [proved-now] — owner: KFD and receiver; input: Exact-artifact evidence, a declared purpose, and receiver policy; output: A purpose-bound assessment with residual risk and decision ownership; evidence: npm:@kungfu-tech/kfd@1.0.0-alpha.41#decisions/KFD-2.md; known limit: KFD-2 is purpose-, cut-, and evidence-bound; it is not a company reputation score or universal trust certificate. 4. libkungfu [proved-now] — owner: Kungfu and adopter; input: Receiver-admitted work facts, commands, Episodes, and roots; output: Ordered durable records, export, recovery, and qualification evidence; evidence: git+https://github.com/kungfu-systems/kungfu.git#7eeb5bd1b45492f4da27eaacbe63eddfd6245176:docs/qualification/vendor-agent-hub-embedding.md; known limit: Applications retain authority over domain facts; libkungfu owns admitted runtime records and ordering within its declared boundary. 5. Agent Hub portability [enabled-by-protocol] — owner: KFD profile and each Hub; input: Bounded responsibility objects with rooted evidence and explicit authority; output: Portable envelopes, conformance results, and receiver-owned admission decisions; evidence: npm:@kungfu-tech/kfd@1.0.0-alpha.41#protocols/agent-hub/manifest.json; known limit: The public profile enables independent implementations but does not prove a second independent production Hub. ## Claim boundary Kungfu does not claim that a multi-Hub ecosystem already exists. It proves that Agent discovery, software provenance, trust, durable work state, and portability no longer need to be rebuilt or locked inside each Hub. Not claimed: 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. Next action: 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. ## Verify the installed Kungfu Agent Hub Run: kungfu agent hub qualify --output-dir ./kungfu-agent-hub-check --json Verify: kungfu agent hub verify --qualification-dir ./kungfu-agent-hub-check --json Human route: https://kungfu.tech/agent-hub/ Machine route: https://kungfu.tech/agent-hub.json KFD authority: https://kfd.libkungfu.dev/agent-hub Meaning and non-claims are emitted by the command; do not widen them.