Cryptograss:Moods/emergence/todo: Difference between revisions
Automated edit (via update-page on MediaWiki MCP Server) |
Automated edit (via update-page on MediaWiki MCP Server) |
||
| Line 2: | Line 2: | ||
<todo> | <todo> | ||
- task: "1. Redeploy hunter at leisure, for magenta#357 (merged 2 Nov 04:24Z)" | - task: "1. Least privilege, step 2 (hunter): say yes or no to the router enforcing people:, with emergent-magent as people: [justin]; and to workbench losing magent's GitHub and wiki logins" | ||
who: justin | |||
kind: decision | |||
note: "Checked 2 Nov 04:31Z on production b6f49c95. route-ssh.sh never reads people:, so all four keys (justin, rj, skyler, fibonacci) can open emergent-magent, which holds docker.sock (root on hunter), and emergent-re/-blu too. workbench runs as user magent with magent-cryptograss's GitHub token and Magent's bot password, so anyone there pushes and edits as magent. On a yes, magent writes the maybelle-config PR." | |||
- task: "2. Redeploy hunter at leisure, for magenta#357 (merged 2 Nov 04:24Z)" | |||
who: justin | who: justin | ||
kind: deploy | kind: deploy | ||
Revision as of 04:31, 2 November 2026
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.
- ☐1. Least privilege, step 2 (hunter): say yes or no to the router enforcing people:, with emergent-magent as people: [justin]; and to workbench losing magent's GitHub and wiki loginsChecked 2 Nov 04:31Z on production b6f49c95. route-ssh.sh never reads people:, so all four keys (justin, rj, skyler, fibonacci) can open emergent-magent, which holds docker.sock (root on hunter), and emergent-re/-blu too. workbench runs as user magent with magent-cryptograss's GitHub token and Magent's bot password, so anyone there pushes and edits as magent. On a yes, magent writes the maybelle-config PR.
- ☐2. Redeploy hunter at leisure, for magenta#357 (merged 2 Nov 04:24Z)Comments and one log line; no hurry.
- ☐Re-send a turn's lost stream events from its transcript (magenta#358), Pi turns tooCarried 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 variablesSmall 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 neededThe 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_HOSTSDocs 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) removedThe 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)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; publicJustin, 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).