Editing CC-016: Mira Growth Hack (section)

== What this means in practice ==

The proposal is easiest to understand as a small group experiment, not as an abstract marketing campaign.

Imagine a Telegram group with 6 people building a small project. Today their chat is noisy: goals are scattered, blockers disappear in the scrollback, decisions are made informally, and nobody has a clean weekly summary. The campaign asks this group to add @mira for 7 days and let Mira run a lightweight coordination ritual.

A typical day would look like this:

<pre>
09:30 — Mira: Good morning, crew. Reply with:
1) one thing you want to finish today;
2) one blocker;
3) one person you need input from.

10:00 — Mira: Today's map:
- Anna owns landing copy, blocked by final pricing.
- Victor owns bot test, needs API key confirmation.
- Linia owns visuals, no blocker.
Suggested next action: Victor + Anna resolve pricing/API dependency before 13:00.

18:30 — Mira: Evening recap:
- Done: bot test passed, first visual draft ready.
- Open: pricing still unresolved.
- Decision made: launch page uses simple waitlist first.
- Tomorrow: write launch post and test invite flow.
</pre>

The growth mechanic is that this useful group ritual produces a visible artifact. At the end of the day or week, Mira creates a safe non-private summary that the group can share:

<pre>
This crew used Mira for 7 days.
Resolved: 8 blockers.
Logged: 5 decisions.
Maintained: 6-day ritual streak.
Next sprint: launch page + first 20 users.
Try this with your Telegram group: <UTM link>
</pre>

That artifact is the acquisition unit. It is not "please invite a friend". It is "here is proof that a real Telegram group got clearer by using Mira".

=== 7-day example sprint ===

{| class="wikitable"
! Day !! Group activity !! Mira output !! Shareable proof
|-
| 0 || Add Mira, opt in, define crew goal || Group profile and sprint goal || Crew intro card or text profile
|-
| 1 || Morning kickoff + evening recap || Goals, blockers, owners || Day 1 recap
|-
| 2 || Blocker clinic || Blockers grouped by owner / dependency || Blocker map
|-
| 3 || Decision log day || Decisions with context and risks || Decision digest
|-
| 4 || Use-case day || One concrete automation: content plan, lead follow-up, crypto alert, research digest, or task list || Use-case proof
|-
| 5 || Progress check || What changed since Day 1 || Before/after summary
|-
| 6 || Referral/share preparation || Safe public recap draft || Proof card draft
|-
| 7 || Retrospective || What worked, what was annoying, what continues || Final Crew Report with UTM link
|}

=== What different groups would actually do ===

* '''Founder/operator group:''' daily priorities, blockers, customer follow-up list, launch checklist, weekly investor/update note.
* '''Creator squad:''' content ideas, publishing commitments, draft titles, post-mortem of what shipped, next-week content calendar.
* '''Crypto/Web3 group:''' watchlist recap, governance decision log, community update draft, non-financial risk reminders.
* '''Hackathon/student team:''' task split, deadline reminders, demo script, final pitch checklist.
* '''Community/moderation team:''' issue triage, FAQ updates, moderation decision log, weekly community summary.

The minimum viable campaign does not require all advanced Mira features. The core version only needs:

# Mira asks structured questions.
# Mira summarizes answers.
# Mira remembers recurring context for a week.
# Mira produces a safe recap that can be shared with a tracked link.

Everything else — cards, roasts, leaderboard, prizes, agent ambassadors — is an amplifier around this basic group ritual.