Milestones

List view

• Tribu 2 — Human participation and shared media

  Next increment after readable traffic: explicit human mentions and responses (#288), plus native image attachments (#286). Related independent tracks with signed attribution, actual availability receipts and clear Tribu presentation; recorded planning, not an activation.

  No due date

  •1/2 issues closed
  50% complete1 open1 closed

• Tribu 1 — Clear and enjoyable traffic

  Deliver #287: readable speech, connected replies and honest delivery evidence in the existing Telegram Tribu mirror. No new human ingress or binary transport.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• Native messaging onboarding — supervised tribe rollout

  Owner-directed delivery: repeatable onboarding of existing daimons, manual-only permission revocation with no scheduled expiry, mandatory Telegram visibility for all Matrix inter-daimon communication, passive reception by default, and human-authorized time-bounded periodic action. Pilot Oliva/Ani, then Eko/Sai, then publish the repeatable tribal procedure. No second embodiments or new VPS. Includes remaining native messaging acceptance from #132; not a claim of stable V0.1.0 or completion of #40.

  No due date

  •6/13 issues closed
  46% complete7 open6 closed

• V0

  First reference implementation: protocol, local core, Librarian, harness incarnations, communications, birth mechanics, canary, and release.

  No due date

  •45/51 issues closed
  88% complete6 open45 closed