taskfloFOR CTO · ENGINEERING · PLATFORM
Ship workflows. Not governance plumbing.
Your team could build permissions, policy, sealed deployments and audit chains around an agent framework. Or they could focus on the workflows.
YOUR RESPONSIBILITY
What you’re accountable for.
Getting AI onto infrastructure you can operate.
Passing your security review.
Avoiding a platform you cannot leave.
THE MECHANISMS
What to bring into the review.
- Durable execution on Temporal
- Content-addressed workflow versions
- Cedar for authorisation and Rego for compliance
- Customer-cloud deployment bundles
- Sandboxed customer components
- An explicit eject path
Questions you’ll ask.
Does each workflow generate code?
The intended runtime uses a versioned interpreter and an immutable workflow document.
Which models?
The architecture uses a gateway bound to your cloud’s model services. Validate regional and model requirements with us.
What happens when we eject?
Exported Temporal Python workflows leave Taskflo’s governance envelope. That boundary must be explicit.
Can we bring custom components?
The specification separates trusted tools from customer-written components in a resource-limited sandbox, without cloud identity or network access. Declare effects and test the isolation before promotion.
How are policy and workflow versions linked?
The sealed bundle pins the workflow, component versions and policy pack. A change creates a new version to review, not an in-place change to an approved artefact.
ONE WORKFLOW. A CLEAR NEXT STEP.
Talk to the people who wrote the specification.
Tell us about the process, the systems and the people. Let’s work through what it would take to run it.