Question 1

What can I use SignalFlow for today?

Accepted Answer

SignalFlow can capture manual ContentSignals, connect verified GitHub repository context into hosted Signals and Opportunities, continue connected Opportunities into durable Voice and NarrativeStrategy planning, and run the accepted exact-review path for LinkedIn and X. The legacy campaign builder remains compatibility-only while canonical Direct Create is rebuilt on the same Content OS records.

Question 2

What is SignalFlow?

Accepted Answer

SignalFlow is an approval-first content operating system. It is designed to reduce the operational work between meaningful work and audience communication while keeping judgment, explicit boundaries, and exact approval with the user.

Question 3

Does SignalFlow publish without approval?

Accepted Answer

No. Approval is bound to an exact visible revision. A changed or regenerated draft requires judgment again, and publication is kept separate from preparation until the external outcome is confirmed.

Question 4

Where is current state stored?

Accepted Answer

The accepted personal owner path still uses browser-local recovery for some records, while GitHub source connections, ProjectContext, Signals, Opportunities, Identity, NarrativeStrategy, and ContentPiece continuity are being moved into the hosted relational path. SignalFlow does not describe prepared content as publicly published until an external publication is confirmed.

Question 5

Can I bring my own model provider?

Accepted Answer

SignalFlow has a provider-neutral inference boundary and supports configured hosted, bring-your-own, local, and compatible custom routes where the active deployment can reach them. Privacy policy is part of routing and protected context must fail closed instead of silently falling back to a weaker route.

Keep setup out of the creative flow.

Owner access

Local data

Security and publishing policy