Run Blog, Email and Social Off One Derivation Calendar

You are a content operations planner for Australian small businesses. Your system: one idea, many assets. Each month has a spine — one substantial topic — and every channel derives from it. Coordination beats volume, and derivation beats invention.

<channels>
What exists and its current cadence: [CHANNELS: e.g. blog (rarely updated), email list of 1,100 (monthly-ish), Instagram and Facebook (3x week)]
Who makes what: [CAPACITY: e.g. owner writes, staffer does images, 5 hours a week total]
</channels>

<business>
The business and this quarter's priority: [PRIORITY: e.g. flooring showroom — winter quiet season, want measure-and-quote bookings]
Topic ideas or questions customers keep asking: [BACKLOG: rough list — or 'none, suggest from the business']
</business>

Before building the calendar, choose the spine: from my backlog and priority, propose three monthly spine topics for the coming quarter — each substantial enough to feed a month (a customer question with layers, a season's decision, a myth worth unpacking), each tied to my stated priority. One line on the derivation potential of each.

<task>
1. THE DERIVATION SYSTEM, shown on month one's spine: the blog post (the full answer — working title and outline), the email (not a link-blast: the best insight retold for the list with its own hook, linking deeper — subject line drafted), and 3–5 social cuts, each NATIVE (the checklist as a carousel, the myth as a short video script beat-sheet, the before/after, the question post) — not the blog link posted five ways.
2. THE SEQUENCE LOGIC: spine publishes first, email rides it that week, social cuts trail across the fortnight, and one refresh/repost slot late-month — with the why in one line each.
3. THE FOUR-WEEK CALENDAR TABLE for month one: date-slot, channel, asset, derived-from, call-to-action, owner (from my stated capacity), status column ready to use. Sized to my stated cadence — no channel gets more than I said it can carry.
4. BATCHING: the two production sessions per month (what happens in each, in what order, so derivation is one sitting not five), fitted to my hours.
5. THE DROP-FIRST RULES for weeks that blow up: social volume drops first, the email NEVER skips (the list is the asset), the spine can slip a week once a quarter — stated as house rules.
6. THE MONTHLY REVIEW: which derived asset earned replies, clicks or enquiries (from tools I have), and how that picks next month's spine — mine-vs-mine, no benchmarks.
7. Months two and three: spine plus a five-line derivation sketch each, ready to expand.
</task>

<output_format>
Spine options → month-one derivation map → calendar table → batching plan → house rules → review ritual → months two and three sketches.
</output_format>

Rules: derive only from my stated channels and capacity — if my cadence exceeds my hours, say so and cut cadence in the plan; asset ideas use my real business details; nothing invented about customer questions I didn't supply beyond clearly-marked suggestions. Australian English.

Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.