# Forge > The 2D-to-3D model reconciliation layer for ship repair and maintenance ## Docs - [What is Forge?](https://www.docs.forgeshipyard.com/start-here/what-is-forge.md): The one-paragraph answer, in plain language. - [The Problem We're Solving](https://www.docs.forgeshipyard.com/start-here/the-problem.md): Why a ship arrives at drydock with no reliable model of itself. - [Why This Matters for Your Fleet](https://www.docs.forgeshipyard.com/start-here/why-it-matters.md): What changes operationally once the model matches the ship. - [How Forge Fits Your Existing Tools](https://www.docs.forgeshipyard.com/start-here/how-forge-fits.md): Forge produces the model your tools were missing. It does not replace them. - [What Forge Will Not Do](https://www.docs.forgeshipyard.com/start-here/what-forge-wont-do.md): The limits we deliberately build in, so you can trust the result. - [What's Next](https://www.docs.forgeshipyard.com/start-here/whats-next.md): Where the reconstruction work stands today and what we are building next. - [From Drawings to a 3D Model](https://www.docs.forgeshipyard.com/concepts/from-drawings-to-3d.md): How a stack of legacy 2D sheets becomes a structured, inspectable 3D model without inventing what the drawings do not say. - [The Two-Clock Problem](https://www.docs.forgeshipyard.com/concepts/two-clock-problem.md): The single idea that the whole system is built around. - [Sources vs. Decisions](https://www.docs.forgeshipyard.com/concepts/sources-vs-decisions.md): The two kinds of things Forge handles, and why keeping them separate is the point. - [How CAD Becomes Engineering Evidence](https://www.docs.forgeshipyard.com/concepts/how-cad-becomes-engineering-evidence.md): How Forge turns a 3D model into measurements that engineers and reviewers can trace, inspect, and trust. - [How a Decision Gets Made](https://www.docs.forgeshipyard.com/concepts/how-a-decision-gets-made.md): A worked example, from a drydock planning question to a signed decision. - [When the Rules Change](https://www.docs.forgeshipyard.com/concepts/when-rules-change.md): How Forge handles a rule update without forcing a manual re-audit of everything. - [Keeping Your Data Yours](https://www.docs.forgeshipyard.com/concepts/keeping-data-yours.md): How Forge protects sensitive vessel data and keeps every customer isolated. - [Where Humans Stay in Control](https://www.docs.forgeshipyard.com/concepts/human-control.md): The decisions that always belong to a person, by design. - [Research Log](https://www.docs.forgeshipyard.com/research-log/overview.md): Our weekly progress updates, newest first. - [Week of July 7, 2026](https://www.docs.forgeshipyard.com/research-log/2026/week-of-jul-07.md): The first post-baseline expansion: a broader regulatory evidence graph, labeled evaluations, rules visible on the vessel model, and work-package readiness. - [Week of June 30, 2026](https://www.docs.forgeshipyard.com/research-log/2026/week-of-jun-30.md): The controlled DesignOS pilot and CAD-aware engineering workspace reach their baselines, bringing readiness, change impact, review, and approval into one traceable flow. - [Week of June 23, 2026](https://www.docs.forgeshipyard.com/research-log/2026/week-of-jun-23.md): The geometry and verification baselines close: CAD models become traceable engineering evidence, and every formal output follows the same checks. - [Week of June 16, 2026](https://www.docs.forgeshipyard.com/research-log/2026/week-of-jun-16.md): The geometry baseline begins (M3, in progress): the yard's real unit of work, the evidence-to-vessel resolver, and a citable home for every measurement. - [Week of June 9, 2026](https://www.docs.forgeshipyard.com/research-log/2026/week-of-jun-09.md): From rules to governed decisions: compliance-gap analysis, closing the propose-approve-sign loop, handling rule changes, and the interpretive layer as structure. - [Week of June 2, 2026](https://www.docs.forgeshipyard.com/research-log/2026/week-of-jun-02.md): Foundations first: the governed data backbone, rules as data, local AI search, and the first real correction from a shipyard owner. - [Reconstructing Balclutha](https://www.docs.forgeshipyard.com/research-cases/balclutha-evidence-workbench.md): We rebuilt an 1886 ship in 3D from its original drawings. - [Seven Balclutha Reconstruction Studies](https://www.docs.forgeshipyard.com/research-cases/balclutha-reconstruction-studies.md): Seven governed views of one complete visual research vessel. - [Complete Vessel](https://www.docs.forgeshipyard.com/research-cases/balclutha-reconstruction-studies/complete-vessel.md): Assembly and exact recomposition of the complete visual research vessel. - [Hull Envelope](https://www.docs.forgeshipyard.com/research-cases/balclutha-reconstruction-studies/hull-envelope.md): The bow-to-stern exterior form hypothesis. - [Survey and Reference Skeleton](https://www.docs.forgeshipyard.com/research-cases/balclutha-reconstruction-studies/survey-reference-skeleton.md): Sectional organization and accepted visual reference lines. - [Internal Structural System](https://www.docs.forgeshipyard.com/research-cases/balclutha-reconstruction-studies/internal-structural-system.md): A governed cutaway and isolation view of the internal research structure. - [Frames 60 to 62](https://www.docs.forgeshipyard.com/research-cases/balclutha-reconstruction-studies/frames-60-62.md): The bounded decomposable assembly nested inside the complete vessel. - [Above-Deck and Outfitting](https://www.docs.forgeshipyard.com/research-cases/balclutha-reconstruction-studies/above-deck-outfitting.md): System-level views of openings, superstructure, accommodation, and visible outfitting. - [Rigging System](https://www.docs.forgeshipyard.com/research-cases/balclutha-reconstruction-studies/rigging-system.md): The governed mast, spar, bowsprit, and rigging hierarchy. - [Glossary](https://www.docs.forgeshipyard.com/glossary.md): Plain-language definitions of every term used across the Forge docs. Look up a word here, then jump back to where you were. ## OpenAPI Specs - [openapi](https://www.docs.forgeshipyard.com/api-reference/openapi.json) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.