[P1][Mobile] Build a low-attention mobile companion for capture, judgment, approval, calendar, and publication exceptions

[Ankit6149]

Parent epics

#56, #62, #150

Product outcome

SignalFlow has a mobile companion optimized for the moments when users naturally have their phone: capturing a thought, sharing a reference, reviewing a finished piece, approving exact revisions, responding to an exception, and checking the editorial calendar.

The phone is the judgment and quick-capture device, not a duplicated full Studio.

Primary mobile journeys

Today

• opportunities needing judgment;
• drafts/media ready for review;
• schedule decisions;
• failed/unknown publication requiring attention;
• connection/privacy blockers.

Capture

Fast entry for:

Thought
Voice note
Photo
Screenshot
File
Link
Paste
Share from another app

Inputs normalize into canonical ContentSignal/Asset/SourceArtifact records.

Review

• inspect platform-native text/media;
• approve exact revision;
• reject;
• request natural-language change;
• choose another asset;
• change/remove destination;
• change schedule.

Calendar

• upcoming campaign pieces;
• scheduled/approved/needs-review state;
• move/skip/leave empty;
• publication exception state.

Notifications

Only high-value classes:

• needs judgment;
• needs recovery;
• requested work completed;
• confirmed publication.

No notification for every raw signal/job step.

Share-sheet intent

When content is shared into SignalFlow, allow intents such as:

Save as reference
Use as evidence
I want to talk about this
Use this in a post
Something else

Do not force campaign/platform/model setup during capture.

Offline/recovery

• queue safe manual thoughts/captures;
• preserve stable IDs;
• reconcile stale approval/schedule state explicitly;
• a stale phone screen cannot approve a newer unseen revision;
• publication remains server/durable-job owned, never a mobile timer.

Privacy

• lock-screen notifications avoid sensitive details by default;
• local cache uses platform secure storage capabilities;
• uploaded/shared media obey workspace ProcessingPolicy;
• optional local preprocessing is capability-driven and not required for heavy reasoning/rendering.

Acceptance criteria

• User can create a manual ContentSignal from phone without creating a Campaign first.
• User can share a link/image/file into SignalFlow with explicit intent.
• Today shows only actionable/relevant items from canonical server state.
• User can review and approve/reject/request changes for exact revisions.
• Approval conflict/staleness is handled safely.
• Calendar state matches web/server state.
• Publication exceptions are actionable without exposing raw secrets/private source.
• Offline capture/retry cannot duplicate signals/assets.
• Mobile app does not duplicate provider/business rules locally.

Non-goals

• no full desktop-style provider configuration UI unless necessary;
• no required large-model/video rendering on phone;
• no duplicated campaign domain model;
• no engagement/gamification notification system.

Definition of done

Close only when a user can capture an idea/reference and later approve a real SignalFlow content revision from a phone with the same canonical history/state visible on web.

[Ankit6149]

Mobile companion media clarification: phone capture/share should preserve user intent, not merely upload bytes. Share-sheet/capture flows should be able to express Use in final content, Reference only, Evidence only, Edit this, Combine, or Do not publish, feeding #179. Mobile review should display exact image/carousel/video revision, privacy/rights blockers and allow natural-language change requests; it should not duplicate the heavy render/edit engine locally. A stale phone must never approve an unseen newer media revision.