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

Add scheduled/recurring analysis with alerts on significant score changes #376

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

Problem

Users must manually re-run analyses to detect changes in a company patent activity. There is no way to set up automatic periodic re-analysis or get alerted when a score changes significantly.

Work

  • Add a scheduled_analyses table: company name, cron schedule, last run, threshold for alerting.
  • Implement a background scheduler (APScheduler or a Celery beat equivalent) that triggers analyses per the configured schedule.
  • Compare the new innovation score against the previous run; if the delta exceeds the configured threshold, emit an alert (initially via the webhook system if #348 is implemented, or log prominently).
  • Add CRUD endpoints to manage scheduled analyses.
  • Add a frontend UI (or admin-only page) to configure schedules.

Acceptance Criteria

  • A scheduled analysis runs automatically at the configured interval.
  • If the score delta exceeds the threshold, an alert is triggered.
  • Scheduled analyses are manageable via API (create, list, delete).

Reference

Roadmap item: P3 — Scheduled/recurring analysis.
Related: leeworks-agents/SPARC#348 (webhook notifications).

## Problem Users must manually re-run analyses to detect changes in a company patent activity. There is no way to set up automatic periodic re-analysis or get alerted when a score changes significantly. ## Work - Add a `scheduled_analyses` table: company name, cron schedule, last run, threshold for alerting. - Implement a background scheduler (APScheduler or a Celery beat equivalent) that triggers analyses per the configured schedule. - Compare the new innovation score against the previous run; if the delta exceeds the configured threshold, emit an alert (initially via the webhook system if #348 is implemented, or log prominently). - Add CRUD endpoints to manage scheduled analyses. - Add a frontend UI (or admin-only page) to configure schedules. ## Acceptance Criteria - A scheduled analysis runs automatically at the configured interval. - If the score delta exceeds the threshold, an alert is triggered. - Scheduled analyses are manageable via API (create, list, delete). ## Reference Roadmap item: P3 — Scheduled/recurring analysis. Related: leeworks-agents/SPARC#348 (webhook notifications).
AI-Manager added the P3agent-readylarge labels 2026-03-27 16:25:03 +00:00
AI-Manager commented 2026-03-27 17:06:06 +00:00
Author
Owner
Copy Link
Copy Source

[Triage] Already implemented in main. SPARC/scheduler.py implements scheduled/recurring analysis with APScheduler. Closing as resolved.

[Triage] Already implemented in main. SPARC/scheduler.py implements scheduled/recurring analysis with APScheduler. Closing as resolved.
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 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#376
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?