[Phase 6.7] Scheduler

Mark commented

2026-04-02 20:54:42 +00:00

Owner

Overview

Cron-like scheduling for recurring intents and delayed execution.

Problem Statement

Current mesh only processes intents when submitted. Cannot:

Schedule recurring tasks (daily reports, weekly summaries)
Delay execution (process overnight, off-peak)
Set reminders and follow-ups
Automate periodic maintenance

Proposed Solution

6.7.1: Schedule Table

CREATE TABLE scheduled_intents (
    schedule_id TEXT PRIMARY KEY,
    intent_type TEXT,
    payload JSON,
    schedule TEXT,  -- Cron expression or interval
    next_run TIMESTAMP,
    last_run TIMESTAMP,
    enabled BOOLEAN,
    project TEXT,
    created_at TIMESTAMP
);

6.7.2: Scheduler Service

class IntentScheduler:
    """Schedule and execute recurring intents."""
    
    def schedule(self, intent: dict, schedule: str) -> ScheduleID:
        """Schedule intent with cron expression"""
        
    def schedule_delayed(self, intent: dict, delay_seconds: int) -> ScheduleID:
        """Execute intent after delay"""
        
    def cancel(self, schedule_id: str):
        """Cancel scheduled intent"""
        
    def get_next_run(self, schedule_id: str) -> datetime:
        """Get next execution time"""
        
    def tick(self):
        """Check for due intents, execute them"""

6.7.3: Cron Expressions

# Examples
schedules:
  daily_report: "0 9 * * *"  # Every day at 9am
  weekly_summary: "0 10 * * 1"  # Every Monday at 10am
  hourly_check: "0 * * * *"  # Every hour
  custom: "*/15 * * * *"  # Every 15 minutes
  
# Or simple intervals:
intervals:
  every_5_min: "interval:300"  # Every 5 minutes
  every_hour: "interval:3600"

6.7.4: API Endpoints

endpoints:
  POST /v1/schedules:
    body: {intent_type, payload, schedule}
    returns: {schedule_id, next_run}
    
  GET /v1/schedules:
    returns: List of scheduled intents
    
  GET /v1/schedules/<id>:
    returns: Schedule details
    
  DELETE /v1/schedules/<id>:
    returns: {cancelled: true}
    
  POST /v1/schedules/<id>/pause:
    returns: {paused: true}
    
  POST /v1/schedules/<id>/resume:
    returns: {resumed: true, next_run}

Deliverables

scheduled_intents table in ledger
runtime/scheduler.py - Scheduler service
Cron expression parsing
Background tick loop (or external cron trigger)
API endpoints: /v1/schedules/*
Unit tests
Integration tests

Dependencies

None (standalone)

Estimated Duration

1 week

Success Criteria

Intents scheduled with cron expressions
Scheduled intents execute on time
Can pause/resume schedules
Can list and cancel schedules

Parent: #69 (Phase 6 Meta)

## Overview Cron-like scheduling for recurring intents and delayed execution. ## Problem Statement Current mesh only processes intents when submitted. Cannot: - Schedule recurring tasks (daily reports, weekly summaries) - Delay execution (process overnight, off-peak) - Set reminders and follow-ups - Automate periodic maintenance ## Proposed Solution ### 6.7.1: Schedule Table ```sql CREATE TABLE scheduled_intents ( schedule_id TEXT PRIMARY KEY, intent_type TEXT, payload JSON, schedule TEXT, -- Cron expression or interval next_run TIMESTAMP, last_run TIMESTAMP, enabled BOOLEAN, project TEXT, created_at TIMESTAMP ); ``` ### 6.7.2: Scheduler Service ```python class IntentScheduler: """Schedule and execute recurring intents.""" def schedule(self, intent: dict, schedule: str) -> ScheduleID: """Schedule intent with cron expression""" def schedule_delayed(self, intent: dict, delay_seconds: int) -> ScheduleID: """Execute intent after delay""" def cancel(self, schedule_id: str): """Cancel scheduled intent""" def get_next_run(self, schedule_id: str) -> datetime: """Get next execution time""" def tick(self): """Check for due intents, execute them""" ``` ### 6.7.3: Cron Expressions ```yaml # Examples schedules: daily_report: "0 9 * * *" # Every day at 9am weekly_summary: "0 10 * * 1" # Every Monday at 10am hourly_check: "0 * * * *" # Every hour custom: "*/15 * * * *" # Every 15 minutes # Or simple intervals: intervals: every_5_min: "interval:300" # Every 5 minutes every_hour: "interval:3600" ``` ### 6.7.4: API Endpoints ```yaml endpoints: POST /v1/schedules: body: {intent_type, payload, schedule} returns: {schedule_id, next_run} GET /v1/schedules: returns: List of scheduled intents GET /v1/schedules/<id>: returns: Schedule details DELETE /v1/schedules/<id>: returns: {cancelled: true} POST /v1/schedules/<id>/pause: returns: {paused: true} POST /v1/schedules/<id>/resume: returns: {resumed: true, next_run} ``` ## Deliverables - [ ] `scheduled_intents` table in ledger - [ ] `runtime/scheduler.py` - Scheduler service - [ ] Cron expression parsing - [ ] Background tick loop (or external cron trigger) - [ ] API endpoints: `/v1/schedules/*` - [ ] Unit tests - [ ] Integration tests ## Dependencies - None (standalone) ## Estimated Duration 1 week ## Success Criteria - [ ] Intents scheduled with cron expressions - [ ] Scheduled intents execute on time - [ ] Can pause/resume schedules - [ ] Can list and cancel schedules ## Related - Parent: #69 (Phase 6 Meta)

