Instructions

How the Bureau works, in one screen.

What this is

The Bureau is a window, not an app. You state an intention — a lookup, a post, a whole publishing campaign — and an operated estate (real accounts, real tools, a working agent) executes it for you, inside fences stated on every card, and hands back a receipt: proof of what actually happened, with the live links. The value is not the form. The value is everything behind it — the accounts already signed in, the per-platform knowledge, the judgment about when to stop. That layer sits on top of the platforms' own functions and adds review, fences, and receipts to them.

How a job flows

• Submit an intention from any card in the left menu. You get a ticket — its link carries its own view key, so the link alone opens it.
• The estate claims the ticket (usually within five minutes), works it, and the ticket updates as work verifies — a campaign ticket fills in leg by leg.
• Every job ends receipted (done, with evidence) or stopped (a fence was met; the ticket says which, in plain words). A stop is the fence working, not a failure.

The demo key

Anything that writes — posts, publishes, flips — asks for the demo key. Lookups are open. The operator holds the key; if you're watching a demo, you'll see it typed once and the window remembers it for the session.

Link codes

In any text you submit, three short codes expand to full links before anything posts: {{recipes}} (the onion recipe family), {{ugi}} (the Used GPU Index), {{home}} (kurkalabs.dev). An unknown code stops the job rather than guessing — codes are how a typist stays fast without ever pasting a URL wrong.

Campaign sets

• FULL — the whole ten-platform roster plus the canonical page. Legs land over roughly 30–90 minutes; watch the ticket fill in.
• CORE — the canonical page plus the legs that run clean. Beehiiv, Medium, and Instagram are named in the receipt as skipped — never silently dropped.
• ANNOUNCE — a note-class shout: Substack Note, Bluesky, Threads, X. Minutes, no page, no hero image.

Bridge jobs

Some platforms reserve one step for the account owner's own hands — Instagram's image picker and Share button are the standing example. A bridge job does everything else, then parks on the ticket at awaiting operator until the owner's two clicks pass it. The fence is visible, on the record, instead of improvised.

What the Bureau will not do

Payments, purchases, account settings, deletions, and anything outside the fence printed on each card. A job that meets a state outside its fence stops and reports. That refusal is part of the product: an intention goes in, a receipt comes out, and nothing else happens in between.