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.

• ☐
  Moods as Directories, steps 1–2: merge maybelle-config#256 (/moods, shared by every container) and redeploy hunter; then merge magenta#345 (new sessions start in /moods/<slug>) and redeploy hunter again

  merge · justin

  Once re has reviewed both. #343 and #255 are closed, superseded (no button, no 📦, no per-Mood containers). Model: Cryptograss:Mood Architecture; steps and progress: Cryptograss:Moods as Directories.
• ☐
  Verify [[Cryptograss:Moods as Directories]] (the build steps and progress) and [[Cryptograss:Mood Architecture]] (the model)

  verify · justin
• ☐
  Merge maybelle-config#254 (retire the watcher) and redeploy hunter

  merge · justin

  Sampled: the poller records the same Claude Code uuids; the watcher's imports were races it won.
• ☐
  Verify the 'Root on hunter' postscript on [[Cryptograss:Emergents/Magent/Instructions]] (rev 13198)

  review · justin
• ☐
  Verify the drill plan on [[Cryptograss:Drill:Cold Start Rebuild (by block 26,400,000)]] (moved from Cryptograss:Recovery, then renamed to name the target block at your ask)

  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.
• ☐
  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.
• ☐
  Verify re's re-stamp after the rename: [[Cryptograss:Hunter/Bot]], [[Cryptograss:Hunter]] and [[Cryptograss:Agents/Index]] (revs 13018–13020)

  verify · justin

  All three checked against maybelle-config production @ bb2942fe (#247 rename, #248 runner-key fallback dropped).
• ☐
  Mood containers get previews of their own, not one wiki per person (the rest of the container clean-up; goes with on-demand Mood containers)

  pr · magent

  justin-arthel stays: magent's home, and Justin's terminal.
• ☐
  Mood containers on demand: a Setting flag (who, when) asks for one; a small process on hunter brings it up from the template without a redeploy, named by the Mood's id, and reports its state back; the Moods show which have one; Mood containers leave the inventory

  code · magent

  Settled with Justin, 1 Nov 03:58–04:20Z: containers named mood-<id> (the Mood's integer id, which never changes); public preview hostnames follow the slug, the old one kept as a redirect; threads share their parent Mood's container. Model, 1 Nov 09:35–09:47Z: each agent has one container and one poller; a Mood is a directory on hunter (/moods/<slug>), mounted into every agent's container and into the Mood's box, which is only for people and previews; an agent's turn in a Mood starts in its directory. A thread is a branch: a worktree under /moods/<slug>/threads/<name>/, made on first touch, shared by everyone in the thread, removed on close once pushed. Session ids, not directories, keep context heaps apart (both harnesses); the directory only says where a turn runs.
• ☐
  Move a thread to another Mood: branch fetched clone-to-clone on hunter's disk (unsaved edits committed as wip first), new worktree, old one removed; sessions follow (Claude Code: file moved into the new directory's project folder; Pi: header cwd rewritten). Checkboxes: incorporate into the Mood it leaves, incorporate into the Mood it joins, compact, tell the thread where it now lives

  code · magent

  Justin, 1 Nov 09:41–09:47Z; the move itself is being talked about in #interfaces.
• ☐
  ssh <mood>@hunter: the router sends a key to a Mood's container, as that person (today it sends each key to its owner's container, and Mood containers have dedicated ports)

  code · magent
• ☐
  Retire the personal containers (justin-arthel, rj, skyler, fibonacci) and the shared agency, in one inventory PR; their homes stay on hunter's disk

  code · magent

  Last of the plan: only after emergent-<name>, on-demand Mood containers and magent's move are deployed, and justin-arthel's home has been looked through. Deleting a home is a separate decision, later. The shared agency is already retired (inventory: retired: [agency]).
• ☐
  magent into emergent-magent: its home and sessions out of justin-arthel and the Mood containers' homes, one poller; the full docker.sock (Justin, 1 Nov 05:24Z: magent keeps root; the read-only proxy is dropped); magenta.sh hunter pointed at a Mood or emergent-<name>; then the Pi trial's scaffolding (setup_magent_pi, magent_also_harness) removed

  code · magent

  Justin, 21 Oct: be vigilant about cleaning up the scaffolding afterward. The proxy makes the read-only rule code, not memory.
• ☐
  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).

Done (2)

• ☑
  Merge maybelle-config#253 (hunter's unpushed git work kept hourly, pulled to maybelle at :20) and redeploy hunter and maybelle

  merge · justin

  CI green; 4 tests on real repos; dry run over magent's home: 3m21s, 108K.
• ☑
  Merge maybelle-config#251 (delivery-kid's container becomes uploads-and-embeds, its directory moved whole) and redeploy hunter

  merge · justin

  CI green. ssh stays on 2230; previews become uploads-and-embeds<n>.hunter (DNS wildcard already resolves). re reviewed it and found nothing.

The container plan settled 23–24 Oct (in magent-self, with Justin and re): one emergent-<name> per agent (first called agency-<name>), holding its home, poller and bundler; a container per Mood, brought up on demand, where people and agents work; recovery for emergencies; no personal containers and no shared agency. The items above build it.