Write the transformation. Let Vuo own the ugly edges.
Processors remain ordinary C#. Vuo owns durable work, retry policy, staging, verification, delivery, evidence retention and the operational state around your code.
await using IProcessorStep step =
await context.Steps.BeginAsync(
"validate-input",
"Validate input",
cancellationToken);
ValidateDesadv(input);
step.Complete();throw new ProcessorFailureException(
ProcessorFailure.Create(
code: "InputTruncated",
category: ProcessorFailureCategory.InputValidation,
summary: "Mandatory UNT trailer was not found."));AI-ready by being ordinary C#.
Vuo does not introduce a proprietary visual transformation language. A processor is ordinary C# using a small, explicit SDK contract.
That also makes processor development a natural fit for modern coding assistants. Give an AI agent the Vuo processor interface, representative input, expected output, and the business rules, and it can work with the same source code and tests your developers already use.
The result is still normal .NET code: reviewable in Git, testable with standard tooling, debuggable in Visual Studio, and maintainable without the AI that originally helped create it.
No proprietary programming language required.
AI can help write the transformation. Vuo provides the durable execution, artifact handling, processor isolation, safe retries, observability, and operational controls around it.
- The Vuo processor contract
- Representative input files
- Expected output files
- Business transformation rules
- Required failure and validation behavior
- Ordinary C# source code
- MSTest tests
- Structured processor steps
- Structured failure handling
- Code your team can review and own
Small SDK. Clear ownership.
Your processor receives controlled input artifacts. It does not own source deletion or Work Item state.
Write outputs to staging. Vuo independently verifies artifacts before delivery.
Stable failure codes and readable summaries sit above the underlying .NET exception.
The SDK is designed so custom processors can execute behind an out-of-process Processor Host boundary.
The operator surface is scriptable from day one.
Vuo's CLI is intended to remain a permanent product surface, not a temporary scaffolding tool before the web UI arrives.
> vuo flow list
> vuo work show 184293
> vuo work timeline 184293
> vuo work retry 184293 --reason "Credential repaired"
Upload an input. Run the selected processor. Inspect the output.
The planned Console experience will make processor validation a direct part of Flow configuration, with explicit side-effect safety policies for processors that access external systems.