Take what we built.
Working automations, and the reasoning behind them. Most of this exists because we needed it ourselves first, which is the only reason any of it is worth handing over.
The toolkit
A catalogue of automation workflows, sorted by who they are for: running a business, studying, or your own life. The catalogue is public and needs nothing from you. Downloading a file asks for an email, once, and confirms it before sending anything.
Every item names what it connects, what it costs to run, and what breaks if the service at the other end changes. An automation you cannot repair is a liability with a nice diagram.
How we think about the work
- Sourced or it does not ship. Every claim traces to a file, an output, a URL, or a person.
- A green build is not a deploy. Load the live URL and confirm before saying it is done.
- Test the seam, not the sides. Bugs live between two individually-correct components.
- Delete dead gates, do not disable them. A flag can re-close by accident.
- Numbers need one declared unit, verified on the artifact the customer sees.
The vision brief
If you have a project in mind and would rather show than describe, the vision brief walks through it and gives us something concrete to respond to.
Design your visionEverything linked here exists and works today. When something is planned rather than built, this page will say so in those words.