Attribute groups to registered and unregistered authors #37

Open
opened 2026-11-01 20:11:54 +00:00 by viacheslavshuka · 0 comments

Authorship describes who wrote a block, round, or package. It must remain independent of ownership, collaboration, and test organization.

Acceptance criteria

  • Group editors can select a Quorum account, select a rating player profile, or enter an author's name without creating an account.
  • A jointly written block can name several authors without splitting the block or assigning individual questions.
  • Attribution alone grants no permissions, creates no organizer role, and sends no invitation.
  • When an account verifies a rating profile, existing attribution for that same stable rating identifier links to the verified account.
  • This link preserves historical attribution and avoids duplicate representations of the verified person.
  • A matching manually entered name does not automatically link to an account.
  • Selecting a rating profile for attribution does not claim account-control verification. An attributed person still completes normal verification when registering.

Validation

Use two authors with identical display names and different rating identifiers. Assert that verification links only the matching identifier and never grants permissions. Cover joint authors, free-text attribution, and verification retries without duplicate attribution. Exercise the website form and API with unauthorized editors.

Dependencies

Authorship describes who wrote a block, round, or package. It must remain independent of ownership, collaboration, and test organization. ## Acceptance criteria - Group editors can select a Quorum account, select a rating player profile, or enter an author's name without creating an account. - A jointly written block can name several authors without splitting the block or assigning individual questions. - Attribution alone grants no permissions, creates no organizer role, and sends no invitation. - When an account verifies a rating profile, existing attribution for that same stable rating identifier links to the verified account. - This link preserves historical attribution and avoids duplicate representations of the verified person. - A matching manually entered name does not automatically link to an account. - Selecting a rating profile for attribution does not claim account-control verification. An attributed person still completes normal verification when registering. ## Validation Use two authors with identical display names and different rating identifiers. Assert that verification links only the matching identifier and never grants permissions. Cover joint authors, free-text attribution, and verification retries without duplicate attribution. Exercise the website form and API with unauthorized editors. ## Dependencies - [#35: Create and reuse author blocks, rounds, and packages](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/35). Provides attributable groups. - [#27: Complete registration through verified rating-profile control](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/27). Provides stable verified rating identifiers for attribution reconciliation. ## Related work - [#39: Let material owners invite collaborators and control group reuse](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/39) - [#47: Manage test co-organizers through accepted invitations](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/47) - [#71: Show tester and organizer activity rankings from recorded participation](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/71) - [#40: Cache external display metadata with explicit freshness](https://code.viacheslavshuka.com/viacheslavshuka/quorum/issues/40)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
viacheslavshuka/quorum#37
No description provided.