reference: note zddc-server tracking-number defaults

Add a "zddc-server defaults" callout to §3 (Tracking numbers): the
reference implementation ships the Basic schema + optional [suffix],
binds originator to the party folder (read-only, folder is the source
of truth), and ships phase/area off by default (project-wide, enabled
per project via .zddc). The universal convention is unchanged — this
just clarifies what the server does out of the box so readers don't
conflate the spec with the default deployment.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

reference.html

@@ -217,6 +217,14 @@ status       = "IFA" / "IFB" / "IFC" / "IFD" / "IFI" / "IFP" / "IFR" / "IFU" / "
           <p><strong>Rule: corporate placeholder.</strong> The Corporate schema substitutes a placeholder for the project identifier, indicating the document belongs to the originator's corporate library rather than a specific project. The placeholder does not have to be <code>000000</code> — any value works as long as it is <em>easily recognizable</em> as a corporate-scope marker and could not be mistaken for a real project number (e.g., <code>000000</code>, <code>CORP</code>, <code>HQ</code>). Pick one and use it consistently. The same originator code and discipline/type conventions apply, so corporate documents sort naturally alongside project documents in a unified archive.</p>
         </div>
 
+        <div class="highlight-box" style="margin-top: var(--spacing-lg);">
+          <p><strong>zddc-server defaults.</strong> The schemas above are deployment-agnostic — any of them is a valid tracking number. The <code>zddc-server</code> reference implementation ships the <strong>Basic</strong> schema by default (<code>originator-project-discipline-type-sequence</code>), plus the optional per-deliverable <code>[suffix]</code> (a hyphenated part marker such as <code>-A</code> for an appendix). Two deployment behaviours are worth knowing:</p>
+          <ul style="margin: var(--spacing-md) 0; padding-left: 1.5rem; color: var(--color-text-muted); line-height: 1.65;">
+            <li><strong>originator is bound to the party folder.</strong> Under <code>archive/&lt;party&gt;/</code>, the server sets <code>originator</code> from the party-folder name and renders it read-only — the folder is its single source of truth, so it can't drift from where the deliverable is filed.</li>
+            <li><strong>phase and area are off by default.</strong> Because they are project-wide (all-or-nothing across a project), the default omits them; a project that needs them enables them on <em>every</em> deliverable by extending the schema in its <code>.zddc</code> configuration.</li>
+          </ul>
+        </div>
+
         <h3>Discipline codes</h3>
         <p>Discipline codes identify the engineering or functional group responsible for the document. They are defined per project and should be documented in the Master Deliverables List.</p>