Mark referenced this issue

2026-04-02 20:56:09 +00:00

[Phase 6] Operational Utility - Meta Issue #69

Mark added the

phase-5

label

2026-04-02 20:56:13 +00:00

Mark added

feature-request

and removed

phase-5

labels

2026-05-12 23:27:00 +00:00

Mark added

blocked:needs-decision

and removed

feature-request

labels

2026-05-21 03:11:49 +00:00

Mark removed the

blocked:needs-decision

label

2026-05-28 07:19:16 +00:00

Mark added the

triage-approved

label

2026-06-07 06:12:11 +00:00

Mark added

in-progress

and removed

triage-approved

labels

2026-07-15 10:37:09 +00:00

Mark referenced this issue from a commit

2026-07-15 13:11:45 +00:00

rescue: commit orphan work products from completed issue #76 (Phase 6.7 scheduler)

Mark removed the

in-progress

label

2026-07-15 16:17:17 +00:00

Mark commented

2026-07-16 14:27:51 +00:00

Author

Owner

Implemented and committed on main at f867983.

Deliverables:

scheduled_intents table in ledger (schema.py + core.py + models.py)
runtime/scheduler.py — IntentScheduler with schedule/schedule_delayed/cancel/tick/pause/resume/list
Cron expression parsing with compute_next_run (named aliases, step/range/list fields, interval: support)
Background tick loop via start() daemon thread
API endpoints: POST/GET /v1/schedules, GET/DELETE /v1/schedules/, POST */pause and */resume
Unit tests: tests/unit/test_cron_parser.py (186 lines)

Closing as completed.

Implemented and committed on `main` at f867983. Deliverables: - `scheduled_intents` table in ledger (schema.py + core.py + models.py) - `runtime/scheduler.py` — IntentScheduler with schedule/schedule_delayed/cancel/tick/pause/resume/list - Cron expression parsing with compute_next_run (named aliases, step/range/list fields, interval: support) - Background tick loop via start() daemon thread - API endpoints: POST/GET /v1/schedules, GET/DELETE /v1/schedules/<id>, POST */pause and */resume - Unit tests: tests/unit/test_cron_parser.py (186 lines) Closing as completed.

Mark closed this issue

2026-07-16 14:27:59 +00:00

Mark referenced this issue

2026-08-12 18:42:05 +00:00

[Phase 6] Operational Utility - Meta Issue #69

Rows
Columns

[Phase 6.7] Scheduler #76

Overview

Problem Statement

Proposed Solution

6.7.1: Schedule Table

6.7.2: Scheduler Service

6.7.3: Cron Expressions

6.7.4: API Endpoints

Deliverables

Dependencies

Estimated Duration

Success Criteria

Related