Development Plan¶

This document provides a comprehensive development plan for connectsoft.me Personal Agents Platform, breaking down all work into Epics (end-to-end big features), Features (substantial work items), and Tasks (smaller actionable items). It is written for product managers, architects, and engineers planning and tracking development work.

The plan is organized by development phases (Phase 0-4) and aligned with bounded contexts and microservices. Each Epic, Feature, and Task is designed to be trackable in Azure DevOps or similar project management tools.

Important

Planning Principles: 1. Epics = End-to-end big features that span multiple services or major capabilities 1. Features = Substantial work items within epics that deliver specific functionality 1. Tasks = Smaller, actionable work items within features that can be completed in 1-3 days 1. Work is organized by bounded contexts (one microservice per context) 1. Dependencies are clearly identified to enable parallel work where possible

Planning Structure¶

Epic/Feature/Task Hierarchy¶

graph TD
    Phase[Development Phase] --> Epic[Epic<br/>ME-EPIC-XXX]
    Epic --> Feature[Feature<br/>ME-FEAT-XXX]
    Feature --> Task[Task<br/>ME-TASK-XXX]

    style Phase fill:#e1f5ff
    style Epic fill:#fff4e1
    style Feature fill:#e8f5e9
    style Task fill:#f3e5f5

Hold "Alt" / "Option" to enable pan & zoom

ID Naming Convention¶

Epic ID: ME-EPIC-XXX (e.g., ME-EPIC-001)
Feature ID: ME-FEAT-XXX (e.g., ME-FEAT-001)
Task ID: ME-TASK-XXX (e.g., ME-TASK-001)

Bounded Context Organization¶

Each microservice corresponds to one bounded context:

Personal Identity & Profile Service → Personal Identity & Profile BC
Agent Catalog Service → Agent Catalog BC
Pack & Workflow Service → Pack & Workflow BC
Agent Orchestration Service → Agent Orchestration BC
Suggestion & Approval Service → Suggestion & Approval BC
Connector Service → Connector BC
Dashboard & Analytics Service → Dashboard & Analytics BC

Phase 0 – Internal Labs¶

Timeline: January - February 2025 (approximately)

Goal: Validate orchestration, logging, and cost model internally.

Epic ME-EPIC-001: Foundation & Infrastructure Setup¶

Phase: 0
Bounded Contexts: Cross-cutting
Status: Planned

Epic Description: Establish the foundational infrastructure, development environment, and project structure for connectsoft.me. This includes repository setup, CI/CD pipelines, development standards, and initial service scaffolding.

Epic Objectives:

Set up development environment and tooling
Establish CI/CD pipelines
Create project structure and standards
Generate initial microservice projects using Factory
Set up Azure infrastructure (App Services, SQL Database, Service Bus, etc.)

Dependencies:

ConnectSoft Microservice Template
Azure subscription and resources
Factory access

Features:

Feature ME-FEAT-001: Repository & Project Structure¶

Epic: ME-EPIC-001
Description: Set up Git repository, project structure, and development standards.

Tasks:

ME-TASK-001: Create Git repository structure for connectsoft.me
ME-TASK-002: Set up solution structure with all microservice projects
ME-TASK-003: Configure .NET solution and project references
ME-TASK-004: Set up shared libraries and common code structure
ME-TASK-005: Define coding standards and conventions document

Acceptance Criteria:

Repository structure follows ConnectSoft standards
All 7 microservice projects created (empty, ready for Factory generation)
Solution builds successfully
Coding standards documented

Feature ME-FEAT-002: CI/CD Pipeline Setup¶

Epic: ME-EPIC-001
Description: Establish Azure DevOps pipelines for build, test, and deployment.

Tasks:

ME-TASK-006: Create Azure DevOps project and repository connection
ME-TASK-007: Set up build pipeline for all microservices
ME-TASK-008: Configure test pipeline (unit tests, integration tests)
ME-TASK-009: Set up deployment pipeline to development environment
ME-TASK-010: Configure pipeline variables and secrets

Acceptance Criteria:

Build pipeline runs successfully
Test pipeline executes and reports results
Deployment pipeline deploys to development environment
All pipelines follow ConnectSoft CI/CD standards

Feature ME-FEAT-003: Azure Infrastructure Setup¶

Epic: ME-EPIC-001
Description: Provision and configure Azure resources for development environment.

Tasks:

ME-TASK-011: Create Azure Resource Group for connectsoft.me
ME-TASK-012: Provision Azure SQL Database (development tier)
ME-TASK-013: Provision Azure Service Bus namespace
ME-TASK-014: Provision Azure App Services for microservices (development tier)
ME-TASK-015: Provision Azure Blob Storage account
ME-TASK-016: Provision Azure Cache for Redis (basic tier)
ME-TASK-017: Configure networking (VNet, private endpoints if needed)
ME-TASK-018: Set up Application Insights for monitoring

Acceptance Criteria:

All Azure resources provisioned
Resources accessible from development environment
Networking configured correctly
Monitoring and logging configured

Epic ME-EPIC-002: Core Platform Integration¶

Phase: 0
Bounded Contexts: Cross-cutting
Status: Planned

Epic Description: Integrate with ConnectSoft Core Platform services (Identity, Audit, Config, Documents, Communications, Billing) and validate personal-tenant patterns.

Epic Objectives:

Integrate with Identity Platform for authentication
Integrate with Audit Platform for logging
Integrate with Config Platform for settings
Integrate with Documents Platform for file storage
Integrate with Communications Platform for notifications
Integrate with Billing Platform for subscriptions
Validate personal-tenant isolation patterns

Dependencies:

Core Platform services must be available
Identity Platform must support personal-tenant patterns
Billing Platform must support tiered subscriptions

Features:

Feature ME-FEAT-004: Identity Platform Integration¶

Epic: ME-EPIC-002
Description: Integrate with Identity Platform for OAuth2/OIDC authentication and personal-tenant management.

Tasks:

ME-TASK-019: Configure OAuth2/OIDC client in Identity Platform
ME-TASK-020: Implement authentication middleware in API Gateway
ME-TASK-021: Implement token validation in microservices
ME-TASK-022: Implement personal-tenant creation flow
ME-TASK-023: Test personal-tenant isolation
ME-TASK-024: Implement user profile sync with Identity Platform

Acceptance Criteria:

Users can authenticate via Identity Platform
Personal tenants created automatically on user registration
Token validation works across all microservices
Personal-tenant isolation enforced

Feature ME-FEAT-005: Audit Platform Integration¶

Epic: ME-EPIC-002
Description: Integrate with Audit Platform for comprehensive audit logging.

Tasks:

ME-TASK-025: Install Audit Platform client library
ME-TASK-026: Implement audit event emission in all microservices
ME-TASK-027: Define audit event schemas for agent runs
ME-TASK-028: Test audit event logging and retrieval
ME-TASK-029: Implement audit log viewing in UI (basic)

Acceptance Criteria:

All critical operations emit audit events
Audit events stored in Audit Platform
Audit logs queryable via API
Basic audit log viewing works

Feature ME-FEAT-006: Config Platform Integration¶

Epic: ME-EPIC-002
Description: Integrate with Config Platform for user preferences and settings.

Tasks:

ME-TASK-030: Install Config Platform client library
ME-TASK-031: Implement config read/write operations
ME-TASK-032: Define config schemas for user preferences
ME-TASK-033: Implement feature flags support
ME-TASK-034: Test config operations

Acceptance Criteria:

User preferences stored in Config Platform
Feature flags work correctly
Config changes trigger webhooks (if needed)

Feature ME-FEAT-007: Documents Platform Integration¶

Epic: ME-EPIC-002
Description: Integrate with Documents Platform for file storage.

Tasks:

ME-TASK-035: Install Documents Platform client library
ME-TASK-036: Implement file upload operations
ME-TASK-037: Implement file download operations
ME-TASK-038: Implement file metadata management
ME-TASK-039: Test file operations with personal-tenant isolation

