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

A supplier PDF can influence more than an AI summary. Follow its path to a CRM update and see where validation, tool permissions and destination controls matter.

Check whether AI shopping channels show the right product, variant, price and availability, then trace discrepancies from your catalog through to checkout.

Add approved hours from Clockify to draft invoices in Dinero. AI writes service descriptions, while fixed rules govern amounts, approvals and reruns.

A blanket AI restriction can limit search discovery. Compare Google and Bing controls, agree content permissions, and check what your CMS actually delivers.

Measure AI automation costs per accepted result, including retries and human review. Check caching, batch processing and spending controls before scaling.

A 502 after maintenance can interrupt enquiries or checkout. Trace the NGINX-to-PHP connection, diagnose the failure, and check the fix survives a restart.

Let AI customer service retrieve order status from Shopify and Shipmondo. Learn how to define the scope, verify the customer's identity and hand over cases when information is uncertain.

Move a useful AI workflow into company-controlled projects, with clear ownership, tested permissions, service accounts and a practical plan for replacing credentials.

Drupal 10 reaches end of life on 9 December 2026. Decide whether to upgrade first or combine it with a relaunch, with clear budgets, compatibility checks and launch criteria.

Before expanding internal AI search, check how permissions survive indexing, retrieval and access changes, with practical tests for staff and client boundaries.