In plain terms: Forge is an intelligence layer that sits around the design
and engineering tools your yard already uses. It keeps track of what is known,
what is missing, what changed, which rules apply, and what needs a human’s
approval before a design moves into production.
The short version
Forge does not replace ShipConstructor, AutoCAD, CADMATIC, NAPA, Rhino, or your ERP system. Those tools draw the ship and run the yard. Forge is the layer that understands the reasoning around the design: which rule applied, what prior vessel it was based on, what evidence supported a choice, who approved it, and what later changed. Today that reasoning is scattered. Rules live in ABS and USCG documents. Drawings live in CAD. Bills of material live in spreadsheets. Prior-vessel knowledge lives in old project folders and in the heads of senior engineers. Decisions live in email threads and meetings. When a senior engineer retires, much of it walks out the door. Forge pulls that scattered reasoning into one place that can be searched, traced, and trusted.What it gives a yard
A memory that does not retire
Decades of contracts, drawings, and decisions become a single searchable
record instead of tribal knowledge.
Rules that check themselves
ABS and USCG requirements are applied automatically, with a citation back to
the exact rule and version every time.
A record of why
Every engineering decision is stored with the reason behind it, so months
later you can answer “why did we do it this way?”
Your data stays yours
Sensitive designs are processed on your own infrastructure. Nothing
proprietary leaves the building.
How to read these docs
Start Here
The plain-language case: the problem, why it matters, and how Forge fits.
No technical background needed.
Concepts
How Forge thinks, one idea at a time. Still plain language, a little deeper.
How It Works
The specifics of the system, layer by layer, for the technically curious.
Research Log
Our weekly progress updates.