Multi-brand channels

Sets up a clean one-persona-per-brand structure in a single ProPost account and keeps it clean: channels mapped to the right voice, queues and times per brand, and a routine that catches a post going to the wrong place.

Before you start

1. get_account: channel and persona limits (max 10 voices), AI drafts left (shared by all brands), weekly cap (shared too), autonomy.
2. list_channels: every channel with its id, network, name or handle. Names are the main way to tell brands apart; ask when two look alike.
3. list_personas: which voices exist and which channels use each.
4. list_posts per channel for status scheduled, draft: what is in flight for each brand right now.
5. get_posting_schedule per channel: the existing queue times.

Workflow

1. Build the brand map. Ask the person (or infer and confirm) which channels belong to which brand and whether clients' content needs their approval. Write a table and get a yes before changing anything:

A founder's personal profile is its own row; it keeps its own voice.

1. One persona per brand. create_persona for each brand with name (the brand), role (who speaks), one tone, a real target_audience, 1-12 niches, and up to 3 writing_samples from that brand's own published posts (never mix brands' samples). With 10 voices maximum, count first: brands plus any personal voices must fit. If they do not, group brands that really share a voice and say so. For wording, use propost-company-brand-voice.
2. Map channels to personas. set_channel_persona for every channel. Verify with list_personas that each channel appears under exactly one brand. Channels left on default will write in the account owner's own voice; flag any that are.
3. Set per-brand queues. get_posting_schedule, then set_posting_schedule (schedule level and up) with days and HH:mm times per channel in the time zone of that brand's audience, not necessarily the person's. suggest_posting_times informs, but avoid two brands posting to a shared audience at the same minute. set_posting_schedule replaces the whole week for that channel, so show the new week and get a yes first. queue_paused: true parks a brand that is on hold.
4. Make content per brand, never across. Batch one brand at a time: generate_draft or create_draft with only that brand's channel_ids. Do not pass persona_id unless deliberately overriding; the channel's own voice then applies. Never put channels from two brands in one call: they would be linked into one group, share a draft and a voice. Say how many AI drafts each brand's batch uses, against the shared total.
5. Check and place. check_post every post. Before scheduling, get_post or list_posts for the batch: confirm each post's channel_id and network belong to the intended brand. Then add_to_queue (that channel's own times) or schedule_post with an ISO time and offset.
6. Review routine (weekly, 5 minutes): list_posts with status: "scheduled" for each channel, group by brand, and report: anything on the wrong channel, two brands posting the same minute, a brand with an empty queue, failed posts and their error, channels with needs_reconnect or paused queues. Per brand, get_channel_stats (range 30d) to see which brand needs attention.
7. Report as one block per brand: voice, channels, schedule, what is queued, what awaits approval.

Writing guidance

• Voices bleed when brands share samples, niches or role lines. Make each persona distinct in a way a reader would notice: different tone, different niches, different sample posts.
• Test for bleed: write the same idea ("we're closed Monday") for two brands and compare. If they read alike, sharpen the samples.
• Name drafts with the brand at the start of the idea ("Harbor Cafe: new autumn menu...") so the review table is readable.
• Keep brand facts apart: prices, hours, claims and names are brand-specific. Never reuse a client's result, quote or customer story on another brand.
• A client-facing review list works best as a table: brand, channel, time, first line. Give it to the client before scheduling when they must approve.

Guardrails

• A post belongs to exactly one brand. When unsure which channel a request means, ask instead of choosing.
• Never move or copy one client's content to another brand's channel (copy_post_to_channel) without the person naming both.
• Don't change a client's persona, queue or channels outside the brief.
• Client confidentiality: don't mention one brand's work, numbers or plans while working on another.
• update_persona and set_posting_schedule overwrite; show the change and get a yes.
• Never publish_now without an explicit yes naming the brand and channel.
• Respect the shared weekly cap: tell the person if brands compete for it.

If something fails

• persona_limit: 10 voices used; propose merging brands that share a voice or removing unused ones in ProPost.
• channel_not_found: reload list_channels; do not reuse remembered ids.
• weekly_limit: prioritise by deadline and the person's ranking of brands; keep the rest as drafts.
• invalid_time / invalid_day / too_many_slots: use HH:mm, mon..sun and at most 12 times a day.
• quota_exceeded: use create_draft with text the person approves.
• Anything else: see ../CONVENTIONS.md.