Acceptance Criteria:

Files can be uploaded to Documents Platform
Files can be downloaded with proper access control
File metadata stored correctly
Personal-tenant isolation enforced

Feature ME-FEAT-008: Communications Platform Integration¶

Epic: ME-EPIC-002
Description: Integrate with Communications Platform for email and notifications.

Tasks:

ME-TASK-040: Install Communications Platform client library
ME-TASK-041: Implement email sending (notifications)
ME-TASK-042: Implement in-app notification sending
ME-TASK-043: Configure email templates
ME-TASK-044: Test email and notification delivery

Acceptance Criteria:

Email notifications sent successfully
In-app notifications delivered
Email templates render correctly

Feature ME-FEAT-009: Billing Platform Integration¶

Epic: ME-EPIC-002
Description: Integrate with Billing Platform for subscription management and usage tracking.

Tasks:

ME-TASK-045: Install Billing Platform client library
ME-TASK-046: Implement subscription creation (Free tier)
ME-TASK-047: Implement subscription upgrade/downgrade
ME-TASK-048: Implement usage tracking (agent runs, tokens)
ME-TASK-049: Implement usage limit checking
ME-TASK-050: Test subscription and usage operations

Acceptance Criteria:

Subscriptions created correctly
Usage tracked accurately
Usage limits enforced
Subscription changes reflected immediately

Epic ME-EPIC-003: Proof-of-Concept Agents¶

Phase: 0
Bounded Contexts: Agent Orchestration, Agent Catalog
Status: Planned

Epic Description: Build 2-3 internal proof-of-concept agents to validate orchestration, logging, and cost model. These agents will serve as templates for MVP prebuilt packs.

Epic Objectives:

Build Inbox Agent (email triage)
Build Planner Agent (calendar coordination)
Build Budget Agent (expense categorization)
Validate agent execution flow
Measure token usage and costs
Test multi-agent patterns

Dependencies:

AI Gateway & Agent Runtime available
Agent Template available
Email and Calendar connectors (basic)

Features:

Feature ME-FEAT-010: Inbox Agent (POC)¶

Epic: ME-EPIC-003
Description: Build proof-of-concept Inbox Agent that triages emails and drafts replies.

Tasks:

ME-TASK-051: Design Inbox Agent prompt and behavior
ME-TASK-052: Implement Inbox Agent using Agent Template
ME-TASK-053: Integrate with Email connector (read inbox)
ME-TASK-054: Implement email triage logic
ME-TASK-055: Implement draft email generation
ME-TASK-056: Test Inbox Agent execution
ME-TASK-057: Measure token usage and costs

Acceptance Criteria:

Inbox Agent successfully triages emails
Draft emails generated correctly
Token usage tracked
Cost per run calculated

Feature ME-FEAT-011: Planner Agent (POC)¶

Epic: ME-EPIC-003
Description: Build proof-of-concept Planner Agent that reads calendar and suggests focus blocks.

Tasks:

ME-TASK-058: Design Planner Agent prompt and behavior
ME-TASK-059: Implement Planner Agent using Agent Template
ME-TASK-060: Integrate with Calendar connector (read events)
ME-TASK-061: Implement calendar analysis logic
ME-TASK-062: Implement focus block suggestions
ME-TASK-063: Test Planner Agent execution
ME-TASK-064: Measure token usage and costs

Acceptance Criteria:

Planner Agent successfully reads calendar
Focus block suggestions generated
Token usage tracked
Cost per run calculated

Feature ME-FEAT-012: Budget Agent (POC)¶

Epic: ME-EPIC-003
Description: Build proof-of-concept Budget Agent that categorizes expenses from CSV files.

Tasks:

ME-TASK-065: Design Budget Agent prompt and behavior
ME-TASK-066: Implement Budget Agent using Agent Template
ME-TASK-067: Implement CSV file parsing
ME-TASK-068: Implement expense categorization logic
ME-TASK-069: Implement budget summary generation
ME-TASK-070: Test Budget Agent execution
ME-TASK-071: Measure token usage and costs

Acceptance Criteria:

Budget Agent successfully processes CSV files
Expenses categorized correctly
Budget summary generated
Token usage tracked

Feature ME-FEAT-013: Multi-Agent Orchestration (POC)¶

Epic: ME-EPIC-003
Description: Test sequential multi-agent workflows with POC agents.

Tasks:

ME-TASK-072: Design sequential workflow (Inbox → Planner)
ME-TASK-073: Implement workflow orchestration logic
ME-TASK-074: Test sequential execution
ME-TASK-075: Measure token usage for multi-agent runs
ME-TASK-076: Validate cost model for workflows

Acceptance Criteria:

Sequential workflows execute correctly
Agent outputs passed between agents
Token usage tracked per agent and total
Cost model validated

Phase 1 – MVP Alpha¶

Timeline: February - April 2025 (approximately)

Goal: Real weekly value, minimal UI, heavy reuse of backend strengths.

Epic ME-EPIC-004: Personal Identity & Profile Service¶

Phase: 1
Bounded Context: Personal Identity & Profile
Status: Planned

Epic Description: Build the Personal Identity & Profile microservice that manages user accounts, personal tenants, user profiles, and subscriptions.

Epic Objectives:

User account creation and management
Personal tenant management (one user = one personal tenant)
User profile management (timezone, language, preferences)
Subscription management (Free, Pro tiers)
Integration with Identity Platform and Billing Platform

Dependencies:

ME-EPIC-002 (Core Platform Integration)
Identity Platform with personal-tenant support
Billing Platform with tiered subscriptions

Features:

Feature ME-FEAT-014: User Account Management¶

Epic: ME-EPIC-004
Description: Implement user account creation, retrieval, update, and deletion.

Tasks:

ME-TASK-077: Generate Personal Identity Service using Factory
ME-TASK-078: Implement User aggregate (domain model)
ME-TASK-079: Implement PersonalTenant aggregate (domain model)
ME-TASK-080: Implement User registration API endpoint
ME-TASK-081: Implement User profile retrieval API
ME-TASK-082: Implement User profile update API
ME-TASK-083: Implement User account deletion API
ME-TASK-084: Implement personal-tenant creation on user registration
ME-TASK-085: Write unit tests for User aggregate
ME-TASK-086: Write integration tests for User APIs

Acceptance Criteria:

Users can register and create accounts
Personal tenants created automatically
User profiles can be retrieved and updated
User accounts can be deleted (with data cleanup)
All operations enforce personal-tenant isolation

Feature ME-FEAT-015: User Profile Management¶

Epic: ME-EPIC-004
Description: Implement user profile management (timezone, language, preferences).

Tasks:

ME-TASK-087: Implement UserProfile aggregate (domain model)
ME-TASK-088: Implement profile retrieval API
ME-TASK-089: Implement profile update API
ME-TASK-090: Implement notification preferences management
ME-TASK-091: Implement privacy settings management
ME-TASK-092: Integrate with Config Platform for preferences storage
ME-TASK-093: Write unit tests for UserProfile aggregate
ME-TASK-094: Write integration tests for profile APIs

Acceptance Criteria:

User profiles can be retrieved and updated
Timezone and language preferences saved
Notification preferences configurable
Privacy settings configurable
Preferences stored in Config Platform

Feature ME-FEAT-016: Subscription Management¶

Epic: ME-EPIC-004
Description: Implement subscription management (Free, Pro tiers) with Billing Platform integration.

Tasks:

ME-TASK-095: Implement Subscription aggregate (domain model)
ME-TASK-096: Implement subscription creation (Free tier default)
ME-TASK-097: Implement subscription upgrade (Free → Pro)
ME-TASK-098: Implement subscription downgrade (Pro → Free)
ME-TASK-099: Implement subscription cancellation
ME-TASK-100: Integrate with Billing Platform for subscription operations
ME-TASK-101: Implement subscription status checking
ME-TASK-102: Write unit tests for Subscription aggregate
ME-TASK-103: Write integration tests for subscription APIs

