Cortex — the construction intelligence layer behind Trunk Tools, the "brain of your project." It reads your project documents, connects them, and powers the agents.

Agents — purpose-built assistants that run on Cortex and handle specific workflows. Trunk Tools builds, maintains, and runs them for you.

TrunkText — the project Q&A agent. Ask a question by text, web, or Teams and get answers cited from your project documents.

TrunkSubmittal — reviews submittals against their specifications and flags compliance issues automatically.

TrunkRegister — reads the spec book and builds your submittal register, categorizing each requirement, then pushes it back to your project management system.

TrunkReview — reviews drawing, bulletin, and revision sets, producing a written narrative of changes and a visual overlay, including changes the architect didn't cloud.

TrunkRFI — checks whether an RFI is actually needed and drafts the ones that are, writing them back to Procore or Autodesk Forma.

TrunkBid — compares subcontractor bids side by side to surface inclusions, exclusions, and scope gaps before buyout.

TrunkBrowse — click any object on a sheet to open its full context: the schedule row, spec section, RFIs, submittals, and other sheets it appears on.

TrunkChange (available for early adopters) — detects a change event the moment a bulletin or RFI response lands, traces every affected trade, reports the cost, schedule, and scope impact, and drafts the change order.

Knowledge graph — the map of relationships between all of your project's documents that lets each agent reason with the full picture, not one file in isolation.

Artifact — an output an agent generates for you (for example, a compliance analysis or a draft email) that you can review, edit, share, or download.

GC (general contractor) — runs the build and coordinates the subcontractors.

Sub / subcontractor — a trade contractor responsible for a specific scope, such as mechanical or drywall.

Owner / developer — the party paying for and commissioning the project.

RFI (Request for Information) — a formal question to the design team to clarify drawings or specs.

Submittal — a subcontractor's proposed product, material, or shop drawing, sent for review against the spec before installation.

Spec (specification) — the written requirements a submittal has to satisfy.

Spec section — a numbered portion of the specification that a submittal or RFI is tied to.

Drawing / sheet — the graphic record of what gets built, communicated through geometry, symbols, callouts, and cross-sheet references.

Bulletin / revision — an issued set of drawing changes during a project.

Revision cloud (clouded vs. unclouded) — a cloud the architect draws to mark a change. An unclouded change is one they didn't mark, the kind that slips past and becomes rework.

ASI — Architect's Supplemental Instruction; a minor design clarification or change.

Change order (CO) — a documented change to scope, cost, or schedule.

Buyout — awarding subcontracts after bidding.

Long-lead procurement — ordering items with long lead times, which can be delayed when submittals are stuck.

Schedule of values — the breakdown of contract value used for billing.

OAC meeting — Owner–Architect–Contractor coordination meeting.

Daily log — the field record of what happened on site each day.

Punch list — the remaining items to complete or fix before closeout.

MEP — mechanical, electrical, and plumbing scopes.

AHU — air handling unit; rooftop HVAC equipment.

PMS (project management system) — the system of record for your project, such as Procore or Autodesk.