How meVSreps is intended to work

The Hooper rebuild is designed around a simple claim: constituent preference on a specific issue should be visible next to the official action taken by the representative responsible for that issue.

The current implementation already enforces one resident vote per issue, keeps officeholder history separate from the office itself, and treats meeting imports as source records that must be curated into item-level public issues.

1. 1Every public issue should map to a real agenda item, ordinance, motion, or recorded public action.
2. 2Each issue should link to at least one official source such as an agenda packet, minutes, recording, or vote record.
3. 3Constituent responses should be limited to verified residents in the applicable jurisdiction and district.
4. 4One verified constituent should be able to submit only one response per issue.
5. 5Majority signal is based on the leading constituent response. A tie or zero-vote state produces no majority signal.
6. 6Official alignment is only scored when the majority signal is SUPPORT or OPPOSE and the official vote is SUPPORT or OPPOSE.
7. 7ABSTAIN, ABSENT, and majority-UNDECIDED outcomes remain visible on the record but do not count toward alignment percentages.

This methodology is still evolving. Verification remains admin-reviewed, and agenda import quality depends on the structure of Hooper's public source pages and documents.