Video work · Explainers
Short films that each answer one question about something we build, told with moving diagrams instead of a talking head. Most run under two minutes.
A five-part series on sharing food and credit between neighbours, in felt. Watch in order.
Gardens make more than one house can eat. Share the surplus and keep what you give as credit for January.
A running tab between two people who trust each other. Each sets a limit; settle up whenever you like.
How a payment travels through someone who trusts you both, and how a loop of three tabs cancels out.
Ten pounds of tomatoes reach people Ada has never met, each person settling only with whoever they dealt with.
Your tabs live underneath the app, so another app like OnLoan opens the same tabs with the same login.
Narrated. An open framework for agent-assisted work, drawn as hydraulic works: one inquiry followed through the whole system, by design.
A website inquiry is checked before it is written and stored before it is acknowledged; work survives a crash; people are linked only on proof; every agent comes through one door; a model can propose but only you approve; and the whole workspace leaves as one file.
Narrated. rheoStream's memory module, shown as an Edison-era exhibition: how it works and why you'd want it.
Every memory says who may read it and to what end. Sessions save on their own, changed facts are retired rather than destroyed, recall searches by the word and by the sense on your own server, and forgetting is entire.
Narrated. A source-backed ElfQuest archive and production library, built at Dreamberry Studio: where every answer comes from.
Pike's entry in the official character guide, stored as written; ties that quote their source; an answer that won't invent what the guide leaves out; then the production side, from every panel of the Original Quest to the second a scene plays.
Music only. Line drawings on a surveyor's plate, drawn in code, that assemble as the story goes.
How a change ships here: issue, branch, draft PR, independent review where bugs stay silent, a merge commit, and a deploy checked live.
Durable work in rheoStream: leased jobs survive a dead worker, a change and its event commit together, and an operation with no audit path stops the service from starting.
What are the Bureau's main parts, and how does work move between them? A map of one run, from the brief to the cold review to the owner's gate.
Why are the Delegate, the Conductor and the specialists separate? How the Bureau classifies a task first, then gives a bug fix and a feature very different amounts of process.
Where does a Bureau run's memory live when the session ends? What gets written to disk at each phase, and how a fresh session picks the run back up.
When is independent review worth its cost? How the Bureau's specialists work in sealed contexts, and the one test that decides when to bring them in.
How is a verdict tied to the exact evidence reviewed? How the Bureau fingerprints each artifact, and what happens when a file changes after approval.
How do separately built pieces get verified together? How the Bureau's Coupler tests the join between two halves that each passed review alone.
Which decisions proceed and which go to the owner? How the Bureau separates routine checkpoints from forks, and why the Delegate waits instead of guessing.
What does the Envoy add above a single run? How the Bureau works through a roadmap, one run at a time, with a handoff and a fresh reviewer at every merge.
A document extraction API, checked: a model reads each bill, a fixed-rule parser checks it, and doubtful values are flagged instead of passed along.
Self-hosting a small studio: one rented box runs most apps behind Traefik and Coolify, each app keeps its own database, and a few things stay off the box on purpose.
A recipe in cups and spoons becomes a nutrition facts table: ingredients matched to food records, summed, rounded per the Canadian or US label rules, and printed ten to a sheet with an audit trail.
A recorded life-story interview becomes written chapters through eight stages, and every passage keeps a trail back to the words actually said.
Screening questionnaires as data: one renderer and one scorer for every instrument, answers encrypted at rest, and a PDF report that says screening only, not a diagnosis.
Picking crews keep tallying with no signal: the phone is the record, pay adds up on the phone, and a batch sent twice is stored once. The sync to the server is drawn as planned.
A metered loan settles on the FOAF ledger: credit checked first, two signatures, no keys held by the app, and the same trustline and login GrowOperative uses.
One SDK gives an app on FOAF a login, the person's contacts and the shared ledger, with every ledger call signed by a custodian so the app holds no keys.
Tools for independent musicians.
Tell your own ChatGPT about a show once, and your tour page, promos and listings follow.
Find the festivals worth playing, keep the ones you want, and follow every application from first look to booked.
Turn the tour you already filmed into vertical clips: scenes sorted, every cut on the beat, karaoke captions. In private beta.
