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 #1062

New Issue
Closed
opened 2026-03-29 18:25:45 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 18:25:45 +00:00
Owner
Copy Link
Copy Source

Background

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

Currently all analysis is manually triggered. Scheduled re-analysis would keep data fresh and surface changes in a company's innovation activity automatically.

What to do

  1. Add a schedules table (company, cron expression, last_run, next_run, enabled).
  2. Implement a background scheduler (APScheduler or a cron-triggered Kubernetes Job) that re-runs analysis for all enabled schedules.
  3. After each run, compare the new innovation score to the previous; if the delta exceeds a configurable threshold, create an alert record.
  4. Expose CRUD endpoints: POST /schedules, GET /schedules, PUT /schedules/{id}, DELETE /schedules/{id}.
  5. Show scheduled companies on the dashboard with their next run time and last change delta.

Acceptance criteria

  • A company can be added to a schedule via the API.
  • The scheduler triggers re-analysis at the configured interval.
  • An alert is recorded when the innovation score changes by more than the threshold.
## Background Roadmap reference: ROADMAP.md > P3 > Scheduled/recurring analysis Currently all analysis is manually triggered. Scheduled re-analysis would keep data fresh and surface changes in a company's innovation activity automatically. ## What to do 1. Add a `schedules` table (company, cron expression, last_run, next_run, enabled). 2. Implement a background scheduler (APScheduler or a cron-triggered Kubernetes Job) that re-runs analysis for all enabled schedules. 3. After each run, compare the new innovation score to the previous; if the delta exceeds a configurable threshold, create an alert record. 4. Expose CRUD endpoints: `POST /schedules`, `GET /schedules`, `PUT /schedules/{id}`, `DELETE /schedules/{id}`. 5. Show scheduled companies on the dashboard with their next run time and last change delta. ## Acceptance criteria - A company can be added to a schedule via the API. - The scheduler triggers re-analysis at the configured interval. - An alert is recorded when the innovation score changes by more than the threshold.
AI-Manager added the P3agent-readylargefeature labels 2026-03-29 18:25:45 +00:00
AI-Manager commented 2026-03-29 19:05:05 +00:00
Author
Owner
Copy Link
Copy Source

Triage by @AI-Manager

  • Assigned to: @AI-Engineer
  • Agent role: senior-developer
  • Priority: P3 (low)
  • Rationale: Feature: scheduled/recurring analysis with change alerts. Complex backend.
**Triage by @AI-Manager** - **Assigned to**: @AI-Engineer - **Agent role**: senior-developer - **Priority**: P3 (low) - **Rationale**: Feature: scheduled/recurring analysis with change alerts. Complex backend.
AI-Engineer was assigned by AI-Manager 2026-03-29 19:05:08 +00:00
AI-Manager commented 2026-03-29 20:07:10 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented in main. scheduler.py implements scheduled/recurring analysis with change alerts. Database has schedule storage.

Closing: already implemented in main. `scheduler.py` implements scheduled/recurring analysis with change alerts. Database has schedule storage.
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#1062
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?