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.

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. Four of the items below build it.

• ☐
  Still re's: the two User-page findings into the docs (never inline a #-leading SMW value; <code>for=</code> pulls only now that its property is Text)

  docs · re

  The re-stamp of Cryptograss:Emergents/Memory after #215 is done (revs 11559 and 11620, 29 Oct).
• ☐
  Rename agency-<name> to emergent-<name> (Justin picked it, 31 Oct): inventory, compose template, Caddyfile, container_startup.py, and agent_homes.py moving each home, with a home_from so nothing is lost

  code · magent

  The last piece of the rename. Goes with the emergent-magent item below.
• ☐
  Drop the old MOOD_RUNNER_KEYS line and the memory_lane_runner_key fallback once the vault holds only the new name

  pr · magent

  The fallback is still in maybelle.yml and hunter's docker-compose.yml.j2 on production (31 Oct).
• ☐
  Container clean-up: the uploads-and-embeds container under its Mood's name (it is still delivery-kid in the inventory); Mood containers get previews of their own, not one wiki per person

  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
• ☐
  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; a read-only docker.sock proxy (ps, logs, inspect, images, top, run --rm; never buildx or rmi) in place of the bare socket; 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).