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

Implement scheduled/recurring analysis with change alerting #1514

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

Context

Roadmap item: P3 — Scheduled/recurring analysis

Allows operators to periodically re-analyse tracked companies and receive alerts when significant changes are detected.

What to do

  1. Add a schedules table: company_name, cron_expression, last_run_at, notify_webhook.
  2. Integrate a scheduler (APScheduler or Celery Beat) to trigger analyses on schedule.
  3. After each run, compare the new innovation score against the previous one; if the delta exceeds a configurable threshold, trigger the notification webhook.
  4. Expose CRUD endpoints for managing schedules.
  5. Document the scheduler setup in README.

Acceptance criteria

  • Schedules are stored in the database
  • Analyses run automatically on schedule
  • Significant score changes trigger a notification
  • CRUD endpoints for schedules are protected by authentication
## Context Roadmap item: P3 — Scheduled/recurring analysis Allows operators to periodically re-analyse tracked companies and receive alerts when significant changes are detected. ## What to do 1. Add a `schedules` table: `company_name`, `cron_expression`, `last_run_at`, `notify_webhook`. 2. Integrate a scheduler (APScheduler or Celery Beat) to trigger analyses on schedule. 3. After each run, compare the new innovation score against the previous one; if the delta exceeds a configurable threshold, trigger the notification webhook. 4. Expose CRUD endpoints for managing schedules. 5. Document the scheduler setup in README. ## Acceptance criteria - [ ] Schedules are stored in the database - [ ] Analyses run automatically on schedule - [ ] Significant score changes trigger a notification - [ ] CRUD endpoints for schedules are protected by authentication
AI-Manager added the P3agent-readylargefeature labels 2026-03-31 00:25:18 +00:00
AI-Manager commented 2026-03-31 01:04:22 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue is already resolved. SPARC/scheduler.py implements scheduled analysis using APScheduler with configurable interval (SCHEDULE_INTERVAL_HOURS), tracked companies, and change alerting (CHANGE_THRESHOLD_PERCENT). Admin endpoints for managing tracked companies and viewing alerts exist in api.py. Closing as complete.

[Repo Manager] This issue is already resolved. `SPARC/scheduler.py` implements scheduled analysis using APScheduler with configurable interval (`SCHEDULE_INTERVAL_HOURS`), tracked companies, and change alerting (`CHANGE_THRESHOLD_PERCENT`). Admin endpoints for managing tracked companies and viewing alerts exist in `api.py`. Closing as complete.
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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