displayName
tasks-mux
protocolType
task
nativeSide
- Claude AskUserQuestion
- MCP question/answer
- Kanban (in-repo)
- CLI prompt
- GitHub Issues
- Linear
- Jira
- git markers
- email
- webhook
canonicalSide
Unified task lifecycle — open → assigned → in-progress → answered/done → closed
position
Between consumer code (SDK orchestrators, hooks) and task backends with bidirectional comment sync
bridgingConcerns
- task kinds (decision — renamed from breakpoint; task — work item with labels; external-task — outside our system)
- cross-cutting axes (actor: human/agent/system, mode: sync/deferred, backend: pluggable, dependencies: DAG of tasks)
- live decision schema (BreakpointStrategy, Urgency, InteractionKind, BreakpointContext, BreakpointRouting, ResponderProfile, BreakpointAnswer + BreakpointAnswerRating + DecisionMemory, ProvenBreakpointAnswer)
- comment sync (bidirectional GitHub/Linear/Jira/Kanban ↔ run journal)
- auto-approval pattern-matching DSL (glob decision IDs, attribute predicates AND-combined, consecutive-approval escalation)
catalogInputNodeKinds
- HumanCheckpoint
- AutomationRule
- Issue
trustChainParticipation
live
description
The lone live Trust Chain primitive — ProvenBreakpointAnswer signs
decision answers with the named Authority of the responder. Bridges
every backend (Linear, GitHub, Jira, MCP, Kanban) with bidirectional
comment sync and the same pattern-matching auto-approval DSL.