# Default project-rollup Risk Register spec, served by zddc-server
# when no operator-supplied table.yaml exists at <project>/rsk/.
#
# This view aggregates every risk row from every party under
# <project>/archive/. Each synthetic row is backed by the real file
# at <project>/archive/<party>/rsk/<file>.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 <project>/archive/<party>/ folder, and writes
# the row inside its rsk/ subfolder. The party folder must already
# exist (create it via the SSR view).

title: Project Risk Register (all parties)
description: Every risk 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/<party>/rsk/ folder.

columns:
  - field: $party
    title: Package
    width: 7em
  - field: id
    title: ID
    width: 6em
  - field: title
    title: Risk
  - field: category
    title: Category
    width: 10em
  - field: likelihood
    title: L
    width: 4em
  - field: impact
    title: I
    width: 4em
  - field: severity
    title: Sev
    width: 5em
  - field: owner
    title: Owner
    width: 12em
  - field: status
    title: Status
    width: 9em
    enum: [open, mitigated, accepted, closed]
  - field: dueDate
    title: Due
    format: date
    width: 8em

defaults:
  sort:
    - { field: severity, dir: desc }
    - { field: $party, dir: asc }