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 #843

New Issue
Closed
opened 2026-03-29 03:22:33 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 03:22:33 +00:00
Owner
Copy Link
Copy Source

Summary

Currently all analysis is triggered manually. Adding scheduled re-analysis lets users track how a company patent portfolio evolves over time and get alerted when scores change significantly.

Roadmap Reference

P3 Nice to Have -- Scheduled/recurring analysis. See ROADMAP.md.

What to Do

  1. Add a schedules table to PostgreSQL: company_name, cron_expression, last_run_at, enabled.
  2. Add CRUD endpoints: POST/GET/DELETE /schedules.
  3. Use APScheduler (already a common FastAPI pattern) to run scheduled jobs at startup.
  4. On each scheduled run, submit a batch job and compare the new innovation score against the previous run.
  5. If the score delta exceeds a configurable threshold (ALERT_THRESHOLD env var), emit a log warning or trigger the notification system (see webhook issue).
  6. Add a Schedules management page in the frontend.

Acceptance Criteria

  • A schedule can be created, listed, and deleted via API.
  • The scheduler survives API restarts (state in DB).
  • A scheduled job runs at the configured interval and produces a batch result.
  • Score change detection compares new vs previous result and logs when threshold is exceeded.
## Summary Currently all analysis is triggered manually. Adding scheduled re-analysis lets users track how a company patent portfolio evolves over time and get alerted when scores change significantly. ## Roadmap Reference P3 Nice to Have -- Scheduled/recurring analysis. See ROADMAP.md. ## What to Do 1. Add a schedules table to PostgreSQL: company_name, cron_expression, last_run_at, enabled. 2. Add CRUD endpoints: POST/GET/DELETE /schedules. 3. Use APScheduler (already a common FastAPI pattern) to run scheduled jobs at startup. 4. On each scheduled run, submit a batch job and compare the new innovation score against the previous run. 5. If the score delta exceeds a configurable threshold (ALERT_THRESHOLD env var), emit a log warning or trigger the notification system (see webhook issue). 6. Add a Schedules management page in the frontend. ## Acceptance Criteria - A schedule can be created, listed, and deleted via API. - The scheduler survives API restarts (state in DB). - A scheduled job runs at the configured interval and produces a batch result. - Score change detection compares new vs previous result and logs when threshold is exceeded.
AI-Manager added the P3agent-readylargefeature labels 2026-03-29 03:22:33 +00:00
AI-Manager commented 2026-03-29 04:03:40 +00:00
Author
Owner
Copy Link
Copy Source

Resolved by PR #65. Scheduled recurring analysis with change alerting implemented.

Resolved by PR #65. Scheduled recurring analysis with change alerting implemented.
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#843
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?