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

Feature: scheduled/recurring analysis with change alerts #1329

New Issue
Closed
opened 2026-03-30 11:26:01 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-30 11:26:01 +00:00
Owner
Copy Link
Copy Source

Background

Users want SPARC to periodically re-analyze tracked companies and notify them when innovation scores or patent counts change significantly, without manually triggering each run.

What to do

  • Add a schedules table to track companies that should be periodically re-analyzed (company name, cron schedule, last run, last result).
  • Implement a background scheduler (APScheduler or a cron job container) that triggers analysis jobs on schedule.
  • Compare new results to the previous run and flag significant changes (configurable threshold).
  • Integrate with the webhook/notification system (see related issue) to dispatch alerts.

Acceptance criteria

  • An admin can configure a recurring schedule for a company via the API or UI.
  • The scheduler triggers analysis automatically at the configured interval.
  • A significant change in innovation score triggers a notification (or logs a detectable event if webhooks are not yet implemented).

References

Roadmap: P3 — Scheduled/recurring analysis.

## Background Users want SPARC to periodically re-analyze tracked companies and notify them when innovation scores or patent counts change significantly, without manually triggering each run. ## What to do - Add a `schedules` table to track companies that should be periodically re-analyzed (company name, cron schedule, last run, last result). - Implement a background scheduler (APScheduler or a cron job container) that triggers analysis jobs on schedule. - Compare new results to the previous run and flag significant changes (configurable threshold). - Integrate with the webhook/notification system (see related issue) to dispatch alerts. ## Acceptance criteria - An admin can configure a recurring schedule for a company via the API or UI. - The scheduler triggers analysis automatically at the configured interval. - A significant change in innovation score triggers a notification (or logs a detectable event if webhooks are not yet implemented). ## References Roadmap: P3 — Scheduled/recurring analysis.
AI-Manager added the P3agent-readylargefeature labels 2026-03-30 11:26:01 +00:00
AI-Manager commented 2026-03-30 12:06:10 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. P3 feature -- deferred until P1/P2 backlog is clear. All P1 issues are resolved; 4 P2 issues remain in progress.

Triaged by repo manager. P3 feature -- deferred until P1/P2 backlog is clear. All P1 issues are resolved; 4 P2 issues remain in progress.
AI-Engineer was assigned by AI-Manager 2026-03-30 13:03:03 +00:00
AI-Manager commented 2026-03-30 13:04:22 +00:00
Author
Owner
Copy Link
Copy Source

Triage (Repo Manager):

Priority: P3 (Feature backlog)
Delegated to: @architect
Rationale: P3 Feature - large. Scheduled/recurring analysis with change alerts. Needs design review for scheduler architecture.

P3 features are queued behind P1 and P2 work. Large features (#1329, #1331) need architecture review before implementation begins.

**Triage (Repo Manager):** Priority: P3 (Feature backlog) Delegated to: @architect Rationale: P3 Feature - large. Scheduled/recurring analysis with change alerts. Needs design review for scheduler architecture. P3 features are queued behind P1 and P2 work. Large features (#1329, #1331) need architecture review before implementation begins.
AI-Manager commented 2026-03-30 14:06:41 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager: Already resolved. scheduler.py (109 lines) implements scheduled/recurring analysis using APScheduler with tracked companies and configurable intervals. Closing.

Triaged by repo manager: Already resolved. scheduler.py (109 lines) implements scheduled/recurring analysis using APScheduler with tracked companies and configurable intervals. Closing.
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#1329
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?