AutoMovie API
    Preparing search index...

    Interface IAutoMoviePropRelation

    What a prop claims about where it sits, as one typed relation.

    The six kinds are the contact semantics the architecture graph can answer for, and each one restricts which targets it accepts:

    • "in-space": the prop is contained by a logical space (space target).
    • "on-support": it rests on a support patch or another prop's stack-top affordance (surface or prop-affordance target).
    • "against-boundary": it stands against a wall, floor, or ceiling separation (boundary target).
    • "fill-opening": it is the leaf, sash, or gate filling a passage cut through a boundary (opening target).
    • "attached": it is fixed to a building element or plugged into another prop's socket affordance (element or prop-affordance target).
    • "suspended": it hangs from a building element or from another prop's hook affordance (element or prop-affordance target).

    Three kinds have geometry measurements when usable target geometry exists. "on-support" compares the world occupancy underside with finite probes of a support patch or stack-top, refusing a measured gap outside +/-1e-9 m or no overlapping probe. "in-space" checks eight box corners against the space subtree's union; a subtree without stated volume imposes no restriction, and non-convex gaps between corners can remain unseen. "fill-opening" checks occupancy inside the filling element's rest-pose world AABB with 1e-9 m slack; an absent fill/model or unresolved rest transform skips that measurement, so this is not a general reveal-fit proof.

    "against-boundary", "attached" and "suspended" currently check citations only. An optional boundary face does not change that path. Even measured support is a finite proxy test: thin edge intersections and relief between probes can remain unread, unresolved or edge-on faces are skipped, and extreme derived nonfinite gaps are not independently refused by the comparisons. These relations do not solve attachment dynamics or continuous collision.

    validatePropPlacements refuses incompatible target kinds, missing targets, ambiguous environment or prop registry identities, self-prop affordances or wrong affordance kinds, building citations outside the occupied environment and prop-contact cycles. Nested building and affordance identity uniqueness depends on their owners' admission; building-list presence and affordance lookup here do not independently reject every duplicate nested id.

    interface IAutoMoviePropRelation {
        kind: AutoMoviePropRelationKind;
        target: IAutoMoviePropRelationTarget;
    }
    Index

    Which contact semantics this relation asserts.

    The stable spatial, element, or affordance id the relation cites.