01. Source of Truth
Fix the project, repository, branch, goal, and write set. This defines what is being handled.
Overview
1. Introduction
In this article, a handoff means preserving the scope, evidence, execution path, and approval boundaries needed to resume work safely—whether or not responsibility passes to someone else.
This article presents a practical framework drawn from experience developing and operating personal projects. It is not a general standard. It treats people, AI-assisted tools, repositories, read-only confirmation, authorized work locations, documents, approvals, runtime, and publication work as parts of one work system.
Context
2. When it helps
A handoff helps when resuming after an interruption, moving between tasks, waiting for review, shifting from investigation to editing, approaching a change decision, or nearing a runtime or publication boundary. It is useful whenever assumptions change, even if the same person continues the work.
Relationship map
3. Four boundaries
These are not steps in a sequence. They are distinct boundaries that must be checked together: define the target, separate the place of execution, advance only through the approved stage, and record what was actually observed.
02. Execution Boundary
Separate read-only locations, authorized work locations, and external operations performed by people. This defines where an action may happen.
03. Approval Boundary
Treat investigation, editing, review, commit, push, and publication as separate stages. This defines what may proceed.
04. Recorded / Observed State
Separate Observed, Inferred, and Unknown. This defines the current evidence and what needs another check.
How the map works: the Source of Truth fixes the target; the Execution Boundary limits where work occurs; the Approval Boundary limits the stage; and the Recorded / Observed State checks all three against current evidence.
Decision aid
4. Decision table before starting
| Category | Examples | Decision before starting |
|---|---|---|
| Fixed information | Target, branch, goal, write set | Obtain renewed approval if it changes. |
| Variable / current information | Revision, worktree, review state | Recheck at transitions and record the time. |
| Approval status | Investigation, editing, commit, publication | Advance only through the stage approved for this work. |
| Observed evidence | Observed, Inferred, Unknown | Record confirmed and unverified items separately. |
Pattern
5. Failure pattern and corrected pattern
Failure pattern
Starting with only “continue from last time,” “it is probably the same branch,” or “it should already be published” leaves the target, evidence, execution location, and approval stage unknown.
Corrected pattern
State the target, goal, Observed evidence, write set, execution boundary, approval boundary, stop condition, and next action briefly. The format itself is not approval.
Reusable template
6. Minimal reusable handoff template
Target: [project / repository / branch]
Goal: [what this work should complete]
Read set: [documents and state to inspect]
Write set: [files allowed to change]
Observed evidence: [directly checked facts and time]
Unverified: [items not yet checked]
Execution / approval boundary: [where work may occur and the approved stage]
Stop condition / next action: [when to stop and what follows]
Sequence
7. A short sequence from confirmation to record
- Confirm
Check the target, current state, and read set. - Bound
Fix the execution location, write set, and approval stage. - Execute
Change and verify only the approved scope. - Record
Leave the result, unverified items, and next action.
This is not the only procedure. Add checks only as the size and boundaries of the work require.
Limits
8. Scope and limits
This article is a general proposal for work design. It is not a security guarantee, legal advice, a runtime procedure, or a substitute for direct observation. Actual changes and external operations must follow each environment’s responsibilities, approval procedures, and direct observations.
Source
9. Authoritative edition
The Japanese edition is the authoritative version of this article. Please consult it when quoting, republishing, or translating this article.
Summary
10. Summary
For a work handoff, separate the target, evidence, execution path, and approval boundaries. Check the four boundaries together, avoid mixing fixed and current information, and recheck only as changes and boundaries require.
About
11. About this article
AI-assisted structure and editing were used in preparing this article. The author, mars70, reviewed and revised the content before publication.