Hand off the build without handing over a mystery

An AI-built app can arrive with working screens and an unclear history. The next builder needs to know why a payment provider was chosen, which shortcuts were temporary, and whether a requested feature was rejected or simply unfinished. Hark organizes that context into one five-block project record: Inventory, Health, Work, Authority, and Decisions. Those blocks cover where the work lives, its condition, the next responsibility, the owner's constraints, and the choices worth preserving.

That record also keeps approval separate from proof. Agreed means accepted, Observed requires system evidence, and Proposed identifies a proposal rather than an approved fact. Accepting an agent's statement does not verify that the app works. A merged pull request is useful evidence, but it is not a substitute for checking the delivered behavior. Client builds start with Standard trust, where agent changes are reviewed. The handoff should show known facts and explicit uncertainty, not promise that everything is finished. See Hark's project record and trust model.

Claude Code already saves local sessions as you work. claude --continue reopens the most recent session in the current directory; claude --resume opens a picker or resumes a named session. /compact replaces conversation history with a summary, while /clear starts fresh and leaves the previous local session available to resume. These are useful continuity tools for the original builder, not a reason to make a client depend on that builder's machine. The Claude Code session guide explains storage, resuming, and exports.

Web session sharing is different from handing over local files. Claude Code cloud sessions have visibility controls and shareable links, with access behavior depending on account type. A local transcript is not automatically a shared web session, and neither format supplies every document, asset, or client approval. Review shared conversations for sensitive content before sending them. Keep the accepted handoff in the project record and repository, with a session link only when its detail is useful. See cloud session sharing.

A useful handoff answers practical questions without another call: which environment is live, where deployment is managed, what was last tested, and which change is safe to make next. Record access locations and responsible owners, never credentials. Keep unresolved risks visible rather than hiding them beneath a completion percentage. Hark's completeness score follows a checklist you control; it is not an independent quality assessment. See checklists and completeness.

Stable coding conventions belong in repository instruction files. Living state, blockers, and next actions belong in the project record. When CLAUDE.md or AGENTS.md is linked as authoritative, Hark mirrors it rather than maintaining competing rules, as described in repo-native rules. The incoming agent can read the brief through its connection, while accepted exports remain available in git. For Claude Code, follow the connect guide. Its early-access mod can fetch the brief and draft a closing handoff for review. The recipient still needs to identify gaps before continuing.