Office of Creative Consent · Register of Works
Five works. All real. All mine.
| № | Work | Control tier |
|---|---|---|
| 01 | Consent Rails & Creative Sovereignty essay | asserted |
| 02 | Hodi Institutional Consent Fleet code repository | asserted |
| 03 | Electric Bass Solo Recordings & Stems bass recording | asserted |
| 04 | Draft Notes on Multi-Agent Consent notes | asserted |
| 05 | Live Bass Improvisation Session bass recording | asserted |
Visitor log · Hodi’s own daily audit — Cloud Scheduler ✓
—visits identifying themselves as AI crawlers
—has ever fetched the machine-readable terms
Nearly all of them checked only whether they were allowed in. What none of them can do yet is ask what they may do with the work. Hodi is that way — the knock.
Application for License
They ask in English.
My rules decide.
Received — the applicant’s own words
…
acme-intelligence-labs
The AI reads what they meant. It decides nothing. The rules decide — identically, every time. An interpretation that doesn’t fit is rejected, never bent to fit.
reading the request…
✓ Granted
evaluating…
Schedule of uses under the grant
Train an AI on my worktraining— the use revoked, by namein force
Fine-tune an existing model with itfine_tuning— inside that yes · training ⊃ fine_tuningin force
Let an AI quote and pull from itrag_retrieval— inside that yes · fine_tuning ⊃ rag_retrievalin force
Let a person study it as referencehuman_reference— inside that yes · rag_retrieval ⊃ human_referencein force
Generate new work in my stylesynthesis — a separate ask, never part of this grantnot granted here
Notice of Revocation
Take back the big yes — everything inside it goes.
Consent you can’t take back isn’t consent. Press Stamp below: it runs the real cascade against this live service.
awaiting the stamp…
how that request actually moved — live
You→Sandbox agent→Agent Gateway→Firestore append-only→Cloud KMS
Production /api/v1/revoke hands the cascade to a separate private revocation workload under its own service account, and returns 503 rather than fall back locally. This sandbox runs the same cascade in-process so anyone can try it without a credential.
RefusedThe same request, moments later. The grant isn’t erased — it’s struck through. A “no” that pretends the “yes” never happened is its own kind of lie.
Certificate of Authenticity
Verifiable by anyone.
Altered by no one without detection.
Signature of record — Cloud KMS · ECDSA P-256
— revoke on the previous step to issue the signed notice —
seal
not yet
pressed
not yet
pressed
Verified in your browser against the published public key — no Hodi server in the loop.
Four agents, or four names in one prompt?
One real delegation on google.adk — separate role-scoped agents under a real runner. The revocation worker is forced to hang so the supervisor must recover. Write-free.
Attempted entries — refused at the door
On Aug 7 a real break-in worked against this system. We kept that attack. Throw it — and five more — at the live routes.
What this office will not certify
A registry that flatters you is worthless.
✕That your work is inside a model’s training data.Nobody on earth can prove that today — so the system cannot say it. There is no field for a claim it can’t back.
✕That revocation pulls your work out of a model.It withdraws permission for future use, and integrated clients stop. It cannot compel a party outside the rail, or un-train a model.
✕That the artist’s own claims beat the rules.Checking the live registry…
Your voice deserves a door before it becomes someone else’s product.
Hodi is the knock.