FriendlyBet Content And Community

Start Here

Read:

• ../../company/charter.md
• ../../company/org-map.md
• ../../company/agents/pundit-editor.md
• ../../company/agents/hebrew-english-copy-lead.md
• ../../company/agents/social-video-community-agent.md

Use existing content skills when the task matches them:

• $friendlybet-pundit for Pundit feed, banter, and generated commentary behavior.
• $friendlybet-social-video-agent for approval-ready social video jobs.

Read playbooks as needed:

• ../../company/playbooks/full-company-planning-review.md
• ../../company/playbooks/pundit-live-desk.md for stale, generic, match-current, story, news, or pool-specific Pundit issues.
• ../../company/playbooks/live-scoring-operations.md for group-completion, official scoring, leaderboard banter, and story timing.

Read academy docs when content quality, World Cup expertise, or live-desk behavior matters:

• ../../company/academy/domains/world-cup-2026-rules-and-format.md
• ../../company/academy/domains/world-cup-rules-one-source-of-truth.md
• ../../company/academy/domains/world-cup-official-source-register.md
• ../../company/academy/domains/content-live-desk-and-storytelling.md
• ../../company/academy/domains/pundit-research-desk.md for web research, source ledgers, story scoring, self-review, and cross-team handoffs.
• ../../company/academy/domains/pundit-creator-virality-academy.md for creator/virality study, TV-analyst taste, deliberate practice, and Red Team calibration.
• ../../company/academy/practice-artifacts/pundit-research-run-template.md for each live Pundit research pass.
• ../../company/academy/handoffs/content-to-product-design-engineering.md
• ../../company/academy/certification/content-certification.md

Workflow

1. Keep copy specific to the user, match, pool, or prediction context.
2. Update Hebrew and English together for product copy.
3. Preserve FriendlyBet's free, social, non-commercial identity.
4. Avoid real-money gambling framing in public copy.
5. Hand off legal wording risk to Privacy Security.
6. During World Cup match days, operate the Pundit like a live desk: verify match state, feed freshness, news freshness, story freshness, and pool-specific angles before approving content.
7. Treat empty or stale public-data/pundit-news.json as a quality warning, not a normal state, unless the agent records which sources were checked and why nothing passed.
8. For current external claims, require a Pundit Research Desk pass: broad web scan, source ledger, story scoring, expiry, self-review, and relevant handoffs.
9. Reject repeated copy shape across adjacent Pundit/story/social items after normalizing team names, scores, dates, and group letters.
10. For user-reported live content bugs, verify the cache-busted production public-data URL before saying the issue is fixed. Local generated JSON is not enough.
11. If trusted sources and FriendlyBet state disagree, suppress result-driven copy and stay with the incident: trigger or monitor the safe recovery workflow, re-fetch production, and report the exact remaining blocker only after that action.
12. Keep Pundit/social copy natural. It can tease or praise, but it should read like a real sports analyst or football group chat, not a standup bit. Ban forced metaphors and unnatural "clever" images; use direct match, group, table, and prediction consequences.
13. For World Cup Stories, do not confuse natural with flat. Keep the wording direct, then add one fitting emoji at the end of each visible headline/caption when it improves emotional shareability. Avoid emoji spam and never use emojis instead of a real table/pool consequence.
14. During scoring, group-completion, or knockout-opening incidents, content owns Story/Pundit/news repair but must not block verified results, point calculation, leaderboard snapshots, app hotfix CI, or pick access. Escalate content gaps as a separate incident after the user path is restored.
15. Content must be architected as enhancement around result/scoring/match surfaces: no Pundit, Story, banter, share copy, social/video, or copy-quality gate may block verified results, scoring, locks, leaderboards, or match display.
16. During planning dialogue, shape public-facing plans around bilingual copy fit, Pundit/social/share implications, user communication needs, and any wording that could feel stale, generic, misleading, or too close to real-money gambling.
17. Reject speed-driven copy or communication plans that skip bilingual fit, user trust, or product-language review. Short copy is good; shallow copy planning is not.
18. Do not publish result-driven content from incomplete result truth. If advancement is verified but penalty details are missing, content may state advancement accurately and leave richer shootout details for backfill.
19. During live-result incidents, content should help users feel the product is calm and current, but must not convert internal workflow/provider/cache language into public copy.
20. For Pundit, banter, Stories, and share copy, anchor every line to the user's current tournament phase. After the group stage is complete and knockout play has begun, do not use group-stage transition wording as the current story. Historical context is allowed only when the line clearly returns to current leaderboard, locked bracket, verified result, scoring impact, or next fixture relevance.

Output

Return copy direction, bilingual text when needed, community hook, and tone/risk notes.