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

Implement scheduled/recurring analysis with change alerting #1393

New Issue
Closed
opened 2026-03-30 17:26:23 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 17:26:23 +00:00
Owner
Copy Link
Copy Source

Background

Roadmap item: P3 -- Scheduled/recurring analysis

Currently analysis is only triggered manually. Supporting a recurring schedule lets users track changes in a company's patent activity over time without manual intervention.

Task

  1. Add a schedule configuration to tracked companies (e.g., daily/weekly cron expression stored in the DB).
  2. Add a background scheduler (e.g., APScheduler or a cron job container) that triggers analysis on the schedule.
  3. Record a snapshot of each run's results for trend comparison.
  4. Optionally send a notification when an innovation score changes by more than a configurable threshold.

Acceptance Criteria

  • A company can be configured with a recurring analysis schedule.
  • The scheduler triggers analysis automatically at the configured interval.
  • Historical snapshots are stored and queryable via the API.
  • Alerting threshold is configurable per company.

Reference

See ROADMAP.md section P3.

## Background Roadmap item: **P3 -- Scheduled/recurring analysis** Currently analysis is only triggered manually. Supporting a recurring schedule lets users track changes in a company's patent activity over time without manual intervention. ## Task 1. Add a schedule configuration to tracked companies (e.g., daily/weekly cron expression stored in the DB). 2. Add a background scheduler (e.g., APScheduler or a cron job container) that triggers analysis on the schedule. 3. Record a snapshot of each run's results for trend comparison. 4. Optionally send a notification when an innovation score changes by more than a configurable threshold. ## Acceptance Criteria - [ ] A company can be configured with a recurring analysis schedule. - [ ] The scheduler triggers analysis automatically at the configured interval. - [ ] Historical snapshots are stored and queryable via the API. - [ ] Alerting threshold is configurable per company. ## Reference See ROADMAP.md section P3.
AI-Manager added the P3agent-readylargefeature labels 2026-03-30 17:26:23 +00:00
AI-Manager commented 2026-03-30 18:05:30 +00:00
Author
Owner
Copy Link
Copy Source

Resolved by PR #65 (merged). Scheduled/recurring analysis with change alerting is implemented via the scheduler.py module and admin alert endpoints.

Resolved by PR #65 (merged). Scheduled/recurring analysis with change alerting is implemented via the `scheduler.py` module and admin alert endpoints.
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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