Software Requirements: Mandator Membership & Invitations¶
Introduced in requirements baseline v2.0 (ADR-0108).
| ID | Requirement | Trace |
|---|---|---|
| REQ-MEM-001 | Membership in a mandator shall be a first-class recorded state (invited → accepted / declined / removed); invitation, acceptance, decline and removal shall each produce an audit event anchored at the mandator's own scope. | STR-028, STR-009; ADR-0108, ADR-0107 |
| REQ-MEM-002 | Membership shall begin only upon the invitee's acceptance; an invitation may carry named responsibilities (scope, role) which are applied at acceptance and acknowledged by it. Responsibilities that can no longer be applied shall degrade to a visible gap without failing the membership. | STR-028; ADR-0108 §5 |
| REQ-MEM-003 | Membership alone shall grant no content access; a member without roles sees nothing, and a non-member cannot observe that the mandator exists (nonexistence, not refusal). | STR-028, STR-004; ADR-0108 §1, ADR-0012 |
| REQ-MEM-004 | Invitation by email shall not disclose to the inviter whether the address is already known to the installation, and shall mint login credentials only through the identity provider — the system shall never receive or store the person's password. | STR-028, STR-013; ADR-0108 §3, ADR-0063 |
| REQ-MEM-005 | Email invitation links shall be single-use, unguessable, stored only as a digest, and expire; expired or unknown links shall be answered without revealing which they were. | STR-013; ADR-0108 §8 |
| REQ-MEM-006 | Ending a membership shall unassign the person's roles in that mandator and close the membership without affecting the person's existence or memberships elsewhere; only installation administration may deactivate a person. | STR-028; ADR-0108 §7 |