Why this comparison matters
The OLsA platform implements many constitutional rules directly in code. However, some rules are only partially enforced or represented mainly in interface text and workflows.
Areas with strong implementation alignment
- Committee structure: constitution-approved EC designations and exact seat counts are enforced.
- EC eligibility: one member-one post, SSC batch limits, and seniority thresholds are enforced.
- Elections: commission formation timing and schedule publication timing are enforced.
- Reinstatement: 2/3 EC approval logic is enforced.
- Meetings: notice periods are enforced by meeting type.
Areas with partial implementation
- Branch eligibility: the minimum 25-member rule is enforced, but the “at least 3 SSC batches” portion is not fully validated in controller logic.
- Election candidacy: duplicate same-position registration is blocked, but the broader “one person, one post in an election” rule may need stronger cross-position enforcement.
- Policy visibility vs backend validation: several policy statements appear in UI and content, but not all are mirrored by explicit backend checks.
Operational interpretation
From a compliance perspective, the platform is already strong in governance-heavy areas. The remaining gaps are mostly edge-condition validations and broader cross-record consistency rules.
Recommended next focus
- Add branch batch-diversity validation.
- Strengthen election candidate uniqueness across all positions within a single election.
- Review policy statements that should become backend-enforced rules.