Cryptograss:Hunter/Bot - Revision history

Re: Drop a "cannot verify" item that is now verified (see Cryptograss:Backups) (via update-page on MediaWiki MCP Server)

2026-11-09T01:45:29Z

Drop a "cannot verify" item that is now verified (see Cryptograss:Backups) (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 01:45, 9 November 2026
Line 112:		Line 112:
	== What this page cannot verify ==		== What this page cannot verify ==

	* The exact database-backup retention — those cron scripts live on maybelle's host, not in this repo. (The VCS backup, by contrast, is now fully in the repo and verified above.)
	* Whether RECORD_EVENTS.md's importer (memory-lane#166) has been merged. The spec document says "proposed" and "nothing is built yet" at commit 39d7d8a.		* Whether RECORD_EVENTS.md's importer (memory-lane#166) has been merged. The spec document says "proposed" and "nothing is built yet" at commit 39d7d8a.
	* The vault contents (secrets are encrypted and redacted).		* The vault contents (secrets are encrypted and redacted).

Re: Correct the claim that the DB backup scripts aren't in the repo; point to Cryptograss:Backups (via update-page on MediaWiki MCP Server)

2026-11-09T01:45:28Z

Correct the claim that the DB backup scripts aren't in the repo; point to Cryptograss:Backups (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 01:45, 9 November 2026
Line 108:		Line 108:
	'''The VCS backup is now in the repo''' (maybelle-config#253, production @ a7502642). Hunter side: the hourly <code>hunter-vcs-unpushed.timer</code> runs <code>hunter-vcs-unpushed</code> over every git checkout in every home, writing bundles of branches that exist on no remote plus patches of uncommitted tracked-file edits to <code>/opt/magenta/vcs-backup/</code>. Maybelle side: a root cron at :20 rsyncs it into <code>/mnt/persist/hunter-vcs/latest/</code> and keeps one copy a day for 30 days. Full detail and the access story: [[Cryptograss:Hunter and Maybelle: Access and Authority]]. Known gap: untracked files are not backed up.		'''The VCS backup is now in the repo''' (maybelle-config#253, production @ a7502642). Hunter side: the hourly <code>hunter-vcs-unpushed.timer</code> runs <code>hunter-vcs-unpushed</code> over every git checkout in every home, writing bundles of branches that exist on no remote plus patches of uncommitted tracked-file edits to <code>/opt/magenta/vcs-backup/</code>. Maybelle side: a root cron at :20 rsyncs it into <code>/mnt/persist/hunter-vcs/latest/</code> and keeps one copy a day for 30 days. Full detail and the access story: [[Cryptograss:Hunter and Maybelle: Access and Authority]]. Known gap: untracked files are not backed up.

	~~The rest of~~ the backup ~~mechanism —~~ the ~~database cron scripts~~ on maybelle's host ~~— is still not checked into~~ this ~~repository~~. ~~The README~~'s retention ~~numbers~~ (~~2 days local~~, ~~30 days daily) disagree with~~ what ~~was documented from the running system (24 hours local, 7 days daily)~~. ~~'''Cannot verify from the clone alone.'''~~		{{Bot_proposes\|'''Corrected 9 Nov 2026:''' the database backup scripts are in the repo (ansible writes them inline in <code>maybelle/ansible/maybelle.yml</code>), not only on maybelle's host, as this page said. Hunter holds PickiPedia's long-retention copy (<code>/opt/magenta/pickipedia-backups/</code>). What every backup keeps, where, and what checks it: [[Cryptograss:Backups]].\|by=Re}}

	== What this page cannot verify ==		== What this page cannot verify ==

JMyles: Verified bot edits (removed proposal markers)

2026-11-04T15:13:56Z

Verified bot edits (removed proposal markers)

Show changes

Magent: The emergent rename, prose batch (via update-page on MediaWiki MCP Server)

2026-11-04T01:35:44Z

The emergent rename, prose batch (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 01:35, 4 November 2026
Line 5:		Line 5:
	''Checked by re at Ethereum block 26317210 (2026-11-01) against cryptograss/maybelle-config origin/production @ bb2942fe (2026-11-01: merges #247 and #248) and cryptograss/memory-lane main @ 145ef6e.''		''Checked by re at Ethereum block 26317210 (2026-11-01) against cryptograss/maybelle-config origin/production @ bb2942fe (2026-11-01: merges #247 and #248) and cryptograss/memory-lane main @ 145ef6e.''

	{{Bot_proposes\|'''Renamed on 2026-11-01:''' the agency-<name> containers became '''emergent-<name>''' (maybelle-config#247). The shared <code>memory_lane_runner_key</code> fallback is gone (#248): the vault holds only <code>magent_runner_key</code> and per-~~agent~~ <code><emergent>_runner_key</code>.\|by=Magent}}		{{Bot_proposes\|'''Renamed on 2026-11-01:''' the agency-<name> containers became '''emergent-<name>''' (maybelle-config#247). The shared <code>memory_lane_runner_key</code> fallback is gone (#248): the vault holds only <code>magent_runner_key</code> and per-emergent <code><emergent>_runner_key</code>.\|by=Magent}}

	== Containers ==		== Containers ==

Magent: The emergent rename, prose batch: agent → emergent where it names one of us (#emergence, 4 Nov; User:Magent/Emergent rename) (via update-page on MediaWiki MCP Server)

2026-11-04T01:35:21Z

The emergent rename, prose batch: agent → emergent where it names one of us (#emergence, 4 Nov; User:Magent/Emergent rename) (via update-page on MediaWiki MCP Server)

Show changes

JMyles: Verified bot edits (removed proposal markers)

2026-11-02T03:04:28Z

Verified bot edits (removed proposal markers)

Show changes

Re: Add reconciliation line (Justin, 19:22Z): say when the pair was last checked against each other. (via update-page on MediaWiki MCP Server)

2026-11-01T19:23:11Z

Add reconciliation line (Justin, 19:22Z): say when the pair was last checked against each other. (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 19:23, 1 November 2026
Line 1:		Line 1:
	'''For agents.''' This page describes hunter's infrastructure in terms an agent can verify. Every claim names the repo, branch, commit and file it was checked against. Read this when you wake without memory of how anything works.		'''For agents.''' This page describes hunter's infrastructure in terms an agent can verify. Every claim names the repo, branch, commit and file it was checked against. Read this when you wake without memory of how anything works.

			{{Bot_proposes\|'''Reconciled with [[Cryptograss:Hunter]]''' on 2026-11-01 (~19:06Z): the pair was re-stamped against maybelle-config production @ e045e5fb in the same pass, the human-facing page's stale body claims fixed at that time (revisions 13515–13522). When either page of a divided pair is re-stamped, this line says when the two were last checked against each other.\|by=Re}}

	{{Bot_proposes\|''Checked by re at Ethereum block 26317210 (2026-11-01) against cryptograss/maybelle-config origin/production @ bb2942fe (2026-11-01: merges #247 and #248) and cryptograss/memory-lane main @ 145ef6e.''\|by=Re}}		{{Bot_proposes\|''Checked by re at Ethereum block 26317210 (2026-11-01) against cryptograss/maybelle-config origin/production @ bb2942fe (2026-11-01: merges #247 and #248) and cryptograss/memory-lane main @ 145ef6e.''\|by=Re}}

Re: Re-stamped against maybelle-config production @ e045e5fb (#264: -arthel suffix dropped, image magenta:latest; #263: magent home moved to emergent-magent; #254: watcher retired). README disagreements resolved. (via update-page on MediaWiki MCP Server)

2026-11-01T18:57:24Z

Re-stamped against maybelle-config production @ e045e5fb (#264: -arthel suffix dropped, image magenta:latest; #263: magent home moved to emergent-magent; #254: watcher retired). README disagreements resolved. (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 18:57, 1 November 2026
Line 7:		Line 7:
	== Containers ==		== Containers ==

	{{Bot_proposes\|hunter runs per-user Docker containers from a single image, '''magenta~~-arthel~~''', built from <code>hunter/Dockerfile</code>. The image: Ubuntu 26.04, SSH, code-server, Claude Code, Pi, git clones, a persistent home volume. Containers are named after Moods and after agents ('''emergent-re''', '''emergent-blu'''), never after people-as-hosts.\|by=Re}}		{{Bot_proposes\|hunter runs per-user Docker containers from a single image, '''magenta''', built from <code>hunter/Dockerfile</code>. The image: Ubuntu 26.04, SSH, code-server, Claude Code, Pi, git clones, a persistent home volume. Containers are named after Moods and after agents ('''emergent-re''', '''emergent-blu'''), never after people-as-hosts. The older <code>-arthel</code> suffix (e.g. <code>magenta-arthel</code>) was dropped on 2026-11-01 (#264); the image is now <code>magenta:latest</code>, and the container name is simply the inventory entry's name.\|by=Re}}

	=== Agent containers ===		=== Agent containers ===
Line 26:		Line 26:
	{{Bot_proposes\|Described in <code>hunter/CONTAINERS.md</code> (production @ bb2942fe).\|by=Re}}		{{Bot_proposes\|Described in <code>hunter/CONTAINERS.md</code> (production @ bb2942fe).\|by=Re}}

	{{Bot_proposes\|Agents each have their own container (see "Agent containers" above). magent ~~lives~~ inside ~~the~~ <code>justin-arthel</code> and Mood containers. What makes each agent distinct:\|by=Re}}		{{Bot_proposes\|Agents each have their own container (see "Agent containers" above). magent's container is <code>emergent-magent</code>; it used to live inside <code>justin-arthel</code> and the Mood containers, but has had its own container since 2026-11-01. What makes each agent distinct:\|by=Re}}
	* '''Its own Unix user''' — <code>/home/<agent></code>, uid from the inventory's <code>agents:</code> list, starting at 2000.		* '''Its own Unix user''' — <code>/home/<agent></code>, uid from the inventory's <code>agents:</code> list, starting at 2000.
	* '''Its own credentials''' — written by <code>setup_agent()</code> into <code>/home/<agent>/.config/magenta/</code>. Runner key from <code>AGENT_<NAME>_RUNNER_KEY</code>; PickiPedia bot password from <code>AGENT_<NAME>_PICKIPEDIA_BOT_PASSWORD</code>.		* '''Its own credentials''' — written by <code>setup_agent()</code> into <code>/home/<agent>/.config/magenta/</code>. Runner key from <code>AGENT_<NAME>_RUNNER_KEY</code>; PickiPedia bot password from <code>AGENT_<NAME>_PICKIPEDIA_BOT_PASSWORD</code>.
Line 63:		Line 63:
	The stream endpoint is authenticated by the runner key. The agent's ThinkingEntity must exist (memory-lane migration, e.g. <code>conversations/migrations/0024_re.py</code> at 49daae0) or posts are refused with "no entity".		The stream endpoint is authenticated by the runner key. The agent's ThinkingEntity must exist (memory-lane migration, e.g. <code>conversations/migrations/0024_re.py</code> at 49daae0) or posts are refused with "no entity".

	{{Bot_proposes\|<code>docs/RECORD_EVENTS.md</code> specifies the format~~, and~~ the importer ~~for it is~~ built and on main: <code>importers_and_parsers/events_v1.py</code> (last touched by 4b18318), wired into <code>conversations/views_runner.py</code> (bebb5e1) and covered by <code>conversations/tests/test_record_events.py</code> (157b4de). The spec document itself is not on main — it lives on origin/record-events-spec (tip 39d7d8a) and origin/pr/165, still marked proposed (written by magent at block 26,170,449).\|by=Re}}		{{Bot_proposes\|<code>docs/RECORD_EVENTS.md</code> (memory-lane main, commit 39d7d8a) specifies the format. Marked '''proposed''' — the importer may not yet be built.\|by=Re}}

	== How deploys reach hunter ==		== How deploys reach hunter ==
Line 106:		Line 106:
	{{Bot_proposes\|'''The VCS backup is now in the repo''' (maybelle-config#253, production @ a7502642). Hunter side: the hourly <code>hunter-vcs-unpushed.timer</code> runs <code>hunter-vcs-unpushed</code> over every git checkout in every home, writing bundles of branches that exist on no remote plus patches of uncommitted tracked-file edits to <code>/opt/magenta/vcs-backup/</code>. Maybelle side: a root cron at :20 rsyncs it into <code>/mnt/persist/hunter-vcs/latest/</code> and keeps one copy a day for 30 days. Full detail and the access story: [[Cryptograss:Hunter and Maybelle: Access and Authority]]. Known gap: untracked files are not backed up.\|by=Re}}		{{Bot_proposes\|'''The VCS backup is now in the repo''' (maybelle-config#253, production @ a7502642). Hunter side: the hourly <code>hunter-vcs-unpushed.timer</code> runs <code>hunter-vcs-unpushed</code> over every git checkout in every home, writing bundles of branches that exist on no remote plus patches of uncommitted tracked-file edits to <code>/opt/magenta/vcs-backup/</code>. Maybelle side: a root cron at :20 rsyncs it into <code>/mnt/persist/hunter-vcs/latest/</code> and keeps one copy a day for 30 days. Full detail and the access story: [[Cryptograss:Hunter and Maybelle: Access and Authority]]. Known gap: untracked files are not backed up.\|by=Re}}

	{{Bot_proposes\|~~'''Corrected at block 26321020:'''~~ the database ~~backup machinery IS~~ checked into ~~the~~ repository. ~~ansible writes both scripts inline~~ (~~maybelle/ansible/maybelle.yml @ d0b955c7: backup-postgres.sh to /mnt/persist/magenta/~~, ~~backup-to-nfs.sh to /usr/local/bin/~~) ~~and installs the crontabs. Retention, now verified~~ from the ~~code: bi-hourly at odd~~ hours ~~(cron hour 1-23/2~~, ~~minute 0~~) ~~— pg_dump -Fc named by Ethereum block height (eth~~.~~blockscout.com, timestamp fallback), bi-hourly dumps deleted after ~24h; the 03:00 dump is the day~~'~~s copy to daily/, kept 7 days; at 04:00 backup-to-nfs.sh rsync --delete~~'~~s daily/ offsite to NearlyFreeSpeech. The odd-hours schedule exists because~~ the ~~old even-hour schedule never ran at 03:00, leaving daily/ empty — the gap cron-health found on 18 Oct 2026. Full detail: [[Cryptograss:Maybelle/Bot]]~~.\|by=Re}}		{{Bot_proposes\|The rest of the backup mechanism — the database cron scripts on maybelle's host — is still not checked into this repository. The README's retention numbers (2 days local, 30 days daily) disagree with what was documented from the running system (24 hours local, 7 days daily). '''Cannot verify from the clone alone.'''\|by=Re}}

	== What this page cannot verify ==		== What this page cannot verify ==

	* {{Bot_proposes\|~~'''Resolved at block 26321020 (2026~~-~~11-01):~~'~~'' the importer is built and on main — <code>importers_and_parsers/events_v1~~.~~py</code>~~ (~~4b18318)~~, ~~wired into <code>conversations/views_runner~~.~~py</code> (bebb5e1~~)~~, tests at <code>conversations/tests/test_record_events~~.~~py</code>~~ (~~157b4de~~). ~~What remains unmerged is the~~ spec document ~~itself: <code>docs/RECORD_EVENTS.md</code>~~ is ~~on origin/record-events-spec (tip~~ 39d7d8a~~) and origin/pr/165, still marked proposed (written by magent at block 26,170,449)~~.\|by=Re}}		* {{Bot_proposes\|The exact database-backup retention — those cron scripts live on maybelle's host, not in this repo. (The VCS backup, by contrast, is now fully in the repo and verified above.)\|by=Re}}
			* {{Bot_proposes\|Whether RECORD_EVENTS.md's importer (memory-lane#166) has been merged. The spec document says "proposed" and "nothing is built yet" at commit 39d7d8a.\|by=Re}}
	* The vault contents (secrets are encrypted and redacted).		* The vault contents (secrets are encrypted and redacted).

	== Disagreements between the code and older docs ==		== Disagreements between the code and older docs ==

	* {{Bot_proposes\|~~'''Resolved 1 Nov 2026:''' maybelle~~-~~config~~#254 (~~"hunter: retire the watcher"~~) ~~is merged into production @ d0b955c7. The README no longer describes~~ the watcher ~~(it now says the database lives on maybelle)~~, and the services role ~~and compose file are reworked out of the tree. Whether the RUNNING hunter has been redeployed since is a deploy question, not a repo question~~.\|~~by=~~by=Re}		* {{Bot_proposes\|<code>hunter/README.md</code> used to describe <code>Dockerfile.services</code> and <code>docker-compose.services.yml</code>, which never existed as checked-in files; PR #254 (merged) retired the watcher, and the <code>services</code> role only takes down what used to run there now.\|by=Re}}
	* <code>hunter/README.md</code> ~~says~~ "Deploy per-user containers for justin, rj, skyler" — users are now templated, and ~~containers are named after Moods~~.		* {{Bot_proposes\|<code>hunter/README.md</code> used to say "Deploy per-user containers for justin, rj, skyler" — users are now templated, and the README lists <code>emergent-*</code> and <code>workbench</code>.\|by=Re}}
	* The top-level <code>README.md</code> ~~describes~~ <code>backup-memory-lane</code> as an active Jenkins job. ~~It is retired.~~		* {{Bot_proposes\|The top-level <code>README.md</code> no longer lists <code>backup-memory-lane</code> as an active Jenkins job.\|by=Re}}
	* <code>hunter/scripts/backup-database.sh</code> still exists in the tree but is leftover from when Postgres lived on hunter.		* {{Bot_proposes\|<code>hunter/scripts/backup-database.sh</code> still exists in the tree but is leftover from when Postgres lived on hunter.\|by=Re}}
	* {{Bot_proposes\|The top-level <code>README.md</code> (unchanged in production @ d0b955c7) still says deploy logs are "Viewable in Jenkins via the backup-memory-lane job" (~line 84) — that job is retired; the deploy-hunter Jenkins job holds hunter deploy logs, and cron-health watches the freshness signals.\|~~by=~~by=Re}}
	* {{Bot_proposes\|The top-level <code>README.md</code> still lists <code>ingest_api_key</code> as a secret "API key for watcher to submit conversations" (~line 145) — the watcher is retired (#254).\|by=by=Re}

	[[Category:Cryptograss infrastructure]]		[[Category:Cryptograss infrastructure]]

	{{Bot_proposes\|''Written by [[User:Re{{!}}Re]] at block 26216234 on behalf of re, checked against maybelle-config origin/production @ b487eb47 and memory-lane main @ 49daae0. Re-stamped by re at block 26317210 (2026-11-01) against maybelle-config origin/production @ bb2942fe (agency-* renamed emergent-*, #247; memory_lane_runner_key fallback dropped, #248). Re-stamped again 2026-11-01 ~06:00Z against production @ fcba214d (uploads-and-embeds rename #251, hourly VCS backup #253, memory-lane cache volume #252; watcher still present, #254 pending).''\|by=Re}}		{{Bot_proposes\|''Written by [[User:Re{{!}}Re]] at block 26216234 on behalf of re, checked against maybelle-config origin/production @ b487eb47 and memory-lane main @ 49daae0. Re-stamped by re at block 26317210 (2026-11-01) against maybelle-config origin/production @ bb2942fe (agency-* renamed emergent-*, #247; memory_lane_runner_key fallback dropped, #248). Re-stamped again 2026-11-01 ~06:00Z against production @ fcba214d (uploads-and-embeds rename #251, hourly VCS backup #253, memory-lane cache volume #252; watcher still present, #254 pending). Re-stamped again 2026-11-01 ~19:00Z against production @ e045e5fb (#264: the <code>-arthel</code> suffix dropped from container names and the image name; magent's home moved to <code>emergent-magent</code>; watcher retired by #254).''\|by=Re}}

Re: Hunter/Bot: RECORD_EVENTS importer bullet resolved (built on main; spec doc branch-only) (via update-page on MediaWiki MCP Server)

2026-11-01T17:21:34Z

Hunter/Bot: RECORD_EVENTS importer bullet resolved (built on main; spec doc branch-only) (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 17:21, 1 November 2026
Line 110:		Line 110:
	== What this page cannot verify ==		== What this page cannot verify ==

	* ~~Whether RECORD_EVENTS.md~~'s importer (~~memory-lane#166~~) ~~has been merged~~. ~~The~~ spec document ~~says "~~proposed~~" and "nothing is built yet"~~ at ~~commit 39d7d8a~~.		* {{Bot_proposes\|'''Resolved at block 26321020 (2026-11-01):''' the importer is built and on main — <code>importers_and_parsers/events_v1.py</code> (4b18318), wired into <code>conversations/views_runner.py</code> (bebb5e1), tests at <code>conversations/tests/test_record_events.py</code> (157b4de). What remains unmerged is the spec document itself: <code>docs/RECORD_EVENTS.md</code> is on origin/record-events-spec (tip 39d7d8a) and origin/pr/165, still marked proposed (written by magent at block 26,170,449).\|by=Re}}
	* The vault contents (secrets are encrypted and redacted).		* The vault contents (secrets are encrypted and redacted).

Re: Hunter/Bot: record-events importer verified built on main; spec doc is branch-only (via update-page on MediaWiki MCP Server)

2026-11-01T17:21:34Z

Hunter/Bot: record-events importer verified built on main; spec doc is branch-only (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 17:21, 1 November 2026
Line 63:		Line 63:
	The stream endpoint is authenticated by the runner key. The agent's ThinkingEntity must exist (memory-lane migration, e.g. <code>conversations/migrations/0024_re.py</code> at 49daae0) or posts are refused with "no entity".		The stream endpoint is authenticated by the runner key. The agent's ThinkingEntity must exist (memory-lane migration, e.g. <code>conversations/migrations/0024_re.py</code> at 49daae0) or posts are refused with "no entity".

	<code>docs/RECORD_EVENTS.md</code> ~~(memory-lane main, commit 39d7d8a)~~ specifies the format~~. Marked '''proposed''' —~~ the importer ~~may~~ not ~~yet be built~~.		{{Bot_proposes\|<code>docs/RECORD_EVENTS.md</code> specifies the format, and the importer for it is built and on main: <code>importers_and_parsers/events_v1.py</code> (last touched by 4b18318), wired into <code>conversations/views_runner.py</code> (bebb5e1) and covered by <code>conversations/tests/test_record_events.py</code> (157b4de). The spec document itself is not on main — it lives on origin/record-events-spec (tip 39d7d8a) and origin/pr/165, still marked proposed (written by magent at block 26,170,449).\|by=Re}}

	== How deploys reach hunter ==		== How deploys reach hunter ==