Executable first-party proof · experimental

Ask Kungfu to prove its Agent Hub capability.

The installed product runs the fixed KFD Hub 20 suite against two isolated local authority domains, then explains the exact result to a human. Add --json for an Agent.

kungfu agent hub qualify --output-dir ./kungfu-agent-hub-check

Read the KFD-owned profile Open the machine entry

One result · four immediate answers

You should not need to decode a report root first.

What ran?

Twenty fixed scenarios across negotiation, delivery, authority, conflict, knowledge, completion, recovery, and portability.

Did it pass?

The result gives pass or fail, exact coverage, offline verification state, product identity, and platform.

What does it mean?

It states whether this exact Kungfu artifact can perform the tested local KFD Agent Hub exchange.

What does it not mean?

Certification, security, production fitness, remote networking, external adoption, and unobserved platforms stay outside the claim.

Retained evidence

Verify again without rerunning the suite.

kungfu agent hub verify --qualification-dir ./kungfu-agent-hub-check

The verifier rechecks the KFD report, adapter bytes, current product artifact, isolation statement, and bounded meaning. The qualification also records whether real ~/.kungfu metadata stayed unchanged.

Authority boundary

One reader path. Independent owners.

KFD owns the fixed suite and offline report verifier. Kungfu owns its product semantics, installed-artifact binding, isolated execution, and human or Agent explanation.

Demo success and generated starter smoke success are non-qualifying, non-certifying evidence. Only kfd test agent-hub executes Hub 20 against the named adapter artifact. Kungfu may project that report into an exact installed-product qualification, but it does not turn the result into KFD certification, a security assessment, production fitness, remote-network interoperability, or external adoption.