Files

Ani (Annie Tunturi) 00382055c6 Initial commit: Community ADE foundation

- Project structure: docs/, src/, tests/, proto/
- Research synthesis: Letta vs commercial ADEs
- Architecture: Redis Streams queue design
- Phase 1 orchestration design
- Execution plan and project state tracking
- Working subagent system (manager.ts fixes)

This is the foundation for a Community ADE built on Letta's
stateful agent architecture with git-native MemFS.

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>

2026-03-18 10:30:20 -04:00

3.3 KiB

Raw Blame History

Community ADE Project - State Management

Project: Letta Community Agentic Development Environment
Orchestrator: Ani (Annie Tunturi)
Created: March 18, 2026
Status: Phase 1 - Orchestration Layer

Active Subagents

Subagent	Type	Status	Assigned Task	Output Location
explorer-1	explore	PENDING	Codebase exploration - task queue patterns	/tmp/ade-explorer-1/
architect-1	feature-architect	PENDING	Design Redis queue integration	/tmp/ade-architect-1/
researcher-1	researcher	COMPLETED	ADE competitive analysis	docs/community-ade-research-synthesis-2026-03-18.md

Document Registry

Research Documents

community-ade-research-2026-03-18.md - Initial research
ade-phase1-orchestration-design.md - Phase 1 technical design
community-ade-research-synthesis-2026-03-18.md - Web research synthesis
ade-phase1-execution-plan.md - 6-week execution plan

Design Documents

ade-redis-queue-design.md - Redis queue architecture (COMPLETED by researcher-2)
ade-task-queue-spec.md - Detailed task queue specification (IN PROGRESS)
ade-worker-pool-design.md - Worker pool architecture (PENDING)
ade-dashboard-wireframes.md - Dashboard UI design (PENDING)

Implementation

ade-queue-prototype/ - In-memory prototype (NOT STARTED)
ade-redis-queue/ - Redis-backed implementation (NOT STARTED)
ade-worker-process/ - Worker daemon (NOT STARTED)

Current Phase: Phase 1 - Orchestration Layer

Goals

Build persistent task queue system
Implement worker pool for subagent execution
Add retry logic with exponential backoff
Integrate with existing Task tool

Decisions Made

Use Redis (not Celery) for direct control
In-memory prototype first, then Redis
Worker pool with heartbeat monitoring
Defer Temporal to Phase 2 evaluation

Open Questions

Should we use Redis Streams or Sorted Sets?
Worker count: Fixed or dynamic?
Task priority levels: Simple (high/normal) or granular?

Subagent Work Queue

Ready to Assign

Explore task queue patterns in codebase
- Type: explore
- Focus: Find existing queue/spawning code
- Output: File locations and patterns
Design Redis queue architecture
- Type: architect
- Focus: Data models, operations, integration points
- Output: Architecture spec document
Research Playwright Computer Use
- Type: researcher
- Focus: Browser automation for agentic coding
- Output: Integration approach

Blocked

None currently

Completed

ADE competitive analysis (researcher-1)

State Updates Log

2026-03-18 09:23 EDT - Project initiated, research documents created 2026-03-18 10:01 EDT - Attempting to spawn parallel subagents 2026-03-18 02:03 EDT - explorer-1 completed: Found Task.ts (line 403), manager.ts (spawnSubagent at line 883), in-memory QueueRuntime class. No Redis currently exists. 2026-03-18 02:07 EDT - researcher-2 completed: Redis queue architecture design. Key decisions: Redis Streams (consumer groups), Hash per task, 5s worker heartbeat, exponential backoff with jitter, adapter pattern integration.

This file is maintained by Ani. Update when subagents report progress.

3.3 KiB Raw Blame History