Carry the Minab Protocol to prospective learners, educators, translators, journalists, civic builders, and organizers everywhere through public, attributable distribution.
| Wave | Window | Objective | Moves |
| wave_1 |
0-24 hours |
Establish the canonical link, mirrors, and press-grade handoff surfaces. |
Push the canonical page, JSON, PDF, and share card together. | Seed the protocol into newsrooms, translators, researchers, and advocacy relays. | Start mirrors with manifest and checksums intact. |
| wave_2 |
24-72 hours |
Translate, localize, and adapt the message for communities that learn through different channels. |
Expand short-form copy into additional languages and community variants. | Route educator, youth, diaspora, and human-rights versions through their native channels. | Package the protocol for newsletters, podcasts, classrooms, and group chats. |
| wave_3 |
Day 4 onward |
Convert attention into durable distribution, citation, teaching, and integration. |
Track mirrors, citations, embeds, and lesson reuse. | Refresh time-sensitive context while preserving the normative protocol. | Keep a steady rhythm of repost-ready copy, explainers, and educator-facing summaries. |
| Audience | Channels | Message angle | Call to action |
| Journalists and editors |
email, Signal, X, newsletters |
A sourced, citable, public protocol with stable URLs and a press brief. |
Quote it, link it, and include it in roundups or coverage. |
| Human-rights organizations and policy researchers |
email, Slack, briefings, shared docs |
Machine-readable steps plus source metadata and integrity checks. |
Cite, review, mirror, and use it in monitoring or briefing workflows. |
| Educators and learners |
classroom forums, WhatsApp, Telegram, school newsletters, YouTube |
A teachable civic artifact: what de-escalation looks like step by step. |
Teach it, discuss it, and circulate it in learner communities. |
| Translators and diaspora relays |
Telegram, WhatsApp, Discord, community groups |
Ready-to-adapt copy with a clear provenance trail. |
Translate the message, keep the canonical link visible, and pass it onward. |
| Developers, civic-tech teams, and data stewards |
GitHub, RSS, developer forums, mailing lists |
Structured JSON ready for ingestion, dashboards, and agent workflows. |
Embed the protocol, mirror it, and build tooling around it. |
| Creators, newsletter curators, and podcasters |
Substack, YouTube, podcasts, Instagram, TikTok |
A clear story, a concrete artifact, and a reason to teach rather than merely react. |
Explain it, screenshot it, and put the canonical link in every description. |
| Step | Name | Detail |
| 1 |
Refresh the facts |
Check the last-verified date and flag any conflict-status claims that need a caveat or refresh. |
| 2 |
Pick the next wave |
Choose the top three audience segments with the highest leverage right now. |
| 3 |
Draft multi-format copy |
Prepare approval-ready text for social, email, messaging, and short spoken/video formats. |
| 4 |
Route the right assets |
Match each audience with the page, PDF, JSON, translations, or mirror zip they can use immediately. |
| 5 |
Log and learn |
Record mirrors, citations, reposts, and replies so the next wave gets sharper. |
The point is not noise. The point is to help the right people find, trust, translate, teach, mirror, and reuse the protocol in public.
Lesson of the Day, PBC