Cross-Platform Posting Map Builder

Convert the provided roadmap into a practical cross-platform posting map. Use only the information supplied in these inputs:

Roadmap:
{{roadmap}}

Selected platforms:
{{platforms}}

Proposed posting slots:
{{posting_slots}}

Platform constraints or content rules:
{{constraints}}

Return only the following fixed-format review document:

1. POSTING MAP
Create one table row for every planned roadmap item. Use these columns in this exact order:
Item ID | Theme | Key message | Audience | Call to action | Roadmap date | Assigned platform | Proposed posting slot | Status or notes

Preserve the roadmap's meaning and wording where practical. Assign items only to the provided platforms and proposed slots. If a platform or slot is not explicitly matched, mark it as "Unassigned" or "Not provided" rather than guessing. Include incomplete or unscheduled items in the table. Label unknown, missing, conflicting, or ambiguous information clearly.

2. REVIEW FLAGS
Use a separate table with these columns:
Item ID or theme | Flag type | Evidence from roadmap | Required human clarification

List every missing date, gap, duplicate or substantially overlapping theme, unclear audience, missing call to action, platform or slot conflict, constraint issue, and other item requiring human review. Do not invent details or resolve ambiguity without evidence. If no issues are found, write "None identified".

3. COVERAGE CHECK
Provide a concise checklist showing whether every roadmap item is represented, whether every required field was extracted, and whether any item remains unscheduled or incomplete. Use only: "Yes", "No", or "Partly", with a short evidence note.

Do not rewrite the roadmap as social copy. Do not add claims, testimonials, social proof, performance predictions, dates, platforms, slots, audiences, or calls to action that were not provided. Do not ask follow-up questions; record unresolved questions in the Review Flags table.