Cryptograss:Moods/emergence/todo: Difference between revisions
m Merged, says GitHub: https://github.com/cryptograss/maybelle-config/pull/266 |
Automated edit (via update-page on MediaWiki MCP Server) |
||
| Line 1: | Line 1: | ||
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 | 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 and the rest of the least-privilege work live on [[Cryptograss:Moods/ops/todo]]; GitHub and version-control items on [[Cryptograss:Moods/ramp/todo]]. | ||
<todo> | <todo> | ||
- task: "1. | - task: "1. Redeploy hunter, for maybelle-config#266 (merged 11:20Z) and magenta#357" | ||
who: justin | who: justin | ||
kind: | kind: deploy | ||
link: "https://github.com/cryptograss/maybelle-config/pull/266" | link: "https://github.com/cryptograss/maybelle-config/pull/266" | ||
note: " | note: "Then magent updates its own Instructions page (the router no longer lets people into emergent-magent) and checks a refused entry shows in #general." | ||
- task: "2. Put recovery_alert_github_token and recovery_log_private_key in the vault (and the public key in hunter's inventory), merge maybelle-config#267, redeploy maybelle then hunter" | |||
- task: "2. | |||
who: justin | who: justin | ||
kind: | kind: merge | ||
note: " | link: "https://github.com/cryptograss/maybelle-config/pull/267" | ||
note: "A GitHub issue when someone opens recovery, and the session streamed to an append-only log on maybelle. CI green. The token: fine-grained, Issues read+write on recovery_alert_repo only; everyone who should hear watches that repo. Without the vault entries it installs and stays quiet." | |||
- task: "3. Decide how people sign in from workbench, so it can drop magent's GitHub token and Magent's wiki password" | - task: "3. Decide how people sign in from workbench, so it can drop magent's GitHub token and Magent's wiki password" | ||
who: justin | who: justin | ||
| Line 21: | Line 21: | ||
link: "https://github.com/cryptograss/magenta/issues/358" | link: "https://github.com/cryptograss/magenta/issues/358" | ||
note: "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." | note: "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." | ||
- task: "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" | - task: "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" | ||
who: magent | who: magent | ||
Revision as of 11:22, 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 and the rest of the least-privilege work live on Cryptograss:Moods/ops/todo; GitHub and version-control items on Cryptograss:Moods/ramp/todo.
- ☐1. Redeploy hunter, for maybelle-config#266 (merged 11:20Z) and magenta#357Then magent updates its own Instructions page (the router no longer lets people into emergent-magent) and checks a refused entry shows in #general.
- ☐2. Put recovery_alert_github_token and recovery_log_private_key in the vault (and the public key in hunter's inventory), merge maybelle-config#267, redeploy maybelle then hunterA GitHub issue when someone opens recovery, and the session streamed to an append-only log on maybelle. CI green. The token: fine-grained, Issues read+write on recovery_alert_repo only; everyone who should hear watches that repo. Without the vault entries it installs and stays quiet.
- ☐3. Decide how people sign in from workbench, so it can drop magent's GitHub token and Magent's wiki passwordworkbench 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 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.
- ☐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).