taskflow 0.3.0-beta.1.2 · Trusted Effects beta

Declare the effect.Verify the path.Commit through one authority.

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

One contract. Four checkpoints.

Declare, admit, transact, explain.

Declare

EffectIR / PathRef

Admit

labels · overlap

Authorize

principal · capability

Stage

snapshot · intent

Commit

or restore + reject

Ledger

durable evidence

Explain

why-effect

Evidence returnverify

finalOutput

Declared report write

PathRef admitted. Resource intent committed. why-effect can explain the principal, capability, lifecycle, and generation.

Admit

effect: fs.write
PathRef: resolved
labels: pass
overlap: checked

Commit

snapshot: durable
intent: journaled
lifecycle: commit | restore
authority: resources

Explain

why-effect: read-only
principal: derived
capability: bound
status: committed

0.3.0-beta.1.2 host installs — select the beta channel.

pi install npm:pi-taskflow@beta

Guide

Runtime contract

A mutation boundary, not a prompt promise.

The candidate makes side effects explicit without claiming a sandbox it does not have.

Declare

EffectIR names the kind, target, purpose, confidentiality, and integrity of a phase effect.

Admit

PathRef resolution, label flow, and mutating-path overlap are checked before the resource transaction proceeds.

Explain

A durable ledger backs why-authorized, why-context, and why-effect explanations without spending model tokens.

Release ledger

0.3 is the trusted-effects turn.

The 0.2 runtime remains the graph engine; the candidate adds a typed, inspectable boundary around declared filesystem effects.

EffectIR

Effects become data

Closed effect kinds, typed refs, and labels travel through validation, FlowIR, hashing, and runtime admission.

Resources

One mutation authority

Snapshot, lease, intent, stage, commit — or restore and reject when the transaction cannot complete.

why-*

Evidence is queryable

why-effect explains authorization and lifecycle from durable resource records, not from model prose.

Boundary

Security claims stay narrow

Declared targets are protected by the MVP path; undeclared writes and OS-level sandboxing remain outside the claim.

0.3-C

Control Plane follows

The ControlHost scaffold exists; stores, receipts, approvals, and WebUI are future 0.3-C stages, not shipped 0.3 GA surface yet.

Hosts

Six hosts · one flow contract

Pi, Codex, Claude Code, OpenCode, Grok, and Hermes share the taskflow runtime while retaining host-specific policy.

Authoring surface

Same runtime. Three contract surfaces.

JSON for transport. TypeScript for authoring. FlowIR and EffectIR for the compiled contract.

1{
2  "name": "review-changes",
3  "budget": { "maxUSD": 2 },
4  "phases": [
5    {
6      "id": "discover",
7      "type": "agent",
8      "agent": "scout",
9      "task": "List changed files as a JSON array of {path} objects",
10      "output": "json",
11      "expect": {
12        "type": "array",
13        "items": {
14          "type": "object",
15          "properties": { "path": { "type": "string" } },
16          "required": ["path"]
17        }
18      }
19    },
20    {
21      "id": "review",
22      "type": "map",
23      "over": "{steps.discover.json}",
24      "agent": "reviewer",
25      "task": "Review {item.path}",
26      "dependsOn": ["discover"]
27    },
28    {
29      "id": "report",
30      "type": "reduce",
31      "from": ["review"],
32      "task": "Prioritized risk summary",
33      "dependsOn": ["review"],
34      "final": true
35    }
36  ]
37}

Difference ledger

What changes when effects are data.

Not a sandbox claim — an operating boundary.

taskflowad-hoc

authority

one resource finalizer

ambient command writes

target

typed PathRef + admission

implicit path string

failure

restore + reject

partial mutation

evidence

ledger-backed why-effect

model explanation

taskflow 0.3 · candidate

Make the side effect explicit.

Declare the target, verify the boundary, commit through one authority, and keep the claim honest.

Read the docs Install