How the group keeps members safe.
Feedback
A collection of qualitative feedback from participants.
Matrix Overview
Where the feedback sits across your library — and where to act
Every member note is one atom; this grid is your whole adopted library crossed by section against stance. Read it to find the contested sections and the heaviest load, then click any cell to read the notes behind it and open the workshop on your copy. Scope-isolated — no one outside your scope sees these notes.
| Section × stance | Agree | Question | Doubts | All |
|---|---|---|---|---|
| minimum-safety-standards | ||||
| code-of-conduct | ||||
| All stances | 6 | |||
Every number traces to its verbatim notes — nothing here is a dead end. Resolve a note in the drawer and it updates in every view at once.
Triage Inbox
Revision worklist
Work your library by signal, not top to bottom. Each section keeps one resolve-state; the lanes sort by where the disagreement actually sits. 3 sections still carry unresolved feedback.
Needs action
3unworked notes — most contested firstResolved
1edit applied, or every note dispositionedTheme Pivot
What the feedback is actually about
The same notes, re-read by theme instead of by section. These codes are derived from the comments themselves — not a fixed taxonomy — so a concern you didn’t anticipate can surface as its own theme. Expand any to trace it to the verbatim notes.
How breaches and reviews are handled.
Synthesis Panel
Synthesise this level on request — claims stay linked to their notes.