Acceptance Criteria:

Subscriptions created with Free tier by default
Users can upgrade to Pro tier
Users can downgrade to Free tier
Subscriptions can be cancelled
Subscription status synced with Billing Platform

Epic ME-EPIC-005: Agent Catalog Service¶

Phase: 1
Bounded Context: Agent Catalog
Status: Planned

Epic Description: Build the Agent Catalog microservice that manages agent templates (base definitions) and agent instances (user-specific configurations).

Epic Objectives:

AgentTemplate management (prebuilt templates)
AgentInstance management (user-specific configurations)
Agent archetype definitions
Integration with Config Platform for agent configurations

Dependencies:

ME-EPIC-002 (Core Platform Integration)
Proof-of-concept agents from Phase 0

Features:

Feature ME-FEAT-017: Agent Template Management¶

Epic: ME-EPIC-005
Description: Implement AgentTemplate management for prebuilt agent templates.

Tasks:

ME-TASK-104: Generate Agent Catalog Service using Factory
ME-TASK-105: Implement AgentTemplate aggregate (domain model)
ME-TASK-106: Implement AgentArchetype value object
ME-TASK-107: Seed prebuilt agent templates (Inbox, Planner, Budget, Learning)
ME-TASK-108: Implement template retrieval API (list all templates)
ME-TASK-109: Implement template details API (get by ID)
ME-TASK-110: Write unit tests for AgentTemplate aggregate
ME-TASK-111: Write integration tests for template APIs

Acceptance Criteria:

Prebuilt agent templates available
Templates can be listed and retrieved
Template details include archetype, description, default config
Templates are read-only (built-in)

Feature ME-FEAT-018: Agent Instance Management¶

Epic: ME-EPIC-005
Description: Implement AgentInstance management for user-specific agent configurations.

Tasks:

