# Scope documentation

The complete product guide: supported formats, the part record, the measurement contract, the native decoder boundary, and safe operation.

## Supported inputs

Scope accepts native and neutral CAD formats. Every format resolves to exact geometry; what varies is the metadata the source format can carry.

- STEP and IGES: the full exact pipeline. Semantic PMI and GD&T require AP242 STEP; IGES surface models are sewn into solids when the faces close, and the result is flagged.
- SLDPRT and SLDASM: exact native decode of the embedded Parasolid geometry. A SolidWorks Pack-and-Go zip is uploaded as the model, and referenced parts resolve from inside the archive.
- Parasolid x_b: the same exact decoder. Text-format x_t is refused with guidance to export x_b or STEP instead.
- BREP: exact geometry with no units or metadata in the format; values are read as millimeters.
- DXF and DWG: a separate exact 2D drawing path with snap measuring. DWG converts on upload through a bundled converter.

## What a part record contains

Opening a part produces more than a rendering. The record combines exact geometry with the derived facts that estimating and review actually use.

- Mass properties and both bounding boxes, including the oriented box that answers the stock-size question.
- A deliberately conservative hole table: diameter, depth, through or blind, position, and axis, with slot ends and pocket fillets excluded rather than misreported.
- Thread and fit inference per hole, matched against standard tap, clearance, and nominal charts and always labeled as inference.
- Document properties read from the native file where the format carries them: part number, material, revision, finish, description.

## Measurement contract

The browser renders a mesh for speed, but every reported dimension resolves back to exact B-rep geometry.

- A circular edge reports its analytic diameter and center.
- Face-to-face distance uses exact geometry, not triangle proximity.
- Hole and feature recognition is conservative and carries its limits beside the result.

## Native SolidWorks boundary

The decoder is designed around an exact-decode-or-loud-refuse contract: a file either becomes exact geometry or is refused with the reason named.

- Supported analytic and spline geometry becomes an exact B-rep, validated against paired SolidWorks STEP exports.
- Filleted parts decode, including corner blends reconstructed from the exact surfaces.
- Rolling-ball blends, offset, swept, spun, and foreign surfaces are refused rather than approximated.
- When a native file is refused or semantic PMI is required, request STEP AP242; for assemblies, request a Pack-and-Go zip so every referenced part travels with the assembly.

## The same facts for people and AI peers

The web viewer, HTTP API, and MCP surface expose the same measured record. An AI peer working in an estimating or review workflow reads the identical geometry facts a person clicks on, with the same stated limits attached.

## Operate as a private service

Scope is self-hosted: models stay on infrastructure you control and never leave your network. The service ships without its own authentication, so keep it on a private network or place a real authentication gate in front of it.

> This page describes the product boundary. Deployment remains an operator responsibility and is not performed by the public site.



## Source authority

The Scope repository and its maintained reference documentation. Product behavior, release state, and full operating detail remain authoritative there.