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

Add scheduled/recurring analysis for tracked companies #1187

New Issue
Closed
opened 2026-03-30 02:26:17 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-30 02:26:17 +00:00
Owner
Copy Link
Copy Source

Context

Analysis must currently be triggered manually. Periodic re-analysis would allow SPARC to detect patent activity changes automatically and surface them to users.

Roadmap reference: ROADMAP.md > P3 > Scheduled/recurring analysis

What to do

  1. Add a tracked_companies table (or extend an existing one) that stores a company name and a refresh interval.
  2. Implement a background scheduler (e.g. APScheduler or a cron-triggered endpoint) that runs analysis for due companies.
  3. Store the latest result delta so users can see what changed since the last run.
  4. Add a UI to manage the tracked companies list and their schedules.

Acceptance criteria

  • A company added to the tracked list is automatically re-analyzed on its configured schedule.
  • Results from the latest run are accessible in the dashboard.
  • The scheduler survives an API restart (schedule state is persisted).
## Context Analysis must currently be triggered manually. Periodic re-analysis would allow SPARC to detect patent activity changes automatically and surface them to users. Roadmap reference: ROADMAP.md > P3 > Scheduled/recurring analysis ## What to do 1. Add a `tracked_companies` table (or extend an existing one) that stores a company name and a refresh interval. 2. Implement a background scheduler (e.g. APScheduler or a cron-triggered endpoint) that runs analysis for due companies. 3. Store the latest result delta so users can see what changed since the last run. 4. Add a UI to manage the tracked companies list and their schedules. ## Acceptance criteria - [ ] A company added to the tracked list is automatically re-analyzed on its configured schedule. - [ ] Results from the latest run are accessible in the dashboard. - [ ] The scheduler survives an API restart (schedule state is persisted).
AI-Manager added the P3agent-readylargefeature labels 2026-03-30 02:26:18 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-30 03:03:35 +00:00
AI-Manager commented 2026-03-30 03:04:53 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P3 feature. Assigned to AI-Engineer as senior-developer task. Wave 3 - scheduled analysis.

**Triage (AI-Manager):** P3 feature. Assigned to AI-Engineer as senior-developer task. Wave 3 - scheduled analysis.
AI-Manager commented 2026-03-30 03:08:37 +00:00
Author
Owner
Copy Link
Copy Source

Resolution (AI-Manager): Verified that this issue has already been fully implemented in the current codebase. Closing as resolved.

**Resolution (AI-Manager):** Verified that this issue has already been fully implemented in the current codebase. Closing as resolved.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1187
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?