S11 · Guilds, institutions and player infrastructure
Implemented components; full stream acceptance is not yet demonstrated.
Current implementation: Membership, invitations, shared treasury approvals, facilities, access controls and contributions are executable.
Outstanding acceptance: Complete institution/home scope, governance and large-party coordination still need acceptance.
The four requirements below preserve the original release target. Their historic baseline is not used as a current completion score. This page does not mark the entire stream complete merely because related components are installed.
Reference
| Requirement | Required deliverable | Acceptance standard |
|---|---|---|
| S11.01 · Implement guild and institution ownership | Build membership, roles, treasury permissions, joint ownership, delegation, departure and succession. | One Discord moderator cannot seize in-game funds; members can leave without undefined asset loss or unfinished custody. |
| S11.02 · Build player facilities and homes | Implement construction inputs, production capacity, access, maintenance, useful improvements and absence behavior. | Existing scene scenery grants no free productive machinery; inactive property cannot permanently monopolize essential access. |
| S11.03 · Implement contribution and reputation | Attribute real campaign work, maker records, service quality and research with fraud-aware records. | Circular transactions, unused deliveries, overkill and self-issued contracts cannot manufacture prestige; legitimate support and industry are recognized. |
| S11.04 · Build party and community coordination | Implement recruitment, appointments, roles, loot agreements, public projects and useful mentorship. | Players can organize and finish expeditions without external spreadsheets being mandatory or leader discretion overriding escrow terms. |