PLATFORM / WORKFLOW ENGINE / FLOW V2.0

One logic.
Many objects.

FLOW v2 runs verified local engines across a bounded batch, evaluates explicit conditions per object and lets you save reusable recipes locally. It still does not automate arbitrary tool UIs: unsupported byte mutations fail closed.

Build workflow →

BATCH≤ 20 OBJECTS→INSPECTSHA-256→IFKIND / PRIVACY / SIZE→ACTWIPE / RENAME / PACK→HANDOFFVERIFIED OUTPUT

LOCAL EXECUTION / MULTI-OBJECTNO SERVER PAYLOAD20 OBJECTS / 512 MBREADY

01 / COMPOSE

Save the logic.
Reuse the flow.

FLOW v2 compiles one verified pipeline, evaluates a bounded condition per object and executes objects sequentially to keep memory predictable.

PIPELINE POLICYPRIVACY SCANWIPE SUPPORTED CONTENTSAFE RENAMEPACK EACH MATCHRENAME SUFFIXAPPLY MUTATIONS WHENBUILD ONE VERIFIED BATCH ZIPRun enabled mutation steps for every object.

LOCAL RECIPES / 0/12

02 / OBJECTS

DROP A LOCAL BATCH

Up to 20 objects. Every object receives its own analysis, condition decision, execution trace and final SHA-256.

01 / REUSABLESave the recipe, not the payload.

Up to twelve local recipes keep only pipeline configuration. File names, content and execution history are not stored with the recipe.

02 / CONDITIONSBranch on verified signals.

Mutation steps can target all objects, sensitive objects, text/data/code, images, archives or objects at least one MiB.

03 / FAIL CLOSEDPartial batch never becomes a clean bundle.

One blocked object does not stop verification of the rest, but the combined ZIP is withheld until every object passes.

04 / LOCALNo workflow cloud.

Files, recipe execution and evidence stay in the browser. Only an explicit final HANDOFF can move a verified result elsewhere.

One logic.Many objects.

One logic.
Many objects.