Declare
EffectIR names the kind, target, purpose, confidentiality, and integrity of a phase effect.
taskflow 1.0.0 · Declarative workflows
taskflow turns coding-agent work into a verifiable runtime: explicit graphs, typed effect declarations, isolated execution, resource-controlled filesystem commits, and ledger-backed explanations across six hosts.
Trusted Effects Bench
Declare, admit, transact, explain.
PathRef admitted. Resource intent committed. why-effect can explain the principal, capability, lifecycle, and generation.
1.0.0 host installation commands.
pi install npm:pi-taskflow@betaRuntime contract
Taskflow 1.0 makes side effects explicit without claiming a sandbox it does not have.
EffectIR names the kind, target, purpose, confidentiality, and integrity of a phase effect.
PathRef resolution, label flow, and mutating-path overlap are checked before the resource transaction proceeds.
A durable ledger backs why-authorized, why-context, and why-effect explanations without spending model tokens.
Release ledger
The mature DAG runtime, DSL and six adapters share a typed, inspectable boundary around declared filesystem effects.
Closed effect kinds, typed refs, and labels travel through validation, FlowIR, hashing, and runtime admission.
Snapshot, lease, intent, stage, commit — or restore and reject when the transaction cannot complete.
why-effect explains authorization and lifecycle from durable resource records, not from model prose.
Declared targets are protected by the MVP path; undeclared writes and OS-level sandboxing remain outside the claim.
ControlHost has private workspace Unix UDS/store code; admission, parked approvals, receipts, global coordination and WebUI remain outside the stable API.
Pi, Codex, Claude Code, OpenCode, Grok, and Hermes share the taskflow runtime while retaining host-specific policy.
Authoring surface
JSON for transport. TypeScript for authoring. FlowIR and EffectIR for the compiled contract.
Difference ledger
Not a sandbox claim — an operating boundary.
taskflow 1.0 · declarative workflows
Declare the target, verify the boundary, commit through one authority, and keep the claim honest.