Commands › Clash Manager / Solver › Clash Solver Assess Space Around Device Six Directions
Clash Solver Assess Space Around Device Six Directions
Coming soon
Before you run this
Active document; one resolvable element (Bot via UniqueId, Human via single selection).
After it runs
No model mutation; audit recorded.
When to use this
- Pre-flight check before any Move*IntoSpace decision.
Don't use this when
Actual movement.
Inputs
| Name | Kind | Type | Required | Default | Description |
|---|---|---|---|---|---|
PresetKind |
config | string |
no | "clash_tolerances" | Deterministic config preset |
Decision flow
1) Resolve element: element unique id (Bot) else single active selection (Human). 2) WireError if unresolved. 3) Probe point = LocationPoint.Point if available, else BB centroid. 4) Delegate to SpaceAnalysisAssessAroundPointInSixDirections.GetAll. 5) Attach element identity to result. 6) Tracker output + TaskDialog on Human path.
What you'll see in the chat
on start
Assessing space around the selected device…
thinking
Resolving element and probe point…
Delegating to SpaceAnalysisAssessAroundPointInSixDirections…
Delegating to SpaceAnalysisAssessAroundPointInSixDirections…
on success
Six-direction clearance recorded for element {elementId}.
on failure
Assessment 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/clash_solver_assess_space_around_device_six_directions- Request body schema (from
[RestApiParam]) - Response schema (from
[RestApiResponse]) - curl / JS / Python code examples
Keywords & intent patterns
clashsolverassessspacearounddevicesixdirections · six direction around device · clash solver assess space around device
Related
| Pillar | Clash Manager / Solver |
|---|