document
roadmap
type
evidence sequence
issue
006
status
no invented dates
brief

ordered by confidence and proof, not by date. branch names show where the current work lives.

roadmap

first receive.
then prove.

intent

the goal is not to make every channel look finished. it is to make one ordinary phone number dependable, inspectable, and useful to an agent before widening the surface.

stages
  1. 01
    now / make the baseline legible

    number setup, sms intake, a deduplicated local inbox, read marks, threads, call history, voicemail import, cli access, and a local browser interface.

  2. 02
    prove / real carrier deliveries

    exercise each provider model with real accounts, actual sms delivery, voice registration, and media. adapter presence alone does not close this stage.

  3. 03
    integrate / the mcp tool surface

    carry the broadest branch's structured tools, javascript sdk, allow and lookup integration, calling code, and live timeline through repeatable end-to-end checks.

  4. 04
    harden / deployment and data boundaries

    document tls, provider authentication, restrictive file permissions, retention, rate limits, service management, and safe remote access without generalizing one branch's gates to every branch.

  5. 05
    extend / calling and device control

    move from local audio and simulated ring proofs toward real registered calls, reliable handoffs, and clearly bounded android or ios support.

  6. 06
    later / omnichannel and meetings

    omni and meetings remain designs until actual deliveries and room joins are demonstrated. they should not be promoted by adding more marketing copy.