[SLICE 13][CORE-D] Implement resumable corpus/backfill engine with stable work IDs, checkpoints, cancellation, and idempotent resume #18

Open
opened 2026-09-08 01:57:00 +00:00 by nsaspy · 0 comments
Owner

Parent epic: #15
Depends on: #22 #23
Refines: #8

Goal

Implement the generic corpus/job runner that discovers durable sources, schedules bounded semantic projection work, checkpoints progress, and resumes without duplication.

Implement:

  • stable source/segment/work IDs;
  • run/job status and progress counts;
  • bounded concurrency and cancellation;
  • per-unit compile/publish state;
  • checkpoint/restart;
  • idempotent unchanged-corpus rerun;
  • selective rework on source/compiler/schema/config fingerprint change;
  • backfill existing memories with absent/stale projection;
  • partial failure isolation and explicit publication completeness;
  • actual provider usage accounting only for compiler calls.

Acceptance

Kill/restart halfway through a multi-source fixture; completed units are not duplicated, pending units resume, failed units remain inspectable/retriable, unchanged rerun is mostly no-op, changed source produces new lineage, and namespace boundaries remain intact.

Parent epic: #15 Depends on: #22 #23 Refines: #8 ## Goal Implement the generic corpus/job runner that discovers durable sources, schedules bounded semantic projection work, checkpoints progress, and resumes without duplication. Implement: - stable source/segment/work IDs; - run/job status and progress counts; - bounded concurrency and cancellation; - per-unit compile/publish state; - checkpoint/restart; - idempotent unchanged-corpus rerun; - selective rework on source/compiler/schema/config fingerprint change; - backfill existing memories with absent/stale projection; - partial failure isolation and explicit publication completeness; - actual provider usage accounting only for compiler calls. ## Acceptance Kill/restart halfway through a multi-source fixture; completed units are not duplicated, pending units resume, failed units remain inspectable/retriable, unchanged rerun is mostly no-op, changed source produces new lineage, and namespace boundaries remain intact.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/symbolic-memory#18
No description provided.