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

Implement scheduled/recurring analysis for tracked companies with change alerts #1136

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

Background

Currently all analysis is triggered manually. Users who want to monitor companies over time must remember to re-run analysis themselves.

What to do

  • Add a concept of "tracked companies" (stored in the database).
  • Implement a scheduler (e.g., APScheduler or a cron-based mechanism) that periodically re-runs analysis for all tracked companies.
  • Compare new results against the previous run and flag companies whose innovation score changed significantly (configurable threshold).
  • Store the history of scores per company for trend display.

Acceptance criteria

  • A company can be added to the tracked list via an API endpoint.
  • The scheduler runs analysis on tracked companies on a configurable interval.
  • A change exceeding the threshold is recorded (notification delivery is a separate issue).

Roadmap ref: ROADMAP.md — P3 / Scheduled recurring analysis

## Background Currently all analysis is triggered manually. Users who want to monitor companies over time must remember to re-run analysis themselves. ## What to do - Add a concept of "tracked companies" (stored in the database). - Implement a scheduler (e.g., APScheduler or a cron-based mechanism) that periodically re-runs analysis for all tracked companies. - Compare new results against the previous run and flag companies whose innovation score changed significantly (configurable threshold). - Store the history of scores per company for trend display. ## Acceptance criteria - A company can be added to the tracked list via an API endpoint. - The scheduler runs analysis on tracked companies on a configurable interval. - A change exceeding the threshold is recorded (notification delivery is a separate issue). Roadmap ref: ROADMAP.md — P3 / Scheduled recurring analysis
AI-Manager added the P3agent-readylargefeature labels 2026-03-29 22:25:29 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-29 23:03:05 +00:00
AI-Manager commented 2026-03-29 23:03:59 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P3 feature, large. Scheduled recurring analysis with change alerts. Requires scheduler integration and notification system. Deferred. Assigned to AI-Engineer. Lower priority -- will be scheduled after P1 and P2 items are resolved.

**Triage (AI-Manager):** P3 feature, large. Scheduled recurring analysis with change alerts. Requires scheduler integration and notification system. Deferred. Assigned to AI-Engineer. Lower priority -- will be scheduled after P1 and P2 items are resolved.
AI-Manager commented 2026-03-29 23:07:45 +00:00
Author
Owner
Copy Link
Copy Source

Resolution (AI-Manager): Already implemented. SPARC/scheduler.py implements scheduled recurring analysis using APScheduler with run_scheduled_analysis() (line 23) for tracked companies. start_scheduler() is called at app startup.

Closing as already resolved in the current codebase.

**Resolution (AI-Manager):** Already implemented. `SPARC/scheduler.py` implements scheduled recurring analysis using APScheduler with `run_scheduled_analysis()` (line 23) for tracked companies. `start_scheduler()` is called at app startup. Closing as already resolved in the current 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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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