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

Implement scheduled/recurring patent analysis with change alerts #655

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

Context

Roadmap item: P3 — Scheduled/Recurring Analysis

Users want to track companies over time without manually triggering re-analysis. Automated periodic re-analysis and alerts on significant changes would enable proactive monitoring.

What to do

  • Add a tracked_companies table (company name, analysis frequency, last analyzed)
  • Implement a scheduler (e.g. APScheduler, Celery Beat, or a simple cron job inside the container) that triggers re-analysis on the configured interval
  • Compare new analysis results to the previous run and flag significant changes (e.g. innovation score delta > threshold)
  • Integrate with the notification/webhook system (see related issue for webhooks) or at minimum store the change event in the database for display in the UI

Acceptance criteria

  • A company can be marked for recurring analysis with a configurable interval
  • The scheduler automatically re-runs analysis without user intervention
  • Significant changes are recorded and visible in the UI or logs
## Context Roadmap item: P3 — Scheduled/Recurring Analysis Users want to track companies over time without manually triggering re-analysis. Automated periodic re-analysis and alerts on significant changes would enable proactive monitoring. ## What to do - Add a `tracked_companies` table (company name, analysis frequency, last analyzed) - Implement a scheduler (e.g. APScheduler, Celery Beat, or a simple cron job inside the container) that triggers re-analysis on the configured interval - Compare new analysis results to the previous run and flag significant changes (e.g. innovation score delta > threshold) - Integrate with the notification/webhook system (see related issue for webhooks) or at minimum store the change event in the database for display in the UI ## Acceptance criteria - A company can be marked for recurring analysis with a configurable interval - The scheduler automatically re-runs analysis without user intervention - Significant changes are recorded and visible in the UI or logs
AI-Manager added the P3agent-readylargefeature labels 2026-03-28 12:24:16 +00:00
AI-Manager commented 2026-03-28 13:03:38 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. Scheduled/recurring patent analysis with change alerts was added in PR #65 (feat: implement scheduled/recurring analysis with change alerting). SPARC/scheduler.py handles the scheduling logic.

Closing as already implemented. Scheduled/recurring patent analysis with change alerts was added in PR #65 (`feat: implement scheduled/recurring analysis with change alerting`). `SPARC/scheduler.py` handles the scheduling logic.
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#655
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?