How it works
Give the work a clear shape before it moves.
A packet keeps the outcome, context, authority, boundaries and evidence request visible.
SourceOne packet, the key questions together.
A packet keeps the work complete enough to hand off without asking a person to carry its operating memory alone.
- Intent: what must become true?
- Context: what is needed?
- Authority: what may happen?
- Boundary: what stays untouched?
- Evidence: what must return?
One accountable root.Add cells only when needed.
Root identifies dependencies, assigns separate scopes and owns integration. A work cell receives one objective and returns one artifact. Parallelism is optional; ownership is not.
Advice arrives before permission.
The system may recommend a route, estimate effort or surface risk. A checkpoint keeps that information separate from authority to write, commit, publish or disclose.
Messages carry information. They do not silently carry permission.
The return shows how to inspect it.
A claim points to an artifact. The artifact names its validation. Unknowns remain visible. The person can accept, narrow, revise or stop without reconstructing the whole run.
The route ends with a choice.
A useful return can be approval, a narrower packet, a request for stronger evidence or a manual exit. Stopping at the boundary is a valid result.
Dwi by thienhoc
Keep the boundary visible.
Start with one reversible task and one return condition.