Kungfu UNGFU™ — Continuity for Agent Work

The problem · then 3 proofs

The problem · 1 of 4

Continuity for Agent Work The pain · 01

One Work. Fresh Agents.

Your agents don't hand off the work. You do.

Every switch means copying context, re-explaining decisions, chasing updates, and checking what got lost. Kungfu keeps the same work moving, no matter which agent takes over.

Agents change. The Work stays.Change the execution surface—not the Work.

Proof 1 of 3 · Continuity Prelude · exact contract

Continuity

Can Work survive a new Agent?

The first proof isolates continuity: one Work continues across two fresh Agent Sessions without copied chat.

The mechanism exists; the next proof asks whether it still holds under real failure conditions.Exact media and its retained evidence remain independently inspectable.

Proof 2 of 3 · Failure retention Prelude · exact contract

Failure retention

Can Work survive failure?

Inside a disposable Project, a dropped connection and a crashed replacement process remain as Attempts under the same Work.

Work survival is only the first step. If an Agent can approve its own result, continuity still is not trustworthy.Exact media and its retained evidence remain independently inspectable.

Proof 3 of 3 · Review and settlement Prelude · exact contract

Review and settlement

Who is allowed to complete Work?

The final proof separates Agent exit, independent review, and Kungfu settlement: an Agent can produce a candidate and evidence, but cannot approve its own Work.

The governed completion boundary is now visible.Exact media and its retained evidence remain independently inspectable.

Kungfu UNGFU™Never Guess. Facts Unfold. Why Kungfu?

Use the best Agent when it matters. Use a cheaper one when it does not. Keep the same Work across Codex, Claude, OpenCode, or your own execution surface.

Two strategic axes

Continuity for work. An open supply chain for Agent products.

KFD explains how people, Agents, and products understand, trust, cooperate, and continue. The Agent Supply Chain connects discovery, exact-artifact evidence, purpose-bound trust, durable work facts, and portability across independently owned Hubs.

KFD-3 Buildchain KFD-2 libkungfu / .kungfu independent Hubs

Today: exact public contracts and first-party proof. Not claimed: a live multi-Hub market or external vendor adoption.

For Agent Builders

Build and own your Hub. Kungfu stays beneath it.

Your users, accounts, billing, models, UI, Agent, cloud, and customer relationship stay yours. Kungfu provides KFD and libkungfu; it does not compete for the Hub.