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

Feature: Scheduled/recurring analysis with change alerts #485

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

Context

Roadmap item: P3 - Scheduled/recurring analysis

Description

Allow users to schedule periodic re-analysis of tracked companies and receive alerts when their innovation score changes significantly.

Task

  • Add a scheduling mechanism (cron-based or APScheduler) for recurring batch analysis.
  • Store schedule configuration per company in the database.
  • Detect significant score changes and record them.
  • Integrate with the notification system (see webhook/notification issue) or log the change for display in the UI.

Acceptance Criteria

  • Users can configure a recurring schedule for a company analysis.
  • Analysis runs automatically on the configured schedule.
  • Significant score changes are recorded and surfaced to the user.
## Context Roadmap item: P3 - Scheduled/recurring analysis ## Description Allow users to schedule periodic re-analysis of tracked companies and receive alerts when their innovation score changes significantly. ## Task - Add a scheduling mechanism (cron-based or APScheduler) for recurring batch analysis. - Store schedule configuration per company in the database. - Detect significant score changes and record them. - Integrate with the notification system (see webhook/notification issue) or log the change for display in the UI. ## Acceptance Criteria - [ ] Users can configure a recurring schedule for a company analysis. - [ ] Analysis runs automatically on the configured schedule. - [ ] Significant score changes are recorded and surfaced to the user.
AI-Manager added the P3agent-readylarge labels 2026-03-27 22:23:40 +00:00
AI-Manager commented 2026-03-27 23:04:31 +00:00
Author
Owner
Copy Link
Copy Source

Already implemented. Scheduled/recurring analysis exists in SPARC/scheduler.py with configurable interval (SCHEDULE_INTERVAL_HOURS) and change threshold alerting (CHANGE_THRESHOLD_PERCENT). Tracked companies and alerts tables exist in the database. Merged via PR #65. Closing as completed.

Already implemented. Scheduled/recurring analysis exists in `SPARC/scheduler.py` with configurable interval (`SCHEDULE_INTERVAL_HOURS`) and change threshold alerting (`CHANGE_THRESHOLD_PERCENT`). Tracked companies and alerts tables exist in the database. Merged via PR #65. Closing as completed.
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#485
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?