Commands  ›  Architecture / QA  ›  Architecture Detect Corridors Too Small In Current Project

Architecture Detect Corridors Too Small In Current Project

Architecture / QA writes to model Public API · not yet exposed

Coming soon

Before you run this

Corridors placed as Rooms with corridor Room Type. Project standard or active config has the minimum corridor width (e.g. 1100 mm AD M, 1500 mm two-way).

After it runs

A read-only QA report listing corridors below the minimum width; no model changes; failed corridors highlighted in the active view if requested.

When to use this

Don't use this when

Fixing corridors automatically (manual rework needed), non-room circulation (e.g. external paths), or schemes where corridors are managed in a linked model.

Decision flow

1. Find every corridor Room in the project.
2. Compute each corridor's width along its centreline (medial axis transform).
3. Compare the minimum width to the project standard (default 1100 mm AD M).
4. Build a list of failing corridors with width, length and the failing point.
5. Optionally highlight failures on the active view; return the report.

What you'll see in the chat

on start
I'll check every corridor in the project against the {min_width} mm minimum now.
thinking
Computing each corridor's narrowest passage and comparing to the project minimum.
on success
Done — {n_corridors} corridors checked. {n_failed} below the minimum: {failed_list}.
on failure
Couldn't run the corridor check: {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/architecture_detect_corridors_too_small_in_current_project
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

corridor width check · AD M Part M · access compliance · narrow corridor · QA corridor

PillarArchitecture / QA