review · segments

Conductor Build: Runtime Orchestration Components

claude 120 events 1 segments main

segment 1 of 1

Implement conductor runtime orchestration support components

Done

The assistant ported the GPU runtime orchestration layer from the lounge project into the new conductor service. It created 11 files: config (conductor-runtimes.php), three models (GpuRuntimeProfile, GpuRuntimeInstance, GpuRuntimeEvent), five runtime services (GpuRuntimeStateStore, GhcrImagePullVerifier, GpuRuntimeInstanceStore, GpuRuntimeProfileResolver, GpuEmbeddingRuntimeManager), and two migrations. It cleaned up the transport-profile layer, renamed config keys, and adapted namespaces. During the build it discovered that the Dto agent's GpuRuntimeStreamIdentity class calls a streamIdentity() method on the resolver that was removed; it restored that method with a default stream identity from config or fallback defaults. All files pass PHP lint and a container bootstrap smoke test verified the resolver, manager, and config work together.

outcome

All 11 files are created, pass PHP lint, and the resolver, manager, and config pass a container bootstrap smoke test including streamIdentity() and resolve('manual') returning the correct adapter class.

next steps

—

key decisions

Dropped transport-profile layer from models/resolver; stream identity now derived from conductor-client's config contract or built-in defaults.
Restored streamIdentity() method on resolver to maintain compatibility with sibling Dto and adapter classes.
Set stream_identity array on resolved config so adapters can pass it to the streamIdentity DTO.
Replaced gpu-embedding-runtimes config key with conductor-runtimes.
Dropped max_runtime_minutes per plan decision #9 (no hard runtime cap).
Used 'database' as default state_driver (env may override to 'sqlite' but that's cosmetic).

open questions

—

2 weeks ago → 2 weeks ago