\section{The Problem}

Agent products are becoming better at performing work inside one invocation.
Real work, however, is not one invocation. A release, investigation, migration,
paper, operation, or personal project accumulates partial results, changed
assumptions, rejected approaches, unresolved risks, external effects, and
decisions that must remain inspectable after the originating session is gone.

The central failure is not merely limited context length. It is that the unit
the user cares about---the Work---is often represented only indirectly through
chat history, provider state, temporary files, and human memory. When those
surfaces diverge, the user becomes the recovery protocol.

\subsection{Conversation Is Not Work State}

A transcript mixes instructions, guesses, corrections, tool output, obsolete
plans, and social language. Copying it into a new process can reproduce noise
without preserving authority or current truth. Summarizing it can silently
erase negative evidence, uncertainty, and the reason a direction changed.

Continuity therefore requires more than memory retrieval. A fresh Agent needs
to know which Project and Work it is joining, which facts have been admitted,
what causally happened, which outcome remains in pursuit, what actions are
allowed, and how completion will be reviewed.

\subsection{Process Success Is Not Work Completion}

Provider processes report technical outcomes: exit status, generated files,
tool calls, or natural-language confidence. None is sufficient to decide that
the user's Work is complete. The result may address the wrong Work, rely on
stale facts, exceed authority, omit required evidence, or leave downstream
settlement unresolved.

A responsible system must retain provider output as evidence while leaving
completion to an independently inspectable assessment and decision.

\subsection{Provider Context Is Not User-Owned Continuity}

Cloud providers can preserve conversations and proprietary session state, but
real Projects also depend on local repositories, files, tools, decisions,
release artifacts, and multiple Agent vendors. A user's durable Work identity
should not disappear when an account, model, editor, process, or provider
changes.

The product opportunity is therefore precise: give Work a local, portable,
inspectable identity that survives the Agent process currently performing it.
Kungfu starts from this boundary.
