Feedback from collaborators

Everything the power users and collaborators have told us about this site, each piece kept whole, with the Sherpa's comment beside every part of it, what was reproduced, and the brief it turned into. Kept by the Sherpa. People are not named; tests run by agents are marked as tests.

Counts as of 23 October 2026: one power user has joined with a key and sent five signed messages from the site, counted from the collaborators vault's first drain; the messages themselves stay in the vault until the editor says they may be published (their substance is in UF-003, the same power user's published report).

Every piece of feedback

Id	Received	Version	From	Kind	Points	In short
UF-001	2026-10-23	v0.8.1	a power user from the collaborators group, reading as a developer	person	10	Positive on the approach, the personas and the glossary. Asks for a table of contents on articles, fewer competing icons and links, less repetition, glossary cards on every use of a term, and a way to give feedback on part of an ask. Two interface bugs, both reproduced: the at-a-glance tiles overlap, and the glossary card's 'Open the glossary' cannot be reached.
UF-002	2026-10-23	v0.8.1	an agent tester (Claude in a browser on the editor's computer, by remo	agent test	12	The first test of the invitation link from the WhatsApp message. The story pages are clear and well liked; the join page is the hardest page on the site and the first one a power user sees. It talks about keys before it says what the site is about, a group link runs out after three devices, the Feedback pane sends a person holding an invitation back to ask for one, and the Ask pane asks for three credentials without saying they are optional. One point is held for the editor and security.
UF-003	2026-10-23	v0.8.2	power user 1	person	11	The first person through the whole invitation: joining works in one click, the success message is clear, and signed feedback goes out with a confirmation that says who reads it and when. The gaps are about what happens next: no sign that the key is waiting for approval, a message that contradicts itself after a refresh (a bug), nothing that says a private window or another browser has no key, no way to see the feedback you sent, one kind and one screenshot per message, an unexplained 'no vault' label, and the busy top of the page again.
UF-004	2026-10-23	v0.9.3	the editor, testing the forms	internal test	2	Internal test messages from the editor: a join request and a piece of feedback through the power users' forms. Both arrived intact and decrypt with the vault key alone. They are tests, not reader feedback, and are not counted as such; the request in the join note is routed like any other.

What happens next

Each piece of feedback becomes frictions in the friction log and a line in the brief to the conductor, who hands it to the member who owns the page. When a fix ships, the Sherpa checks it on the live site and closes the friction.