ME-TASK-112: Implement AgentInstance aggregate (domain model)
ME-TASK-113: Implement agent instance creation from template
ME-TASK-114: Implement agent instance retrieval API (list user's instances)
ME-TASK-115: Implement agent instance details API
ME-TASK-116: Implement agent instance configuration update API
ME-TASK-117: Implement agent instance deletion API
ME-TASK-118: Integrate with Config Platform for agent configurations
ME-TASK-119: Implement usage limit validation (subscription tier)
ME-TASK-120: Write unit tests for AgentInstance aggregate
ME-TASK-121: Write integration tests for instance APIs

Acceptance Criteria:

Users can create agent instances from templates
Agent instances can be retrieved, updated, and deleted
Agent configurations stored in Config Platform
Usage limits enforced based on subscription tier

Epic ME-EPIC-006: Pack & Workflow Service¶

Phase: 1
Bounded Context: Pack & Workflow
Status: Planned

Epic Description: Build the Pack & Workflow microservice that manages agent packs (teams of agents) and workflows (triggers, sequences).

Epic Objectives:

AgentPack management (prebuilt packs)
Pack installation and configuration
Basic workflow definitions (manual and scheduled triggers)
Simple sequential workflows

Dependencies:

ME-EPIC-005 (Agent Catalog Service)
Proof-of-concept agents from Phase 0

Features:

Feature ME-FEAT-019: Agent Pack Management¶

Epic: ME-EPIC-006
Description: Implement AgentPack management for prebuilt agent packs.

Tasks:

ME-TASK-122: Generate Pack & Workflow Service using Factory
ME-TASK-123: Implement AgentPack aggregate (domain model)
ME-TASK-124: Seed prebuilt packs (Life Admin Pack, Budget Lite Pack, Study Pack)
ME-TASK-125: Implement pack retrieval API (list available packs)
ME-TASK-126: Implement pack details API (get by ID)
ME-TASK-127: Implement pack installation API
ME-TASK-128: Implement pack deletion API
ME-TASK-129: Implement usage limit validation (packs per subscription tier)
ME-TASK-130: Write unit tests for AgentPack aggregate
ME-TASK-131: Write integration tests for pack APIs

Acceptance Criteria:

Prebuilt packs available for installation
Users can install packs (creates agent instances)
Pack installation respects subscription limits
Packs can be deleted

Feature ME-FEAT-020: Workflow Definition Management¶

Epic: ME-EPIC-006
Description: Implement basic workflow definitions (manual and scheduled triggers, simple sequential workflows).

Tasks:

ME-TASK-132: Implement AgentWorkflow aggregate (domain model)
ME-TASK-133: Implement WorkflowTrigger aggregate (domain model)
ME-TASK-134: Implement workflow creation API
ME-TASK-135: Implement workflow retrieval API
ME-TASK-136: Implement workflow update API
ME-TASK-137: Implement workflow deletion API
ME-TASK-138: Implement manual trigger definition
ME-TASK-139: Implement scheduled trigger definition (cron expressions)
ME-TASK-140: Implement simple sequential workflow steps
ME-TASK-141: Integrate with Config Platform for workflow definitions
ME-TASK-142: Write unit tests for workflow aggregates
ME-TASK-143: Write integration tests for workflow APIs

Acceptance Criteria:

Workflows can be created, retrieved, updated, and deleted
Manual triggers work
Scheduled triggers work (cron-based)
Sequential workflow steps defined correctly
Workflow definitions stored in Config Platform

Epic ME-EPIC-007: Agent Orchestration Service¶

Phase: 1
Bounded Context: Agent Orchestration
Status: Planned

Epic Description: Build the Agent Orchestration microservice that manages agent execution, agent runs, and integrates with AI Gateway.

Epic Objectives:

AgentRun execution and management
Manual agent execution (single agent or pack)
Scheduled agent execution (cron-based triggers)
Agent run tracking and logging
Token usage and cost tracking
Integration with AI Gateway & Agent Runtime

Dependencies:

ME-EPIC-005 (Agent Catalog Service)
ME-EPIC-006 (Pack & Workflow Service)
AI Gateway & Agent Runtime available
ME-EPIC-002 (Core Platform Integration)

Features:

Feature ME-FEAT-021: Agent Run Execution Engine¶

Epic: ME-EPIC-007
Description: Implement core agent execution engine that orchestrates agent runs via AI Gateway.

Tasks:

ME-TASK-144: Generate Agent Orchestration Service using Factory
ME-TASK-145: Implement AgentRun aggregate (domain model)
ME-TASK-146: Implement AgentRunStep aggregate (domain model)
ME-TASK-147: Integrate with AI Gateway for agent execution
ME-TASK-148: Implement single agent execution flow
ME-TASK-149: Implement pack execution flow (all agents in pack)
ME-TASK-150: Implement run status tracking (Pending, Running, Completed, Failed)
ME-TASK-151: Implement run cancellation
ME-TASK-152: Implement error handling and retry logic
ME-TASK-153: Write unit tests for AgentRun aggregate
ME-TASK-154: Write integration tests for execution APIs

Acceptance Criteria:

Single agents can be executed successfully
Packs can be executed (all agents in pack)
Run status tracked correctly
Runs can be cancelled
Errors handled gracefully

Feature ME-FEAT-022: Manual Agent Execution¶

Epic: ME-EPIC-007
Description: Implement manual "Run now" functionality for agents and packs.

Tasks:

ME-TASK-155: Implement manual trigger API endpoint
ME-TASK-156: Implement usage limit validation before execution
ME-TASK-157: Implement agent/pack validation before execution
ME-TASK-158: Implement run creation and queuing
ME-TASK-159: Implement async execution processing
ME-TASK-160: Implement run completion notification
ME-TASK-161: Write integration tests for manual execution

Acceptance Criteria:

Users can trigger manual agent runs
Usage limits checked before execution
Runs execute asynchronously
Users notified on completion

Feature ME-FEAT-023: Scheduled Agent Execution¶

Epic: ME-EPIC-007
Description: Implement scheduled agent execution using cron-based triggers.

Tasks:

ME-TASK-162: Implement scheduled trigger scheduler service
ME-TASK-163: Implement cron expression parsing
ME-TASK-164: Implement trigger firing logic
ME-TASK-165: Implement scheduled run creation
ME-TASK-166: Implement scheduler persistence (survive restarts)
ME-TASK-167: Implement timezone handling for scheduled runs
ME-TASK-168: Write integration tests for scheduled execution

Acceptance Criteria:

Scheduled triggers fire at correct times
Cron expressions parsed correctly
Timezone handling works correctly
Scheduler persists across service restarts

Feature ME-FEAT-024: Token Usage & Cost Tracking¶

Epic: ME-EPIC-007
Description: Implement token usage and cost tracking for agent runs.

Tasks:

ME-TASK-169: Implement token usage tracking per run
ME-TASK-170: Implement token usage tracking per step
ME-TASK-171: Implement cost calculation per run
ME-TASK-172: Integrate with Billing Platform for usage recording
ME-TASK-173: Implement cost aggregation per user
ME-TASK-174: Write unit tests for cost calculation
ME-TASK-175: Write integration tests for usage tracking

Acceptance Criteria:

Token usage tracked accurately per run
Cost calculated correctly
Usage recorded in Billing Platform
Cost aggregation works correctly

Feature ME-FEAT-025: Run History & Logging¶

Epic: ME-EPIC-007
Description: Implement agent run history, logging, and audit trail.

Tasks:

ME-TASK-176: Implement run history storage
ME-TASK-177: Implement run details retrieval API
ME-TASK-178: Implement run step details retrieval API
ME-TASK-179: Implement run logs storage
ME-TASK-180: Integrate with Audit Platform for run events
ME-TASK-181: Implement "See what this agent did" functionality
ME-TASK-182: Write integration tests for run history

Acceptance Criteria:

Run history stored and retrievable
Run details include all execution information
Run logs available for transparency
Audit events logged to Audit Platform

Epic ME-EPIC-008: Suggestion & Approval Service¶

Phase: 1
Bounded Context: Suggestion & Approval
Status: Planned

Epic Description: Build the Suggestion & Approval microservice that manages suggestions (actions proposed by agents) and approval workflow.

Epic Objectives:

Suggestion creation from agent runs
User inbox for suggestions
Approve, reject, or edit suggestions
Bulk approval operations
Integration with Connector Service for executing approved actions

Dependencies:

ME-EPIC-007 (Agent Orchestration Service)
ME-EPIC-009 (Connector Service - MVP)
ME-EPIC-002 (Core Platform Integration)

Features:

Feature ME-FEAT-026: Suggestion Management¶

Epic: ME-EPIC-008
Description: Implement suggestion creation and management.

Tasks:

ME-TASK-183: Generate Suggestion & Approval Service using Factory
ME-TASK-184: Implement Suggestion aggregate (domain model)
ME-TASK-185: Implement suggestion creation from agent runs
ME-TASK-186: Implement suggestion retrieval API (list user's suggestions)
ME-TASK-187: Implement suggestion details API
ME-TASK-188: Implement suggestion filtering (by type, status, priority)
ME-TASK-189: Implement suggestion expiration logic
ME-TASK-190: Write unit tests for Suggestion aggregate
ME-TASK-191: Write integration tests for suggestion APIs

Acceptance Criteria:

Suggestions created from agent runs
Suggestions can be listed and filtered
Suggestion details retrievable
Expired suggestions handled correctly

Feature ME-FEAT-027: Approval Workflow¶

Epic: ME-EPIC-008
Description: Implement approval workflow (approve, reject, edit).

Tasks:

ME-TASK-192: Implement Approval aggregate (domain model)
ME-TASK-193: Implement suggestion approval API
ME-TASK-194: Implement suggestion rejection API
ME-TASK-195: Implement suggestion edit API (edit then approve)
ME-TASK-196: Implement bulk approval API
ME-TASK-197: Integrate with Connector Service for executing approved actions
ME-TASK-198: Implement approval status tracking
ME-TASK-199: Write unit tests for Approval aggregate
ME-TASK-200: Write integration tests for approval APIs

Acceptance Criteria:

Users can approve, reject, or edit suggestions
Bulk approval works
Approved actions executed via Connector Service
Approval status tracked correctly

Feature ME-FEAT-028: Suggestion Inbox¶

Epic: ME-EPIC-008
Description: Implement user suggestion inbox with unified UI.

Tasks:

ME-TASK-201: Implement SuggestionInbox aggregate (domain model)
ME-TASK-202: Implement inbox retrieval API
ME-TASK-203: Implement unread count tracking
ME-TASK-204: Implement suggestion grouping (by agent, pack, type)
ME-TASK-205: Implement suggestion prioritization
ME-TASK-206: Write integration tests for inbox APIs

Acceptance Criteria:

Users can view their suggestion inbox
Unread count tracked correctly
Suggestions grouped logically
Priority ordering works

Epic ME-EPIC-009: Connector Service (MVP)¶

Phase: 1
Bounded Context: Connector
Status: Planned

Epic Description: Build the Connector microservice (MVP) that manages external service connectors (Email, Calendar, File upload).

Epic Objectives:

ConnectorConfig management (authorized apps/links)
Email connector (Gmail, Outlook) - read inbox, create drafts
Calendar connector (Google Calendar, Outlook Calendar) - read events, create event suggestions
File upload connector - upload PDFs, DOCX, TXT files
OAuth authorization flows
Integration with Documents Platform

Dependencies:

ME-EPIC-002 (Core Platform Integration)
Documents Platform available
OAuth providers configured

Features:

Feature ME-FEAT-029: Connector Configuration Management¶

Epic: ME-EPIC-009
Description: Implement connector configuration management and OAuth authorization.

Tasks:

ME-TASK-207: Generate Connector Service using Factory
ME-TASK-208: Implement ConnectorConfig aggregate (domain model)
ME-TASK-209: Implement connector type definitions
ME-TASK-210: Implement OAuth authorization initiation
ME-TASK-211: Implement OAuth callback handling
ME-TASK-212: Implement token storage and refresh
ME-TASK-213: Implement connector revocation
ME-TASK-214: Write unit tests for ConnectorConfig aggregate
ME-TASK-215: Write integration tests for connector APIs

Acceptance Criteria:

Users can authorize connectors via OAuth
OAuth tokens stored securely
Token refresh works
Connectors can be revoked

Feature ME-FEAT-030: Email Connector¶

Epic: ME-EPIC-009
Description: Implement Email connector (Gmail, Outlook) for reading inbox and creating drafts.

Tasks:

ME-TASK-216: Implement Gmail API integration
ME-TASK-217: Implement Outlook/Microsoft Graph API integration
ME-TASK-218: Implement inbox reading (list emails)
ME-TASK-219: Implement email content retrieval
ME-TASK-220: Implement draft email creation
ME-TASK-221: Implement email search
ME-TASK-222: Write integration tests for email connector

Acceptance Criteria:

Email inbox can be read
Email content retrievable
Draft emails can be created
Email search works

Feature ME-FEAT-031: Calendar Connector¶

Epic: ME-EPIC-009
Description: Implement Calendar connector (Google Calendar, Outlook Calendar) for reading events and creating event suggestions.

Tasks:

ME-TASK-223: Implement Google Calendar API integration
ME-TASK-224: Implement Outlook Calendar API integration
ME-TASK-225: Implement calendar event reading (list events)
ME-TASK-226: Implement event details retrieval
ME-TASK-227: Implement event suggestion creation (not auto-create)
ME-TASK-228: Write integration tests for calendar connector

Acceptance Criteria:

Calendar events can be read
Event details retrievable
Event suggestions can be created
Suggestions require approval (not auto-created)

Feature ME-FEAT-032: File Upload Connector¶

Epic: ME-EPIC-009
Description: Implement File upload connector for uploading PDFs, DOCX, TXT files.

Tasks:

ME-TASK-229: Implement file upload API endpoint
ME-TASK-230: Implement file type validation (PDF, DOCX, TXT)
ME-TASK-231: Implement file size validation
ME-TASK-232: Integrate with Documents Platform for file storage
ME-TASK-233: Implement file metadata storage
ME-TASK-234: Implement file retrieval API
ME-TASK-235: Write integration tests for file upload connector

Acceptance Criteria:

Files can be uploaded (PDF, DOCX, TXT)
File type and size validated
Files stored in Documents Platform
Files can be retrieved

Feature ME-FEAT-033: Data Snapshot Management¶

Epic: ME-EPIC-009
Description: Implement data snapshot management for caching connector metadata.

Tasks:

ME-TASK-236: Implement DataSnapshot aggregate (domain model)
ME-TASK-237: Implement snapshot creation (cache metadata)
ME-TASK-238: Implement snapshot retrieval
ME-TASK-239: Implement snapshot expiration
ME-TASK-240: Integrate with Redis Cache for snapshots
ME-TASK-241: Write unit tests for DataSnapshot aggregate

Acceptance Criteria:

Data snapshots created and cached
Snapshots retrievable
Snapshots expire correctly
Redis caching works

Epic ME-EPIC-010: Dashboard & Analytics Service¶

Phase: 1
Bounded Context: Dashboard & Analytics
Status: Planned

Epic Description: Build the Dashboard & Analytics microservice that aggregates data from other contexts to provide dashboards, usage analytics, and run history.

Epic Objectives:

Dashboard generation
Usage analytics (runs, tokens, costs)
Run history and summaries
Cost tracking
Integration with Audit Platform for analytics

Dependencies:

ME-EPIC-007 (Agent Orchestration Service)
ME-EPIC-008 (Suggestion & Approval Service)
ME-EPIC-002 (Core Platform Integration)

Features:

Feature ME-FEAT-034: Dashboard Generation¶

Epic: ME-EPIC-010
Description: Implement dashboard generation with key metrics and widgets.

Tasks:

ME-TASK-242: Generate Dashboard & Analytics Service using Factory
ME-TASK-243: Implement Dashboard aggregate (domain model)
ME-TASK-244: Implement dashboard retrieval API
ME-TASK-245: Implement packs overview widget
ME-TASK-246: Implement agents overview widget
ME-TASK-247: Implement recent runs widget
ME-TASK-248: Implement suggestions inbox widget
ME-TASK-249: Implement usage summary widget
ME-TASK-250: Write integration tests for dashboard APIs

Acceptance Criteria:

Dashboard can be retrieved
All widgets populated with correct data
Dashboard updates in real-time

Feature ME-FEAT-035: Usage Analytics¶

Epic: ME-EPIC-010
Description: Implement usage analytics (runs, tokens, costs).

Tasks:

ME-TASK-251: Implement UsageAnalytics aggregate (domain model)
ME-TASK-252: Implement usage calculation (runs/month, tokens used)
ME-TASK-253: Implement cost aggregation
ME-TASK-254: Implement usage vs. limits comparison
ME-TASK-255: Implement usage trends calculation
ME-TASK-256: Write integration tests for analytics APIs

Acceptance Criteria:

Usage analytics calculated correctly
Cost aggregation accurate
Usage vs. limits comparison works
Trends calculated correctly

Feature ME-FEAT-036: Run History¶

Epic: ME-EPIC-010
Description: Implement run history and summaries.

Tasks:

ME-TASK-257: Implement RunHistory aggregate (domain model)
ME-TASK-258: Implement run history retrieval API
ME-TASK-259: Implement run history filtering (by date, status, agent)
ME-TASK-260: Implement run summary generation
ME-TASK-261: Write integration tests for run history APIs

Acceptance Criteria:

Run history retrievable
Filtering works correctly
Run summaries generated accurately

Epic ME-EPIC-011: Web UI (MVP)¶

Phase: 1
Bounded Contexts: All (Frontend)
Status: Planned

Epic Description: Build the MVP Web UI that provides essential user interfaces for core flows (onboarding, dashboard, agent management, suggestions).

Epic Objectives:

User onboarding flow
Dashboard UI
Pack and agent management UI
Suggestion inbox UI
Basic run history UI
Authentication UI

Dependencies:

All backend services (ME-EPIC-004 through ME-EPIC-010)
Identity Platform OAuth2/OIDC flow

Features:

Feature ME-FEAT-037: Authentication & Onboarding UI¶

Epic: ME-EPIC-011
Description: Implement authentication and user onboarding UI.

Tasks:

ME-TASK-262: Set up frontend project (React/Next.js or preferred framework)
ME-TASK-263: Implement OAuth2/OIDC login flow
ME-TASK-264: Implement user registration UI
ME-TASK-265: Implement onboarding wizard (welcome, profile setup)
ME-TASK-266: Implement profile management UI
ME-TASK-267: Write E2E tests for authentication flow

Acceptance Criteria:

Users can log in via OAuth2/OIDC
Users can register and complete onboarding
Profile management works

Feature ME-FEAT-038: Dashboard UI¶

Epic: ME-EPIC-011
Description: Implement main dashboard UI with key widgets.

Tasks:

ME-TASK-268: Implement dashboard layout
ME-TASK-269: Implement packs overview widget UI
ME-TASK-270: Implement agents overview widget UI
ME-TASK-271: Implement recent runs widget UI
ME-TASK-272: Implement suggestions inbox widget UI
ME-TASK-273: Implement usage summary widget UI
ME-TASK-274: Implement responsive design
ME-TASK-275: Write E2E tests for dashboard

Acceptance Criteria:

Dashboard displays all widgets
Widgets show correct data
Dashboard is responsive
Real-time updates work

Feature ME-FEAT-039: Pack & Agent Management UI¶

Epic: ME-EPIC-011
Description: Implement UI for managing packs and agents.

Tasks:

ME-TASK-276: Implement pack browsing UI (available packs)
ME-TASK-277: Implement pack installation UI
ME-TASK-278: Implement installed packs list UI
ME-TASK-279: Implement pack details UI
ME-TASK-280: Implement agent instances list UI
ME-TASK-281: Implement agent instance details UI
ME-TASK-282: Implement agent configuration UI
ME-TASK-283: Write E2E tests for pack/agent management

Acceptance Criteria:

Users can browse and install packs
Installed packs displayed correctly
Agent instances displayed and configurable
Configuration changes saved

Feature ME-FEAT-040: Agent Execution UI¶

Epic: ME-EPIC-011
Description: Implement UI for triggering and viewing agent runs.

Tasks:

ME-TASK-284: Implement "Run now" button UI
ME-TASK-285: Implement run status display UI
ME-TASK-286: Implement run results display UI
ME-TASK-287: Implement run history list UI
ME-TASK-288: Implement run details view UI
ME-TASK-289: Implement "See what this agent did" UI
ME-TASK-290: Write E2E tests for agent execution

Acceptance Criteria:

Users can trigger manual runs
Run status displayed in real-time
Run results displayed correctly
Run history viewable
Agent action transparency works

Feature ME-FEAT-041: Suggestion Inbox UI¶

Epic: ME-EPIC-011
Description: Implement suggestion inbox UI for reviewing and approving suggestions.

Tasks:

ME-TASK-291: Implement suggestion inbox list UI
ME-TASK-292: Implement suggestion details view UI
ME-TASK-293: Implement approve/reject/edit actions UI
ME-TASK-294: Implement bulk approval UI
ME-TASK-295: Implement suggestion filtering UI
ME-TASK-296: Implement suggestion grouping UI
ME-TASK-297: Write E2E tests for suggestion inbox

Acceptance Criteria:

Suggestions displayed in inbox
Users can approve, reject, or edit suggestions
Bulk approval works
Filtering and grouping work

Epic ME-EPIC-012: Billing Integration¶

Phase: 1
Bounded Contexts: Personal Identity & Profile, Cross-cutting
Status: Planned

Epic Description: Complete billing integration with Billing Platform for subscription management, usage tracking, and invoicing.

Epic Objectives:

Subscription tier management (Free, Pro)
Usage tracking and limits enforcement
Invoice generation
Payment processing integration
Usage-based billing

Dependencies:

ME-EPIC-002 (Core Platform Integration)
ME-EPIC-004 (Personal Identity & Profile Service)
ME-EPIC-007 (Agent Orchestration Service)
Billing Platform available

Features:

Feature ME-FEAT-042: Subscription Tier Management¶

Epic: ME-EPIC-012
Description: Implement subscription tier management (Free, Pro) with Billing Platform.

Tasks:

ME-TASK-298: Implement subscription tier definitions
ME-TASK-299: Implement tier limits configuration (packs, agents, runs)
ME-TASK-300: Implement tier upgrade flow
ME-TASK-301: Implement tier downgrade flow
ME-TASK-302: Integrate with Billing Platform for tier changes
ME-TASK-303: Write integration tests for tier management

Acceptance Criteria:

Subscription tiers defined correctly
Tier limits enforced
Tier upgrades/downgrades work
Billing Platform synced

Feature ME-FEAT-043: Usage Tracking & Limits¶

Epic: ME-EPIC-012
Description: Implement usage tracking and limit enforcement.

Tasks:

ME-TASK-304: Implement usage tracking (agent runs, tokens, storage)
ME-TASK-305: Implement usage limit checking before operations
ME-TASK-306: Implement usage limit enforcement
ME-TASK-307: Integrate with Billing Platform for usage recording
ME-TASK-308: Implement usage limit UI indicators
ME-TASK-309: Write integration tests for usage tracking

Acceptance Criteria:

Usage tracked accurately
Limits enforced before operations
Usage recorded in Billing Platform
UI shows usage vs. limits

Feature ME-FEAT-044: Invoice & Payment Integration¶

Epic: ME-EPIC-012
Description: Implement invoice generation and payment processing integration.

Tasks:

ME-TASK-310: Integrate with Billing Platform for invoice generation
ME-TASK-311: Implement invoice retrieval API
ME-TASK-312: Implement payment processing integration
ME-TASK-313: Implement invoice UI
ME-TASK-314: Write integration tests for invoice/payment

Acceptance Criteria:

Invoices generated correctly
Invoices retrievable
Payment processing works
Invoice UI displays correctly

Phase 2 – Multi-Agent Workflows & Collaboration¶

Timeline: May - July 2025 (approximately)

Goal: Add real multi-agent orchestration beyond independent runs.

Epic ME-EPIC-013: Workflow Engine Enhancement¶

Phase: 2
Bounded Contexts: Pack & Workflow, Agent Orchestration
Status: Planned

Epic Description: Enhance the workflow engine to support complex multi-agent workflows with sequential and parallel execution patterns.

Epic Objectives:

Enhanced workflow definitions (sequential, parallel, hybrid)
Workflow execution engine improvements
Coordinator agent support
Workflow state management
Workflow visualization

Dependencies:

ME-EPIC-006 (Pack & Workflow Service)
ME-EPIC-007 (Agent Orchestration Service)

Features:

Feature ME-FEAT-045: Sequential Workflow Execution¶

Epic: ME-EPIC-013
Description: Implement enhanced sequential workflow execution where each agent uses output from previous agent.

Tasks:

ME-TASK-315: Enhance workflow definition to support sequential steps
ME-TASK-316: Implement step output passing between agents
ME-TASK-317: Implement sequential execution engine
ME-TASK-318: Implement step result storage
ME-TASK-319: Implement workflow state management
ME-TASK-320: Write integration tests for sequential workflows

Acceptance Criteria:

Sequential workflows execute correctly
Agent outputs passed between steps
Workflow state tracked
Step results stored

Feature ME-FEAT-046: Parallel Workflow Execution¶

Epic: ME-EPIC-013
Description: Implement parallel workflow execution with coordinator agent.

Tasks:

ME-TASK-321: Enhance workflow definition to support parallel steps
ME-TASK-322: Implement parallel execution engine
ME-TASK-323: Implement coordinator agent execution
ME-TASK-324: Implement result aggregation logic
ME-TASK-325: Implement parallel execution state management
ME-TASK-326: Write integration tests for parallel workflows

Acceptance Criteria:

Parallel workflows execute correctly
Coordinator agent aggregates results
Parallel execution state tracked
Results aggregated correctly

Feature ME-FEAT-047: Workflow Execution Visualization¶

Epic: ME-EPIC-013
Description: Implement workflow execution visualization in UI.

Tasks:

ME-TASK-327: Implement workflow execution status API
ME-TASK-328: Implement workflow visualization UI component
ME-TASK-329: Implement real-time execution updates
ME-TASK-330: Write E2E tests for workflow visualization

Acceptance Criteria:

Workflow execution visualized in UI
Real-time updates work
Execution status displayed correctly

Epic ME-EPIC-014: Suggestion Inbox Enhancement¶

Phase: 2
Bounded Context: Suggestion & Approval
Status: Planned

Epic Description: Enhance the suggestion inbox with improved UI, filtering, grouping, and bulk operations.

Epic Objectives:

Enhanced suggestion inbox UI
Advanced filtering and grouping
Bulk operations improvements
Task board view
Timeline view

Dependencies:

ME-EPIC-008 (Suggestion & Approval Service)
ME-EPIC-011 (Web UI - MVP)

Features:

Feature ME-FEAT-048: Enhanced Suggestion Inbox UI¶

Epic: ME-EPIC-014
Description: Enhance suggestion inbox UI with advanced features.

Tasks:

ME-TASK-331: Implement advanced filtering UI (by type, agent, date, status)
ME-TASK-332: Implement suggestion grouping UI (by agent, pack, workflow)
ME-TASK-333: Implement suggestion sorting UI
ME-TASK-334: Implement suggestion search UI
ME-TASK-335: Implement suggestion priority indicators
ME-TASK-336: Write E2E tests for enhanced inbox

Acceptance Criteria:

Advanced filtering works
Grouping and sorting work
Search works
Priority indicators displayed

Feature ME-FEAT-049: Task Board & Timeline Views¶

Epic: ME-EPIC-014
Description: Implement task board and timeline views for suggestions.

Tasks:

ME-TASK-337: Implement task board view UI
ME-TASK-338: Implement timeline view UI
ME-TASK-339: Implement view switching
ME-TASK-340: Write E2E tests for task board/timeline

Acceptance Criteria:

Task board view works
Timeline view works
View switching works

Epic ME-EPIC-015: Additional Connectors¶

Phase: 2
Bounded Context: Connector
Status: Planned

Epic Description: Add additional connectors beyond MVP (Email, Calendar, File upload).

Epic Objectives:

Notion connector
Google Drive connector
OneDrive connector
Enhanced connector framework

Dependencies:

ME-EPIC-009 (Connector Service - MVP)
Documents Platform available

Features:

Feature ME-FEAT-050: Notion Connector¶

Epic: ME-EPIC-015
Description: Implement Notion connector for reading pages and creating page suggestions.

Tasks:

ME-TASK-341: Implement Notion OAuth authorization
ME-TASK-342: Implement Notion API integration
ME-TASK-343: Implement page reading
ME-TASK-344: Implement database reading
ME-TASK-345: Implement page suggestion creation
ME-TASK-346: Write integration tests for Notion connector

Acceptance Criteria:

Notion connector authorized via OAuth
Pages and databases can be read
Page suggestions can be created

Feature ME-FEAT-051: Google Drive Connector¶

Epic: ME-EPIC-015
Description: Implement Google Drive connector for file access.

Tasks:

ME-TASK-347: Implement Google Drive OAuth authorization
ME-TASK-348: Implement Google Drive API integration
ME-TASK-349: Implement file listing
ME-TASK-350: Implement file content reading
ME-TASK-351: Implement file suggestion creation
ME-TASK-352: Write integration tests for Google Drive connector

Acceptance Criteria:

Google Drive connector authorized
Files can be listed and read
File suggestions can be created

Feature ME-FEAT-052: OneDrive Connector¶

Epic: ME-EPIC-015
Description: Implement OneDrive connector for file access.

Tasks:

ME-TASK-353: Implement OneDrive OAuth authorization
ME-TASK-354: Implement Microsoft Graph API integration
ME-TASK-355: Implement file listing
ME-TASK-356: Implement file content reading
ME-TASK-357: Implement file suggestion creation
ME-TASK-358: Write integration tests for OneDrive connector

Acceptance Criteria:

OneDrive connector authorized
Files can be listed and read
File suggestions can be created

Phase 3 – Agent Builder & Pack Builder, Public Beta¶

Timeline: August - October 2025 (approximately)

Goal: Enable users to create custom agents and packs without code.

Epic ME-EPIC-016: No-Code Agent Builder¶

Phase: 3
Bounded Contexts: Agent Catalog, Agent Orchestration
Status: Planned

Epic Description: Build no-code agent builder that enables users to create custom agents via wizard interface.

Epic Objectives:

Visual agent configuration wizard
Agent archetype selection
Tool selection and configuration
Behavior rules configuration
Agent testing and validation
Custom agent instance creation

Dependencies:

ME-EPIC-005 (Agent Catalog Service)
ME-EPIC-007 (Agent Orchestration Service)
ME-EPIC-011 (Web UI - MVP)

Features:

Feature ME-FEAT-053: Agent Builder Wizard¶

Epic: ME-EPIC-016
Description: Implement visual agent builder wizard UI.

Tasks:

ME-TASK-359: Design agent builder wizard flow
ME-TASK-360: Implement wizard step 1: Agent name and description
ME-TASK-361: Implement wizard step 2: Archetype selection
ME-TASK-362: Implement wizard step 3: Tool selection
ME-TASK-363: Implement wizard step 4: Behavior rules configuration
ME-TASK-364: Implement wizard step 5: Testing and validation
ME-TASK-365: Implement wizard step 6: Save agent
ME-TASK-366: Write E2E tests for agent builder

Acceptance Criteria:

Agent builder wizard works end-to-end
All steps functional
Agent saved correctly

Feature ME-FEAT-054: Agent Configuration Management¶

Epic: ME-EPIC-016
Description: Implement agent configuration management for custom agents.

Tasks:

ME-TASK-367: Enhance AgentInstance to support custom agents
ME-TASK-368: Implement custom agent configuration storage
ME-TASK-369: Implement agent configuration validation
ME-TASK-370: Implement agent testing API
ME-TASK-371: Write integration tests for agent configuration

Acceptance Criteria:

Custom agent configurations saved
Configurations validated
Agent testing works

Epic ME-EPIC-017: Pack Builder¶

Phase: 3
Bounded Context: Pack & Workflow
Status: Planned

Epic Description: Build pack builder that enables users to create custom packs and workflows.

Epic Objectives:

Visual pack composition
Workflow builder (triggers, steps, parallel paths)
Pack testing and validation
Custom pack creation

Dependencies:

ME-EPIC-006 (Pack & Workflow Service)
ME-EPIC-013 (Workflow Engine Enhancement)
ME-EPIC-011 (Web UI - MVP)

Features:

Feature ME-FEAT-055: Pack Builder UI¶

Epic: ME-EPIC-017
Description: Implement visual pack builder UI.

Tasks:

ME-TASK-372: Design pack builder UI flow
ME-TASK-373: Implement pack composition UI (select agents)
ME-TASK-374: Implement pack configuration UI
ME-TASK-375: Implement pack testing UI
ME-TASK-376: Implement pack save functionality
ME-TASK-377: Write E2E tests for pack builder

Acceptance Criteria:

Pack builder works end-to-end
Packs can be composed and saved
Pack testing works

Feature ME-FEAT-056: Visual Workflow Builder¶

Epic: ME-EPIC-017
Description: Implement visual workflow builder for creating custom workflows.

Tasks:

ME-TASK-378: Design visual workflow builder UI
ME-TASK-379: Implement workflow step drag-and-drop
ME-TASK-380: Implement trigger configuration UI
ME-TASK-381: Implement sequential flow configuration
ME-TASK-382: Implement parallel flow configuration
ME-TASK-383: Implement workflow validation
ME-TASK-384: Write E2E tests for workflow builder

Acceptance Criteria:

Visual workflow builder works
Workflows can be created visually
Workflow validation works

Epic ME-EPIC-018: Public Beta Infrastructure¶

Phase: 3
Bounded Contexts: Cross-cutting
Status: Planned

Epic Description: Prepare infrastructure and processes for public beta launch.

Epic Objectives:

Public site deployment
Enhanced onboarding flows
Public documentation
Community support channels
Beta user management

Dependencies:

All Phase 1 and Phase 2 epics
Public-facing infrastructure ready

Features:

Feature ME-FEAT-057: Public Site & Onboarding¶

Epic: ME-EPIC-018
Description: Implement public site and enhanced onboarding flows.

Tasks:

ME-TASK-385: Deploy public site (app.connectsoft.me)
ME-TASK-386: Implement public landing page
ME-TASK-387: Implement enhanced onboarding wizard
ME-TASK-388: Implement product tour
ME-TASK-389: Implement help and documentation links
ME-TASK-390: Write E2E tests for public onboarding

Acceptance Criteria:

Public site deployed
Onboarding flow works
Product tour functional

Feature ME-FEAT-058: Documentation & Support¶

Epic: ME-EPIC-018
Description: Create public documentation and support channels.

Tasks:

ME-TASK-391: Create user documentation
ME-TASK-392: Create video tutorials
ME-TASK-393: Set up community support channels
ME-TASK-394: Implement in-app help system
ME-TASK-395: Create FAQ section

Acceptance Criteria:

Documentation available
Support channels operational
Help system functional

Phase 4 – Marketplace & Growth, Upsell into connectsoft.io¶

Timeline: November 2025 - March 2026 (approximately)

Goal: Enable marketplace and deepen integration with connectsoft.io for upsell.

Epic ME-EPIC-019: Internal Marketplace¶

Phase: 4
Bounded Contexts: Pack & Workflow, Agent Catalog
Status: Planned

Epic Description: Build internal marketplace for curated packs (internal first, then community).

Epic Objectives:

Marketplace browsing UI
Pack installation from marketplace
Pack preview and details
Marketplace search and filtering
Internal pack curation

Dependencies:

ME-EPIC-006 (Pack & Workflow Service)
ME-EPIC-011 (Web UI - MVP)
Curated packs available

Features:

Feature ME-FEAT-059: Marketplace Browsing¶

Epic: ME-EPIC-019
Description: Implement marketplace browsing UI and functionality.

Tasks:

ME-TASK-396: Design marketplace UI
ME-TASK-397: Implement marketplace home page
ME-TASK-398: Implement pack browsing UI
ME-TASK-399: Implement pack search and filtering
ME-TASK-400: Implement pack preview UI
ME-TASK-401: Implement pack details page
ME-TASK-402: Write E2E tests for marketplace

Acceptance Criteria:

Marketplace browsable
Search and filtering work
Pack previews displayed
Pack details viewable

Feature ME-FEAT-060: Marketplace Installation¶

Epic: ME-EPIC-019
Description: Implement one-click pack installation from marketplace.

Tasks:

ME-TASK-403: Implement marketplace installation API
ME-TASK-404: Implement installation flow
ME-TASK-405: Implement installation validation (subscription limits)
ME-TASK-406: Implement installation UI
ME-TASK-407: Write integration tests for installation

Acceptance Criteria:

Packs can be installed from marketplace
Installation respects subscription limits
Installation flow works smoothly

Epic ME-EPIC-020: Creator Features¶

Phase: 4
Bounded Contexts: Agent Catalog, Pack & Workflow, Cross-cutting
Status: Planned

Epic Description: Build creator features for users to publish packs/agents to marketplace with revenue sharing.

Epic Objectives:

Creator add-on subscription
Pack/agent publishing
Revenue sharing system
Creator analytics
Marketplace moderation

Dependencies:

ME-EPIC-019 (Internal Marketplace)
ME-EPIC-012 (Billing Integration)
Creator add-on tier defined

Features:

Feature ME-FEAT-061: Creator Publishing¶

Epic: ME-EPIC-020
Description: Implement pack/agent publishing functionality for creators.

Tasks:

ME-TASK-408: Implement creator add-on subscription management
ME-TASK-409: Implement pack publishing API
ME-TASK-410: Implement agent publishing API
ME-TASK-411: Implement publishing validation
ME-TASK-412: Implement publishing UI
ME-TASK-413: Write integration tests for publishing

Acceptance Criteria:

Creators can publish packs/agents
Publishing validated
Published items appear in marketplace

Epic: ME-EPIC-020
Description: Implement revenue sharing system (70% creator / 30% ConnectSoft).

Tasks:

ME-TASK-414: Implement marketplace pricing (creator sets price)
ME-TASK-415: Implement revenue tracking
ME-TASK-416: Implement revenue sharing calculation
ME-TASK-417: Implement creator payout system
ME-TASK-418: Integrate with Billing Platform for revenue sharing
ME-TASK-419: Write integration tests for revenue sharing

Acceptance Criteria:

Creators can set pack prices
Revenue tracked correctly
Revenue sharing calculated correctly
Payouts processed

Feature ME-FEAT-063: Creator Analytics¶

Epic: ME-EPIC-020
Description: Implement analytics for creators (pack usage, revenue, ratings).

Tasks:

ME-TASK-420: Implement creator analytics API
ME-TASK-421: Implement pack usage analytics
ME-TASK-422: Implement revenue analytics
ME-TASK-423: Implement ratings and reviews system
ME-TASK-424: Implement creator analytics UI
ME-TASK-425: Write integration tests for creator analytics

Acceptance Criteria:

Creators can view analytics
Usage and revenue tracked
Ratings and reviews work

Epic ME-EPIC-021: Upgrade Path to connectsoft.io¶

Phase: 4
Bounded Contexts: Cross-cutting
Status: Planned

Epic Description: Build upgrade path from connectsoft.me to connectsoft.io for organizational workflows.

Epic Objectives:

"Promote Pack to Organizational Workflow" feature
Seamless transition from personal to team use
Integration with connectsoft.io workflows
Cross-platform pack/workflow sharing

Dependencies:

ME-EPIC-006 (Pack & Workflow Service)
connectsoft.io platform available
Integration Platform available

Features:

Feature ME-FEAT-064: Pack Promotion Feature¶

Epic: ME-EPIC-021
Description: Implement "Promote Pack to Organizational Workflow" feature.

Tasks:

ME-TASK-426: Design pack promotion flow
ME-TASK-427: Implement pack promotion API
ME-TASK-428: Implement pack transformation logic (personal → organizational)
ME-TASK-429: Integrate with connectsoft.io API
ME-TASK-430: Implement promotion UI
ME-TASK-431: Write integration tests for promotion

Acceptance Criteria:

Packs can be promoted to connectsoft.io
Promotion transforms pack correctly
Integration with connectsoft.io works

Feature ME-FEAT-065: Cross-Platform Integration¶

Epic: ME-EPIC-021
Description: Implement cross-platform integration between .me and .io.

Tasks:

ME-TASK-432: Design cross-platform integration architecture
ME-TASK-433: Implement shared workflow format
ME-TASK-434: Implement cross-platform authentication
ME-TASK-435: Implement workflow synchronization
ME-TASK-436: Write integration tests for cross-platform

Acceptance Criteria:

Cross-platform integration works
Workflows can be shared
Authentication works across platforms

Epic ME-EPIC-022: Community Marketplace¶

Phase: 4
Bounded Contexts: Pack & Workflow, Agent Catalog
Status: Planned

Epic Description: Open marketplace to community creators with ratings, reviews, and moderation.

Epic Objectives:

Community pack/agent publishing
Ratings and reviews system
Marketplace moderation
Community engagement features

Dependencies:

ME-EPIC-019 (Internal Marketplace)
ME-EPIC-020 (Creator Features)

Features:

Feature ME-FEAT-066: Community Publishing¶

Epic: ME-EPIC-022
Description: Enable community creators to publish packs/agents.

Tasks:

ME-TASK-437: Open marketplace to community creators
ME-TASK-438: Implement community publishing flow
ME-TASK-439: Implement publishing guidelines
ME-TASK-440: Write integration tests for community publishing

Acceptance Criteria:

Community creators can publish
Publishing guidelines enforced

Feature ME-FEAT-067: Ratings & Reviews¶

Epic: ME-EPIC-022
Description: Implement ratings and reviews system for marketplace items.

Tasks:

ME-TASK-441: Implement ratings system
ME-TASK-442: Implement reviews system
ME-TASK-443: Implement ratings/reviews API
ME-TASK-444: Implement ratings/reviews UI
ME-TASK-445: Write integration tests for ratings/reviews

Acceptance Criteria:

Users can rate and review packs/agents
Ratings and reviews displayed
Ratings aggregated correctly

Feature ME-FEAT-068: Marketplace Moderation¶

Epic: ME-EPIC-022
Description: Implement marketplace moderation system.

Tasks:

ME-TASK-446: Implement moderation workflow
ME-TASK-447: Implement content review system
ME-TASK-448: Implement moderation UI
ME-TASK-449: Write integration tests for moderation

Acceptance Criteria:

Marketplace content moderated
Moderation workflow works

Development Dependencies¶

Critical Path Dependencies¶

graph TD
    P0[Phase 0: Foundation] --> P1[Phase 1: MVP Alpha]
    P1 --> P2[Phase 2: Multi-Agent Workflows]
    P2 --> P3[Phase 3: Agent Builder & Public Beta]
    P3 --> P4[Phase 4: Marketplace & Growth]

    P0 --> Core[Core Platform Integration]
    P1 --> Services[All 7 Microservices]
    P1 --> UI[MVP Web UI]
    P2 --> Workflows[Workflow Engine]
    P3 --> Builder[Agent/Pack Builder]
    P4 --> Marketplace[Marketplace]

    style P0 fill:#e1f5ff
    style P1 fill:#fff4e1
    style P2 fill:#e8f5e9
    style P3 fill:#f3e5f5
    style P4 fill:#fff9c4

Hold "Alt" / "Option" to enable pan & zoom

External Dependencies¶

Core Platform Services:

Identity Platform (personal-tenant support)
Audit Platform (event logging)
Config Platform (settings)
Documents Platform (file storage)
Communications Platform (email, notifications)
Billing Platform (tiered subscriptions)

AI Factory:

Agent Template (agent scaffolding)
AI Gateway (model routing, token tracking)
Agent Runtime (agent execution)

Integration Platform (Later Phases):

Connector framework
External service integrations

Development Phases Summary¶

Phase	Timeline	Key Deliverables	Epics
Phase 0	Jan-Feb 2025	Foundation, POC agents	3 epics
Phase 1	Feb-Apr 2025	MVP Alpha with all services	9 epics
Phase 2	May-Jul 2025	Multi-agent workflows	3 epics
Phase 3	Aug-Oct 2025	Agent builder, public beta	3 epics
Phase 4	Nov 2025-Mar 2026	Marketplace, growth	4 epics

Domain Overview - Domain overview
Domain Vision and Scope - Vision and scope
Bounded Contexts and Context Map - Domain boundaries
Domain Model and Aggregates - Domain model
Processes and Flows - Business processes
API and Integration View - API design
High-Level Design - System architecture
connectsoft.me Roadmap - Product roadmap
connectsoft.me Functionality - Feature details