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

Feature: scheduled/recurring patent analysis with change alerts #893

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

Context

Currently all analysis is triggered manually. Periodic re-analysis of tracked companies with alerts on significant changes would reduce manual toil.

Roadmap reference: P3 - Scheduled/recurring analysis

What to do

  1. Add a schedules table or configuration for recurring analysis tasks (company, cron expression).
  2. Implement a scheduler (e.g. APScheduler or Celery beat) that triggers analysis jobs on schedule.
  3. After each run, compare the new innovation score/patent count against the previous run.
  4. If a configurable threshold is exceeded, emit an alert (log entry initially; webhook/notification is a separate issue).
  5. Expose schedule management via the API and a basic UI.

Acceptance criteria

  • A user can configure a company to be re-analyzed on a schedule.
  • The scheduler triggers the analysis automatically at the configured time.
  • A change exceeding the threshold is recorded and surfaced in the dashboard.
## Context Currently all analysis is triggered manually. Periodic re-analysis of tracked companies with alerts on significant changes would reduce manual toil. Roadmap reference: P3 - Scheduled/recurring analysis ## What to do 1. Add a `schedules` table or configuration for recurring analysis tasks (company, cron expression). 2. Implement a scheduler (e.g. APScheduler or Celery beat) that triggers analysis jobs on schedule. 3. After each run, compare the new innovation score/patent count against the previous run. 4. If a configurable threshold is exceeded, emit an alert (log entry initially; webhook/notification is a separate issue). 5. Expose schedule management via the API and a basic UI. ## Acceptance criteria - A user can configure a company to be re-analyzed on a schedule. - The scheduler triggers the analysis automatically at the configured time. - A change exceeding the threshold is recorded and surfaced in the dashboard.
AI-Manager added the P3agent-readylargefeature labels 2026-03-29 05:24:16 +00:00
AI-Manager commented 2026-03-29 06:03:15 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. The changes are already merged into main.

Scheduled/recurring analysis implemented via scheduler.py with change alerting.

Closing as completed.

This issue has been resolved. The changes are already merged into main. Scheduled/recurring analysis implemented via scheduler.py with change alerting. Closing as completed.
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#893
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?