AutoMovie API
    Preparing search index...

    Service and building declarations used to report which checks have applicable geometry.

    A record existing is not an analysis, and the honest way to say so is to say so. The structural rules below are the ones the engine really performs; the per-discipline entries are the quantitative questions nothing here solves, listed once for each discipline the network actually declares so a report names the missing solver rather than implying a pass.

    The building is required rather than optional because the geometric answers depend on it. A crossing is read off logical space volumes, so a building whose partitions are names with no cells cannot be asked where a run left a room; a sleeve is placed on its boundary's own face, so a boundary written before faces existed cannot be asked where its holes are. Saying supported in either case would be the dressing-up this report exists to prevent. This is capability metadata, not a record that validation ran. No current production report consumes these rows; topology tests exercise their wording.

    Index

    Borrowed building whose stated space volumes and sleeve-host faces determine geometric applicability.

    Borrowed disciplines and penetration references used to select capability explanations; no network validation runs.