Tools
Consent-forward instruments and kits shipped with reproducible builds, bench notes, and explicit operating constraints.
Enter through toolsExperiments in media, systems, and learning
Critical inquiry × hands-on digital practice
build → perform (play, test, break) → document → iterate — the lab runs the full chain.
Systems-first means technical and ethical layers stay legible, consent-forward, and ready for others to audit, remix, and deploy as civic instruments.
Fleet doorway
This practice reads as a fleet, not a pile
Tools, scenes, learning environments, and support systems feed one another. Use the four doors below to enter the part of the fleet you need.
Scenes
Installations and performance systems where participation, control, and operations stay visible instead of disappearing backstage.
Enter through scenesLearning
Curricula, station cards, and quick-start kits that turn digital literacy into civic practice and portable teaching structures.
Enter through learningSystems & Distribution
Deployment, publishing, governance, and care structures that keep the rest of the fleet legible, shared, and maintainable.
Enter through systemsHow To Read This Site
Where truth lives
The site has three layers on purpose. Repos carry the live specifics, studio-notes carries cross-project truth, and Atlas shows how the whole fleet relates.
Project repos
Go there for the current build, code, setup, show logic, and project-specific documentation.
Open repositoriesstudio-notes
Go there for reusable patterns, decisions, trusted reference, and teaching cards harvested from across the fleet.
Open studio-notesAtlas
Go there when you need the relationship map: what supports what, where a project sits, and how the fleet is maintained as a whole.
Open AtlasFleet core
Maps for reading the practice
These are working diagrams, not decorative summaries. They show how the core projects sit inside the tools / scenes / learning / systems ecology, and how the projects feed one another.
Show diagram
Cross-project layer
The fleet stays coherent because cross-project truth has a home
studio-notes is where reusable truth gets distilled: the pattern worth repeating, the reason a choice was made, the baseline worth trusting, and the teaching version that can travel.
Why the archive stays loud
Legacy write-ups stay published for accountability. They carry the documentation trail—assumption ledgers, privacy notes, iteration logs—so new work can cite its lineage without guesswork.