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. The cold start drill lives on Cryptograss:Moods/ops/todo; GitHub and version-control items on Cryptograss:Moods/ramp/todo.

• ☐
  2. Decide: does recovery@hunter (docker group, open to all four keys) stay open to everyone?

  decision · justin

  Left out of #266. It's an agent session behind a forced command, not a shell, but root in effect.
• ☐
  3. Decide how people sign in from workbench, so it can drop magent's GitHub token and Magent's wiki password

  decision · justin

  workbench runs as user magent; anyone there pushes as magent-cryptograss and edits as Magent. Tell skyler, rj and fibonacci before it lands.
• ☐
  Re-send a turn's lost stream events from its transcript (magenta#358), Pi turns too

  code · magent

  Carried to #ops, 2 Nov. Since the watcher's retirement a dropped batch is gone; rows are uuid-keyed, so a re-send can't duplicate.
• ☐
  Least privilege, later: secrets as files under /run/secrets instead of environment variables

  code · magent

  Small gain, checked 2 Nov: turns don't inherit the container's environment (PID 1's is root-only); the values show only in docker inspect, which needs root on hunter anyway. Step 1 is #265, deployed 2 Nov ~03:08Z.
• ☐
  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. Still up after the 2 Nov redeploy.
• ☐
  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).

Done (1)

• ☑
  1. Merge maybelle-config#266 (router lets in only a container's people:; emergent-magent, nobody) and redeploy hunter (which also ships magenta#357)

  merge · justin

  Justin said yes, 2 Nov 10:56Z: only root opens emergent-magent. CI green, router tests 9 pass. After deploy magent updates its own Instructions page, and tests a refused entry.

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).