From 617351f11d262aab0edd142214d037e0c2b00b8f Mon Sep 17 00:00:00 2001 From: ZDDC Date: Thu, 21 May 2026 15:46:34 -0500 Subject: [PATCH] reference: note zddc-server tracking-number defaults MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- reference.html | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/reference.html b/reference.html index eed046d..e2f257c 100644 --- a/reference.html +++ b/reference.html @@ -217,6 +217,14 @@ status = "IFA" / "IFB" / "IFC" / "IFD" / "IFI" / "IFP" / "IFR" / "IFU" / "

Rule: corporate placeholder. 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 000000 — any value works as long as it is easily recognizable as a corporate-scope marker and could not be mistaken for a real project number (e.g., 000000, CORP, HQ). 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.

+
+

zddc-server defaults. The schemas above are deployment-agnostic — any of them is a valid tracking number. The zddc-server reference implementation ships the Basic schema by default (originator-project-discipline-type-sequence), plus the optional per-deliverable [suffix] (a hyphenated part marker such as -A for an appendix). Two deployment behaviours are worth knowing:

+
    +
  • originator is bound to the party folder. Under archive/<party>/, the server sets originator 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.
    • +
  • phase and area are off by default. Because they are project-wide (all-or-nothing across a project), the default omits them; a project that needs them enables them on every deliverable by extending the schema in its .zddc configuration.
    • +
+
+

Discipline codes

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.