# Default project-rollup Master Deliverables List spec, served by # zddc-server when no operator-supplied table.yaml exists at # /mdl/. # # This view aggregates every deliverable row from every party under # /archive/. Each synthetic row is backed by the real file # at /archive//mdl/.yaml; the leading `$party` # column is the server-synthesized source-party identity (path- # injected on read, not stored in the YAML). The `$` sigil marks it # as system-managed — tables tool renders read-only and strips it # before submitting a row write. # # + Add row IS enabled here: the form schema's `party` field doubles # as the routing key — the server reads the submitted `party` field, # finds the matching /archive// folder, and writes # the row inside its mdl/ subfolder. The party folder must already # exist (create it via the SSR view). title: Project Deliverables (all parties) description: Every deliverable across all parties under archive/. Click a row to edit; + Add row uses the Package column to route the new row to the matching archive//mdl/ folder. columns: - field: $party title: Package width: 7em - field: originator title: Originator width: 8em # - field: phase # project-wide; uncomment with form.yaml + filename_format # title: Phase # width: 5em - field: project title: Project width: 8em # - field: area # project-wide; uncomment with form.yaml + filename_format # title: Area # width: 5em - field: discipline title: Disc. width: 5em - field: type title: Type width: 6em - field: sequence title: Seq. width: 5em - field: suffix title: Suffix width: 5em - field: title title: Deliverable - field: plannedRevision title: Rev. width: 5em - field: plannedDate title: Planned format: date width: 8em - field: status title: Status width: 6em enum: [DFT, IFR, IFA, IFC, AFC, AB] - field: owner title: Owner width: 12em defaults: sort: - { field: $party, dir: asc } - { field: plannedDate, dir: asc }