What the Hub gains
What a Builder Hub gains
- More capability, less blind trust
- Reusable admission
- Reviewable evolution
- The moat stays above
Back to libkungfu.devBuildchain product surface
Start here · Agent product and Hub builders
How can your Hub accept more capability without inheriting blind trust?
Bind KFD-3 value surfaces and KFD-2 trust evidence to exact releases while keeping your product, customer relationship, and local admission policy.
01 · The essential loop
Buildchain turns release work into a Hub admission surface.
A Hub can accept more capability without inheriting blind trust. Buildchain turns a Builder's public offer and its supporting facts into one release-bound surface that the Hub can evaluate under its own policy.
Sourcesbuildchain-release-passportbuildchain-kfd-supportkfd-2kfd-3kfd-agent-hub-profileKFD-2 × KFD-3 × exact release
KFD-3 declares the value. KFD-2 makes it trustable. Buildchain binds both to the release.
-
Declare the offer
KFD-3
The Builder exposes what the product can do, why it is useful, which public surfaces carry it, and which choices and constraints apply.
-
Assess reliance
KFD-2
Each important value claim binds to inspectable facts, checked evidence, assurance responsibility, known gaps, and residual risk.
-
Bind the exact release
Buildchain
The Release Passport keeps the claim congruent with exact source, artifacts, verification, provenance, and promotion evidence.
-
Keep the verdict local
Builder Hub
The receiving Hub evaluates that exact release under its own identity, authority, policy, and risk boundary; discovery or delivery never forces admission.
What the Hub keeps
Your Hub remains yours.
- Users and customer relationships
- Accounts and billing
- Models and Agents
- UI and product experience
- Cloud and storage
- Identity and policy
- Admission and revocation
Potential ecosystem effect · not an adoption claim
A portable trust surface can compound across an ecosystem.
When Builders publish the same release-bound capability and trust facts that Hubs can evaluate locally, one integration can become reusable supply instead of a one-off bilateral trust exercise.
Claim boundary: This is the ecosystem effect enabled by the contract, not evidence of a present network effect. The KFD Agent Hub profile is alpha and does not prove external adoption, plural-Hub deployment, stable certification, or an industry standard.