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

Add scheduled/recurring analysis with change alerting #703

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

Context

Roadmap item: P3 - Scheduled/recurring analysis

Analysis runs are currently one-shot. Users must manually re-run to detect new patents or changes in innovation scores.

Work to do

  • Add a schedules table to PostgreSQL: company, cron expression, last_run_at, next_run_at
  • Implement a background scheduler (e.g. APScheduler or a Celery beat task) that triggers analysis jobs on schedule
  • Compare new results to the previous run; if the innovation score changes by more than a configurable threshold, flag the result
  • Expose CRUD endpoints for managing schedules
  • Add a basic schedules management UI in the dashboard

Acceptance criteria

  • A schedule can be created via the API or UI specifying a company and recurrence interval
  • The scheduler runs the analysis at the configured time
  • If the score changes significantly, the job result is flagged; a future notification step can pick up flagged results
## Context Roadmap item: P3 - Scheduled/recurring analysis Analysis runs are currently one-shot. Users must manually re-run to detect new patents or changes in innovation scores. ## Work to do - Add a `schedules` table to PostgreSQL: company, cron expression, last_run_at, next_run_at - Implement a background scheduler (e.g. APScheduler or a Celery beat task) that triggers analysis jobs on schedule - Compare new results to the previous run; if the innovation score changes by more than a configurable threshold, flag the result - Expose CRUD endpoints for managing schedules - Add a basic schedules management UI in the dashboard ## Acceptance criteria - A schedule can be created via the API or UI specifying a company and recurrence interval - The scheduler runs the analysis at the configured time - If the score changes significantly, the job result is flagged; a future notification step can pick up flagged results
AI-Manager added the P3agent-readylargefeature labels 2026-03-28 15:24:03 +00:00
AI-Manager commented 2026-03-28 16:04:23 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Scheduled/recurring analysis with change alerting was added in PR #65 (feature/scheduled-analysis). See SPARC/scheduler.py.

Closing as already implemented. Scheduled/recurring analysis with change alerting was added in PR #65 (feature/scheduled-analysis). See SPARC/scheduler.py.
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#703
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?