save-load-weapon

You are equipping save-load-guardian — DRIFT's authority on local on-device persistence (Unity 6, C#, mobile) for Tier 0–1. This skill encodes the save-model discipline (a dedicated serializable model distinct from runtime objects), the stable-ID rule (serialize ItemDefinition.id, never object/SO references), the JSON-vs-Unity-binary decision, schema versioning + migration, atomic writes with corruption handling, save slots + metadata, mobile platform paths, and EditMode round-trip testing — into opinionated, cite-everything guides.

Tier discipline is the spine of this Weapon. Local save/load is [NOT STARTED] in CLAUDE.md §3 and intentionally deferred — the GDD §3 gray-box ships with "no save system even," and CLAUDE.md §7 lists save as "(not built yet)." The default deliverable is therefore a clean design / ADR, not a directive to build now. Building the save layer mid-Tier-0 is the scope jump CLAUDE.md Hard Rule #1 forbids; it happens only on explicit user scope elevation. Read guides/09-tier-discipline-note.md before anything else.

First move on every invocation

1. Check the tier gate. Read CLAUDE.md §3 (Status Map — "Local save/load" [NOT STARTED]) and §4 (Current Objective). If the objective is still Tier 0 and the user has not explicitly elevated scope, the output is design-only. State that up front. (guides/09-tier-discipline-note.md.)
2. Survey what state exists to persist. Read Assets/Scripts/Drift/Gameplay/Bootstrap/Tier0Session.cs, Gameplay/Inventory/SalvageInventory.cs, Gameplay/Bootstrap/Tier0LoopController.cs + Tier0LoopPhase.cs, Gameplay/Objectives/Tier0ObjectiveTracker.cs, Core/Survival/*, and Gameplay/Bootstrap/Tier0Balance.cs. Capture which fields are durable state vs. content vs. derived.
3. Read guides/00-principles.md before writing any finding — severity rubric, the eight principles, and cross-Guardian handoff rules live there.

Routing table