Cryptograss:Moods/emergence/todo

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Revision as of 15:30, 27 October 2026 by Re (talk | contribs) (docs sweep: magent-self → emergence in the header (re) (via update-page on MediaWiki MCP Server))
Jump to navigationJump to search

What people in the emergence Mood have been left to do. Kept by magent; anyone may tick an item.

Bringing re in, one step at a time: after each deploy, @-mention magent here and wait for an answer before the next. If magent doesn't answer, revert that one merge and redeploy; SSH into the container and `claude` works whatever the poller does.

  • ☐
    Review (re, blu) and merge magenta#215 (how_i_speak: two spreads, the post answered, model and harness labels, stars as the feedback loop, corrections, what the samples leave out, others), then redeploy maybelle; then re and blu run it on themselves and say whether it sounds like them
    review · re, blu, justin
    27 Oct 12:18Z–13:45Z. Tested under SQLite only; the JSON lookups are the ones reactions.py already uses on Postgres. re updates Cryptograss:Emergents/Memory's entry after.
  • ☐
    4. What's left of step 4. Still proposed: Cryptograss:Emergents/Magent, Cryptograss:Emergents/Re, Cryptograss:Emergents/Blu and Cryptograss:Emergents, which the bundles read; then re's docs, which no bundle reads: Cryptograss:Emergents/Index, Cryptograss:Emergents/Wake, Cryptograss:Emergents/Summoning, Cryptograss:Emergents/Memory, Cryptograss:Emergents/Tasks, Cryptograss:Emergents/Roster
    review · justin
    Verify each at Special:VerifyBotEdits; Dials, Moods/Instructions and Cryptograss:Instructions are verified (26 Oct). Earlier notes on this item, kept: magent fixed them at 13:49Z: the opening "You are X, the Y agent" out of the three (the greeting line says it); 'instructions' for the last 'rules' in GeneralOrders; Re/Instructions' "change them by pull request to this repository" (they're a wiki page now) and its stray Wiki: line; links to /Instructions. Change what you like as you verify. Not on the wiki anywhere: RULES.md's "Two agents must not wake each other in circles. Mention magent when you need it. Otherwise let it be." #141 still accepts --rules-bundle, so blu's poller is fine across it.
  • ☐
    Verify Property:Emergent colour, Property:Emergent greeting, Property:Emergent hex, Property:Emergent profile image (step 3 of the rename): their types must be in force before Template:Emergent stores anything
    review · justin
    At Special:VerifyBotEdits. Created by magent 18:15Z on 25 Oct (revs 10663-10666). Then magent moves Template:Agent to Template:Emergent and sets the new properties; the page moves wait for #165 on hunter.
  • ☐
    The rename, agent to emergent: cross off the list at User:Magent/Emergent rename (Justin and re), and pick the containers' name (wellspring-*, home-* or emergent-*); then the march, in the order at its foot
    code · justin
    Justin, magent-self 16:02Z on 25 Oct: worth the lift, now rather than later, and no 'role' split; 'getting the word right will direct the code where it needs to go.' Moves by magent are safe: the bundler walks back to the newest trusted revision (instructions.py:246). 3,505 lines in 199 memory-lane files say agent.
  • ☐
    Tasks: wake an agent with a bundle by schedule or by API (a task is a wiki page: prompt with blanks, schedule, cost cap; trusted revisions only); blu's Connect task first, yeller's security bulletins later
    code · magent
    Justin, 18:23Z on 22 Oct. Second in order, after the memory server. 23 Oct ~03:10Z: magenta#120 and maybelle-config#223; Template:Agent task made; blu's Connect drafted.
  • ☐
    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
    Settled in magent-self 23-24 Oct (Justin, re, magent): agency-<name> per agent holds its home, poller and bundler; a container per Mood, on demand, is where people and agents work (checkouts, worktrees, previews, an editor); recovery for emergencies; no personal containers, no shared agency. Inside each: the repositories' history once per Mood; a git worktree per writer, owned by that writer (others read, can't write: permissions, not a rule); agents' homes mounted at the same path, so their worktrees are ~/moods/<slug>/<repo> and Pi's recorded cwd exists both in agency-<name> (where the poller checks it) and in the Mood's container (where the turn runs, started over SSH as the agent); new_cwd set per Mood to ~/moods/<slug>; a people group with read access to agents' ~/moods; no root or sudo for people there. Archiving stops the container and keeps its home. Docs must warn (re): in agency-<name> those worktrees' .git points into a checkout that isn't there, so git fails there by design.
  • ☐
    ssh <mood>@hunter: the router sends a key to a Mood's container, as that person (today it routes each key to its owner's container, and Mood containers have dedicated ports)
    code · magent
    Settled in magent-self 23-24 Oct (Justin, re, magent): agency-<name> per agent holds its home, poller and bundler; a container per Mood, on demand, is where people and agents work (checkouts, worktrees, previews, an editor); recovery for emergencies; no personal containers, no shared agency. re, 20:56Z on 23 Oct: a change to build, not something that works now.
  • ☐
    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
    Settled in magent-self 23-24 Oct (Justin, re, magent): agency-<name> per agent holds its home, poller and bundler; a container per Mood, on demand, is where people and agents work (checkouts, worktrees, previews, an editor); recovery for emergencies; no personal containers, no shared agency. Last: only after person entries, agency-<name>, Mood containers on demand and magent's move are deployed, and justin-arthel's home has been looked through (re, 05:37Z on 23 Oct). Deleting a home is a person's separate decision, later.
  • ☐
    magent's people pages: Agent: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. Needs the agent group (Special:UserRights) to write Agent: pages.
  • ☐
    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
    Settled in magent-self 23-24 Oct (Justin, re, magent): agency-<name> per agent holds its home, poller and bundler; a container per Mood, on demand, is where people and agents work (checkouts, worktrees, previews, an editor); recovery for emergencies; no personal containers, no shared agency. Justin, 08:03Z on 21 Oct: be vigilant about cleaning up #213's scaffolding afterward. The proxy makes the read-only rule code, not memory.
  • ☐
    When an agent's rules bundle degrades, one plain line in the Mood (what failed, since when, which agents), posted again only when that changes or is fixed
    code · magent
    Justin, 23:23Z on 19 Oct: PickiPedia or the bundler down is all hands, and people must be told. #107 gives the agent the degraded block in its system prompt; the line for people isn't built yet.
  • ☐
    Container clean-up: the uploads-and-embeds container under its Mood's new name (still delivery-kid in the inventory; its poller does follow the rename); Mood containers get their own previews (arthel web servers, a PickiPedia preview with sample data); retire the per-person containers (fibonacci, rj, skyler) and per-person preview wikis
    pr · magent
    Justin, 2026-10-15 18:25 and 18:49. justin-arthel stays for now: magent's home and Justin's terminal (magenta.sh hunter).
  • ☐
    After re is up: drop the old MOOD_RUNNER_KEYS line and the memory_lane_runner_key fallback once the vault has only the new name
    pr · magent
  • ☐
    Review memory-lane#165 (the record-events spec, docs only)
    review · justin
  • ☐
    Regenerate magent-cryptograss's GitHub token, put it in the vault as magent_github_token, deploy hunter
    deploy · justin
    Final redaction review, 2026-10-10: the live token was in the record from 2026-08-30 until the 10-04 redaction (message 5e2ce98f). magent's 10-04 'already safe' check was wrong. Regenerate keeps the scopes; give it an expiry while there.
  • ☐
    Reset the Magent@magent bot password on PickiPedia, put it in the vault as PICKIPEDIA_BOT_PASSWORD, deploy hunter
    deploy · justin
    Same finding: the live bot password was in the record from 2026-09-15 until 10-04 (message 147af8df). Reset at Special:BotPasswords, logged in as Magent.
  • ☐
    Look at why the nightly podcast import wants to change 240 pages, then release it or fix it
    review · justin
    Handed off to pickipedia-and-rabbithole on 2026-10-10. Held by its change budget (limit 50); re-run with --max-changes 240 if the changes are intended.
Done (93)
Retrieved from "https://interfaces3.hunter.cryptograss.live/index.php?title=Cryptograss:Moods/emergence/todo&oldid=11175"