The Workshop Artifact, You Own It
By Michael Polzin · July 1, 2026 · Anti-extraction, human-in-the-loop.
A workshop day should end with something you can carry out the door. Not a receipt for attention rented. This page is the plain-English contract: what "you own it" actually means, and what we will not pretend it means.
The anti-extraction principle
Most training economies work by extraction: your attention comes in, a slide deck goes out, and the working artifact stays with the vendor. That pattern is comfortable for the vendor. It is expensive for you, because next week you have a memory of a talk and nothing you can open. Our rule for the room is the inverse. Whatever we build together belongs to you, in a form you can inspect, edit, run, and hand to someone else.
The commitment is boring on purpose. Boring commitments survive contact with a bad week.
What "you own it" covers
1. The files. The configuration, the schema you wrote against, the sample inputs you tested, the gate definitions, the run outputs. All of it, in a folder you name, in formats a plain text editor and a shell can open (Class C, configuration and integration). No proprietary bundler. No opaque container that phones home to us before it will run.
2. The decisions. Every choice you made in the room, in the order you made it, with the reason recorded beside it. This is the ledger habit in miniature (Class B, code and inspection). Six months later, when you disagree with your past self, the reason is legible and the decision is falsifiable. Your judgment stays inspectable, by you.
3. The keys. If your build touches anything that requires a credential, we walk you through creating that credential in your own account, on your own device, with you doing the entry. We do not hold the keys for you. We do not create a shadow account that we can quietly keep after you leave. See our standing rule on credentials in the transparency page.
4. The export path. Before the room closes, we run the export together: a zip, a git repo, a directory on your drive. You leave with a copy in your hand. If you cannot reproduce the run at home the following morning, we did not finish (Class F, falsifier present, and the falsifier is you opening the folder on Tuesday).
What "you own it" does not cover
You do not own the underlying research program. Universal Natural Intelligence is a working hypothesis on an attainable path toward General Natural Intelligence: a natural, active-inference approach whose evidence is growing, evidence-classed, and tested in the open. The program continues to change. Your build is a snapshot against the schema we taught that day. When the schema updates, you decide whether to migrate. We publish the diff; you choose.
You do not own a warranty that the build will hold in production. A one-day cut is an initial cut. It is meant to survive contact with reality, and to be edited. What we do stand behind is the shape: the gates are where we said they were, the ledger is in the format we walked through, and the run is reproducible on your machine (Class U, unverified for your specific downstream use case, until you test it).
You do not own the wider active-inference literature by virtue of attending. Active inference is a technical framework in cognitive science (Class E, expert citation: Parr, Pezzulo, Friston, 2022). Your build uses concepts from it. Reading the source material is on you, and we will point you at it.
Why we bother to write this down
Because the default in this industry is the opposite. Because "yours to take home" is a phrase people say and rarely honor. Because if we do not write it down, the ambiguity is a knob someone can turn against you later. And because the anti-extraction principle is not a marketing line for us: it is a load-bearing beam under the whole program. If we ever quietly walk it back, you have this page to hold us to.
For the fuller ownership map beyond the artifact itself, our transparency page lists every piece of data we log, why, for how long, and how to have it deleted. If any of that reads as extraction to you, tell us in the room and we will change it.
What to do next
- See the workshop dates, format, and the honest fences on /workshop. It names who this is for and who it is not for.
- Read: What You Take Home From a Workshop, the inventory piece this one sits next to.
- Read the transparency page for the logging, retention, and deletion policies that back the ownership promise up.