FTFernhollow ToolsDraft 2 · rewritten from your note
Every blade on our bench has a story. This one came back after eleven years in a joinery workshop, still cutting clean. Here is what its owner did right.
153 / 3,000 characters
Cuckoo is a bigger personal project, now in pilot. Each client gets a workspace with its own brand voice and language. AI drafts a whole week of posts for every channel; the decision-maker approves or asks for changes from a phone; approved posts join a publishing queue. The publishing connections are built and waiting on the platforms’ own approvals.
Pilot · core built 15–16 Sep 2026 · platform approvals pending · numbers observed 2026-10-05
01 · Before
For most businesses, social media is either neglected or it quietly eats a person’s week. Someone drafts posts for each platform in each brand’s voice. Someone sends them for approval and waits. Feedback comes back in fragments. Someone logs into every platform to post. The week the coordinator is busy, the posting stops.
02 · What I built
A workspace holds everything that makes a brand sound like itself: voice, language, rules, and which AI keys to use. From that, the engine drafts the whole week per channel, already within each platform’s length and format rules. The client sees it on a phone, signs in with a one-time code, and approves or writes a note. The note goes straight into the rewrite.
MonLinkedIn
Three signs a blade is costing you more than a new one.
Approved
TueInstagram
Behind the bench: how we test every edge before it ships.
Approved
WedX
Downtime rarely starts with a breakdown. It starts with a blunt edge nobody logged.
Approved
ThuLinkedIn
Rewrite requested: “less salesy, lead with the workshop story.”
Changes asked
FriFacebook
Weekend project: sharpening angles, explained in one drawing.
Waiting for you
SatInstagram
Customer bench of the week (photo from the client library).
Waiting for you
Sun—
No post. Rest day in the brand rules.
Off
Thursday · LinkedIn · 09:00
FTFernhollow ToolsDraft 2 · rewritten from your note
Every blade on our bench has a story. This one came back after eleven years in a joinery workshop, still cutting clean. Here is what its owner did right.
153 / 3,000 characters
Signed in with a one-time code. No password.
03 · Who did what
agent://researcher
Mapped each platform’s API, its developer review and its content rules.
Never allowed to: post anything.
agent://architect
Designed the workspace model: one voice, language and set of AI keys per client, with secrets encrypted at rest.
human://vegardHUMAN GATE
Set two rules: nothing publishes without the client’s approval, and the agency never holds a client’s password.
agent://writer
Drafts a week of posts per channel in the client’s voice, in any of 4 languages.
Never allowed to: publish a post nobody approved.
agent://tester
Runs ~200 test cases, from encryption tamper detection and one-time-code lockout to the publish runner.
human://clientHUMAN GATE
Approves, declines or writes a note per post, per day or for the whole week. Notes feed the rewrite.
agent://watcher
Claims due posts every minute, refreshes platform tokens before they expire, and emails on any failure.
human://vegardHUMAN GATE
Runs the platform reviews: developer apps, business verification, and privacy pages reviewers can read without JavaScript.
04 · Results
| Number | What it measures | How it was measured | Observed |
|---|---|---|---|
| ~2 days✓ verified | to build the core (phases 0–4) | git history 15–16 Sep 2026 | 2026-10-05 |
| 4✓ verified | AI providers (Claude, GPT, Gemini, Grok) | codebase | 2026-10-05 |
| 6✓ verified | publishing integrations built (LinkedIn, Facebook, Instagram, X, TikTok, YouTube), pending platform approvals | codebase | 2026-10-05 |
| ~200✓ verified | test cases in 14 files (encryption tamper, OTP lockout, publish runner, portal) | test suite count | 2026-10-05 |
| 4✓ verified | output languages: English, German, Norwegian, Swiss German | codebase | 2026-10-05 |
| Not measured yet | Posts published for pilot clients | starts when the platform approvals land | — |
| Not measured yet | Minutes a client spends approving a week | measured from the first pilot weeks | — |
Cuckoo is labelled PILOT. I won’t claim live publishing on any platform until that platform has approved it.
05 · Running costs
The running cost is mostly AI tokens, billed to each workspace’s own provider key, so an agency can pass it straight through to the client it belongs to. Hosting is Cloudflare Workers, a database, object storage and a key-value store. Images and video stay in private storage and are copied to a public bucket only at the moment a platform fetches them.
06 · Ownership
07 · What I’d build for you
If your expertise deserves more reach than your team has hours, I’ll set up the distribution module for you: your voice, your channels, your approval. Your part is a quick yes or “change this” from your phone; the rest runs on schedule.
Not for you if you want AI to post with nobody looking. Every post here waits for a human yes.
Mapped offer · Cited
Text extracted from the HTML this server sends — no JavaScript executed, the way GPTBot, ClaudeBot and PerplexityBot fetch pages. It is also the Markdown twin I publish for AI agents.
Loading…
<!doctype html> <title>Custom Web Tools & Cookie-Free Websites | AIWebRevolution</title> … <body> <div id="root"></div> <script type="module" src="/assets/index.js"></script> </body> → 0 words of page content. Beautiful to people. Blank to ChatGPT.
Two minutes · personal reply