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

Add non-blocking thought save path with deferred metadata/embedding enrichment #26

New Issue
Closed
opened 2026-04-13 20:13:29 +00:00 by sgcommand · 0 comments
sgcommand commented 2026-04-13 20:13:29 +00:00
Member
Copy Link

Problem

Thought capture must not fail or time out because downstream metadata extraction or embedding generation is slow or unavailable. The current reliability concerns suggest user-facing save requests may still be coupled too tightly to enrichment work.

Impact

  • User-visible timeout/errors during thought save
  • Lost confidence in capture reliability
  • Slow AI/background dependencies can break core write path

Expected behavior

Saving a thought should succeed quickly once the core record is persisted. Metadata extraction and embedding generation should be deferred to background processing and must not block the user request.

Acceptance criteria

  • Thought save returns success after core persistence without waiting for metadata/embedding completion
  • Metadata extraction and embedding generation are queued or scheduled asynchronously
  • If enrichment fails, the thought remains saved and available
  • Failures are recorded for later retry instead of surfacing as request failure
  • Logging/metrics make deferred enrichment failures visible without breaking capture flow
## Problem Thought capture must not fail or time out because downstream metadata extraction or embedding generation is slow or unavailable. The current reliability concerns suggest user-facing save requests may still be coupled too tightly to enrichment work. ## Impact - User-visible timeout/errors during thought save - Lost confidence in capture reliability - Slow AI/background dependencies can break core write path ## Expected behavior Saving a thought should succeed quickly once the core record is persisted. Metadata extraction and embedding generation should be deferred to background processing and must not block the user request. ## Acceptance criteria - Thought save returns success after core persistence without waiting for metadata/embedding completion - Metadata extraction and embedding generation are queued or scheduled asynchronously - If enrichment fails, the thought remains saved and available - Failures are recorded for later retry instead of surfacing as request failure - Logging/metrics make deferred enrichment failures visible without breaking capture flow
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#26
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?