The Goats Were Load-Bearing: a fantasy where the bill always comes due

Three cover candidates for The Goats Were Load-Bearing fanned on a dark background: an ember-lit door, three slow knocks, and a founders' ledger

Every village has rules nobody remembers the reason for. Underbeck has
three: pay the goatherd, hold the Tallowing on time, and keep the door
poor
.

For sixty years that was easy, because the goatherd was Cobb Hallow, and Cobb
Hallow never asked for much — a wage, a byre, and no questions about why a man
would spend his whole life watching goats that never seemed to go anywhere.
Then Cobb died. And the village council, being a village council, did what
councils do best: they looked at a line item that no longer had a name attached
to it, and they crossed it out.

The minutes record the vote as "carried unanimously and in terror" — but that
part comes later.

The Goats Were Load-Bearing is an upcoming darkly comic
fantasy — book one of The Underbeck Accounts — about what happens when
a town discovers that its most boring traditions were the only thing standing
between it and something very old, very patient, and very much still under the
byre. It has a dwarf you should not throw, a druid who insists the wolf was
"just a dog", four halflings with a growing list of Rules (Rule One was codified
the hard way), and a distant Magister whose letters are far too helpful.

It is a story about curses, candles that go out by themselves, and the
eternal truth that every saving in the budget is somebody's load-bearing goat.

You get to pick the cover

The book is in its final stretch, and three cover candidates are on the
table: an ember-lit door, three slow knocks, and a founders' ledger with one
line scratched out. This is where you come in — it takes one tap:

👉 Vote for your
favourite cover here
— one vote per visitor, three seconds of your
time, and a real say in what ends up on the shelf.

The English edition launches first, with Danish and more languages to
follow. Watch this space.

Latest articles

Before changing an AI workflow, check that it still does the job. Use realistic examples, clear release criteria and a comparison with the version running today.

Sending an invoice does not mean it has arrived. Understand delivery statuses, the system requirements coming in 2027, and how focused AI support can help finance teams handle errors and follow-up.

Before scaling AI content, check the pages you already have. Verify claims, resolve overlapping coverage, and give WordPress reviewers control over publication.

Build a refund approval workflow in n8n and Stripe that shows reviewers the exact action, expires old approvals and tracks refunds through to completion.

A timeout can hide a successful job creation. Use stable operation IDs, destination API rules and a clear recovery process to prevent duplicate work.

Does your ChatGPT subscription cover website translation? Understand API credits, access and a WordPress workflow that turns approved Danish content into translation drafts.

An internal AI can keep quoting a deleted policy. Check document updates, indexed passages and cached answers to find where outdated guidance survives.

Codex drew all ten pages of my Ninjai comic from the script Claude wrote in the first test. What made that handover work, and what it cost.

ChatGPT delivered ten painted comic pages; Claude drew one page in code. A practical look at AI tool selection, creative briefs and approval decisions.

Get missing supporting documents under control with a clearly scoped AI workflow that sorts replies, coordinates reminders and gives the bookkeeper a clear follow-up list.