Workstream, evidence & decision gates
Coordinate human and agent tasks through explicit state transitions, required proof artifacts, and auditable approvals.
Work item state machine
Every task in Workstream follows a deterministic lifecycle designed to separate active execution from verified completion:
queued ──▶ in_progress ──▶ review ──▶ verified
│ ▲
▼ │
blocked ─────────┘ queued: Scoped work item with a named owner, bound workflow version, and measurable Definition of Done.in_progress: Active work by a human or assigned agent within declared budget and connector bounds.blocked: Explicitly paused on a missing dependency, failed check, or unresolved Decision Gate—naming who must unblock it.review: Execution steps finished; awaiting inspection of attached evidence and pending approvals.verified: All required evidence types are attached, linked Decision Gates are approved, and the accountable owner signs off.
Accountable ownership vs delegation
AgentSpace distinguishes who performs a step from who owns the outcome:
- An agent participant can draft outputs, invoke allowlisted read tools, and attach trace or evaluation evidence.
- Every work item retains an accountable human participant responsible for risk boundaries and final verification.
- Messages in work-linked conversation threads preserve context and identity—they never implicitly grant connector permissions or bypass a Decision Gate.
Attaching typed evidence
Workflows declare which evidence categories must be attached before a task can enter verified state—such as source citations, evaluation scores, diff reviews, or test summaries.
Evidence records store structured summaries, source URIs, SHA-256 hashes, and verification timestamps so teams can prove work quality without duplicating sensitive raw documents across systems.
Resolving decision gates
- Inspect the pending gate
Open Decisions or select the gated work item in Workstream to inspect the trigger reason, due date, and linked evidence.
- Record an explicit rationale
Approvers choose Approve, Request changes, or Reject alongside a written decision note.
- Verify immutable audit linkage
Resolving a gate appends a tamper-evident record to Ledger linking the approver, timestamp, work item, and inspected evidence IDs.
Handling blocked work and audit trail
When a required evidence type is missing or a Decision Gate is rejected, AgentSpace blocks premature verification and surfaces the exact unmet requirement in the inspector. Re-attaching corrected proof and recording a fresh approval unblocks the transition cleanly while preserving the earlier rejection in Ledger history.
tests/backend/workspace-lifecycle.test.tstests/backend/audit.test.ts