Overview
This article compiles the applied business logic of the OLsA platform in a format suitable for software requirements analysis and system review. The intent is to bridge operational rules, constitutional obligations, and backend enforcement.
Core requirement groups
- Alumni onboarding: duplicate active/pending applications are blocked, terms acceptance is required, and new self-registered applicants must verify email.
- Membership lifecycle: only active alumni may self-enroll; General and Life are the self-service types; Life requires at least 10 years since SSC.
- Membership activation: payment alone does not activate membership; self-service applications move to
pending_ec_approval. - Annual expiry: annual memberships expire automatically when the validity end date passes; Life membership does not expire.
- Governance controls: committee structure, EC assignments, elections, meetings, branches, and reinstatements enforce constitution-driven rules.
- Eligibility gates: job posting and resume-bank access depend on active membership or approved partner status.
Membership requirements summary
- Allowed admin member types: General, Honarary, Life.
- Founding Member is a separate boolean status, not a member type.
- Life members cannot remain in plain pending state.
- Validity for annual members runs to December 31 of the paid year.
Governance requirements summary
- EC seat counts are constitution-fixed by designation.
- A member can hold only one EC position at a time.
- At most two members from the same SSC batch may serve in the same EC.
- President, General Secretary, and Treasurer require minimum SSC seniority thresholds.
- Election commission members must be Life members and cannot be candidates in the same election.
Conclusion
The OLsA platform already operates as a rules-driven governance and membership system. The applied logic is strongest around membership eligibility, constitutional compliance, approval workflows, and access control for member-only platform features.