> ## Documentation Index > Fetch the complete documentation index at: https://www.docs.forgeshipyard.com/llms.txt > Use this file to discover all available pages before exploring further. # Research Log > Our weekly progress updates, newest first. **What this is.** A running record of what we are building and learning, updated every week. It is meant to be skimmable: every entry follows the same template, so you always know where to look for what shipped, what we learned, and what is next. ## How to read an entry Every weekly entry has the same five sections: Two or three sentences. If you read nothing else, read this. Concrete progress this week, tied to a build milestone where possible. Findings from interviews, experiments, or the work itself. Often the most useful part for a shipyard reader. What needs partner configuration, validation, or a decision next. We keep this clear so readers can distinguish shipped capability from the path into use. What we are focused on next. ## Entries The first post-baseline expansion: a broader regulatory evidence graph, labeled evaluations, rules visible on the vessel model, and work-package readiness. From controlled pilot to CAD-aware review: build readiness, change impact, governed approval, and a shareable review package (M5-M6). CAD becomes traceable engineering evidence, and every formal output follows the same verification path (M3-M4). The geometry baseline begins (M3, in progress). From rules to governed decisions: compliance gaps, signed decisions, and rule changes (M2 complete). Foundations first: the governed backbone, rules as data, and the first field correction (M0-M1). ## Research log vs. blog This log is the **specifics of our work**, week by week. Our [blog](https://your-site.com/blog) is for longer narrative articles and argument (like the founding essay). When in doubt: progress updates go here; essays and opinion go on the blog.