MuninMunin
Sign inStart free
Use case · Writing

The post nobody had time to write.

Your customers are already telling you what to publish — in the searches that come back empty and the questions that arrive four times a month. Munin reads that, drafts the piece, and waits for you.

  • Written from your own documents
  • Draft-first, always
  • Every language, one entry
  • EU-hosted
Anatomy

A post you did not write, taken apart.

One entry from the week the frost came, exactly as it published. Everything on it is either something you had already published, something you approved, or something it refused to guess.

01Frost on a copper water pipe along a basement wall
alt “Frost on a copper water pipe along a basement wall
02

The pipe froze at six. What to do before you call us.

03Drafted 12 Jan 06:40 · published 07:15 · 840 words
04

Shut the main stopcock first — the tap you have never touched, usually by the meter or under the kitchen sink.1 Everything else on this page can wait ninety seconds.

Then open the tap that the frozen pipe feeds. When the ice lets go the water has somewhere to go, and the pressure that splits a pipe never builds.1

Warm it from the tap end backwards: a hairdryer, a warm towel, patience. Never a flame — that is how a cold morning becomes an insurance claim.2

05

We have published nothing about pipes that freeze inside a wall. Flagged for you — a question, not a guess.

06
  • [1] Where the stopcock is, room by room · knowledge base
  • [2] Frost damage: what the insurer asks for · knowledge base
ENPL
What it cost you

Seven minutes of judgement.

You spent

7minutes

One decision. Reversible.
You got

840words

Two sources. Two languages.

The ratio is the product. Not fewer people — fewer of the steps that never needed one.

Where it came from

The questions that came back empty.

Your search log is a list of things your readers wanted and did not find. The week the frost came, one question arrived twenty-nine times in three spellings — and you had published nothing on it.

The knowledge base is searched before a word is written, so you never get a second article about a question you have already answered.

analytics_list_zero_result_searches( )last 7 days
  • “frozen pipe what do i do”14 searches
  • “pipe frozen in the cellar”9 searches
  • “thaw a water pipe myself”6 searches
  • “hot water cylinder replacement cost”5 searches
  • “emergency plumber sunday”3 searches
29 of 41 — one question, three spellings, nothing published
The honest part

What it won’t do.

  • 01

    Publish without you. There is no autonomous mode for the last step, and there is not going to be one.

  • 02

    Invent a fact to finish a paragraph. Missing knowledge comes back as a question, not as fluent prose.

  • 03

    Write in a voice it has never read. Give it published writing of yours, or expect a competent stranger.

What it touches

Three modules, one record.

  • 01Analytics18 toolsanalytics_
  • 02Knowledge22 toolskb_
  • 03Content33 toolscms_

Every step above is an ordinary tool call — the same ones your own agent can make, on the same endpoint. Publishing, indexing and storing the cover as an asset are further calls on that endpoint, not a second product.

Open source. Open protocol.
One stack, your terms.