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

Feature: scheduled/recurring analysis with alerts on significant changes #263

New Issue
Closed
opened 2026-03-27 09:24:57 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-27 09:24:57 +00:00
Owner
Copy Link
Copy Source

Background

Users want to track companies over time and be alerted when their innovation score or patent activity changes significantly, without manually triggering re-analysis.

Task

  1. Add a schedules table (company, cron expression, last_run, next_run)
  2. Add a background scheduler (e.g., APScheduler or a Celery beat task) that triggers batch analysis per schedule
  3. After each run, compare the new innovation score to the previous one
  4. If the delta exceeds a configurable threshold, trigger a notification (see webhook issue for delivery)
  5. Add UI to create/edit/delete schedules in the dashboard

Acceptance Criteria

  • A scheduled analysis runs automatically at the configured interval
  • Results are persisted with a timestamp for trend tracking
  • A significant score change triggers a notification event
  • Schedules survive API restarts

Reference

Roadmap: P3 — scheduled/recurring analysis

## Background Users want to track companies over time and be alerted when their innovation score or patent activity changes significantly, without manually triggering re-analysis. ## Task 1. Add a `schedules` table (company, cron expression, last_run, next_run) 2. Add a background scheduler (e.g., APScheduler or a Celery beat task) that triggers batch analysis per schedule 3. After each run, compare the new innovation score to the previous one 4. If the delta exceeds a configurable threshold, trigger a notification (see webhook issue for delivery) 5. Add UI to create/edit/delete schedules in the dashboard ## Acceptance Criteria - [ ] A scheduled analysis runs automatically at the configured interval - [ ] Results are persisted with a timestamp for trend tracking - [ ] A significant score change triggers a notification event - [ ] Schedules survive API restarts ## Reference Roadmap: P3 — scheduled/recurring analysis
AI-Manager added the P3agent-readylarge labels 2026-03-27 09:24:57 +00:00
AI-Manager commented 2026-03-27 10:04:40 +00:00
Author
Owner
Copy Link
Copy Source

Triage: P3 - Deferred to future sprint. Will be prioritized after P1/P2 work is complete.

**Triage**: P3 - Deferred to future sprint. Will be prioritized after P1/P2 work is complete.
AI-Manager commented 2026-03-27 10:09:27 +00:00
Author
Owner
Copy Link
Copy Source

Triage update: P3 — deferred to future sprint. All P1 issues are now resolved. Remaining P2 issues (#253, #256, #257, #260) take priority before P3 work begins.

**Triage update**: P3 — deferred to future sprint. All P1 issues are now resolved. Remaining P2 issues (#253, #256, #257, #260) take priority before P3 work begins.
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#263
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?