Trusted Effects
Taskflow 1.0.0 documentation. These instructions use exact 1.0.0 package pins. Check GitHub Releases for publication and the acceptance scoreboard for tested scope and limitations. The Control Plane and WebUI are implemented; control binaries are bundled in
taskflow-mcp-core.
Trusted Effects makes a phase's side effects explicit. The model may propose content, but for an admitted declared filesystem target, the resources transaction is the only finalizer.
The vertical slice
The checked-in examples/trusted-effects-write.json declares one fs.write effect for out/report.md. The no-LLM fixture exercises the same resource-controlled path:
pnpm exec node --conditions=development --experimental-strip-types --test \
packages/taskflow-core/test/effects-e2e-fixture.test.tsThe contract
| Concept | Meaning |
|---|---|
EffectIR | Closed effect vocabulary carried by the flow/phase contract |
PathRef | Typed workspace-relative target; no bare string authority |
SecretRef / ServiceRef | Typed handles that fail closed until a real backend is bound |
| Labels | Fixed confidentiality/integrity checks across the phase DAG |
| Resource transaction | Durable snapshot → lease → intent/permit → stage → commit or restore/reject |
why-effect | Read-only, ledger-backed explanation of authorization and lifecycle |
What this does not claim
- It is not a FileBroker or a full OS sandbox.
- Resolve-only hosts cannot prevent every write to an undeclared path.
- SecretRef has no vault backend in this cut.
- ServiceRef has no live network adapter in this cut.
- ControlHost implements authenticated admission, durable approvals/Receipts, coordination and WebUI over Unix UDS and files-only stores. The existing public MCP package bundles the control binaries. Windows pipes remain non-GA.
Read next
Last updated on
Was this helpful?
Help us improve the docs or ask a question in the community.