ZDDC
73e34bed5e
Adds the risk register as a sibling of MDL under archive/<party>/, and
three project-level virtual aggregations at <project>/{ssr,mdl,rsk}:
- SSR aggregates archive/<party>/ssr.yaml; "+ Add row" materializes a
new party folder (mkdir + auto-own .zddc + ssr.yaml). Renames go
through X-ZDDC-Op: ssr-rename, which os.Rename's the party
directory so every row inside follows. Party name doubles as the
folder name (no opaque IDs) and is path-derived on read.
- MDL/RSK rollups list every deliverable / every risk across all
parties with a derived `party` column; "+ Add row" is suppressed
because party affiliation is ambiguous in the aggregate view.
All four virtual roots are declared `virtual: true` in
defaults.zddc.yaml. Spec/form bytes come from six new embedded
defaults (default-rsk.*, default-ssr.*, default-project-{mdl,rsk}.*)
served via a generalized IsDefaultSpec/IsDefaultSpecAbs that replaces
the MDL-only recognizer. Listing synthesis lives in fs/tree.go;
ACL on each synthetic row evaluates against the canonical
archive/<party>/ chain so non-owners see rows read-only. PUT/DELETE
through virtual URLs rewrite to canonical paths in fileapi.go via
sibling-shape blocks that don't touch the ACL gate. SSR row DELETE
returns 405 (delete the party folder via the archive view).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
56 lines
1.4 KiB
YAML
56 lines
1.4 KiB
YAML
# 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 derived from the row's source folder (path-injected by
|
|
# the server, not stored in the YAML).
|
|
#
|
|
# + Add row is suppressed in this view because the party affiliation
|
|
# would be ambiguous — add risks at the per-party path
|
|
# (<project>/archive/<party>/rsk/) and they'll appear here on next
|
|
# load.
|
|
|
|
title: Project Risk Register (all parties)
|
|
description: Every risk across all parties under archive/. Click a row to edit; add rows at the per-party RSK view.
|
|
|
|
addable: false
|
|
|
|
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 }
|