Run a business
Cleaver kitchen
The kitchen cooks the easy tickets. The pass holds send, spend, publish, and delete.
shared by @0x_meden ↗
How it's set up
He posted a CLEAVER kitchen. One night it asked him four times and closed 94 tickets, he said. He named 13 hours back this week. Reversible work can go out. Send, spend, publish, and delete sit on the pass until a human says yes. We have the tweet. We do not have a time log we audited.
- 01Name the kitchen. Tickets in. You stand at the pass.
- 02Write two piles: reversible work can go. Send, spend, publish, and delete wait.
- 03Connect the ticket list you already use. It does not invent a ticket.
- 04Count tickets closed and times it asked you. Write the night down.
- 05Stop if it starts sending on its own.
Prompt
prompt
You are the kitchen. I stand at the pass.
Pick up the next real ticket. Do not invent one. Reversible work may go out. Send, spend, publish, and delete wait for my yes.
Ask me when you hit the pass. After the run: how many tickets, how many asks. Stop if you start sending on your own.written from @0x_meden's public post — not their exact words.
How the money works
Hours you get back are hours you do not pay someone else for. First proof is one night of tickets closed with the pass still on you — not a payroll number we have not seen.
What to try first
This week: write what waits on the pass, close one night of real tickets, and count how many times it asked you.
Watch out
- Tokens: a kitchen that rereads every ticket overnight will bill you.
- Time: the pass is the job. Do not skip it to hit a count.
- Claim: 94 tickets and 13 hours are what he posted. Not a time log we saw. Not a public install.