deploy.

App/wwwroot/HiAPI-docsite/manual/run/building-a-mission.html

@@ -141,6 +141,53 @@ kind can appear in this dialog before this manual has a page for it.</p>
 pressed. The five category headings are the grouping in the table above, the search box at the top
 is what narrows them, and the first result is highlighted ready for <kbd>Enter</kbd>.</p>
 <p><img src="building-a-mission-img/add-command.en.png" alt="The Add Command dialog open over the Execution page: a Search commands box above thirteen entries under five headings — Setup with Machining Resolution, Machining Motion Resolution, Collision Detection, Pause on Failure and Physics; Program with Program File, NC Code and Script; Optimization with NC Optimization Config; Output with Post-Execution, Record Meshed Geometry and Export Meshed Geometry STL; and Flow with List"></p>
+<h2 id="the-shape-to-start-from">The shape to start from</h2>
+<p>An empty list is legal, but it is not where a project should end up. A finished mission has the
+same shape whatever it machines: <strong>setup at the top, the program in the middle, the program held
+between two Record Meshed Geometry entries, output at the bottom.</strong></p>
+<table>
+<thead>
+<tr>
+<th></th>
+<th></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Setup</td>
+<td>Machining Resolution, Machining Motion Resolution, Collision Detection, Pause on Failure, Physics</td>
+</tr>
+<tr>
+<td>Output</td>
+<td><strong>Record Meshed Geometry</strong> — <code>Cache/&lt;stage&gt;-init.wct</code>, the stock</td>
+</tr>
+<tr>
+<td>Program</td>
+<td>Program File</td>
+</tr>
+<tr>
+<td>Output</td>
+<td><strong>Record Meshed Geometry</strong> — <code>Cache/&lt;stage&gt;-done.wct</code>, the result</td>
+</tr>
+<tr>
+<td>Output</td>
+<td>Post-Execution</td>
+</tr>
+</tbody>
+</table>
+<p>The two records are what make a run restartable, and they are part of the shape rather than an
+advanced extra — a mission without them replays the whole job from the stock every time. Two rules
+travel with them:</p>
+<ul>
+<li><strong>Machining Resolution belongs above the first record.</strong> The cache is meshed at whatever
+resolution is in force when the record runs, so a resolution set below it is silently baked out
+of the file.</li>
+<li><strong>Keep the first record where the stock is an STL, drop it where the stock is procedural</strong> (a box
+or a cylindroid) or is already a recorded mesh. Meshing an STL is a fixed cost paid on every
+play; a box the kernel builds instantly, and caching it costs more than it saves.</li>
+</ul>
+<p><a href="a-mission-that-resumes.html">A Mission That Resumes</a> is this layout in full, with the reasoning and
+the measurements behind each row.</p>
 <h2 id="read-a-row">Read a row</h2>
 <p>Each row shows the command's kind followed by the detail that identifies it, in brackets. Where you
 can name a command that detail is the title you typed, so a row still says what it is after it has
@@ -215,7 +262,7 @@ the child node's own checkbox. Which commands do that, and what each card holds,
 <li><a href="index.html">Running a Simulation</a> — the rest of running a job</li>
 <li><a href="playing-a-program.html">Playing a Program</a> — the two commands that put NC code into a run</li>
 <li><a href="the-other-commands.html">The Other Commands</a> — what the rest of the command kinds are for</li>
-<li><a href="a-mission-that-resumes.html">A Mission That Resumes</a> — a layout that reads as values and restarts mid-job</li>
+<li><a href="a-mission-that-resumes.html">A Mission That Resumes</a> — the shape a mission should start from, in full</li>
 <li><a href="running-a-simulation.html">Starting and Stepping</a> — the transport that plays the list built here</li>
 <li><a class="xref" href="../../anatomy/execution/mission/mission-root-panel.html">Mission Root Panel</a> — the component behind this branch: the list editor, the picker and the three drag landings</li>
 <li><a class="xref" href="../../anatomy/execution/mission/ListCommand-panel.html">List Command Panel</a> — the component behind a group: what nesting costs, and what a disabled list skips</li>