# `AnchorSpec.at`

> Contract 2.0.0 · package sha256 `a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e` · generated from `configurator-runtime.d.ts` by `services/onsite-scripter/scripts/build-contract-docs.mjs`; edit the source, not this file.

Property of [`AnchorSpec`](AnchorSpec.md) · stable · since 2.0.0

```ts
at: Point3;
```

World point, or local to the first part [`on`](AnchorSpec.on.md) matches in document order ([`Parts.first()`](Parts.first.md)):
for `{ node }`, which matches the model's root and every part under it, that is the model's
root, so the point is in the model's frame; to follow one part, give [`on`](AnchorSpec.on.md) a query that
matches only it (`{ node, id }`, `{ node, name }`) or that [`Part`](Part.md). While [`on`](AnchorSpec.on.md) matches no part (a node not loaded,
failed or removed, a removed item), the anchor reports `visible: false` with [`x`](Point3.x.md), [`y`](Point3.y.md) and
`depth` 0, as 1.x does, and records no Problem, 'target-unmatched' included. It follows the
part from the frame the part exists.

## Generic-API test (spec 3.1)

| Rule | Result |
| --- | --- |
| 1. Neutral name | pass: `at` names no product |
| 2. A precedent | not recorded: no ledger row (coverage.json) names this member or its owner |
| 3. Two apps, or labs | not recorded: no ledger row names this member or its owner |
| 4. The cheaper fix first | not recorded per member (Appendix B decides it per need) |