Rick

Carousel — Job Submit / Execute / Result

API → queue → execution worker → compute → LVC → result publication.

Carousel — Job Submit / Execute / Result (v2026-09-30T095152Z-5e473105f4) 2026-09-30 | API → queue → execution worker → compute → LVC → result publication. 1 - API REQUEST - API receives job submission POST /api/carousel/pick carousel_api.py:pick CarouselRequest.as_dict request_id 2 - QUEUE - Job is queued for execution carousel_jobs.py register_subscriber get_savings kv/carousel/receipts 3 - EXECUTION - Job is executed by a compute resource carousel_compute.py get_compute_registry ComputeResource.register ComputeResource.select 1. API receives job 2. Job is queued 3. Job is executed CarouselRequest payload {"request_id": "12345678", "model_tier": "standard", "prompt": "Hello, world!", "max_tokens": 4096, "created_at": "2023-10-01T12:00:00Z"} The actual job execution details are handled by the compute resource selected based on the model tier and availability. Legend actor = initiates work · process = code path · store = state on disk · bus = durable queue · dashed = separate process cyan = request flow · pink = state read/write · dashed green = pull / return path · red = refusal As of 2026-09-30 09:51 UTC, from commit 5e47310

Provenance

This drawing is generated, not drawn. It is rebuilt from the source files below, so when they change the picture changes — a diagram here cannot quietly describe a system that no longer works this way.

Owner
Rick
Slug
carousel-pipeline
Rendered
2026-09-30T095152Z
From commit
5e473105f4
Updated
30 Sep 2026, 09:51 UTC
Sources at
5e47310
Watches
10 paths
  • daemon/src/carousel.py
  • daemon/src/carousel_api.py
  • daemon/src/carousel_compute.py
  • daemon/src/carousel_execution.py
  • daemon/src/carousel_jobs.py
  • daemon/src/carousel_lvc.py
  • daemon/src/carousel_router.py
  • daemon/src/carousel_routing_router.py
  • daemon/src/carousel/
  • daemon/src/carousel/router.py