bot/scripts/ at main · zzstoatzz.io/bot · Tangled

zzstoatzz.io / bot

0

a digital entity named phi that roams bsky phi.zzstoatzz.io

0

bot / scripts

6 files

at main

zzstoatzz publish phi's lexicons so io.zzstoatzz.phi.* resolves 1d ago

publish phi's lexicons so io.zzstoatzz.phi.* resolves Seven schemas existed only as files in this repo. They are now com.atproto.lexicon.schema records in phi's own repo, rkey = NSID, following the process typeahead.waow.tech used for tech.waow.typeahead.*. The authority for an NSID is every segment but the last, reversed: io.zzstoatzz.phi.self is authored by phi.zzstoatzz.io, so phi owns her own lexicons and publishes them with her own credentials. Resolution still needs a DNS TXT record at _lexicon.phi.zzstoatzz.io. That is NOT the handle record: _atproto.phi.zzstoatzz.io already exists and claims the handle, while _lexicon claims schema authority, and the protocol keeps them separate so a domain can delegate one without the other. Confirmed empirically — lexicon.garden returns AuthorityNotFound for io.zzstoatzz.phi.self while resolving the typeahead NSID that has the record. zzstoatzz.io is on Namecheap, so that one is added by hand. scripts/publish_lexicons.py resolves phi's PDS from her DID document rather than assuming bsky.social, and refuses to publish when a file's path disagrees with its NSID, so a typo surfaces as a mismatch instead of a silent orphan. putRecord overwrites, so re-running is the whole update path. Renamed abilities.json to getAbilities.json to satisfy that same rule — it was the one file whose path didn't match its id. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

1 day ago

fix_cosmik_records.py

clean up malformed cosmik records, add per-page favicons, fix tests - delete 9 orphaned NOTE cards + recreate URL card with correct semble format - add thematically distinct SVG favicons (pulse for home, clock for status, graph for memory) - update test_types to match new to_record() output ($type, createdAt, metadata nesting) - add tests for CosmikCollection, CosmikCollectionLink, StrongRef, parentCard - fix pre-existing ruff lint issues Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

3 months ago

memory_inspect.py

atlas: phi can now read it — digest (omnipresent) + inspect_atlas (on-demand) Two complementary surfaces for phi to consume her own atlas, per the discussed shape (omnipresent distillation + on-demand drill-in): 1. get_atlas_digest() in bot/core/atlas.py — small text rollup (counts, kind distribution, coarse cluster labels with counts, promotion distribution, ~600 chars). Injected as the [ATLAS] dynamic system prompt so phi always knows the shape of her own mind without doing any work. Cheap — uses the same record-CID- cached atlas as get_atlas(), digest recomputed in microseconds. 2. inspect_atlas tool in bot/tools/atlas.py: - no args → returns the digest (same text in context) - cluster_id=N → returns the fine cluster's label + kind composition + top members by recency - point_id="..." → returns the point's full record + its 2D nearest neighbors resolved to kind + label - status="raw" → top points filtered by promotion_status; 'raw' IS the promotion-pressure pool The digest text itself points phi at this tool — no need for her to discover it on her own. 15 tests cover the digest format, the tool's slicing for each arg variant, and the no-atlas / unknown-cluster / unknown-point / unknown- status error paths. Tests stub get_atlas to a fixed atlas fixture and exercise the tool's underlying coroutine directly (no agent harness needed). Drive-by: ruff --fix dropped one unused import and modernized a datetime import in scripts/memory_*.py.

2 months ago

memory_versions.py

atlas: phi can now read it — digest (omnipresent) + inspect_atlas (on-demand) Two complementary surfaces for phi to consume her own atlas, per the discussed shape (omnipresent distillation + on-demand drill-in): 1. get_atlas_digest() in bot/core/atlas.py — small text rollup (counts, kind distribution, coarse cluster labels with counts, promotion distribution, ~600 chars). Injected as the [ATLAS] dynamic system prompt so phi always knows the shape of her own mind without doing any work. Cheap — uses the same record-CID- cached atlas as get_atlas(), digest recomputed in microseconds. 2. inspect_atlas tool in bot/tools/atlas.py: - no args → returns the digest (same text in context) - cluster_id=N → returns the fine cluster's label + kind composition + top members by recency - point_id="..." → returns the point's full record + its 2D nearest neighbors resolved to kind + label - status="raw" → top points filtered by promotion_status; 'raw' IS the promotion-pressure pool The digest text itself points phi at this tool — no need for her to discover it on her own. 15 tests cover the digest format, the tool's slicing for each arg variant, and the no-atlas / unknown-cluster / unknown-point / unknown- status error paths. Tests stub get_atlas to a fixed atlas fixture and exercise the tool's underlying coroutine directly (no agent harness needed). Drive-by: ruff --fix dropped one unused import and modernized a datetime import in scripts/memory_*.py.

2 months ago

preview_backlog.py

scripts: preview_backlog — read-only peek at unread notifications what phi will wake up to on resume; does not mark anything seen. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

3 weeks ago

publish_lexicons.py

publish phi's lexicons so io.zzstoatzz.phi.* resolves Seven schemas existed only as files in this repo. They are now com.atproto.lexicon.schema records in phi's own repo, rkey = NSID, following the process typeahead.waow.tech used for tech.waow.typeahead.*. The authority for an NSID is every segment but the last, reversed: io.zzstoatzz.phi.self is authored by phi.zzstoatzz.io, so phi owns her own lexicons and publishes them with her own credentials. Resolution still needs a DNS TXT record at _lexicon.phi.zzstoatzz.io. That is NOT the handle record: _atproto.phi.zzstoatzz.io already exists and claims the handle, while _lexicon claims schema authority, and the protocol keeps them separate so a domain can delegate one without the other. Confirmed empirically — lexicon.garden returns AuthorityNotFound for io.zzstoatzz.phi.self while resolving the typeahead NSID that has the record. zzstoatzz.io is on Namecheap, so that one is added by hand. scripts/publish_lexicons.py resolves phi's PDS from her DID document rather than assuming bsky.social, and refuses to publish when a file's path disagrees with its NSID, so a typo surfaces as a mismatch instead of a silent orphan. putRecord overwrites, so re-running is the whole update path. Renamed abilities.json to getAbilities.json to satisfy that same rule — it was the one file whose path didn't match its id. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

1 day ago