Notifications

WARNING — > Push/FCM delivery is not qualified in C3 Mobile 0.1.2 and is deferred from the current launch scope. Do not rely on it for agent attention. The behavior below documents the intended design and the development surface that remains behind that gate.

The point of C3 Mobile is not watching agents — it's being interruptible. Notifications close the loop: when an agent blocks on a decision, your phone tells you, and Signal tells you what.

Opting in

When notification qualification resumes, notifications will remain off until explicitly enabled in Settings → Notifications. The phone will register its push token with each paired bridge over the encrypted channel; the bridge — not a hosted C3 service — will trigger delivery through the platform push system.

What a notification contains

Always and only:

C3 — An agent needs your attention.

plus a random identifier. No host name, no agent name, no session, no prompt text. Push infrastructure (Google's and Apple's servers) learns that something happened — never what or where. Tapping through opens the app, and the attention queue has the specifics, fetched over your encrypted hub connection.

Delivery behavior

• Debounced — rapid-fire events from one agent collapse (3-second window) instead of buzzing repeatedly.
• Rate-limited — at most one notification per device per 30 seconds.
• Self-cleaning — if the platform reports a device token dead (app uninstalled, token rotated), the bridge drops it automatically.

Nothing will ever be approved, rejected, or executed from a notification. Even after release, notifications will be best-effort; Signal remains the decision surface.