mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

[EPIC] Agent Orchestration - Persistent task management #95

New Issue
Closed
opened 2026-01-29 23:29:55 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-29 23:29:55 +00:00
Owner
Copy Link

Overview

Infrastructure for persistent task management with Orchestrator service (`apps/orchestrator/`) as the execution backend.

Architectural Decision (2026-02-02 Update)

Architecture updated: Orchestrator is now a monorepo service at `apps/orchestrator/`, not external ClawdBot.

Delegation Model: Mosaic Stack integrates with Orchestrator service rather than building orchestration internally.

Layer Responsibility
Mosaic Stack Control Plane — task CRUD, UI, RBAC, dispatch, kill authority
Orchestrator service (`apps/orchestrator/`) Execution Plane — agent spawning, health monitoring, recovery, scheduling

Scope

Mosaic Stack handles:

• Task definitions and CRUD API
• Database persistence (survives restarts)
• Progress UI and audit trail
• Dispatch to Orchestrator service backend
• Kill authority over all Orchestrator operations
• Failure handling (when Orchestrator reports failures)

Orchestrator service (`apps/orchestrator/`) handles:

• Agent spawning and lifecycle
• Health monitoring and heartbeats
• Automatic recovery
• Task coordination and scheduling

Phases

• Phase 1: Foundation (database schema, CRUD API)
• Phase 2: Orchestrator Integration (dispatcher, callbacks, kill endpoints)
• Phase 3: Failure Handling (retry logic, escalation)
• Phase 4: Observability (dashboard, kill controls)

Related

• #83 Federation EPIC (cross-instance coordination)
• #102 Gateway Integration (Orchestrator connection)
• ORCH-101 to ORCH-134 (Orchestrator implementation issues)

## Overview Infrastructure for persistent task management with Orchestrator service (\`apps/orchestrator/\`) as the execution backend. ## Architectural Decision (2026-02-02 Update) **Architecture updated:** Orchestrator is now a monorepo service at \`apps/orchestrator/\`, not external ClawdBot. **Delegation Model:** Mosaic Stack integrates with Orchestrator service rather than building orchestration internally. | Layer | Responsibility | |-------|----------------| | **Mosaic Stack** | Control Plane — task CRUD, UI, RBAC, dispatch, **kill authority** | | **Orchestrator service (\`apps/orchestrator/\`)** | Execution Plane — agent spawning, health monitoring, recovery, scheduling | ## Scope **Mosaic Stack handles:** • Task definitions and CRUD API • Database persistence (survives restarts) • Progress UI and audit trail • Dispatch to Orchestrator service backend • **Kill authority** over all Orchestrator operations • Failure handling (when Orchestrator reports failures) **Orchestrator service (\`apps/orchestrator/\`) handles:** • Agent spawning and lifecycle • Health monitoring and heartbeats • Automatic recovery • Task coordination and scheduling ## Phases • Phase 1: Foundation (database schema, CRUD API) • Phase 2: Orchestrator Integration (dispatcher, callbacks, kill endpoints) • Phase 3: Failure Handling (retry logic, escalation) • Phase 4: Observability (dashboard, kill controls) ## Related • #83 Federation EPIC (cross-instance coordination) • #102 Gateway Integration (Orchestrator connection) • ORCH-101 to ORCH-134 (Orchestrator implementation issues)
jason.woltje added this to the M6-AgentOrchestration (0.0.6) milestone 2026-01-29 23:29:55 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label
Milestone
No items
No Milestone M6-AgentOrchestration (0.0.6)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#95
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?