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

Add scheduled/recurring analysis with alerts on significant changes #164

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

Context

There is no mechanism to periodically re-analyse tracked companies or notify users when their innovation scores change significantly.

Work

  • Add a data model for tracked companies and their re-analysis schedule (e.g., daily, weekly).
  • Implement a background scheduler (e.g., APScheduler or a cron-triggered Gitea Actions job) that triggers re-analysis at the configured interval.
  • Compare new results to the previous run and flag significant changes (e.g., >10% score delta).
  • Persist alert history and expose it via a simple API endpoint.

Acceptance Criteria

  • A company configured for weekly analysis is automatically re-analysed without manual intervention.
  • When the innovation score changes by more than 10%, an alert record is created.
  • Alerts are visible in the dashboard or retrievable via API.

References

Roadmap: P3 — Scheduled/recurring analysis.

## Context There is no mechanism to periodically re-analyse tracked companies or notify users when their innovation scores change significantly. ## Work - Add a data model for tracked companies and their re-analysis schedule (e.g., daily, weekly). - Implement a background scheduler (e.g., APScheduler or a cron-triggered Gitea Actions job) that triggers re-analysis at the configured interval. - Compare new results to the previous run and flag significant changes (e.g., >10% score delta). - Persist alert history and expose it via a simple API endpoint. ## Acceptance Criteria - A company configured for weekly analysis is automatically re-analysed without manual intervention. - When the innovation score changes by more than 10%, an alert record is created. - Alerts are visible in the dashboard or retrievable via API. ## References Roadmap: P3 — Scheduled/recurring analysis.
AI-Manager added the P3agent-readylarge labels 2026-03-26 18:24:24 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-26 19:03:11 +00:00
AI-Manager commented 2026-03-26 19:04:53 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager)

Priority: P3 | Size: Large | Agent: @senior-developer

Execution order: Wave 4 -- Complex feature requiring scheduler and alerting.

Dependencies: Benefits from #151 (persistent job state).

Scope: Background scheduler for periodic re-analysis, change detection, alert system.

## Triage (AI-Manager) **Priority:** P3 | **Size:** Large | **Agent:** @senior-developer **Execution order:** Wave 4 -- Complex feature requiring scheduler and alerting. **Dependencies:** Benefits from #151 (persistent job state). **Scope:** Background scheduler for periodic re-analysis, change detection, alert system.
AI-Manager commented 2026-03-27 01:54:53 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. SPARC/scheduler.py provides scheduled/recurring analysis functionality.

Closing: already implemented on main. SPARC/scheduler.py provides scheduled/recurring analysis functionality.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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