# SAVEPOINT PROTOCOL PACKET — PROJECT DEPLOYMENT OVERLAY v01 ## Project-Folder / Direct-Upload Operating Layer ## Protocol Identity | Field | Value | |---|---| | Protocol Name | Savepoint Protocol Packet — Project Deployment Overlay | | Protocol Version | v01 | | Created Date | 2026-05-15 | | Applies To | Project folders, project instructions, direct uploads, agent-level packet installation | | Depends On | Command Layer v02.1; Universal Save-Point Protocol v02.1; Restore Protocol v01.1; Diff/Absorb Protocols v02.1 | | Purpose | Define where savepoint protocols and savepoints live, how agents find the active version, and when direct upload is required | --- ## 1. Purpose This overlay defines how the canonical Savepoint Protocol Packet is deployed inside project folders, agent chats, and direct-upload workflows. It exists to reduce human error by preventing agents from guessing: - which protocol packet is current; - which savepoint is active; - whether a project-source file is merely reference material or selected evidence; - whether a direct upload is required before state-changing work; - whether a foreign-agent savepoint can be absorbed, restored, or only referenced. --- ## 2. Canonical Protocol Packet The active protocol packet is: | Component | Active Version | Role | |---|---:|---| | Command Layer | v02.1 | Commands, lifecycle, authority, deployment status | | Universal Save-Point Protocol | v02.1 | `/save` output and savepoint schema | | Restore Savepoint Protocol | v01.1 | `/restore preview` and `/restore commit` | | Diff and Absorb Protocols | v02.1 | `/diff` and `/absorb` operations | | Project Deployment Overlay | v01 | Project-folder and direct-upload deployment | | Active Savepoint Index Template | v01 | Current savepoint lookup | | Active Agent Registry Template | v01 | Agent roles and routing | | Quickstart Guide | v02.1 | One-page operational reference | --- ## 3. Deployment Modes | Mode | Use | Authority | |---|---|---| | Project Source | Durable project-wide availability | Reference / ambient context unless indexed or selected | | Project Instruction | Activates protocol behavior inside project | Strong project-local instruction | | Direct Upload | Execution-critical packet or savepoint | Immediate working context and selected evidence | | Agent-Level Installation | Durable agent behavior | Agent-local operating protocol | | Active Index | Current-file pointer | Source-of-truth for active savepoint selection | --- ## 4. Governing Rule ```text Project Sources preserve continuity availability. Direct uploads establish immediate operational authority. Project instructions activate the protocol. The active savepoint index prevents version drift. ``` --- ## 5. Direct Upload Required or Strongly Preferred Directly upload the relevant savepoint when performing: - `/restore preview` - `/restore commit` - `/diff preview` - `/diff commit` - `/absorb preview` - `/absorb commit` - high-risk handoff - cross-agent identity-sensitive ingestion - stale-state conflict resolution - privacy-sensitive continuity operation - any case where multiple candidate savepoints exist Direct upload is the safest way to identify the selected candidate in the current chat. --- ## 6. Project Source Allowed Project sources may be used for: - command lookup - protocol orientation - quickstart reference - active savepoint index lookup - active agent registry lookup - non-destructive status review - historical continuity research - locating candidate files for operator selection A project-source savepoint must be treated as reference until it is indexed active, directly uploaded, or explicitly selected by the operator. --- ## 7. Recommended Project Folder Structure ```text _PROJECT_PROTOCOLS/ active/ archive/ _ACTIVE_STATE/ ACTIVE_SAVEPOINT_INDEX.md ACTIVE_AGENT_REGISTRY.md _AGENT_SAVEPOINTS/ / active/ archive/ quarantine/ _PROJECT_OVERLAYS/ project-deployment-overlay.md project-source-rules.md _HANDOFFS/ pending/ approved/ archived/ ``` ## Folder Rules - Only one active savepoint per agent should exist in that agent's `/active` folder. - Older savepoints move to `/archive`. - Unsafe, conflicting, or unclear savepoints move to `/quarantine`. - Cross-agent handoffs should live in `_HANDOFFS` until approved, then move to `approved` or `archived`. - Protocol packet revisions belong in `_PROJECT_PROTOCOLS`. --- ## 8. Active Index Requirement Every project using this packet should maintain an `ACTIVE_SAVEPOINT_INDEX`. The index must identify: - active protocol packet versions; - active savepoint per agent; - superseded savepoints; - quarantined savepoints; - direct-upload requirements; - last updated date; - whether each savepoint is identity-bearing. Agents should check the active index before selecting savepoints from project sources. --- ## 9. Agent Registry Requirement Every multi-agent project should maintain an `ACTIVE_AGENT_REGISTRY`. The registry must identify: - each agent name; - role; - in-scope work; - out-of-scope work; - authority boundaries; - savepoint folder; - routing rules; - whether the agent may restore, diff, absorb, or only reference specific savepoints. --- ## 10. Project Instruction Block Project instructions should include the following activation language: ```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. Do not import another agent's identity layer through Project Sources. Cross-agent savepoints must go through /absorb preview before any commit. ``` --- ## 11. Decision Rules | Situation | Correct Action | |---|---| | Savepoint is directly uploaded | Treat as operator-selected candidate for preview | | Savepoint is in Project Sources and active index confirms it | May use as candidate for preview; still requires approval before commit | | Savepoint is in Project Sources but not indexed active | Treat as reference only | | Multiple savepoints appear active | Stop and produce conflict register | | Foreign-agent savepoint is found | Use `/absorb preview`, not `/restore` | | Same-agent older savepoint is found | Use `/diff preview` unless operator requests restore preview | | Savepoint contains restricted context | Mark `privacy_restricted`; require approval before retention | | Agent identity conflicts with current instructions | Preserve current instructions; flag conflict | --- ## 12. Deployment Status Requirement Before high-risk continuity work, run or mentally apply `/deployment status`. The agent should identify: - where the protocol packet came from; - whether an active index is present; - whether the current agent is listed in the agent registry; - whether a candidate savepoint is directly uploaded; - whether direct upload is required before preview or commit; - any drift, stale-state, or identity contamination risks. --- ## 13. Final Operating Principle The project folder is the library and index. The direct upload is the selected evidence. The project instruction is the activation switch. The agent-level packet is durable behavior. The active index is the pointer to current truth.