Continuity

Good work should survive the tool.

Assistant systems change. Models, tools, providers, sessions, and workflows come and go. The human context should not disappear with them.

VaporHuman treats continuity as a design problem: record the right context, keep boundaries visible, and make handoffs easy to audit.

Continuity pattern

The point is not perfect memory. The point is recoverable work.

01

Capture decisions

Keep the durable facts, approvals, boundaries, and blockers findable.

02

Checkpoint before switching

Pause with enough state for another tool, agent, or human to continue safely.

03

Design for replacement

Assume today’s model, platform, or workflow will eventually be replaced.

Handoffs

A handoff should carry enough truth to be useful.

A good handoff says what changed, what was verified, what remains blocked, what must not happen without approval, and where the next person or tool should look first.

It should also say what not to trust: stale assumptions, parked lanes, private data, old drafts, or external actions that have not actually been performed.

Replaceability

Ask what replaces the current system.

A human-centered assistant should avoid lock-in where it can. If a model, provider, tool, or workflow fails, the important context should still be portable enough to move.

Replaceability is not pessimism. It is respect for future humans who need the work to keep making sense.