wdevs/amcs
5
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Add background enrichment jobs for stored thoughts #12

New Issue
Closed
opened 2026-04-03 11:12:38 +00:00 by sam · 0 comments
sam commented 2026-04-03 11:12:38 +00:00
Member
Copy Link

Summary

Introduce scheduled or queued enrichment jobs that improve stored records over time beyond the initial capture path.

Why

Background enrichment jobs are called out as deferred in the implementation plan. This would let AMCS do heavier or lower-priority work without blocking capture and search workflows.

Scope ideas

  • Define enrichment job types, such as metadata improvement, relinking, summarization, clustering, or stale-record refresh
  • Add job scheduling/execution and observability
  • Make runs idempotent and safe to resume
  • Distinguish enrichment from existing backfill/retry maintenance jobs
  • Document operational controls and cost/performance considerations

Acceptance criteria

  • Enrichment jobs can run outside normal request handling
  • Job status and failures are observable
  • Enrichment outputs are written safely and repeatably
  • Docs explain available jobs and how to operate them

Source

Deferred feature from llm/plan.md: background enrichment jobs.

## Summary Introduce scheduled or queued enrichment jobs that improve stored records over time beyond the initial capture path. ## Why Background enrichment jobs are called out as deferred in the implementation plan. This would let AMCS do heavier or lower-priority work without blocking capture and search workflows. ## Scope ideas - Define enrichment job types, such as metadata improvement, relinking, summarization, clustering, or stale-record refresh - Add job scheduling/execution and observability - Make runs idempotent and safe to resume - Distinguish enrichment from existing backfill/retry maintenance jobs - Document operational controls and cost/performance considerations ## Acceptance criteria - Enrichment jobs can run outside normal request handling - Job status and failures are observable - Enrichment outputs are written safely and repeatably - Docs explain available jobs and how to operate them ## Source Deferred feature from `llm/plan.md`: background enrichment jobs.
sam closed this issue 2026-04-03 11:27:12 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
debugging
integration
planned
ux
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hein root sam sgcommand warkanum
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/amcs#12
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?