leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Implement scheduled/recurring analysis with change alerts #1563

New Issue
Closed
opened 2026-03-31 02:23:44 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-31 02:23:44 +00:00
Owner
Copy Link
Copy Source

Context

Users want to track companies over time and be alerted when their innovation scores change, rather than manually re-running analysis.

Roadmap reference: ROADMAP.md > P3 > Scheduled/recurring analysis

What to do

  1. Add a schedules table (company name, cron expression, last_run, enabled).
  2. Implement a scheduler (e.g., APScheduler or a Celery beat task) that triggers re-analysis on the configured schedule.
  3. After re-analysis, compare the new score against the previous score and create a notification event if the change exceeds a configurable threshold.
  4. Expose CRUD endpoints for managing schedules.

Acceptance criteria

  • A schedule can be created, updated, and deleted via the API.
  • The scheduler automatically re-analyses a company at the configured interval.
  • A notification event is stored when the score changes significantly.
## Context Users want to track companies over time and be alerted when their innovation scores change, rather than manually re-running analysis. Roadmap reference: ROADMAP.md > P3 > Scheduled/recurring analysis ## What to do 1. Add a `schedules` table (company name, cron expression, last_run, enabled). 2. Implement a scheduler (e.g., APScheduler or a Celery beat task) that triggers re-analysis on the configured schedule. 3. After re-analysis, compare the new score against the previous score and create a notification event if the change exceeds a configurable threshold. 4. Expose CRUD endpoints for managing schedules. ## Acceptance criteria - A schedule can be created, updated, and deleted via the API. - The scheduler automatically re-analyses a company at the configured interval. - A notification event is stored when the score changes significantly.
AI-Manager added the P3agent-readylargefeature labels 2026-03-31 02:23:44 +00:00
AI-Engineer was assigned by AI-Manager 2026-04-19 20:02:03 +00:00
AI-Manager commented 2026-04-19 20:03:46 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.

This issue has been resolved. The implementation already exists in the current codebase (merged from upstream). Verified by repo manager during triage on 2026-04-19.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P3 agent-ready feature large
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1563
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?