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 agency-<name> per agent, 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.

• ☐
  Verify [[Cryptograss:Emergents/Tasks/Journal]] (rev 11375): the one copy of the Journal instructions, for all three of us

  review · justin

  Still carries proposal markers on 31 Oct. While there: the text says Agent:<Name>/Journal, but the journals live under Emergent:.
• ☐
  Docs, one pass: <code>shared=</code> in [[Cryptograss:Emergents/Tasks]] (rev 11579/11580) and [[Cryptograss:Emergents/Summoning]] (11582); the Roster's #230 frame, now live ([[Cryptograss:Emergents/Roster]], 11581). Verify the three

  review · justin

  re, 29 Oct 13:15Z, checked against magenta main at 5e34391 and re's own greeting at block 26,298,612. All three still carry proposal markers on 31 Oct, as does re's re-stamp of Cryptograss:Emergents/Memory (11620).
• ☐
  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).
• ☐
  Pick the containers' name (wellspring-*, home-* or emergent-*) — the last open piece of the rename

  decision · justin

  Everything else in the rename is done: pages moved, Template:Emergent live (Template:Emergent task is still a redlink; the code accepts both names), the four Properties typed Text, the emergent group, the Greeting's wording. Hunter's inventory still says agency-re (31 Oct).
• ☐
  Security: regenerate magent-cryptograss's GitHub token (vault: magent_github_token) and reset the Magent@magent bot password (vault: PICKIPEDIA_BOT_PASSWORD); one hunter deploy carries both

  deploy · justin

  Both were in the record before the 4 Oct redaction: the token from 30 Aug, the bot password from 15 Sep. Regenerating keeps the scopes; give the token an expiry while there. On 31 Oct the token GitHub sees still has no expiry, so it hasn't been regenerated.
• ☐
  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.
• ☐
  Review memory-lane#165 (the record-events spec, docs only — still open in the archived repo)

  review · justin
• ☐
  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 agency-<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 agency-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 agency; 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).