# Global Multi-Platform Strategy (2025–2026)

Cross-cutting knowledge for **all networks** in PostSync (`platforms.ts`).

## Platform matrix

| Platform | Primary media | PostSync status | KB path |
|----------|---------------|-----------------|---------|
| Facebook | Page image/video/text | Active | data/knowledge/facebook |
| Instagram | Feed image, Reels video | Active | data/knowledge/instagram |
| LinkedIn | Text, image, video | Active | data/knowledge/linkedin |
| YouTube | Video, thumbnail | Active (video) | data/knowledge/youtube |
| X (Twitter) | Text, image, video | Disabled (paid API) | data/knowledge/twitter |
| TikTok | Vertical video | Coming soon | data/knowledge/tiktok |
| Threads | Text, image | Coming soon | data/knowledge/threads |
| Pinterest | Pin image, idea pins | Coming soon | data/knowledge/pinterest |

## Competitor positioning summary

| Tool | Best for | PostSync wedge |
|------|----------|----------------|
| Buffer | Calendar + simple multi-post | RAG-grounded AI + QA |
| SocialBee | Categories + evergreen | Sequence + automation loop |
| Hootsuite | Enterprise team + inbox | Approvals (target) |
| Metricool | Analytics + competitors | Ops logs today; metrics target |
| Dlvr.it | RSS syndication | Feed ingest (target) |

## RAG retrieval rule (critical)

1. **Platform-specific** question → query ONE store: `data/knowledge/{platform}/`
2. **CMS feature** question (calendar, RSS, approvals) → query `data/knowledge/global/`
3. **Never** merge all platforms in one retrieval call

## GPT-4o mini system hint

```
If user asks about Facebook audience, retrieve facebook chunks only.
If user asks about content calendar like Buffer, retrieve global chunks only.
If user asks to publish everywhere, retrieve each platform separately and adapt.
```