> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bedrock.cv/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> AEC industry and Bedrock platform terminology.

## AEC Industry Terms

<ResponseField name="Sheet">
  A single page from a construction drawing PDF. Identified by sheet number (A-101, E-201, S-301). The letter prefix indicates discipline.
</ResponseField>

<ResponseField name="Discipline">
  The engineering trade responsible for a sheet. Common codes: A (Architectural), S (Structural), M (Mechanical), E (Electrical), P (Plumbing), FP (Fire Protection), C (Civil).
</ResponseField>

<ResponseField name="Grid">
  The building's coordinate system. Grid lines (A, B, C / 1, 2, 3) are shared across all disciplines and floors. Grid intersection "B-3" refers to the same physical location on every sheet.
</ResponseField>

<ResponseField name="Schedule">
  A table on a drawing sheet listing specifications for a category of elements (door schedule, window schedule, finish schedule, equipment schedule).
</ResponseField>

<ResponseField name="Legend">
  A table pairing graphical symbols with their text descriptions. Used to define what each symbol on a plan view represents.
</ResponseField>

<ResponseField name="Keynote">
  A numbered annotation on a plan view with a leader arrow pointing to a specific element. References a keynote table elsewhere on the drawing set.
</ResponseField>

<ResponseField name="RFI">
  Request for Information — a formal question from the contractor to the design team about ambiguities or conflicts in the drawings.
</ResponseField>

<ResponseField name="Clash">
  A conflict where two building elements from different disciplines occupy the same physical space (e.g., a duct intersecting a beam at the same grid location and elevation).
</ResponseField>

## Bedrock Platform Terms

<ResponseField name="Drawing">
  A PDF file uploaded to Bedrock. Contains one or more sheets. Often represents one revision of a drawing set (e.g., "Arch Set Rev B").
</ResponseField>

<ResponseField name="Block">
  A self-contained region on a sheet — a plan view, detail, schedule, legend, notes section. Bedrock detects blocks automatically during processing.
</ResponseField>

<ResponseField name="Feature">
  A detected entity within a block — a room, door, wall, receptacle, dimension, symbol. Features nest via parent containment (a receptacle is inside a room).
</ResponseField>

<ResponseField name="Overlay">
  A visual comparison between two matched blocks from different drawing revisions, highlighting additions (green) and deletions (red).
</ResponseField>

<ResponseField name="Relation">
  A typed edge in the Drawing Index knowledge graph connecting blocks or features. Examples: scheduled\_in (door to schedule), defined\_by (symbol to legend), references (callout to detail on another sheet).
</ResponseField>

<ResponseField name="Drawing Index">
  The structured knowledge graph that Bedrock builds from construction drawings. Contains all sheets, blocks, features, relations, and grid data — queryable via REST API or MCP.
</ResponseField>

<ResponseField name="MCP">
  Model Context Protocol — an open standard for connecting AI agents to external data sources. The Bedrock MCP server gives agents like Claude and ChatGPT direct access to the Drawing Index.
</ResponseField>