Matrices, tables and analysis panels
CRUD / data-access matrix
Which actor Creates, Reads, Updates and Deletes which entity — the access contract as a grid.
matrix.crud@1New DDN source
Why use it?
Access questions get answered at the cell instead of in a meeting.
When it helps
Permission reviews, API design, or onboarding to a data model.
How to read it
- Read actor against entity: the letter is the permission.
- An empty row is an inaccessible entity — deliberate or defect?
What you need
- The actors
- The entities
- The permissions per cell
Things to check
- Do not write "admin" as the actor — name the role.
- Do not leave D without an owner for retention questions.
Scope of this diagram
Declared permissions only; the grid is documentation, not an enforcement point.
Work with the converted example
- Open the viewer and select
crud. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.