# Forge > AI Digital Twin technology for your shipyard ## Docs - [How a Decision Gets Made](https://www.docs.forgeshipyard.com/concepts/how-a-decision-gets-made.md): A worked example, from the engineer's click to the signed decision. - [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. - [Where Humans Stay in Control](https://www.docs.forgeshipyard.com/concepts/human-control.md): The decisions that always belong to a person, by design. - [Keeping Your Data Yours](https://www.docs.forgeshipyard.com/concepts/keeping-data-yours.md): How Forge protects sensitive ship designs and keeps each yard isolated. - [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. - [The Two-Clock Problem](https://www.docs.forgeshipyard.com/concepts/two-clock-problem.md): The single idea that the whole system is built around. - [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. - [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. - [Architecture Overview](https://www.docs.forgeshipyard.com/how-it-works/architecture-overview.md): The seven layers of Forge, and the three principles that shape all of them. - [The Build Path](https://www.docs.forgeshipyard.com/how-it-works/build-path.md): The milestones, from foundations to a CAD-aware IDE. What's shipped and what's next. - [How We Measure Quality](https://www.docs.forgeshipyard.com/how-it-works/evaluation-targets.md): The numbers Forge holds itself accountable to before any production use. - [L0 · Source & Authority Registry](https://www.docs.forgeshipyard.com/how-it-works/layers/l0-source-authority.md): The first layer. Classifies every input before anything else can touch it. - [L1 · Ingestion & Normalization](https://www.docs.forgeshipyard.com/how-it-works/layers/l1-ingestion.md): Turns raw documents into structured objects without losing the source. - [L2.5 · Engineering Decision Ledger](https://www.docs.forgeshipyard.com/how-it-works/layers/l2-5-decision-ledger.md): Where the 'why' lives. The event clock of the whole system. - [L2 · Maritime Design Ontology](https://www.docs.forgeshipyard.com/how-it-works/layers/l2-ontology.md): The connected model of the vessel: the answer to 'what is this ship?' - [L3 · CAD & Geometry World Model](https://www.docs.forgeshipyard.com/how-it-works/layers/l3-geometry.md): The deterministic geometry service. The AI never computes geometry itself. - [L4 · Rules & Applicability Engine](https://www.docs.forgeshipyard.com/how-it-works/layers/l4-rules.md): Decides which rules apply, what evidence is missing, and what conflicts exist. - [L5 · Capability Catalog & Agents](https://www.docs.forgeshipyard.com/how-it-works/layers/l5-capabilities.md): The fixed menu of moves the AI is allowed to make. No free-form prompting. - [L6 · Verification Ladder](https://www.docs.forgeshipyard.com/how-it-works/layers/l6-verification.md): The ordered set of checks every output passes before it can become a decision. - [L7 · Outcome Observer](https://www.docs.forgeshipyard.com/how-it-works/layers/l7-outcomes.md): Closes the loop. Compares decisions to what actually happened, and learns. - [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 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. - [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 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 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 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. - [Research Log](https://www.docs.forgeshipyard.com/research-log/overview.md): Our weekly progress updates, newest first. - [How Forge Fits Your Existing Tools](https://www.docs.forgeshipyard.com/start-here/how-forge-fits.md): Forge sits around your current software, not in place of it. - [The Problem We're Solving](https://www.docs.forgeshipyard.com/start-here/the-problem.md): Why U.S. shipyards need this, in plain language. - [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 system. - [What is Forge?](https://www.docs.forgeshipyard.com/start-here/what-is-forge.md): The one-paragraph answer, in plain language. - [Why This Matters for Your Yard](https://www.docs.forgeshipyard.com/start-here/why-it-matters.md): The competitive and strategic case, in plain language. ## OpenAPI Specs - [openapi](https://www.docs.forgeshipyard.com/api-reference/openapi.json)