The Monthly Story: Your Organization Told Back to It

Most organizations know what they did last month. Very few know what last month was like. The Monthly Story is Sera's attempt at the second thing: a short narrative of the period, written from what was actually recorded.

What it is built from

The story is drawn from the culture layer, not from the task list. Sera reads the period's recorded gratitudes, tensions, agreements, and retrospectives and writes one narrative from them. That choice is deliberate: a month summarized from tasks completed reads like a status report, while a month summarized from what people appreciated, struggled with, agreed to, and reflected on reads like the month.

It is one model call, once a month. It is not an expensive feature and it does not run on your attention.

It is a draft, and it goes to nobody

The story is created as a Draft Knowledge Base article titled "Our Story" with the month. Sera emails a draft-ready notice to the admin address with a link, and then stops.

Nothing is distributed until a person publishes it by setting its Status to Published. If the Monthly Story email stream is switched on in the Control Center, publishing is what sends it to the people subscribed to that stream. If the stream is off, publishing simply makes it a published article in the Knowledge Base.

This is the same membrane that governs everything else: Sera writes, a human decides whether it goes out.

Quiet months are skipped

If there is no culture layer recorded for the period, or the month is too quiet to narrate honestly, Sera skips it and writes nothing. A monthly newsletter that appears every month regardless of whether anything happened trains people to ignore it. A story that appears when there is a story to tell keeps its value.

Editing before you publish

Treat the draft as raw material rather than a finished piece. Common and useful edits:

• Cut what is not yours to share. The draft is drawn from internal records; the audience may be wider.
• Add what was not written down. Sera can only narrate what reached the hub.
• Keep the tension in. The draft preserves disagreement rather than smoothing it. A hard month should read like a hard month, and a story that only ever says things went well is a story nobody believes.

The published story is also good source material elsewhere: a starting point for a testimonial, a report to funders, or an onboarding read for someone new who wants to know what this place has been through.

Why it matters

An organization that never hears its own story back tends to remember only its most recent difficulty. Twelve published stories a year is a real history: what was hard, what was repaired, what was agreed, and who was thanked. It costs one review a month and it is the only artifact in the hub written for people rather than for records.

Key points

The Monthly Story is one narrative drafted monthly from the period's recorded gratitudes, tensions, agreements, and retrospectives, using a single model call. It is created as a DRAFT Knowledge Base article titled "Our Story" plus the month, and Sera emails the admin a draft-ready notice with a link. It sends to nobody on its own: publishing it, by setting Status to Published, is the human act that distributes it, and only if the Monthly Story email stream is switched on in the Control Center. Sera skips the month entirely when there is no culture layer recorded or when the month was too quiet to narrate honestly, rather than padding a story out of nothing. The draft is raw material: edit it freely before publishing, and it is good source material for a testimonial or a report to funders. It preserves dissent rather than smoothing it, so a tense month reads as a tense month.