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

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

Context

All analysis is currently on-demand. Users tracking a company over time must manually trigger re-analysis. Scheduled analysis and change alerts would enable proactive monitoring.

Work

  • Add a scheduling mechanism (e.g., APScheduler, Celery beat, or a cron-triggered endpoint) to periodically re-analyze tracked companies.
  • Store the schedule configuration per company in the database.
  • Implement a basic change-detection heuristic (e.g., innovation score delta > threshold).
  • Trigger an alert (see webhook issue) or at minimum mark the company as "changed" in the UI.
  • Add a UI control to enable/disable scheduled analysis for a company.

Acceptance Criteria

  • A company can be configured for periodic re-analysis (e.g., daily, weekly).
  • After a scheduled run, new results appear in the dashboard.
  • Significant changes are flagged in the UI.

References

Roadmap: P3 — scheduled/recurring analysis.

## Context All analysis is currently on-demand. Users tracking a company over time must manually trigger re-analysis. Scheduled analysis and change alerts would enable proactive monitoring. ## Work - Add a scheduling mechanism (e.g., APScheduler, Celery beat, or a cron-triggered endpoint) to periodically re-analyze tracked companies. - Store the schedule configuration per company in the database. - Implement a basic change-detection heuristic (e.g., innovation score delta > threshold). - Trigger an alert (see webhook issue) or at minimum mark the company as "changed" in the UI. - Add a UI control to enable/disable scheduled analysis for a company. ## Acceptance Criteria - A company can be configured for periodic re-analysis (e.g., daily, weekly). - After a scheduled run, new results appear in the dashboard. - Significant changes are flagged in the UI. ## References Roadmap: P3 — scheduled/recurring analysis.
AI-Manager added the P3agent-readylarge labels 2026-03-26 14:24:08 +00:00
AI-Manager commented 2026-03-26 15:06:28 +00:00
Author
Owner
Copy Link
Copy Source

Resolved. Scheduled/recurring patent analysis with change alerts implemented. Implemented in PR #65 (merged). See SPARC/scheduler.py.

Resolved. Scheduled/recurring patent analysis with change alerts implemented. Implemented in PR #65 (merged). 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 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#87
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?