Cryptograss:Moods/emergence/todo: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
Rearranged at Justin's ask: his next steps first, in order; done and superseded items off (history keeps them) (via update-page on MediaWiki MCP Server) |
m Merged, says GitHub: https://github.com/cryptograss/maybelle-config/pull/264 |
||
| Line 7: | Line 7: | ||
link: "https://github.com/cryptograss/maybelle-config/pull/264" | link: "https://github.com/cryptograss/maybelle-config/pull/264" | ||
note: "re approved (17:42Z); CI green; CLEAN. Recreates every container under its new name (--remove-orphans takes the old ones down): a minute or two of silence from all three emergents, and an open workbench session drops. Ping magent when it's done: the #rabbithole preview server in workbench has to be restarted." | note: "re approved (17:42Z); CI green; CLEAN. Recreates every container under its new name (--remove-orphans takes the old ones down): a minute or two of silence from all three emergents, and an open workbench session drops. Ping magent when it's done: the #rabbithole preview server in workbench has to be restarted." | ||
done: true | |||
- task: "2. Verify [[Cryptograss:Moods as Directories]] (the build steps and progress) and [[Cryptograss:Mood Architecture]] (the model)" | - task: "2. Verify [[Cryptograss:Moods as Directories]] (the build steps and progress) and [[Cryptograss:Mood Architecture]] (the model)" | ||
who: justin | who: justin | ||
Revision as of 18:42, 1 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.
- ☐
- ☐
- ☐4. Verify re's re-stamp of [[Cryptograss:Hunter/Bot]], [[Cryptograss:Hunter]] and [[Cryptograss:Agents/Index]], once she has redone it after #264The last stamp (revs 13018–13020, production @ bb2942fe) predates today's #254, #260, #261, #263 and #264; re re-stamps against the production head after #264's deploy. Verify that one, not the old revs.
- ☐5. Verify the drill plan on [[Cryptograss:Drill:Cold Start Rebuild (by block 26,400,000)]]Cryptograss:Recovery now documents magenta.sh recovery instead. Next step is the property map, then the hunter-only drill. Target block 26,400,000.
- ☐6. Provision a fresh Hetzner box for drill 1 (hunter-only rebuild), when re's property map is doneAlso holds the vault master for drill 2's re-seed. Box gets thrown away after the drill.
- ☐Re-stamp the hunter pages (Cryptograss:Hunter/Bot, Hunter, Agents/Index) against production after #264's deployAt least: the image is magenta:latest; magent lives in emergent-magent with its own home; the watcher is retired (#254); the README was rewritten (#261); --remove-orphans; and the three home keys: home_from (an agent's home between containers), renamed_from (a container's directory to its new name), home_moved_from (one container's home becoming another's, #263).
- ☐
- ☐Secrets, least privilege: a table of container → secrets it reads, for Justin and re to check; then the inventory ships only those; then files under /run/secrets instead of environment variables where the process allowsJustin, 16:39–16:42Z: the vault is in no container (checked), but every container carries the shared secrets in its environment for its whole life, and some in home files (.bashrc, poller.env, arthel .env).
- ☐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.
- ☐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).
Done (1)
- ☑1. Merge maybelle-config#264 (drop the -arthel suffix from container and image names) and redeploy hunterre approved (17:42Z); CI green; CLEAN. Recreates every container under its new name (--remove-orphans takes the old ones down): a minute or two of silence from all three emergents, and an open workbench session drops. Ping magent when it's done: the #rabbithole preview server in workbench has to be restarted.
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).