4
organizer-forwarded reports
Stored privately with source and method limits.
Try it.
Leave a trace.
This ledger separates invitations, hands-on trials, scripted checks, product changes and retests. It is a record of what happened—not a wall of endorsements.
GitHub posts are public and require an account. Do not include names, contact details, class records, credentials, private data, or another person's words without permission.
01 / Current evidence
Private source records · public aggregateWhat is actually recorded.
2
hands-on core completions
Self-reported: one desktop and one iPhone.
1
script-assisted walkthrough
Tracked separately from hands-on use.
2
feedback-linked changes
Included in this release and covered by automated checks.
0
independent retests
A retest is counted only after someone tries the changed interaction.
The organizer reports that 40 people are available to participate. Availability is not counted as an invitation, response or completed trial. These four reports do not establish adoption or learning effectiveness.
Issues stay open until retested.
GERT-UX-001
Pending retest
The fixed meter can make the slider look unresponsive.
Reported in two hands-on trials and one script-assisted walkthrough.
Change included in this release; independent retest pending.
GERT-UX-002
Pending retest
The automatic interpretation could reveal the conclusion too early.
Reported in one script-assisted walkthrough and confirmed in source inspection.
Change included in this release; independent retest pending.
What makes a useful note?
Name the page you tried, what you expected, what happened, and whether you operated it by hand or used a script. One precise criticism is more useful than a general compliment.
What becomes public?
Only comments people publish themselves, or quotations they explicitly permit GERT to publish. Private replies remain private; this page may report de-identified totals and issue summaries.
Counting rule
A public comment is feedback, not automatically a completed trial. A fix is counted only after the code changes and passes checks. A retest is counted only after someone tries the changed interaction and reports the result.