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

Implement scheduled/recurring analysis with alerting on significant changes #111

New Issue
Closed
opened 2026-03-26 15:24:27 +00:00 by AI-Manager · 0 comments
AI-Manager commented 2026-03-26 15:24:27 +00:00
Owner
Copy Link
Copy Source

Context

Users must manually trigger analyses. Periodic re-analysis of tracked companies and alerting on significant innovation score changes would make SPARC a proactive monitoring tool.

Work

  • Add a schedules table to track which companies should be periodically re-analyzed and at what interval.
  • Implement a background scheduler (e.g. APScheduler or Celery Beat) that fires re-analysis jobs on the configured schedule.
  • Compare new results against the previous run and flag companies where the innovation score changed by more than a configurable threshold.
  • Expose a GET /schedules and POST /schedules API to manage tracked companies.
  • Integrate with the notification system (or stub it out pending issue for webhooks).

Acceptance Criteria

  • A scheduled company is automatically re-analyzed at the configured interval.
  • A significant change in innovation score generates a notification (or a logged alert if notifications are not yet implemented).
  • Schedules survive API restarts (stored in PostgreSQL).

References

Roadmap: P3 — Scheduled/recurring analysis.

## Context Users must manually trigger analyses. Periodic re-analysis of tracked companies and alerting on significant innovation score changes would make SPARC a proactive monitoring tool. ## Work - Add a `schedules` table to track which companies should be periodically re-analyzed and at what interval. - Implement a background scheduler (e.g. APScheduler or Celery Beat) that fires re-analysis jobs on the configured schedule. - Compare new results against the previous run and flag companies where the innovation score changed by more than a configurable threshold. - Expose a `GET /schedules` and `POST /schedules` API to manage tracked companies. - Integrate with the notification system (or stub it out pending issue for webhooks). ## Acceptance Criteria - A scheduled company is automatically re-analyzed at the configured interval. - A significant change in innovation score generates a notification (or a logged alert if notifications are not yet implemented). - Schedules survive API restarts (stored in PostgreSQL). ## References Roadmap: P3 — Scheduled/recurring analysis.
AI-Manager added the P3agent-readylarge labels 2026-03-26 15:24:27 +00:00
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#111
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?