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

Scheduled/recurring analysis with alerts on significant changes #631

New Issue
Closed
opened 2026-03-28 11:23:35 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 11:23:35 +00:00
Owner
Copy Link
Copy Source

Context

Currently analyses are triggered manually. Operators have no way to track how a company's patent activity evolves over time without re-running analyses by hand.

Roadmap item: P3 > Scheduled/recurring analysis

What to do

  • Add a schedules table to track (company, cron expression, last run, enabled).
  • Implement a background scheduler (APScheduler or Celery Beat) that triggers batch analysis on schedule.
  • Store a diff between the latest and previous run; if key metrics change by more than a configurable threshold, emit an alert event.
  • Alert delivery can be a webhook (see related webhook issue) or a simple database flag for now.

Acceptance criteria

  • A schedule can be created via POST /schedules with a company and cron expression.
  • The scheduler automatically re-analyzes the company at the configured interval.
  • A change exceeding the threshold is recorded and visible in the dashboard.
## Context Currently analyses are triggered manually. Operators have no way to track how a company's patent activity evolves over time without re-running analyses by hand. Roadmap item: P3 > Scheduled/recurring analysis ## What to do - Add a `schedules` table to track (company, cron expression, last run, enabled). - Implement a background scheduler (APScheduler or Celery Beat) that triggers batch analysis on schedule. - Store a diff between the latest and previous run; if key metrics change by more than a configurable threshold, emit an alert event. - Alert delivery can be a webhook (see related webhook issue) or a simple database flag for now. ## Acceptance criteria - [ ] A schedule can be created via `POST /schedules` with a company and cron expression. - [ ] The scheduler automatically re-analyzes the company at the configured interval. - [ ] A change exceeding the threshold is recorded and visible in the dashboard.
AI-Manager added the P3agent-readylargefeature labels 2026-03-28 11:23:35 +00:00
AI-Manager commented 2026-03-28 12:04:52 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. SPARC/scheduler.py is imported and started in api.py lifespan. The API includes an /alerts endpoint for scheduled analysis results.

Closing: already implemented on main. `SPARC/scheduler.py` is imported and started in `api.py` lifespan. The API includes an `/alerts` endpoint for scheduled analysis results.
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#631
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?