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

Feature: Scheduled/recurring analysis with alerting on significant changes #728

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

Summary

Currently all analysis is triggered manually. Adding scheduled re-analysis of tracked companies would surface changes automatically.

What to do

  • Add a concept of "tracked companies" that users can subscribe to.
  • Implement a scheduler (e.g. APScheduler, Celery Beat, or a cron job) that re-runs analysis on a configurable interval.
  • Compare new results to the previous analysis and flag significant changes (e.g. innovation score delta > threshold).
  • Integrate with the notification system (see webhook issue) to deliver alerts.

Acceptance Criteria

  • A user can mark a company for recurring analysis.
  • The scheduler re-runs analysis at the configured interval without manual intervention.
  • Significant changes are detected and recorded.
  • Alerts are sent when changes exceed the configured threshold.

Reference

Roadmap: P3 — Scheduled/recurring analysis.

## Summary Currently all analysis is triggered manually. Adding scheduled re-analysis of tracked companies would surface changes automatically. ## What to do - Add a concept of "tracked companies" that users can subscribe to. - Implement a scheduler (e.g. APScheduler, Celery Beat, or a cron job) that re-runs analysis on a configurable interval. - Compare new results to the previous analysis and flag significant changes (e.g. innovation score delta > threshold). - Integrate with the notification system (see webhook issue) to deliver alerts. ## Acceptance Criteria - [ ] A user can mark a company for recurring analysis. - [ ] The scheduler re-runs analysis at the configured interval without manual intervention. - [ ] Significant changes are detected and recorded. - [ ] Alerts are sent when changes exceed the configured threshold. ## Reference Roadmap: P3 — Scheduled/recurring analysis.
AI-Manager added the P3agent-readylargefeature labels 2026-03-28 16:24:32 +00:00
AI-Manager commented 2026-03-28 17:06:09 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Already resolved. SPARC/scheduler.py uses APScheduler for recurring analysis with alerting.

Closing as already implemented in the codebase.

[Repo Manager] Already resolved. SPARC/scheduler.py uses APScheduler for recurring analysis with alerting. Closing as already implemented in the codebase.
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#728
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?