SynapseFlow AI · finance & supply chain
A clear view of the proposed evaluation, the data-handling statements on this site, and the current limits on live execution.
Read the full PoC scopeStraight answers
The proposed PoC focuses on one agreed finance or supply-chain exception path, evaluated alongside your current process. It is intended to clarify the operating model and scope. It does not replace that process, run exceptions live, or make changes to business systems.
The site describes a proposed data boundary of ephemeral processing, with no persistent client-payload cache, and says client payloads are not proposed for training foundation models. These statements are not a certification or compliance attestation. The public materials do not specify other details such as processing location, encryption, access controls, subprocessors, or retention beyond the stated cache boundary; discuss those before sharing data.
The public PoC scope does not claim live SAP, NetSuite, or WMS integrations, or vendor exception execution. Live integrations, live transactions, and writes to business systems are outside this PoC. Existing systems remain the source of truth and are not changed. Reviewing one exception path and its system context is not a connector or production-compatibility commitment.
The proposed operating model says cases below its proposed 95% confidence threshold pause for human approval. The threshold is a design target, not validated live performance. The PoC scope allows no live system actions, so this describes a proposed review boundary rather than live execution with approvals.
A practical next step
Share the operating context and request a qualification review.