Commands › › Voxel Multi Service Request
Voxel Multi Service Request
Coming soon
Before you run this
Voxel grid cached; services list non-empty.
After it runs
0..N placeholders per service, all inside one Transaction.
When to use this
- Corridor multi-service stacking.
Don't use this when
Single service — use the single-service command.
Inputs
| Name | Kind | Type | Required | Default | Description |
|---|---|---|---|---|---|
PresetKind |
config | string |
no | "voxel_routing" | Deterministic config preset |
Decision flow
1) Resolve cached grid. 2) For each service in order: (a) inflate clearance zones of prior services, (b) A*, (c) emit placeholder segments. 3) If any service fails, rollback whole Transaction. 4) Emit per-service results + totals.
What you'll see in the chat
on start
Planning multi-service rack…
thinking
Running A* per service with cumulative clearance…
Emitting placeholders…
Emitting placeholders…
on success
Routed {service_count} services.
on failure
Rack route failed: {error}
REST API
Not yet exposed
This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:
POST /api/v1/commands/voxel_multi_service_request- Request body schema (from
[RestApiParam]) - Response schema (from
[RestApiResponse]) - curl / JS / Python code examples
Keywords & intent patterns
voxelgridroutemultiservicerackthroughcorridor · route multi service rack · voxel rack corridor
Related
| Pillar |
|---|