A continuation package helps the next conversation understand the predecessor, but live GDP state still wins. The destination must revalidate the repository, task, policy, and any material operation before continuing.
Treat handoff context as evidence, not authority
GDP continuation separates predecessor conversation evidence from current operational truth. Full Context archives and compact hydration or handoff material help a fresh conversation resume, but they do not grant repository permissions, approvals, claims, leases, or command authority.
Use the handoff as a start cursor rather than rediscovering the whole project.
Let fresh GDP repository, task, and check evidence override stale handoff statements.
Do not repeat an uncertain mutation until its exact GDP operation has been reconciled.
Resume the substantive goal
Prepare or open the fresh continuation conversation using the available GDP handoff flow.
Keep the latest substantive user goal and exact next action visible in the handoff.
At the destination, confirm the intended GDP connection and repository context before material work.
Read fresh GDP evidence for anything that may have changed while the conversation moved.
Continue from the first unproven step instead of rerunning already verified work.
A copied transcript saying that something succeeded is not a completion certificate. Material completion still requires current GDP evidence.
Keep continuation separate from a fork
A normal context-limit rollover continues the same workstream. A genuinely different mission should be treated as a separate fork or task rather than silently inheriting the old conversation’s assumptions.
Lineage is not authority: even a valid continuation must establish fresh destination identity and current target/policy checks before material action.
