Skip to content

feat: implement centralized single-writer state coordination (TaskEngine) #204

@Aureliolo

Description

@Aureliolo

Summary

The spec describes a centralized single-writer pattern where a TaskEngine owns all task/project mutations via asyncio.Queue. Agents submit requests, the engine applies model_copy(update=...) sequentially and publishes snapshots. Not implemented.

Design Spec Reference

  • §6.8 State Coordination vs Workspace Isolation (table)
  • §15.5 Engineering Conventions — "State coordination" row

Scope

  • TaskEngine single-writer service with asyncio.Queue
  • Sequential mutation application via model_copy(update=...)
  • Snapshot publishing for consumers
  • Optional version: int field on state models for future optimistic concurrency

Metadata

Metadata

Assignees

No one assigned

    Labels

    prio:highImportant, should be prioritizedscope:large3+ days of workspec:agent-systemDESIGN_SPEC Section 3 - Agent Systemspec:architectureDESIGN_SPEC Section 15 - Technical Architecturespec:communicationDESIGN_SPEC Section 5 - Communication Architecturespec:task-workflowDESIGN_SPEC Section 6 - Task & Workflow Enginetype:featureNew feature implementation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions