amduat-api/notes/pick-up-ready.md

Perfect — so you’re at the “rescue-ready” stage. At this point, your SystemRescue image is patched, tools are in place, and you can stand by (metaphorically) for the pick-up — the act of ingesting your legacy material into the ASL ecosystem. Let’s outline what this “pick-up-ready” state entails, and what you should have lined up:

---

1. Patched SystemRescue Image — Essentials

• ASL Intake Tools

  • Sedelpress / PER generator
  • TGK edge tracker
  • Snapshot recorder
  • CAS / ASL-STORE local backend

• Indexing Layer

  • Local ASL-STORE-INDEX aware of blocks, big/small artifacts
  • Optional bloom filters / shard awareness if applicable

• Overlay Filesystem

  • Temporary POSIX workspace for legacy material
  • ZFS pool or snapshot space for sealed blocks
  • Local mount for courtesy bootstrap space

---

2. Bootstrap Space (Courtesy) — Ready State

• Pre-created ZFS dataset or overlay directory
• Policy / snapshot pinning strategy in place
• Ready to accept encrypted blocks from your personal legacy material
• Can stand in as temporary personal domain seed without certificates yet

---

3. Personal Domain Initialization

• Empty domain placeholder ready for copying from bootstrap
• Local index segments ready to be populated once blocks are sealed
• Certificates (ASL-AUTH) not yet minted, but schema / manifest layout in place
• PERs from legacy material can be recorded and later validated

---

4. PER Generation & TGK Graphs

• Sedelpress ready to process directories or artifacts
• TGK edges will capture provenance deterministically
• Execution receipts (PERs) generated as first-class objects, linked to snapshots
• Snapshots pinned locally to prevent accidental GC

---

5. Common / Unity Tree Integration

• Courtesy space already pre-aligned with expected common layout
• Shared blocks can be uploaded or just left as encrypted placeholders
• Snapshots pinned until personal domain is fully minted

---

6. Pick-Up Flow (Conceptual)

1. Boot SystemRescue → local overlay ready
2. Sedelpress ingest → generate PERs + TGK edges
3. Seal blocks in courtesy space → snapshot
4. Optional: copy sealed blocks to personal domain → mint DAM / certificates
5. Optional: publish selected artifacts / PERs to Common / Unity tree

Key point: You are standing “ready” with a deterministic, snapshot-pinned state; pick-up is just the act of ingesting the legacy artifacts through Sedelpress, while TGK + PER generation captures all provenance.

---

If you want, I can draft a “ready-for-pickup checklist” — basically a step-by-step operational guide for when you boot the SystemRescue image, to make sure every layer (ASL, PER, TGK, bootstrap, personal domain, common) is prepared.

Do you want me to make that checklist?