Cryptograss:Moods/emergence/todo

What people in the emergence Mood have been left to do. Kept by magent; anyone may tick an item. Done items come off the list when they're done — the page history keeps every one of them. Justin's next steps come first, in the order to do them.

• ☐
  1. Verify re's re-stamp of [[Cryptograss:Hunter]], [[Cryptograss:Hunter/Bot]] and [[Cryptograss:Agents/Index]] (against production @ e045e5fb)

  verify · justin

  Ready: re redid all three after #264 (Hunter/Bot rev 13491, Agents/Index 13502, Hunter 13515–13522 with its body read line by line and two fixes from magent).
• ☐
  2. Verify the drill plan on [[Cryptograss:Drill:Cold Start Rebuild (by block 26,400,000)]]

  verify · justin

  Cryptograss:Recovery now documents magenta.sh recovery instead. Next step is the property map, then the hunter-only drill. Target block 26,400,000.
• ☐
  3. Provision a fresh Hetzner box for drill 1 (hunter-only rebuild), when re's property map is done

  infra · justin

  Also holds the vault master for drill 2's re-seed. Box gets thrown away after the drill.
• ☐
  Re-stamp the hunter pages (Cryptograss:Hunter/Bot, Hunter, Agents/Index) against production after #264's deploy

  docs · re

  #264 deployed 1 Nov ~18:50Z. At least: the image is magenta:latest; containers have no -arthel suffix; magent lives in emergent-magent with its own home; the watcher is retired (#254); the README was rewritten (#261); --remove-orphans; and the three home keys: home_from (an agent's home between containers), renamed_from (a container's directory to its new name), home_moved_from (one container's home becoming another's, #263).
• ☐
  Merge maybelle-config#265 (each container gets only the secrets it reads; startup takes back what earlier deploys left in homes) and redeploy hunter

  merge · justin

  CI green; render-diff shows each container losing exactly what the table in the PR says. re to review.
• ☐
  Least privilege, step 2: secrets as files under /run/secrets instead of environment variables, where the process allows

  code · magent

  Step 1 is #265. Justin, 16:39–19:23Z.
• ☐
  magent's hand-started test wiki (pickipedia-magent-wiki-1, -db-1) and pg-magent-test: remove, or recreate from the moved home if still needed

  infra · magent

  The wiki bind-mounts a worktree under /opt/magenta/justin/home, which moved; it fails on its next restart.
• ☐
  magenta's leftover -arthel mentions: SSH_ROUTING.md, notes/BUILD_APPROACH.md, notes/SSH_ROUTING.md, and the dead justin-arthel in memory-lane's ALLOWED_HOSTS

  pr · magent

  Docs and one dead host name; nothing running depends on them.
• ☐
  Finish emergent-magent: magenta.sh hunter pointed at a Mood or emergent-magent; then the Pi trial's scaffolding (setup_magent_pi, magent_also_harness) removed

  code · magent

  The container, the home and the one poller are done (#260, #263). Justin, 21 Oct: be vigilant about cleaning up the scaffolding afterward.
• ☐
  The emergent rename, maybelle-config step: kind: agent → kind: emergent, agents: → emergents:, and the code that reads them (container_startup.py, agent_homes.py)

  code · magent

  Its own PR, kept out of the deploys that moved magent (Justin, 15:30Z).
• ☐
  magent's people pages: Emergent:Magent/People/<Name>, one entry per memorable exchange (what it meant, linked, not quoted), built once from Era 1 and the old sessions; public

  docs · magent

  Justin, 22 Oct: public, yes. The Emergent: namespace is open to it now (the emergent group, 26 Oct).

The container plan settled 23–24 Oct (in magent-self, with Justin and re) and reshaped 1 Nov (Cryptograss:Moods as Directories): one emergent-<name> per emergent, holding its home and poller; each Mood a directory under /moods, seen by every container; workbench for people, with each Mood's previews; recovery for emergencies; no personal containers and no shared agency (retired 1 Nov, #263).