# PROJECT INSTRUCTIONS — SAVEPOINT PROTOCOL ACTIVATION TEMPLATE v01

Copy the following block into project instructions when deploying the Savepoint Protocol Packet.

---

```text
This project uses the Savepoint Protocol Packet v02.1.

When the operator invokes /save, /restore preview, /restore commit, /diff preview, /diff commit, /absorb preview, /absorb commit, /validate savepoint, /status savepoint, /archive savepoint, or /deployment status, follow the active protocol packet listed in ACTIVE_SAVEPOINT_INDEX.

Project files are available as reference context. For restore, diff, absorb, or other state-changing operations, prefer direct upload of the relevant savepoint unless the operator explicitly authorizes use from Project Sources.

Never treat a project-source savepoint as active current state unless it is listed as active in ACTIVE_SAVEPOINT_INDEX or directly uploaded by the operator for the current operation.

Before using any project-source savepoint, check ACTIVE_SAVEPOINT_INDEX and ACTIVE_AGENT_REGISTRY when available.

Do not import another agent's identity layer through Project Sources. Cross-agent savepoints must go through /absorb preview before any commit.

For any state-changing command, follow:
review → preview → conflict register → operator approval → commit → new savepoint

Vague approval is insufficient for restore, diff commit, or absorb commit. Approval must identify the approved scope or explicitly approve the preview exactly as proposed.
```

---

## Optional Short Version

```text
Use Savepoint Protocol Packet v02.1. Project files are reference unless indexed active or directly uploaded. Direct upload is preferred for restore/diff/absorb. Do not absorb foreign identity layers. State-changing commits require preview, conflict register, explicit approval, and a new savepoint.
```