ATProto Integration Ideas

Just a few thoughts on atproto integration.

Instead of logging in with your atproto handle, we implement an “add your player” flow that only needs a sign-in step once, run in the browser. After that the new player takes one of the slots in the game.

As lexicons I see two things: de.pixelsp33d.player and de.pixelsp33d.level, each with its own designer tool in the browser, writing its results as lexicon entries to the player’s own PDS.

Huge interop opportunities with trezy.codes games lexicons. Players can borrow ideas from rpg.actor similarly to how we borrowed the HKDF method for generative art - basically all kinds of traits can be built in a similar way. pixelsp33d game can integrate with rpg.actor directly as the player avatar; otherwise we need to write a game designer (level, player avatar) that writes records on the user’s behalf on their PDS. Loaded in the game with the “add player” flow as described above.

Two possible contribution flows: 1) select from a palette derived from pixelsp33d lore - music and FX can be written by our tooling, or (in the case of bytebeat) re-use existing library content (assuming all is in the public domain, royalty-free, BSD). 2) Coders can contribute via Claude Skills and code-forks and build against a spec provided by us.

Bottom line: this connects with haiku.garden’s guide, which was discussed on the community discourse as a covenant, etc. Two tasks: minting credentials is one of them.

Some existing interop candidates from my own fleet:

pixelsp33d as game host and lexicon authority (NSID) uervel.net as player example kn00t and Mama currently have no protocol provenance

haiku.garden as an episode or level design space memo.dog as a guard similar to the tailored-clothes guard

atmospheric.computer as the project handle

research tasks

Check out trezy.codes’ games.games ideas. Revisit the gen art in haiku.garden and its two origin sites.

MVP is the “add player” flow and a minimal lexicon. Then post in the community forum.