Yokefellow - Governance & Future Structure
Congress
The constitutional governance draft for Yokefellow Congress, chamber design, voter verification, seat qualification, and limits.
Article 1. Nature of Congress
Section 1. Constitutional governing body.
Congress is Yokefellow’s constitutional governing body. It is the highest governing authority within the governed Yokefellow domain to the extent this Constitution assigns constitutional effect.
Section 2. Platform-domain legislature.
Congress governs Yokefellow as a platform domain rather than as a general state over private life. Its authority exists to govern the structured public rules of the Yokefellow system, not to claim general civil authority beyond the platform and the lawful relationships created within it.
Section 3. Governing domain.
Congress’s governing domain includes governed buckets, bucket recognition, bucket standards, bucket categories, governed taxes, governed disclosure duties, governed reporting duties, lawful participation structures, lawful rights structures, lawful builder pathways, lawful app-layer governance, lawful shared asset governance, lawful oversight structures, and other lawful frameworks attached to the governed Yokefellow system.
Section 4. Buckets as core surface.
Because buckets are Yokefellow’s core programmable funding and participation surface, congressional authority over governed buckets also shapes the rule environment for offerings, rights, redemptive paths, closeout expectations, apps, tools, integrations, and other governed surfaces built on Yokefellow’s rails.
Section 5. Builder and ecosystem effect.
Congress may govern the conditions under which outside builders, partners, operators, and other approved participants may widen the governed Yokefellow system through app surfaces, integrations, shared infrastructure, or other lawful platform extensions.
Section 6. Sale and proceeds governance after activation.
Once Congress is constitutionally active, Congress governs how the company’s yearly YES sale is publicly structured within the fixed YES emission schedule, which governed buckets are used to present that sale, what governed purposes those proceeds are directed toward, and how those proceeds are routed through governed use-of-proceeds buckets. Congress does not govern a raise or sale that began before Congress was constitutionally active except where this Constitution expressly provides continuing review or supervisory authority.
Section 7. Platform advancement purpose.
Congress exists not only to govern static rules, but to guide Yokefellow’s lawful advancement into stronger bucket structure, clearer participation paths, builder expansion, app surfaces, shared assets, infrastructure, public proof, and other lawful platform development over time.
Section 8. No constitutional theater.
Congress exists to govern something real. It shall not be treated as a decorative institution, symbolic council, or purely ceremonial branding layer detached from actual platform structure, actual records, and actual subject matter.
Article 2. Limits of Congressional Power
Section 1. Fixed YES emission boundary.
Congress does not set, expand, reduce, or otherwise alter the protocol-level yearly YES emission schedule by ordinary law. The yearly YES cap remains fixed by protocol.
Section 2. No general authority beyond the governed domain.
Congress governs Yokefellow as a platform domain. It does not act as a general civil authority over private life, private property outside the platform, or conduct outside the governed Yokefellow system except where a lawful platform relationship expressly brings that conduct within the governed domain.
Section 3. No fictional technical effect.
Congress may not treat an ordinary vote, act, approval, or resolution as if it instantly changes live contract behavior, deployment state, issuance capacity, settlement logic, custody logic, or other implementation-dependent conditions that still require a valid technical path.
Section 4. No false claim of completion.
No congressional act, approval, report, or public statement may represent a matter as technically complete where the required implementation, deployment, migration, enforcement, or integration path does not yet exist or has not yet been validly completed.
Section 5. Recognition does not fabricate capability.
Congress may recognize, approve, govern, restrict, suspend, tax, or subject a bucket, framework, app-layer surface, builder pathway, or other governed platform use to disclosure and reporting, but recognition or approval alone does not create technical capabilities the platform does not actually possess.
Section 6. Constitutional supremacy over ordinary law.
No ordinary act, resolution, committee rule, chamber rule, committee report, or platform practice may override a constitutional boundary established by this Constitution.
Section 7. No disguised constitutional change.
Congress may not use ordinary legislation, committee procedure, emergency posture, or platform implementation language as a disguised amendment of this Constitution.
Section 8. Public truth duty.
If Congress adopts a valid measure that is not yet implemented, the public record must distinguish clearly between adopted law, implementation in progress, implemented and live effect, and not yet technically available status.
Article 3. Bicameral Design
Section 1. Two chambers.
Congress consists of two chambers: the House and the Senate.
Section 2. Purpose of bicameral structure.
The bicameral structure exists so Yokefellow governance is shaped by both granular field representation and broader strategic continuity.
Section 3. House as granular chamber.
The House is the granular representation chamber. Its seats shall be defined more narrowly and specifically than Senate seats. House seats shall represent more acute profession, trade, degree, field-of-work, practice, and qualification tracks lawfully defined under this Constitution.
Section 4. Senate as strategic chamber.
The Senate is the strategic continuity chamber. Its seats shall be broader than House seats and shall represent higher-order sectors, grouped domains, strategic fields, and longer-horizon judgment across the governed Yokefellow system.
Section 5. Non-geographic representation.
Neither chamber is geographic. No House seat or Senate seat shall be based on state, district, territory, or other geographic apportionment. Both chambers shall be organized through profession-, trade-, practice-, degree-, and qualification-based representation as lawfully defined under this Constitution.
Section 6. Chamber relation.
The House and Senate are distinct but related chambers. The House provides sharper field-level representation. The Senate provides broader continuity, integration, review, and longer-horizon judgment. Neither chamber replaces the other.
Section 7. House terms.
House members serve one-year terms unless this Constitution expressly provides otherwise.
Section 8. Senate terms and classes.
Senate members serve three-year terms. Senate seats shall be divided into classes so that, as nearly as practicable, one-third of the Senate stands for election each year.
Section 9. No chamber without real work.
Neither chamber exists merely to mirror the other. Each chamber must have real constitutional work, real committee structure, and real subject matter within the governed Yokefellow system.
Article 4. Committees and Subcommittees
Section 1. Committee authority.
The House and Senate may establish standing committees, subcommittees, select committees, special committees, temporary committees, investigatory committees, emergency committees, joint committees, and other lawful working bodies needed to carry out congressional duties under this Constitution.
Section 2. Chamber control of chamber committees.
Each chamber controls its own committees. The House may create, organize, combine, divide, dissolve, and govern House committees by lawful House rules. The Senate may create, organize, combine, divide, dissolve, and govern Senate committees by lawful Senate rules.
Section 3. Joint committees.
Congress may create joint committees for cross-chamber work where both chambers determine that shared review, coordination, record development, investigation, standards work, or other subject-matter development is useful to the governed Yokefellow system.
Section 4. No independent committee sovereignty.
No committee or subcommittee possesses independent constitutional sovereignty separate from the chamber or congressional authority that lawfully creates and governs it. A committee or subcommittee acts only within the authority lawfully delegated to it.
Section 5. Standing committees.
Standing committees are the ordinary recurring working committees of a chamber and shall hold subject-matter jurisdiction under lawful chamber rules.
Section 6. Subcommittees.
A committee may establish subcommittees to handle narrower work lanes within the committee’s jurisdiction. Subcommittees may study, hear, investigate, review, refine, and recommend, but they do not replace the committee that creates them.
Section 7. Committee jurisdiction.
Committees may be assigned subject-matter jurisdiction over recognition, expansion, governed bucket standards, disclosures, reporting, participation structures, rights, fulfillment, builder pathways, app-layer governance, shared assets, infrastructure, yearly YES sale structure, proceeds routing, treasury supervision, elections, qualification, chamber administration, oversight, audit, public records, ethics, anti-capture, emergency review, continuity, and other lawful congressional work.
Section 8. Referral.
Legislative measures, oversight matters, hearings, investigations, qualification-related matters, sale and proceeds matters, ethics matters, records matters, emergency matters, and other congressional business may be referred to the appropriate committee or committees under chamber rules or joint rules consistent with this Constitution.
Section 9. Subcommittee review.
A committee may assign business to a subcommittee for preliminary review, hearing, investigation, drafting, revision, or recommendation. A subcommittee may report upward to its parent committee under lawful chamber rules.
Section 10. Hearings and investigations.
Committees and subcommittees may hold hearings, conduct review, request records, develop findings, and conduct investigations within their lawful jurisdiction. Further investigatory powers, including compulsory process if any, shall exist only where lawfully provided.
Section 11. Reports and recommendations.
Committees may issue reports, findings, recommendations, referrals, or refusals to report under lawful chamber rules. Subcommittees may issue preliminary reports or recommendations to their parent committees under lawful rules.
Section 12. No binding effect without lawful adoption.
No committee report, subcommittee recommendation, hearing result, investigative finding, or committee action has binding constitutional or ordinary-law effect unless adopted through the lawful process required for the relevant measure or action.
Section 13. Committee and subcommittee votes.
Chamber rules shall define committee and subcommittee voting procedure, quorum, reporting thresholds, referral practice, dissent treatment if any, and other internal procedural requirements consistent with this Constitution.
Section 14. Public record and transparency.
Committee records, subcommittee records, hearing records, reports, findings, votes, referrals, and other working records required by this Constitution or by lawful rule must be publicly maintained consistent with the public-record principle of this Constitution, except where lawful redaction of protected private information is necessary.
Section 15. Committee procedure by chamber rule.
Further rules for committee size, quorum, leadership, subcommittee creation, hearing procedure, witness handling, report procedure, cross-referral, member rights, decorum, scheduling, and posting duties may be established by lawful chamber rule or lawful enactment consistent with this Constitution.
Section 16. Committee membership fixed by the appendices.
Each standing committee consists of the seats assigned to it in Appendix A for the House and Appendix B for the Senate. No standing committee may exceed or fall below its assigned constitutional seat count unless this Constitution is amended.
Section 17. Committee officers.
Each standing committee shall elect a chair and a vice chair from among its own members by majority vote at its first meeting after each regular election cycle.
Section 18. Subcommittee membership.
A standing committee shall assign its own members to its subcommittees by majority vote. No person who is not a member of the parent committee may sit as a voting member of that committee’s subcommittee.
Section 19. Quorum.
Committee quorum consists of a majority of the lawfully occupied seats of the committee. Subcommittee quorum consists of a majority of the assigned voting members of that subcommittee.
Section 20. Reporting threshold and separate views.
A committee report or subcommittee report requires a majority vote of those present while quorum is present. One-third or more of the voting members of a committee may file separate views to be posted with the official report.
Article 5. The Electorate
Section 1. Verified electorate.
The electorate of Congress consists only of persons verified under Yokefellow’s lawful voter-verification rules. No person may vote in a congressional election without verified voter status.
Section 2. No automatic vote power.
Verified status alone does not create voting power. A person receives voting power only by lawfully acquiring YES and spending YES in accordance with this Constitution and the election laws adopted under it.
Section 3. Real YES requirement.
Congressional voting must be conducted with real YES. Congress shall not treat fictional, automatically issued, symbolic, or non-spendable election units as votes where this Constitution requires YES to be spent.
Section 4. Spend-to-vote rule.
Congressional voting is spend-to-vote. YES used to cast votes is spent in the election process and is not returned to the voter except where this Constitution expressly provides otherwise.
Section 5. House voting rule.
In House elections, each verified voter may spend up to one YES on each House seat contest. No verified voter may spend more than one YES in the same House race. A verified voter may spend YES separately across House seats as permitted by election law, subject to the one-YES-per-seat cap.
Section 6. Senate voting rule.
In Senate elections, each verified voter may spend up to 10,000 YES in a Senate election cycle. A verified voter may distribute that 10,000 YES Senate voting budget across the Senate seats open in that cycle however the voter chooses, subject to lawful counting, disclosure, and anti-fraud rules.
Section 7. Lawful acquisition and lawful use.
Only YES lawfully acquired and lawfully held or routed for voting under the election rules may be spent in congressional elections. Election law may define the eligible source, timing, settlement, and recording rules for YES used in voting.
Section 8. Verification before rollout.
Congressional elections may not begin unless Yokefellow has an operating voter-verification capability sufficient to establish verified voter status, prevent duplicate voter identities, and administer the congressional electorate under this Constitution.Article
Article 6. One Person, One Verified Voter Identity
Section 1. Single verified voter identity.
Each natural person may hold only one verified voter identity for purposes of congressional elections.
Section 2. No multiple voting identities.
No person may obtain, control, use, or attempt to use more than one verified voter identity, whether directly or indirectly, for voting, registration, candidacy support, vote routing, or any other electoral purpose.
Section 3. Person-based electorate.
The congressional electorate is verified-person-based, not unlimited-wallet-based. Wallet count alone does not create multiple voter identities, and no person may multiply voting power by splitting activity across multiple wallets, credentials, accounts, or fraudulent verification records.
Section 4. Registration review.
Before a person may vote in a congressional election, that person’s voter registration and verification record must be reviewed under the voter-verification system lawfully used by Yokefellow. No registration is final while a material identity challenge, duplicate-identity challenge, or fraud review remains unresolved.
Section 5. Duplicate-identity challenge.
A lawful challenge may be brought against a claimed voter identity where there is evidence of duplicate registration, false personhood, materially misleading identity records, coordinated identity laundering, or other facts suggesting that the claimed voter is not a unique natural person entitled to a separate verified voter identity.
Section 6. Investigation and temporary suspension.
Where a duplicate-identity challenge or fraud claim is materially credible, the affected registration or registrations may be placed into temporary suspended status pending investigation. A suspended voter identity may not cast valid congressional votes until the suspension is lifted.
Section 7. Fraud determination.
If review determines that a voter identity was obtained or used through fraud, duplicate identity abuse, materially false records, or coordinated false verification, that identity shall be invalid for congressional purposes and any votes cast through it may be voided.
Section 8. Vote invalidation and result correction.
Votes cast through a fraudulent or invalid voter identity may be removed from the contest totals. If the invalid votes are materially outcome-affecting, the affected result may be corrected, decertified, reopened, or otherwise remedied under the constitutional election procedures.
Section 9. Appeal.
A person whose registration is denied, suspended, or invalidated under this Article shall have a right to a recorded appeal through the lawful review path established for congressional elections. Final disposition must be entered into the official election record.
Section 10. No valid vote without valid identity.
No congressional vote is constitutionally valid unless it is cast through one verified voter identity belonging to one natural person lawfully entitled to vote in that election.
Section 11. No hidden parallel identities.
No chamber, committee, officer, operator, or platform process may knowingly tolerate hidden duplicate voter identities, parallel identity records, or informal exceptions to the one-person, one-identity rule.
Section 12. Public record of enforcement.
Final determinations of duplicate-identity fraud, vote invalidation, result correction, and related enforcement actions under this Article must be entered into the official election record, subject only to lawful redaction of protected private information.
Article 7. Congressional Voting Power and Chamber Voting Rules
Section 1. One seated member, one chamber vote.
Each lawfully seated House member has one vote in the House. Each lawfully seated Senator has one vote in the Senate.
Section 2. Seat-based voting power.
Congressional voting power belongs to the seat lawfully occupied in the relevant chamber. No member may cast more than one vote on the same question in the same chamber.
Section 3. Chamber separation.
House members vote only in the House. Senators vote only in the Senate. No member of one chamber may vote in the other chamber except where this Constitution expressly provides otherwise.
Section 4. Final chamber action by chamber vote.
No act, resolution, approval, censure, expulsion, committee report with adopted effect, or other chamber action has final force unless approved by the required vote of the chamber acting on it.
Section 5. Majority as the default rule.
Unless this Constitution expressly requires a higher threshold, a matter submitted for chamber action passes by a majority of votes lawfully cast in that chamber while quorum is present.
Section 6. Higher thresholds where required.
Where this Constitution requires a supermajority, enhanced threshold, or bicameral concurrence, the matter shall not pass by simple majority alone.
Section 7. Quorum requirement.
No chamber may conduct final binding business without quorum. Unless this Constitution expressly provides otherwise, quorum consists of a majority of the lawfully occupied seats of that chamber.
Section 8. Abstention.
A member may abstain unless recusal, discipline, or chamber rule requires nonparticipation. An abstention does not count as an affirmative vote and does not count as a negative vote.
Section 9. Recusal and nonparticipation.
Where recusal is required by this Constitution or by lawful chamber rule, the affected member shall not vote on the matter and shall not be counted as voting on that matter.
Section 10. No proxy voting by default.
No member may cast a proxy vote for another member unless this Constitution expressly authorizes it or lawful chamber rules adopted under this Constitution authorize a limited proxy procedure.
Section 11. Recorded votes.
Final chamber votes must be recorded in the official record in a form sufficient to show the measure, the chamber, the voting members, abstentions where recorded, and the result.
Section 12. Tie effect.
A tie vote does not pass the matter unless this Constitution expressly provides otherwise.
Article 8. Candidate Qualification
Section 1. Seat-specific candidacy.
Candidacy for Congress is seat-specific. A person may run only for a seat the person is qualified to hold under this Constitution and the lawful seat definition adopted for that seat.
Section 2. Qualification-based eligibility.
A person runs for Congress by qualification, not by geography. Each seat must be tied to a defined profession, degree, trade, field-of-work, practice, or other lawful qualification track sufficient to distinguish that seat from adjacent seats.
Section 3. Written seat qualification profile.
Every congressional seat must have a written qualification profile. That profile must state the seat’s field purpose, accepted qualification paths, accepted proof types, and explicit exclusions or limitations where adjacent but insufficient backgrounds do not qualify.
Section 4. Multiple valid proof paths.
Qualification may be established through multiple valid proof paths depending on the seat. Degree alone is not automatically the sole route unless the seat definition truly requires it.
Section 5. Acceptable proof.
Depending on the seat, acceptable proof may include degree, certification, license, apprenticeship, portfolio, practice history, employer verification, publications, field contribution, trade standing, or other equivalent records sufficient to show real qualification for that seat.
Section 6. Explicit exclusion of insufficient adjacency.
A seat may expressly exclude adjacent but insufficient backgrounds. A person is not qualified merely because the person works near the field, studies near the field, or holds a loosely related title if the written seat profile requires more specific proof.
Section 7. Verified qualification track.
A person may appear on the ballot only for seats the person’s verified qualification record lawfully supports.
Section 8. Multiple-seat qualification.
A person may qualify for multiple seats if the person meets the written qualification standard for each of them.
Section 9. One seat per election.
No person may seek more than one congressional seat in the same election. A person who qualifies for multiple seats must choose one seat for that election cycle.
Section 10. No qualification by desire alone.
No person is entitled to ballot access merely by wanting to run. Candidate qualification proof is a constitutional requirement of congressional legitimacy.
Article 9. Seat Definition
Section 1. No undefined seats.
No congressional seat shall constitutionally exist unless it is defined under this Constitution.
Section 2. Required elements of a valid seat.
A valid congressional seat must have all of the following:
a formal seat title
a chamber assignment
a defined field purpose
a written qualification profile
accepted proof paths
accepted proof types where needed for review
explicit exclusions where adjacent but insufficient backgrounds do not qualify
a distinction from adjacent seats sufficient to keep the seat intelligible and reviewable
Section 3. Formal title.
Every seat must have a formal title specific enough to identify the field, trade, practice, profession, or qualification track the seat represents.
Section 4. Chamber assignment.
Every seat must be assigned to either the House or the Senate. No seat may exist without chamber assignment.
Section 5. Field purpose.
Every seat must state the field purpose it exists to represent. That purpose must be specific enough to distinguish the seat from broad umbrella categories and from neighboring seats.
Section 6. Qualification profile.
Every seat must have a written qualification profile stating the qualification paths that may establish eligibility to hold the seat and the proof standards by which those paths may be reviewed.
Section 7. Accepted proof paths.
Every seat must identify the accepted proof paths by which a candidate may qualify.
Section 8. Explicit exclusions.
Every seat may state explicit exclusions or limitations where adjacent, partial, or loosely related backgrounds do not qualify. A seat definition is incomplete if it cannot distinguish what counts from what does not.
Section 9. Distinction from adjacent seats.
Every seat must be distinguishable from adjacent seats. No seat definition may remain so vague, duplicative, or overlapping that qualification review cannot be administered consistently.
Section 10. Named seats in both chambers.
The House must consist of specifically named seats. The Senate must consist of specifically named seats. Broad seat families, sector groupings, or classification maps may exist only as organizational indexes and not as substitutes for actual seat definitions.
Section 11. House precision rule.
Because the House is the granular chamber, House seat definitions must be narrower and more specific than Senate seat definitions.
Section 12. Senate breadth rule.
Because the Senate is the strategic continuity chamber, Senate seat definitions may be broader than House seats, but they must still be specifically named, qualification-based, and reviewable under this Constitution.
Article 10. Qualification Review Body
Section 1. Constitutional review body.
There shall be a constitutional qualification review body responsible for administering candidate eligibility for congressional seats.
Section 2. Core duty.
The qualification review body shall review candidate eligibility before ballot access and shall determine whether a candidate meets the written qualification profile of the seat the candidate seeks.
Section 3. Seat-specific review.
The qualification review body shall apply seat-specific standards. It shall review each candidacy against the formal title, field purpose, qualification profile, accepted proof paths, accepted proof types, and explicit exclusions lawfully attached to that seat.
Section 4. Candidate proof submission.
A candidate filing for a seat must include the proof materials necessary to evaluate the claimed qualification path for that seat. No candidacy is complete without the required proof record.
Section 5. Written decisions.
The qualification review body shall issue written eligibility decisions. Those decisions shall state whether the candidate is approved, denied, or suspended for further review, and shall identify the governing basis for the decision.
Section 6. Approval standard.
A candidate shall be approved only where the submitted proof materially satisfies the written seat qualification profile. Uncertain, partial, or weak proof is not enough for approval.
Section 7. Appeals.
A denied or suspended candidate may file one recorded appeal within the time window established for that election cycle. The appeal decision shall be final for that cycle unless material fraud is later proven.
Section 8. Precedent and consistency.
The qualification review body shall maintain a record of precedents, interpretations, and prior seat-eligibility decisions sufficient to support consistent administration across election cycles.
Section 9. Fraud and challenge jurisdiction.
The qualification review body shall have authority to investigate qualification fraud, materially false records, challenge petitions, duplicate or misleading qualification claims, and post-election eligibility disputes arising under this Constitution.
Section 10. Post-election review.
If material qualification fraud or material ineligibility is proven after an election, the qualification review body may refer the matter for vote invalidation, seat vacancy, special election, or other lawful constitutional remedy.
Section 11. No self-certification by candidates.
No candidate may satisfy constitutional qualification solely by self-description or unsupported self-attestation where the seat requires reviewable proof.
Section 12. Public record of qualification decisions.
Final qualification decisions must be entered into the official election record, subject only to lawful redaction of protected private information.
Article 11. Election Administration
Section 1. Regular elections.
Congressional elections shall be conducted on a regular yearly cycle. Each regular House cycle shall include all House seats. Each regular Senate cycle shall include the Senate class scheduled for election that year.
Section 2. Public notice.
Public notice of a regular congressional election must be posted before candidate filing opens. The notice must identify the House seats and Senate seats open in that cycle, the filing window, the qualification-review window, the voting window, and the certification window.
Section 3. Candidate filing window.
Candidate filing for a regular election must remain open for not less than fourteen calendar days.
Section 4. Qualification review window.
Qualification review shall begin when candidate filing begins and shall close before ballots or contests open for live voting. No candidate may remain on the ballot while still unresolved in qualification status.
Section 5. Ballot formation.
Only candidates approved through qualification review may appear in the final contest list for that election cycle.
Section 6. Voting window.
Each regular congressional election must remain open for a defined voting window of not less than seven calendar days.
Section 7. Vote recording and counting.
All votes must be recorded in a form sufficient to preserve auditability, contest totals, identity validity, and result review. Counting must be based only on valid votes cast under this Constitution.
Section 8. Ties.
If a final contest ends in a tie, a recount shall occur first. If the tie remains after recount, the tied contest shall proceed to a runoff election.
Section 9. Recount.
A recount shall occur automatically in any tie and may also occur where a challenge shows a material basis for recount review.
Section 10. Challenge window.
A provisional result shall remain challengeable for a defined post-count window of not less than seven calendar days before final certification.
Section 11. Provisional results.
At the close of the voting window, provisional contest totals shall be posted in the official election record.
Section 12. Certification of results.
Final certification of congressional election results shall be made by the Qualification Review Body after the challenge window closes and all material pending challenges affecting the contest are resolved.
Section 13. Vacancy declaration.
A vacancy shall be formally declared by the presiding officer of the affected chamber upon death, resignation, expulsion, disqualification, or other constitutionally recognized vacancy event. The declaration must be entered into the official record on the day it is recognized or, if that is not possible, on the next sitting day.
Section 14. Special election notice.
When a vacancy is declared, public notice of the special election must be posted within seven calendar days unless the seat is lawfully left for the next regular election under this Constitution.
Section 15. Election appeals.
Appeals concerning counting, provisional totals, identity invalidation, certification, or vacancy-related election procedure shall be decided by the Qualification Review Body. Its final decision for that cycle shall be entered into the official election record.
Section 16. Seating.
No person may be seated in Congress until the relevant contest has been finally certified and any material pending challenge affecting that contest has been resolved.
Section 17. Certification record.
Every final certification must identify the contest, the candidates, the winning result, any disqualified or invalidated votes materially affecting the contest, and the final effective date of certification.
Article 12. Terms, Classes, and Vacancies
Section 1. House terms.
House members serve one-year terms.
Section 2. Full House election each cycle.
All House seats shall be elected in each regular House election cycle unless this Constitution expressly provides otherwise.
Section 3. Senate terms.
Senate members serve three-year terms.
Section 4. Senate classes.
Senate seats shall be divided into classes so that, as nearly as practicable, one-third of the Senate stands for election each year.
Section 5. Class assignment.
Each Senate seat must be assigned to a class under this Constitution and the official Senate seat record. No Senate seat may remain unclassified.
Section 6. Events creating vacancy.
A congressional seat becomes vacant upon death, resignation, removal, disqualification, failure to qualify lawfully for office, or any other constitutionally recognized event that makes the member unable or ineligible to continue holding the seat.
Section 7. Duty to fill vacancies.
A vacant congressional seat must be filled through a constitutionally valid process. No seat may remain permanently vacant except where this Constitution expressly permits delay until the next regular election.
Section 8. Vacancy declaration.
A vacancy must be entered into the official congressional record when the triggering event is formally recognized.
Section 9. Chamber continuity.
A vacancy does not eliminate the seat itself. The seat remains part of its chamber and must return to lawful occupancy through the filling process required by this Constitution.
Section 10. No dual occupancy or inherited occupancy.
No congressional seat may be inherited, transferred, or occupied by substitution outside the lawful vacancy-filling process required by this Constitution.
Article 13. Proceedings, Referral, and Chamber Action
Section 1. Proceedings by recorded rule.
The House and Senate shall conduct business by recorded chamber rules consistent with this Constitution. No chamber may act through purely unwritten custom where this Constitution requires a recorded procedure.
Section 2. Introduction of measures.
A seated member may introduce a legislative measure in the member’s own chamber. No person who is not a lawfully seated member may introduce a congressional measure.
Section 3. Sponsorship and first reading.
Every introduced measure must identify its sponsor, any co-sponsors, its measure class, and its full text. Upon introduction, the measure shall receive a first reading and shall be entered into the official record.
Section 4. Referral to committee.
The presiding officer of the chamber shall refer an introduced measure to the appropriate standing committee no later than the next sitting day after introduction.
Section 5. Subcommittee path.
If a committee assigns a matter to a subcommittee, that matter must first be reported from the subcommittee to the parent committee before it may be reported to the floor, unless this Constitution expressly provides otherwise.
Section 6. Subcommittee passage.
A subcommittee report requires a majority vote of the assigned subcommittee members while quorum is present. A failed subcommittee report does not reach the floor unless the parent committee withdraws the matter from the subcommittee or the chamber discharges it under this Article.
Section 7. Committee reporting.
A committee may adopt, amend, reject, table, or refuse to report a measure. A committee report to the floor requires a majority vote of the committee while quorum is present.
Section 8. Floor calendar.
A measure reported from committee shall be placed on the chamber calendar by the clerk or secretary of that chamber in the order reported, unless the chamber reorders the calendar by majority vote.
Section 9. Mandatory posting before floor vote.
No measure may receive a final floor vote until its full reported text and committee report have been publicly posted for at least seventy-two hours, except where the chamber waives that waiting period by a three-fifths vote for an emergency measure.
Section 10. Debate and recognition.
The sponsor of a measure shall have the first right of recognition on that measure. The presiding officer shall then recognize opposition and further speakers under chamber order. Unless the chamber sets a different limit by majority vote, floor debate on a measure shall proceed with an opening period of twenty minutes for the sponsor side, twenty minutes for the opposition side, and further five-minute recognitions thereafter.
Section 11. Amendments.
All amendments must be submitted in writing and entered into the record before a vote on the amendment occurs. No amendment shall be adopted unless it is read or publicly posted in full before the vote.
Section 12. Germaneness.
Amendments must be germane to the measure under consideration unless the chamber waives germaneness by majority vote.
Section 13. Discharge.
If a committee has not reported a referred measure within twenty-one calendar days after referral, the sponsor may file a discharge motion. A discharge motion passes by majority vote of the chamber and places the measure directly on the chamber calendar.
Section 14. Recorded action required.
No final chamber vote, committee report with adopted effect, oversight finding with governed effect, disciplinary action, or other final official action shall be constitutionally valid unless it is entered into the official record.
Section 15. Joint action.
Where this Constitution requires action by both chambers, the House and Senate shall act through the bicameral process required for the relevant class of measure. No chamber may pretend to speak for Congress as a whole without the required bicameral basis.
Section 16. Special and emergency sessions.
The House and Senate may hold special sessions and emergency sessions under recorded chamber rules consistent with this Constitution. No special or emergency session may be used to evade the thresholds, transparency duties, or constitutional limits otherwise governing congressional action.
Article 14. Committee and Subcommittee Procedure
Section 1. Standing committees.
Standing committees are the ordinary working committees of a chamber and shall hold recurring subject-matter jurisdiction under lawful chamber rules.
Section 2. Subcommittees.
A standing committee may establish subcommittees to handle narrower work lanes within the committee’s jurisdiction. Subcommittees exist to study, hear, review, investigate, refine, and recommend.
Section 3. Subcommittees do not replace committees.
A subcommittee is subordinate to the committee that creates it. No subcommittee possesses independent constitutional sovereignty or permanent jurisdiction outside the authority delegated by its parent committee and chamber.
Section 4. Hearings.
Committees and subcommittees may hold hearings under lawful rules. Hearing rules shall define notice, witness handling, documentary submission, questioning rights, and public posting duties consistent with this Constitution.
Section 5. Investigations.
Committees and subcommittees may conduct investigations, request records, and develop factual findings within their lawful jurisdiction. Further investigatory powers, including compulsory process if any, shall exist only where lawfully provided.
Section 6. Committee reports.
A committee may issue reports, findings, recommendations, record summaries, and legislative referrals. A subcommittee may issue preliminary reports or recommendations to its parent committee under lawful rules.
Section 7. Committee vote.
Chamber rules shall define how committees and subcommittees vote, what quorum is required, how dissent or minority views if any are handled, and how a matter is reported upward.
Section 8. Quorum.
No committee or subcommittee may conduct final business without the quorum required by lawful chamber rules. Hearing or discussion rules for below-quorum informational sessions may be defined by chamber rules.
Section 9. Multi-referral and joint jurisdiction.
Chamber rules may allow multiple committees to share review of a matter where jurisdictions overlap. Joint committees may be used for cross-chamber coordination where both chambers lawfully agree.
Section 10. Committee findings are not self-executing.
No committee report, subcommittee recommendation, hearing result, or investigative finding has binding constitutional or ordinary-law effect unless adopted through the lawful process required for the relevant measure or action.
Section 11. Public records of committee work.
Committee agendas, hearing notices, reports, votes, findings, witness materials where lawfully public, and other committee records required by this Constitution or chamber rule shall be publicly maintained.
Section 12. Committee decorum and order.
Each chamber may adopt further rules for witness order, questioning, member conduct in hearing, time limits, evidentiary order, public posting deadlines, and related procedural discipline for committee and subcommittee work.
Article 15. Rules of Decorum, Duties, and Discipline
Section 1. Duty of orderly conduct.
Members, officers, and constitutionally relevant congressional actors shall conduct themselves in a manner consistent with orderly proceedings, truthful public record, lawful process, and the governed trust described by this Constitution.
Section 2. Decorum in chambers and committees.
The House, Senate, committees, and subcommittees may adopt decorum rules governing speaking order, interruptions, relevance, disorderly conduct, abusive obstruction, witness treatment, and other conduct necessary for usable proceedings.
Section 3. Duty of attendance and active work.
Members have a duty of attendance, participation, and active work consistent with chamber rules and lawful compensation standards. Chronic nonparticipation may be disciplined under lawful procedures.
Section 4. Duty of truthful presentation.
No member may knowingly present false procedural status, false vote status, false implementation status, false qualification claims, false reporting status, or other materially false official representation in congressional proceedings.
Section 5. Disclosure before participation.
A member must disclose any material conflict, direct personal stake, immediate financial interest, or other constitutionally relevant relationship before debating, voting, reporting, or otherwise participating in the affected matter.
Section 6. Recusal objection.
Any seated member of the relevant chamber, or any voting member of the relevant committee or subcommittee, may raise a recusal objection before final action on a matter.
Section 7. Interim status pending recusal ruling.
Once a recusal objection is raised, the challenged member may answer factual questions about the claimed conflict but may not vote, report, or move the matter until the objection is resolved.
Section 8. Recusal ruling.
For floor matters, the chamber shall decide the recusal objection by majority vote without the challenged member voting. For committee or subcommittee matters, the relevant body shall decide the recusal objection by majority vote without the challenged member voting. A tie sustains the recusal.
Section 9. Effect of recusal violation.
If a member participates in violation of a required recusal and that participation was materially outcome-affecting, the affected action may be vacated and must be reconsidered without the improper participation.
Section 10. Disorder does not create validity.
No chamber or committee action becomes valid merely because it occurred in a disorderly proceeding. Where lawful procedure required notice, quorum, vote, record, recusal, or other mandatory process, failure of that process may invalidate the action under lawful review.
Section 11. Duty to preserve institutional legibility.
Members and officers shall not use decorum rules, secrecy, procedural gamesmanship, false emergency posture, or record manipulation to defeat the public-record principle or to conceal the real basis of congressional action.
Section 12. Further chamber rules.
The House and Senate may adopt further decorum, attendance, discipline, and work rules consistent with this Constitution, including committee decorum, witness conduct rules, filing deadlines, recognition practice, voting conduct, and record-correction procedures.
Section 13. Compensation tied to active work.
Congressional compensation shall be earned only through active office and active work. Symbolic title-holding alone does not earn full compensation.
Section 14. Minimum active-work standard.
Unless excused by illness, emergency, or lawful recusal, a member must attend at least two-thirds of scheduled chamber sittings and two-thirds of assigned committee and subcommittee meetings in a compensation period to remain in full active-work standing.
Section 15. Compensation consequence for chronic nonattendance.
A member who falls below the constitutional active-work standard may have compensation reduced or suspended by majority vote of the member’s chamber after recorded notice and opportunity to respond.
Article 16. Legislative Instruments
Section 1. Recognized classes of measures.
Congress shall act through recognized classes of legislative measures established by this Constitution. Congress does not merely pass things. Its acts and resolutions must belong to a lawful class of measure.
Section 2. Constitutional Amendments.
Constitutional Amendments are measures that alter, add to, repeal, or replace this Constitution or any of its constitutional limits, structures, rights, duties, or institutional rules. No ordinary act or resolution may function as a Constitutional Amendment.
Section 3. Bucket Acts.
Bucket Acts are ordinary legislative measures governing the bucket system. They may define or alter governed bucket rules, categories, structures, permissions, processes, duties, and other lawful features of the governed bucket domain.
Section 4. Recognition Acts.
Recognition Acts are measures governing whether a bucket, category, framework, app-layer surface, integration class, builder pathway, or other governed use of Yokefellow’s rails is recognized, approved, restricted, suspended, or otherwise placed into lawful standing within the governed platform domain.
Section 5. Standards Acts.
Standards Acts are measures establishing, revising, or repealing governed platform standards, qualification standards, disclosure standards, reporting duties, operational standards, and other lawful rule frameworks needed to make the governed Yokefellow system legible and administrable.
Section 6. Tax Acts.
Tax Acts are measures establishing, revising, suspending, phasing, or repealing governed bucket taxes, governed platform taxes, or other lawful tax structures within the constitutional authority of Congress.
Section 7. Sale and Proceeds Approval Acts.
Sale and Proceeds Approval Acts are measures approving how the company’s yearly YES sale is publicly structured once Congress is constitutionally active, which governed buckets are used to present that sale, what governed purposes those proceeds are directed toward, and how those proceeds are routed through governed use-of-proceeds buckets. These Acts do not change the protocol-level YES emission schedule itself.
Section 8. Oversight Resolutions.
Oversight Resolutions are measures used to conduct review, inquiry, supervision, censure, reporting demands, investigations, hearings, findings, or other lawful oversight functions within the governed Yokefellow system. Oversight Resolutions do not amend this Constitution by implication.
Section 9. Advisory Resolutions.
Advisory Resolutions are non-binding measures used to state guidance, recommendation, policy preference, interpretation, or other advisory judgment without creating binding constitutional or ordinary-law effect unless another lawful measure adopts that effect.
Section 10. No disguised measures.
No measure may be treated as belonging to a class of greater or different authority than the class under which it was lawfully adopted. A resolution may not be used as a disguised amendment. An ordinary act may not be used as a disguised constitutional change.
Section 11. Further lawful subtypes.
Congress may establish additional lawful subtypes, procedures, or naming conventions for legislative measures by Constitutional Amendment or by lawful enactment where this Constitution permits it, provided that no such subtype erases the constitutional distinction between amendments, ordinary binding acts, oversight measures, and advisory measures.
Article 17. Passage Thresholds
Section 1. No measure without the required threshold.
No legislative measure is valid unless it receives the passage threshold required for its class under this Constitution.
Section 2. Ordinary acts.
Bucket Acts, Recognition Acts, Standards Acts, and other ordinary binding acts pass by a majority in both chambers unless this Constitution expressly requires a higher threshold.
Section 3. Sale and Proceeds Approval Acts.
Sale and Proceeds Approval Acts pass by a majority in both chambers unless this Constitution expressly requires a higher threshold for a particular sale structure or related enactment.
Section 4. Tax Acts.
Tax Acts that impose a new governed tax or increase an existing governed tax require a three-fifths vote in both chambers. Tax Acts that reduce, suspend, phase down, or repeal an existing governed tax pass by a majority in both chambers unless this Constitution expressly provides otherwise.
Section 5. Constitutional Amendments.
Constitutional Amendments require a two-thirds vote in both chambers and any further ratification rule required elsewhere in this Constitution.
Section 6. Expulsion and severe disciplinary action.
Expulsion of a member from a chamber, or other severe disciplinary action that removes or nullifies a member’s right to continue serving, requires a two-thirds vote of the chamber to which that member belongs.
Section 7. Chamber-specific oversight measures.
An Oversight Resolution that is chamber-specific and does not create binding platform-wide effect passes by a majority of the chamber adopting it.
Section 8. Joint oversight measures with binding effect.
An Oversight Resolution that purports to create binding platform-wide effect, require formal cross-chamber findings, or compel action beyond one chamber’s internal proceedings passes by a majority in both chambers unless this Constitution requires a higher threshold.
Section 9. Advisory Resolutions.
An Advisory Resolution passes by a majority of the chamber adopting it. A joint Advisory Resolution intended to speak for Congress as a whole passes by a majority in both chambers.
Section 10. Temporary emergency action.
A temporary emergency measure requires a three-fifths vote in both chambers unless this Constitution expressly provides a different emergency rule. Any such emergency measure must be time-limited, subject to review, and incapable of functioning as a disguised Constitutional Amendment.
Section 11. No threshold evasion by relabeling.
No measure may avoid the threshold applicable to its real substance by being labeled as a lower class of act or resolution. The threshold follows the true legal effect of the measure, not merely its title.
Article 18. Transparency and Records
Section 1. Public-record principle.
Congress shall operate under a public-record principle. Its seat structure, qualification logic, legislative measures, votes, approvals, oversight findings, and other governed records must be publicly posted except where this Constitution permits narrow redaction for protected private information.
Section 2. Seat definitions and qualification standards.
The official record of Congress must publicly include the formal definition of every House seat and Senate seat, including the seat title, field purpose, qualification profile, accepted proof paths, and explicit exclusions sufficient to make the seat intelligible and reviewable.
Section 3. Candidate filings and proof summaries.
Candidate filings must be publicly posted. Candidate proof summaries must also be publicly posted in a form sufficient to show the basis of qualification while allowing protected private details to be redacted where necessary.
Section 4. Bills, amendments, and legislative text.
Bills, amendments, resolutions, and other legislative texts must be publicly posted in a form sufficient for public reading, comparison, and recordkeeping before and after final action.
Section 5. Committee and proceeding records.
Committee records, subcommittee records, hearing records, oversight proceeding records, and other congressional working records required by this Constitution must be publicly maintained except where lawful redaction is necessary for protected private information or active fraud review.
Section 6. Vote records.
Vote records must be publicly posted. The official record must show how each legislative measure, chamber contest, and other recorded congressional action was decided under the rules of this Constitution.
Section 7. Attendance and active-work records.
Attendance and other lawful active-work records of members must be publicly posted. Because congressional compensation is tied to active office and active work rather than symbolic title-holding, the public record must be sufficient to support that standard.
Section 8. Disciplinary records.
Disciplinary actions, censure, suspension, expulsion proceedings, and related final findings must be publicly posted, subject to lawful redaction of protected private information where necessary.
Section 9. Compensation records.
Congressional compensation rules and compensation records must be publicly posted in a form sufficient to show how the compensation pool operates and how members are paid for active office and active work.
Section 10. Yearly YES sale and proceeds approvals.
Once Congress is constitutionally active, yearly YES sale approvals, sale-bucket approvals, use-of-proceeds-bucket approvals, and related reporting obligations must be publicly posted.
Section 11. Oversight findings.
Oversight findings, formal reviews, and other final congressional findings with governed effect must be publicly posted so the governed system remains legible and reviewable.
Section 12. Redaction boundary.
Protected private information may be redacted where lawful and necessary, but redaction may not be used to defeat the public-record principle, conceal the legal basis of congressional action, or hide the existence of a qualification, vote, approval, compensation rule, or final finding that this Constitution requires to be public.
Section 13. No secret constitutional government.
No seat definition, qualification standard, binding legislative act, final vote record, yearly YES sale approval, use-of-proceeds approval, or final oversight finding has constitutional effect while kept wholly secret from the public record unless this Constitution expressly provides otherwise.
Article 19. Ethics and Anti-Capture
Section 1. Constitutional duty of integrity.
Congressional office is a governed trust inside the Yokefellow system. No person may hold, seek, influence, or exercise congressional power through fraud, bribery, hidden conflicts, collusive capture, or other conduct that defeats the integrity of qualification-based representation.
Section 2. Credential and qualification fraud prohibited.
No person may obtain ballot access, office, committee standing, or other congressional advantage through credential fraud, materially false qualification claims, forged records, misleading seat-specific proof, or concealment of disqualifying facts.
Section 3. Verification fraud and multi-identity abuse prohibited.
No person may obtain or use congressional voting power through coordinated false verification, duplicate voter identities, multi-identity voting, identity laundering, or other fraudulent personhood schemes.
Section 4. Bribery and unlawful vote-buying prohibited.
Bribery is prohibited. Vote-buying is prohibited except where disclosed campaign support or other lawful political support is expressly permitted under this Constitution.
Section 5. Undisclosed conflicts prohibited.
No member, candidate, reviewer, or other constitutionally relevant actor may participate in congressional action while concealing a material conflict of interest that bears on the seat, the act, the proceeding, the governed bucket, the governed tax, the recognition decision, or the company YES sale and proceeds structure at issue.
Section 6. Undisclosed self-dealing prohibited.
Undisclosed self-dealing is prohibited in congressional acts touching governed buckets, taxes, recognition, standards, compensation, yearly YES sale approvals, use-of-proceeds approvals, or related governed platform structures.
Section 7. Collusive seat capture prohibited.
No coordinated group, guild, firm, operator bloc, credential cartel, builder bloc, or other organized interest may collusively capture seats, qualification review, election administration, or congressional action through hidden coordination, fraudulent exclusion, reciprocal sham qualification, or comparable manipulation designed to defeat the constitutional purpose of qualification-based representation.
Section 8. Recusal duty.
A member, candidate, reviewer, or other constitutionally relevant actor must recuse from matters where a material conflict, direct personal stake, immediate financial interest, or other constitutionally significant conflict makes participation improper under this Constitution.
Section 9. Disclosure duty.
Material conflicts, material financial interests relevant to congressional action, qualification-relevant conflicts, and other material relationships necessary to prevent concealed capture of the governed system must be disclosed in the official record.
Section 10. Enforcement and remedy.
This Constitution permits investigation, challenge, censure, suspension, removal, vote invalidation, vacancy, referral, or other lawful remedy where conduct prohibited by this Article is proven.
Section 11. No profession-based guild government.
This Constitution shall not be interpreted to protect closed professional cartels, inherited gatekeeping, nepotistic field capture, or insider-only rule under the pretense of qualification. Qualification exists to make representation real and reviewable, not to recreate the same exclusionary patterns Yokefellow is meant to resist.
Section 12. No hidden coordinated support structures.
No hidden coordinated support structure may be used to conceal effective control over a seat, caucus, review body, committee, or congressional act.
Article 20. Congressional Power Over the Company YES Sale
Section 1. No power over the protocol-level emission schedule.
Congress does not set, expand, reduce, or otherwise alter the protocol-level YES emission schedule by ordinary law. The yearly YES cap remains fixed by protocol.
Section 2. Sale-structure authority after activation.
Once Congress is constitutionally active, Congress approves how the company’s yearly YES allocation is publicly structured within the fixed YES emission schedule.
Section 3. Sale-bucket approval.
Congress approves which governed buckets are used to present, organize, or publicly structure the company’s yearly YES sale.
Section 4. Proceeds-bucket approval.
Congress approves which governed use-of-proceeds buckets receive routed funds from the company’s yearly YES sale.
Section 5. Purpose and routing authority.
Congress approves what governed purposes the yearly YES sale is meant to support and how proceeds are routed among the governed proceeds structures established for those purposes.
Section 6. Disclosure, reporting, and proof requirements.
Congress may require disclosures, reporting duties, updates, receipts, proof records, and other lawful public-record obligations tied to the governed sale buckets and governed use-of-proceeds buckets.
Section 7. Supervision after launch.
Congress may supervise the governed sale structure and the governed proceeds structure once live, including oversight of whether the approved buckets, disclosures, routing rules, and reporting duties are being followed.
Section 8. No retroactive control over pre-congressional raises.
Congress does not govern a raise or yearly YES sale structure that began before Congress was constitutionally active unless this Constitution expressly grants continuing review, reporting, or supervisory authority over structures that remain live after activation.
Section 9. No disguised emission change.
No Sale and Proceeds Approval Act, bucket approval, proceeds-routing decision, or related congressional measure may be used as a disguised alteration of the fixed YES emission schedule.
Article 21. Implementation Boundary
Section 1. Governing measures are real measures.
Congress establishes valid governing measures within the authority granted by this Constitution. Those measures may govern rules, standards, recognitions, tax structure, sale approvals, disclosure duties, reporting duties, and other lawful obligations within the governed Yokefellow system.
Section 2. Measures take effect through the layer they belong to.
The live platform shall implement congressional measures through whatever layer the change actually belongs to. Where a measure belongs to policy, governance status, recognition, disclosure, reporting, bucket administration, election administration, or other governable platform procedure, it takes effect through that layer.
Section 3. Platform-configuration measures.
Where a congressional measure requires platform configuration, policy changes, disclosure changes, reporting changes, bucket-layer enforcement, election administration, or other offchain or platform-governed implementation, the measure becomes effective through that lawful implementation path.
Section 4. Technical-implementation measures.
Where a congressional measure would require future technical implementation, contract work, deployment changes, migration, indexing changes, execution wiring, or other implementation-dependent work, the measure becomes effective only through a valid implementation path sufficient to carry that measure into the live system.
Section 5. No fictional technical effect.
No act, approval, resolution, or other congressional measure may be represented as already technically effective where the necessary implementation does not yet exist or has not yet been validly completed.
Section 6. Recognition is not fabrication.
Congress may recognize, approve, govern, restrict, or deny lawful standing within the Yokefellow domain, but recognition alone does not create technical capability, contract functionality, issuance capacity, settlement behavior, or app behavior that the live system does not actually possess.
Section 7. Contract boundaries remain real.
Where durable system behavior depends on onchain enforcement, contract deployment, settlement logic, custody logic, recognized collection structure, or other technical boundaries identified in the live architecture, congressional intent must still pass through the valid implementation path that reaches those boundaries. Congress does not bypass technical reality by declaration alone.
Section 8. Public truth duty.
If a congressional measure has been validly adopted but is not yet fully implemented, the governed public record must distinguish between adopted law or approval, implementation in progress, implemented and live effect, and not yet technically available status.
Section 9. No disguised constitutional overclaim.
No chamber, committee, officer, operator, or platform surface may describe a congressional measure as producing a live technical result that the platform has not yet lawfully implemented.
Article 22. Amendment and Constitutional Hierarchy
Section 1. Constitutional supremacy.
This Constitution is the superior governing document of Congress and of the governed Yokefellow system to the extent this Constitution assigns constitutional effect. No ordinary act, resolution, approval, procedure, committee rule, chamber rule, or platform practice may override or conflict with this Constitution.
Section 2. Ordinary acts subordinate to the Constitution.
All Bucket Acts, Recognition Acts, Standards Acts, Tax Acts, Sale and Proceeds Approval Acts, Oversight Resolutions, Advisory Resolutions, and related enactments must operate within the limits of this Constitution. Any enactment inconsistent with this Constitution is invalid to the extent of the inconsistency.
Section 3. Amendment required for constitutional change.
No change to the constitutional structure, constitutional powers, constitutional limits, chamber design, electorate rules, voting model, seat-definition requirements, qualification framework, or other constitutional rule may take effect except through a Constitutional Amendment validly adopted under this Article.
Section 4. Amendment threshold.
A Constitutional Amendment requires a two-thirds vote in both chambers unless this Constitution expressly requires a higher threshold for a specially protected article or rule.
Section 5. Ratification rule.
If this Constitution requires ratification beyond chamber passage for a specified class of Constitutional Amendment, the amendment is not effective until that ratification rule is satisfied.
Section 6. No amendment by implication.
No ordinary act, resolution, interpretation, implementation step, repeated platform practice, or procedural convenience may amend this Constitution by implication.
Section 7. Protected constitutional articles.
This Constitution may designate certain articles, sections, or principles as specially protected. A specially protected constitutional rule may require a higher amendment threshold than the ordinary constitutional amendment threshold.
Section 8. Possible protected subjects.
Special protection may be applied to core constitutional identity rules, including the non-geographic and qualification-based character of Congress, the bicameral structure, the one-person one-verified-voter rule, the fixed protocol-level YES emission boundary, the requirement that seats be specifically defined and reviewable, and other foundational rules this Constitution expressly entrenches.
Section 9. No disguised constitutional repeal.
No amendment may be disguised as an ordinary act, and no ordinary act may function as a partial constitutional repeal by changing the practical meaning of a constitutional rule while avoiding the amendment process.
Section 10. Public record of constitutional change.
All proposed Constitutional Amendments, amendment texts, amendment votes, ratification records if any, and final constitutional updates must be publicly posted in the constitutional record.
Article 23. Activation and Rollout
Section 1. No automatic immediate activation.
Congress does not exist in full constitutional operation by default at launch. Congressional power begins only when this Constitution’s activation conditions are satisfied.
Section 2. Proof-before-governance principle.
Congress shall be activated only after Yokefellow has developed enough real bucket structure, operating proof, governance need, and institutional readiness for Congress to govern something real rather than hypothetical.
Section 3. Pre-congressional governance.
Before Congress is constitutionally active, Yokefellow may govern buckets, raises, sale structures, use-of-proceeds structures, platform rules, and related development through internal governance, founder governance, operator governance, or other lawful pre-congressional governance arrangements consistent with this Constitution’s activation framework.
Section 4. Minimum activation conditions.
Congressional activation requires, at minimum, a completed constitutional framework, a completed named-seat structure for both chambers, written qualification profiles for all seats, an operating qualification review body, an operating voter-verification capability sufficient to enforce the verified electorate rules, a formal election process sufficient to administer congressional elections, a public record system sufficient to support the transparency duties of this Constitution, and enough live bucket and platform development for congressional governance to have real subject matter.
Section 5. No election before readiness.
No congressional election may be held before the activation conditions required by this Constitution are satisfied.
Section 6. Limited initial activation permitted.
Congress may be activated in a limited initial form if this Constitution or a lawful activation measure expressly defines which powers are live, which remain withheld, and what further conditions must be met before full activation.
Section 7. Transfer of YES sale governance after activation.
Congressional authority over the company’s yearly YES sale structure, sale-bucket approval, use-of-proceeds-bucket approval, and related reporting or supervision begins only after Congress is constitutionally active, except where this Constitution expressly grants review or supervisory authority over continuing pre-congressional structures that remain live after activation.
Section 8. No retroactive automatic control.
Congress does not automatically acquire retroactive governing authority over a raise, sale structure, or proceeds structure that began before activation merely because Congress later comes into existence.
Section 9. Activation record.
Congress shall not be treated as constitutionally active unless the activation determination, the legal basis for activation, the readiness findings, and the effective activation date are publicly posted in the constitutional record.
Section 10. Full activation.
Full activation occurs only when the governed Yokefellow system is ready for Congress to exercise the constitutional powers assigned to it and any remaining withheld powers have been lawfully released under the activation framework.
Appendix A. House Seats and Committee Assignments
House 435.
44-seat committees
• Recognition and Expansion Committee — 44
• Subcommittee 1 — Recognition and Standing
1. Founder — knows real build from pitch.
2. Operator — knows whether something can actually run.
3. Accountant — tests whether the numbers are real.
4. Auditor — tests whether the proof holds up.
5. Lawyer — checks whether the structure is actually coherent.
6. Compliance Officer — sees whether it is fit to be governed.
7. Clerk — knows whether it can stay orderly and legible.
8. Journalist — pressure-tests the public story.
9. Researcher — separates evidence from assertion.
10. Project Manager — sees whether the plan is actually workable.
11. Paralegal — catches weak records and bad process discipline.
• Subcommittee 2 — Provisional, Restricted, and Pilot Status
12. Risk Manager — sees what should stay bounded.
13. QA Tester — catches “works once” versus “works reliably.”
14. Claims Adjuster — handles partial proof and messy edge cases.
15. Product Manager — sees what is usable but not yet mature.
16. Systems Administrator — spots fragile operating reality.
17. Property Manager — knows what is not truly ready for live use.
18. Teacher — sees whether ordinary people can safely navigate it.
19. Nurse — spots duty-of-care problems in early rollout.
20. Service Manager — knows when fulfillment is too soft for full launch.
21. Warehouse Manager — sees whether real capacity exists yet.
22. Contractor — knows when something is still pre-ready, not launch-ready.
• Subcommittee 3 — Sector Readiness and Proof Review
23. Chef — catches throughput lies and fulfillment pressure.
24. Farmer — catches seasonality lies and production fantasy.
25. Truck Driver — knows route truth and movement constraints.
26. Builder — sees whether physical delivery is real.
27. Electrician — spots fake operational readiness.
28. Manufacturer — separates prototype from repeatable output.
29. Video Producer — catches fake milestones and soft completion claims.
30. Event Producer — knows whether a live operation can really be carried.
31. Mechanic — spots hidden dependency and maintenance weakness.
32. Landlord — knows whether recurring obligations are actually manageable.
33. Community Organizer — tests whether the local participation claim is real.
• Subcommittee 4 — Outside Builders, Partners, and Widening
34. Software Engineer — judges whether the technical surface is real.
35. Product Designer — sees whether widening will create misleading user paths.
36. Data Engineer — catches weak state truth and bad data assumptions.
37. DevOps Engineer — knows whether scaling claims are credible.
38. Cybersecurity Analyst — spots widening risk before damage happens.
39. App Founder — brings builder-side reality.
40. Integrations Specialist — knows whether outside connections will actually hold.
41. IT Administrator — catches operational fragility behind the interface.
42. Platform Operator — knows what wider adoption will break first.
43. Solutions Engineer — tests whether outside users can really implement it.
44. Partner Manager — sees whether partner-facing expansion is actually workable.
• Bucket Standards, Disclosures, and Records Committee — 44
• Subcommittee 1 — Bucket Structure Standards
45. Operator — knows whether a bucket structure can actually be run.
46. Project Manager — sees whether the structure can hold across stages and milestones.
47. Product Manager — knows whether the participation path is coherent.
48. Business Analyst — catches weak logic and missing structure.
49. Process Manager — sees whether the workflow is actually administrable.
50. Contractor — knows when physical-project structure is too soft to trust.
51. Property Manager — catches recurring obligation structures that will break in use.
52. Event Producer — knows when a live-operating bucket is understructured.
53. Manufacturer — sees whether production-linked claims are structurally believable.
54. Builder — tests whether the promised structure matches the real work.
55. App Founder — knows whether a bucket-linked product surface is actually usable.
• Subcommittee 2 — Disclosure and User Reading Standards
56. Journalist — pressure-tests whether the public explanation is honest.
57. Teacher — sees whether normal people can actually understand the path.
58. UX Designer — catches misleading or unreadable user-facing structure.
59. Consumer Lawyer — spots disclosure that hides real obligations or limits.
60. Claims Adjuster — knows when the reading surface is too soft for contested outcomes.
61. Nurse — catches duty-of-care gaps hidden behind simple language.
62. Social Worker — sees when vulnerable users will misunderstand or get trapped.
63. Customer Support Manager — knows where people will predictably get confused.
64. Technical Writer — turns system truth into readable explanation.
65. Video Producer — understands staged communication and proof-facing clarity.
66. Researcher — separates real disclosure from decorative explanation.
• Subcommittee 3 — Reporting, Receipts, and Closeout
67. Accountant — knows what real reporting looks like.
68. Auditor — tests whether the reporting can survive review.
69. Bookkeeper — catches reporting that cannot be maintained over time.
70. Grant Manager — understands restricted-use tracking and use-of-proceeds proof.
71. Program Administrator — knows whether ongoing reporting duties are actually carryable.
72. Inspector — brings proof-through-verification discipline.
73. QA Analyst — catches reporting that looks complete but is not trustworthy.
74. Logistics Coordinator — understands receipts, handoffs, and proof of movement.
75. Property Manager — knows what real closeout looks like in recurring-use settings.
76. Project Manager — sees whether milestone reporting actually matches delivered work.
77. Video Producer — useful where visible completion proof matters.
• Subcommittee 4 — Public Record and Record Format Standards
78. Clerk — knows how records stay official, readable, and durable.
79. Records Manager — understands retention, order, and retrievability.
80. Archivist — sees long-horizon record integrity.
81. Librarian — understands public findability and usable organization.
82. Paralegal — catches weak filing logic and incomplete record structure.
83. Documentation Specialist — knows how formal records should be built and kept.
84. Data Engineer — sees where record systems lose truth at scale.
85. Compliance Officer — knows what has to be preserved for reviewability.
86. Election Administrator — strong on public-record legitimacy and process clarity.
87. Database Administrator — catches brittle storage and bad record architecture.
88. Information Governance Manager — ties retention, access, and record discipline together.
• Participation, Rights, and Fulfillment Committee — 44
• Subcommittee 1 — Offerings and Participation Paths
89. Product Manager — sees whether the participation path is actually coherent.
90. UX Designer — catches confusing or misleading entry flows.
91. Teacher — tests whether ordinary people can understand the path.
92. Community Organizer — knows whether people will actually enter and follow through.
93. Event Producer — understands structured entry, access, and participation sequencing.
94. Game Designer — spots weak participation logic, gating, and progression structure.
95. Service Manager — knows whether the promised path can be carried in practice.
96. Project Manager — catches weak sequencing, hidden steps, and fake simplicity.
97. App Founder — sees whether the path works in a real product surface.
98. Researcher — separates a usable path from a vague concept.
99. Customer Support Manager — knows where participants will predictably break down.
• Subcommittee 2 — Rights, Access, and Transfer Logic
100. Lawyer — checks whether rights are actually bounded and intelligible.
101. Paralegal — catches weak right definitions and bad scope discipline.
102. Systems Administrator — understands permission logic and scoped access.
103. Locksmith — brings the practical reality of access and controlled entry.
104. Property Manager — understands access rights tied to place and recurring use.
105. Librarian — strong on classification, scope, and clear user-facing meaning.
106. Archivist — sees how rights meaning can drift if boundaries are weak.
107. Product Designer — catches rights logic that users will misread in practice.
108. Compliance Officer — sees when transfer or access rules are too soft to govern.
109. Identity Administrator — understands who should be able to do what and where.
110. IP Lawyer — useful when rights, licenses, and use permissions blur together.
• Subcommittee 3 — Redemption and Fulfillment States
111. Chef — understands fulfillment under timing, spoilage, and throughput pressure.
112. Warehouse Manager — knows whether promised output can actually be allocated and sent.
113. Logistics Coordinator — sees whether redemption can really move to completion.
114. Contractor — understands staged delivery, punch-list reality, and incomplete fulfillment.
115. Manufacturer — separates one finished result from repeatable fulfillment.
116. Video Producer — catches fake completion and weak deliverable proof.
117. Mechanic — spots when “resolved” really means “temporarily patched.”
118. Nurse — understands duty-of-care in time-sensitive fulfillment.
119. Property Manager — knows whether access or use rights are actually being honored.
120. Event Producer — sees live fulfillment failure before it becomes public chaos.
121. Service Technician — understands real completion versus work still pending.
• Subcommittee 4 — Disputes, Exceptions, and Partial Completion
122. Claims Adjuster — excellent at messy facts, partial completion, and contested outcomes.
123. Auditor — tests whether the exception story is backed by records.
124. QA Tester — catches edge cases and failure paths the happy flow hides.
125. Mediator — useful when both sides have some claim to legitimacy.
126. Social Worker — sees where exceptions hit real people hardest.
127. Customer Support Manager — understands disputes at the point participants actually feel them.
128. Inspector — brings verification discipline to “was this actually done?”
129. Paralegal — strong on process, documentation, and dispute legibility.
130. Journalist — pressure-tests whether the operator’s story survives scrutiny.
131. Risk Manager — sees repeat failure patterns and unresolved exposure.
132. Program Administrator — knows how to handle exceptions without collapsing the whole system.
• Builder, Apps, and Integration Committee — 44
• Subcommittee 1 — Builder Access and Integration Classes
133. Solutions Engineer — knows whether an outside builder can actually integrate.
134. Integrations Specialist — catches weak connection logic between systems.
135. Platform Engineer — sees whether the platform boundary is ready for outside use.
136. Systems Administrator — spots fragile operating posture behind the interface.
137. Identity Administrator — understands builder identity, auth, and permission scope.
138. Compliance Officer — catches access models that should not widen loosely.
139. Developer Relations Manager — knows where builders will get lost or blocked.
140. Technical Writer — turns builder access rules into usable guidance.
141. Product Manager — sees whether access classes make sense as a real product.
142. Partner Manager — understands structured outside participation and builder onboarding.
143. Security Engineer — catches widening risk before it gets normalized.
• Subcommittee 2 — App Surface Standards
144. UX Designer — catches unreadable or misleading app surfaces.
145. Product Designer — knows whether the surface actually preserves Yokefellow structure.
146. Frontend Engineer — sees whether the user-facing state can be shown honestly.
147. Mobile App Developer — tests whether the surface holds outside desktop assumptions.
148. Game Developer — useful for progression, gating, and interaction-heavy surfaces.
149. Accessibility Specialist — catches nominal access that is not real access.
150. Service Designer — sees whether the app flow works as a lived service path.
151. Customer Support Manager — knows where users will predictably get confused.
152. QA Tester — catches happy-path surfaces that break in real use.
153. Teacher — tests whether ordinary people can actually follow the app.
154. Information Architect — keeps surface meaning, flow, and structure legible.
• Subcommittee 3 — API, SDK, and Tooling Governance
155. API Engineer — knows whether the route surface is actually coherent.
156. SDK Engineer — sees whether the packaged builder surface really matches reality.
157. Backend Engineer — catches weak server-side assumptions and broken lifecycle shape.
158. DevOps Engineer — knows whether the tooling can survive real use and scale.
159. Data Engineer — catches weak state truth and broken data flow.
160. Cybersecurity Analyst — spots auth, exposure, and trust-boundary problems.
161. Developer Tools Engineer — understands what makes tooling actually usable.
162. Database Administrator — catches brittle record and persistence assumptions.
163. Site Reliability Engineer — tests whether the toolchain holds under live conditions.
164. Documentation Specialist — keeps the builder surface explainable and checkable.
165. Release Manager — knows whether changes can ship without breaking integrators.
-
Subcommittee 4 — App Review and Ecosystem Expansion
-
App Founder — knows whether a surface is a real app or just a demo.
-
Platform Operator — sees what wider adoption will break first.
-
Community Manager — understands how the app behaves once real users arrive.
-
Community Organizer — tests whether expansion is socially real, not just technically open.
-
Auditor — pressure-tests whether app claims survive review.
-
Researcher — separates evidence of fit from launch theater.
-
Journalist — pressure-tests whether the public story survives scrutiny.
-
Risk Manager — spots expansion that outruns control.
-
Partnership Manager — understands outside partner expansion and surface fit.
-
Venture Builder — sees whether a surface can become a durable product.
-
Incubator Manager — understands ecosystem growth without filling it with weak surfaces.
• Shared Assets, Infrastructure, and Capacity Committee — 44
• Subcommittee 1 — Shared Technical Infrastructure
177. Network Engineer — keeps shared connectivity real and dependable.
178. Systems Administrator — understands shared system upkeep and access control.
179. DevOps Engineer — sees whether shared technical capacity can actually hold.
180. Site Reliability Engineer — catches uptime weakness in core shared systems.
181. Database Administrator — protects shared data infrastructure and continuity.
182. Cloud Infrastructure Engineer — understands scalable shared compute and storage.
183. Cybersecurity Analyst — catches shared infrastructure risk before it spreads.
184. IT Support Lead — knows what breaks first in real daily use.
185. Platform Operator — sees whether shared technical systems are truly operable.
186. Data Center Technician — understands physical technical infrastructure reality.
187. Telecom Technician — useful for real-world communications infrastructure.
• Subcommittee 2 — Shared Real-World Assets and Facilities
188. Property Manager — knows how shared physical assets are actually run.
189. Facilities Manager — understands recurring building obligations and readiness.
190. Venue Operator — sees whether a shared place can carry real use.
191. Building Engineer — catches hidden infrastructure weakness in occupied spaces.
192. Maintenance Supervisor — knows whether shared assets can actually be sustained.
193. Contractor — tests whether physical upgrades are real and buildable.
194. Electrician — catches fake readiness in powered spaces and facilities.
195. HVAC Technician — understands environmental readiness and long-term serviceability.
196. Plumber — useful for functional facility reality, not just appearance.
197. Landscape Manager — sees whether grounds and shared exterior assets can be maintained.
198. Fleet Manager — useful where shared transport assets support many initiatives.
• Subcommittee 3 — Content, Media, and Production Capacity
199. Studio Manager — understands shared production spaces and creative operations.
200. Video Producer — knows whether media capacity is real or just branded.
201. Audio Engineer — catches weak sound and recording infrastructure.
202. Photographer — useful for visual production capacity and deliverable realism.
203. Editor — sees whether content pipelines can actually finish what they start.
204. Publisher — understands whether content output can be packaged and released.
205. Creative Director — tests whether production capacity can support public-facing output.
206. Production Coordinator — catches weak scheduling and resource allocation in content work.
207. Print Producer — useful for physical media and production logistics.
208. Event Producer — understands multi-use capacity, staging, and live support systems.
209. Media Archivist — keeps shared content assets organized and reusable.
• Subcommittee 4 — Multi-Initiative Support Systems
210. Warehouse Manager — knows whether shared stored assets can be tracked and deployed.
211. Logistics Coordinator — sees whether shared resources can actually move where needed.
212. Procurement Manager — understands how shared capacity gets supplied and maintained.
213. Tooling Manager — knows how shared equipment actually stays usable.
214. Program Administrator — understands support systems used by many initiatives at once.
215. Operations Manager — sees whether shared support capacity is really carryable.
216. Finance Manager — tests whether shared assets are economically supportable.
217. Accountant — keeps shared-asset reporting grounded and reviewable.
218. Auditor — tests whether shared capacity claims survive scrutiny.
219. Community Manager — understands shared-use friction across many participant groups.
220. Builder Support Lead — sees whether shared capacity actually helps outside builders.
43-seat committees
• YES Sale, Proceeds, and Treasury Supervision Committee — 43
• Subcommittee 1 — Sale Structure and Sale Buckets
221. Treasurer — understands sale structure and capital staging.
222. Corporate Finance Manager — sees whether the sale structure is financially coherent.
223. Investment Banker — knows how offerings are structured and presented.
224. Securities Lawyer — checks whether sale language and structure are actually bounded.
225. Compliance Officer — catches sale design that should not widen loosely.
226. Market Analyst — pressure-tests pricing and market-facing posture.
227. Founder — sees whether the raise fits the real stage of the system.
228. Investor Relations Manager — knows whether the sale surface reads credibly in public.
229. Accountant — grounds the sale structure in real numbers.
230. Auditor — tests whether the structure can survive scrutiny.
231. Controller — catches weak internal financial discipline at the design stage.
• Subcommittee 2 — Proceeds Buckets and Routing
232. Budget Manager — knows whether proceeds buckets match real planned use.
233. Program Administrator — understands designated-purpose spending across multiple initiatives.
234. Grant Manager — is strong on restricted-use funds and purpose-bound routing.
235. Project Manager — sees whether routed funds match real execution paths.
236. Procurement Manager — understands how funds actually turn into inputs and assets.
237. Operations Manager — pressure-tests whether use-of-proceeds plans can be carried.
238. Treasury Analyst — tracks movement, allocation, and routing logic.
239. Fund Accountant — keeps designated buckets and balances distinct.
240. Capital Planner — sees whether proceeds are staged sensibly over time.
241. Contract Administrator — understands how routed funds become bound work and obligations.
242. Financial Analyst — pressure-tests the logic of where money is going.
• Subcommittee 3 — Reporting, Receipts, and Treasury Supervision
243. Bookkeeper — knows whether reporting can actually be maintained.
244. Financial Reporting Manager — understands recurring financial output and close discipline.
245. Records Manager — keeps proceeds records legible and retrievable.
246. Clerk — strengthens official record and posting discipline.
247. Documentation Specialist — turns treasury activity into usable public records.
248. Internal Controls Manager — catches weak approvals and bad money handling.
249. Inspector — tests whether reported use matches what actually happened.
250. Paralegal — supports reviewable records and procedural legibility.
251. Accounts Payable Manager — understands outgoing use and payment trail truth.
252. Accounts Receivable Manager — catches inflow and settlement confusion.
253. Cash Manager — focuses on live cash position, movement, and control.
• Subcommittee 4 — Long-Horizon Capital Use and Reserve Discipline
254. Portfolio Manager — sees long-horizon capital allocation tradeoffs.
255. Asset Manager — understands stewardship of resources over time.
256. Economist — sees macro pressure, timing, and capital-use consequence.
257. Risk Manager — catches long-run exposure and fragility.
258. Credit Analyst — understands solvency, reserves, and downside discipline.
259. Reserve Manager — focuses on held capacity and rainy-day strength.
260. Banker — grounds reserve and liquidity thinking in real finance practice.
261. Investor — pressure-tests whether long-run use builds real value.
262. Actuary — is useful for reserve logic and long-tail obligation thinking.
263. Finance Director — ties capital discipline to long-horizon operating reality.
• Elections, Qualification, and Chamber Administration Committee — 43
• Subcommittee 1 — Seat Definitions and Qualification Review
264. Seat Definition Drafter — writes seat titles, field purpose, and qualification profiles clearly.
265. Qualification Reviewer — tests whether a candidate actually fits the seat.
266. Credential Analyst — checks degrees, licenses, certifications, and formal proof.
267. Paralegal — catches weak qualification records and bad proof logic.
268. Lawyer — checks whether the seat definition is intelligible and defensible.
269. Records Manager — keeps qualification files orderly and reviewable.
270. Clerk — strengthens filing, posting, and formal review discipline.
271. Licensing Administrator — understands profession-based proof and standing.
272. Academic Registrar — is strong on transcript, degree, and credential verification.
273. Compliance Officer — catches qualification rules that are too soft to administer.
274. Archivist — helps preserve precedent and consistency across cycles.
• Subcommittee 2 — Election Law and Vote Administration
275. Election Administrator — understands how elections are actually run.
276. Ballot Operations Manager — knows ballot flow, contest setup, and voting logistics.
277. Vote Counting Administrator — focuses on tally integrity and count procedure.
278. Identity Verification Specialist — strengthens one-person, one-voter enforcement.
279. Fraud Investigator — catches duplicate identity, manipulation, and election abuse.
280. Database Administrator — protects vote records and election-state accuracy.
281. Cybersecurity Analyst — catches election-system exposure and tampering risk.
282. Compliance Officer — keeps election procedure inside lawful rules.
283. Public Records Clerk — ensures election posting and result legibility.
284. Auditor — tests whether vote handling survives scrutiny.
285. Policy Analyst — helps turn election design into workable law.
• Subcommittee 3 — Vacancy, Term, and Chamber Procedure
286. Parliamentarian — understands chamber rules, order, and formal procedure.
287. Legislative Counsel — checks whether chamber actions fit the constitution.
288. Chamber Clerk — keeps term, vacancy, and proceeding records clean.
289. Calendar Administrator — tracks election cycles, terms, and procedural timing.
290. Committee Administrator — understands referral, reporting, and chamber workflow.
291. Governance Analyst — sees where procedures break or conflict.
292. Rules Administrator — focuses on chamber process and procedural consistency.
293. Session Administrator — keeps chamber activity orderly across active terms.
294. Case Administrator — helps process disputes, appeals, and vacancy events.
295. Records Officer — maintains continuity across term changes and membership changes.
296. Process Manager — pressure-tests whether procedure is actually administrable.
• Subcommittee 4 — Internal House and Senate Administration
297. Operations Manager — sees whether chamber administration can actually run day to day.
298. Office Administrator — understands recurring institutional support work.
299. HR Manager — handles staffing, service continuity, and internal personnel systems.
300. Payroll Administrator — keeps member and staff compensation handling orderly.
301. IT Administrator — supports chamber systems, accounts, and internal technical continuity.
302. Facilities Manager — understands the upkeep of chamber spaces and shared work areas.
303. Procurement Manager — keeps internal purchasing and support systems disciplined.
304. Member Services Administrator — focuses on helping members operate inside the chamber.
305. Public Records Officer — keeps internal posting and public-facing records current.
306. Program Administrator — understands multi-step administrative systems that must stay coherent.
• Oversight, Audit, and Public Record Committee — 43
• Subcommittee 1 — Hearings and Investigations
307. Investigator — knows how to turn suspicion into reviewable fact.
308. Hearing Counsel — structures hearings so testimony and evidence actually hold.
309. Litigator — understands contested facts, pressure, and adversarial questioning.
310. Fraud Investigator — catches deception, concealment, and manipulation patterns.
311. Forensic Accountant — follows money when the story does not add up.
312. Inspector — brings field verification to public claims.
313. Journalist — pressure-tests whether the public story survives scrutiny.
314. Researcher — separates evidence from assertion and rumor.
315. Case Manager — keeps complicated matters orderly across many moving parts.
316. Evidence Analyst — spots weak proof, missing proof, and bad inference.
317. Whistleblower Intake Officer — understands how serious complaints first enter the system.
• Subcommittee 2 — Audit and Review of Governed Activity
318. Auditor — tests whether governed activity survives structured review.
319. Internal Auditor — understands control weakness inside live operating systems.
320. Compliance Officer — checks whether governed actors are following the rules.
321. Risk Manager — sees recurring exposure and unresolved weakness.
322. QA Analyst — catches breakdown between claimed process and real process.
323. Program Evaluator — tests whether activity actually matches stated purpose.
324. Operations Analyst — sees whether live activity is functioning as reported.
325. Controller — catches weak financial discipline in governed operations.
326. Financial Analyst — pressure-tests whether results and use patterns are believable.
327. Site Inspector — verifies whether real-world claims are actually true on the ground.
328. Process Reviewer — sees whether activity can be repeated and audited consistently.
• Subcommittee 3 — Reporting Demands and Findings
329. Legislative Counsel — turns oversight conclusions into formal findings and measures.
330. Policy Analyst — helps convert raw review into usable judgment.
331. Report Writer — makes findings readable without softening them.
332. Technical Writer — keeps complex findings clear and reviewable.
333. Editor — catches weak wording, drift, and hidden ambiguity.
334. Statistician — tests whether reported patterns actually mean what they claim.
335. Data Analyst — turns records into legible evidence and trend findings.
336. Program Administrator — understands what information can realistically be demanded and maintained.
337. Documentation Specialist — keeps reporting structure consistent and usable.
338. Research Librarian — strengthens sourcing, support, and citation discipline.
339. Communications Manager — helps findings land publicly without distortion.
• Subcommittee 4 — Public Record Maintenance and Reviewability
340. Clerk — keeps the official record orderly, current, and formal.
341. Records Manager — understands retention, retrieval, and record integrity.
342. Archivist — preserves long-horizon institutional memory.
343. Librarian — improves public findability and intelligibility of records.
344. Public Records Officer — manages what must stay visible to the public.
345. Database Administrator — protects storage truth and retrievability at scale.
346. Information Governance Manager — ties access, retention, and discipline together.
347. Paralegal — supports reviewable filing and documentary order.
348. Record Indexer — keeps large record sets searchable and usable.
349. Digital Archivist — understands durable preservation of electronic records.
• Ethics, Conflicts, and Anti-Capture Committee — 43
• Subcommittee 1 — Recusal and Conflict Review
350. Ethics Counsel — knows when a person should be out of the room.
351. Compliance Officer — catches conflicts before they become normalized.
352. Auditor — tests whether the decision path was actually clean.
353. Governance Analyst — sees where process is too weak to protect integrity.
354. Inspector General Analyst — understands internal conflict review and institutional abuse patterns.
355. Paralegal — keeps conflict records and recusal logic reviewable.
356. HR Investigator — is useful where relationship and reporting-line conflicts matter.
357. Procurement Auditor — spots decision-makers touching matters they should not control.
358. Records Manager — keeps disclosures and recusals legible over time.
359. Clerk — strengthens formal filing and official recusal record discipline.
360. Judge — brings hard-line impartiality and conflict-boundary thinking.
• Subcommittee 2 — Disclosure and Material Relationships
361. Disclosure Officer — knows what relationships actually need to be disclosed.
362. Forensic Accountant — follows hidden financial relationships and indirect benefit.
363. Journalist — pressure-tests whether the disclosed story is really the whole story.
364. Researcher — finds missing links and undeclared connections.
365. Data Analyst — catches patterns that point to hidden relationships.
366. Public Records Officer — keeps disclosure material visible and searchable.
367. Documentation Specialist — turns messy relationship data into usable records.
368. Compliance Analyst — checks whether disclosures are complete enough to rely on.
369. Licensing Administrator — understands how outside standing and affiliations should be shown.
370. Archivist — preserves material-relationship history across cycles.
371. Communications Analyst — spots disclosure language designed to hide the real meaning.
• Subcommittee 3 — Anti-Self-Dealing and Influence Abuse
372. Fraud Investigator — catches private gain hiding inside public action.
373. Internal Auditor — tests whether process was bent for someone’s benefit.
374. Controller — spots suspicious money flow and favored handling.
375. Contract Lawyer — sees when legal structure is being used to mask self-dealing.
376. Procurement Manager — understands favoritism, steering, and quiet inside advantage.
377. Whistleblower Intake Officer — helps serious misuse surface early.
378. Risk Manager — sees how influence abuse spreads through the system.
379. Inspector — verifies whether claimed public purpose matches actual benefit.
380. Vendor Risk Analyst — catches conflicted outside relationships and dependency abuse.
381. Mediator — is useful where influence and private interest blur into procedural fights.
382. Claims Adjuster — understands messy fact patterns where partial truth is being used defensively.
• Subcommittee 4 — Capture, Collusion, and Integrity Enforcement
383. Antitrust Lawyer — understands organized control and coordinated exclusion.
384. Compliance Investigator — catches repeated collusion patterns across actors.
385. Intelligence Analyst — sees networked behavior and hidden coordination.
386. Election Administrator — is useful where bloc capture touches internal legitimacy.
387. Community Organizer — can tell when participation is being crowded out by insiders.
388. Auditor — tests whether the captured structure leaves a readable trace.
389. Investigative Journalist — pressure-tests cartel behavior and insider narratives.
390. Policy Analyst — sees where the rules themselves are inviting capture.
391. Program Administrator — understands how collusion hides inside normal-looking administration.
392. Ethics Enforcement Officer — focuses on remedy, discipline, and institutional cleanup.
• Emergency, Continuity, and Incident Review Committee — 43
• Subcommittee 1 — Emergency Measures
393. Emergency Manager — knows when a situation needs immediate but bounded action.
394. Incident Commander — understands decisive action under pressure.
395. Continuity Planner — sees what must stay alive first.
396. Public Safety Director — understands emergency priorities and real response burden.
397. Risk Manager — catches when fast action creates bigger downstream harm.
398. Operations Manager — knows what can actually be carried during disruption.
399. Logistics Coordinator — sees where emergency action will fail in movement and supply.
400. Communications Director — understands how to communicate emergency action clearly.
401. Legal Counsel — checks whether emergency action stays inside lawful bounds.
402. Policy Analyst — helps turn urgency into a time-limited, reviewable measure.
403. Facilities Manager — knows what physical systems fail first in a live emergency.
• Subcommittee 2 — Continuity and Degraded-State Governance
404. Business Continuity Manager — understands how systems keep functioning while damaged.
405. Site Reliability Engineer — sees degraded-state truth behind “still online” claims.
406. Systems Administrator — knows what can be stabilized and what cannot.
407. Platform Operator — understands live service degradation and operational fallback.
408. Database Administrator — protects continuity of records and system state.
409. Network Engineer — sees communication fragility during degraded operation.
410. Program Administrator — knows which core workflows must continue and which can pause.
411. Clerk — keeps governance legible while normal process is strained.
412. Records Manager — protects continuity of the official record under disruption.
413. Property Manager — understands continuity burdens in occupied real-world spaces.
414. Finance Manager — sees what continuity costs and what reserves are needed.
• Subcommittee 3 — Incident Review and Failure Analysis
415. Investigator — turns breakdown into reviewable fact.
416. Auditor — tests whether the incident story survives scrutiny.
417. Forensic Accountant — follows money where failure involved misuse or loss.
418. QA Analyst — catches hidden edge-case failure and weak testing discipline.
419. Inspector — verifies what actually happened on the ground.
420. Data Analyst — reconstructs patterns, timelines, and operational signals.
421. Researcher — separates root cause from narrative cover.
422. Journalist — pressure-tests whether the public explanation holds.
423. Paralegal — keeps incident records, evidence, and procedural review orderly.
424. Cybersecurity Analyst — catches attack, exposure, and technical compromise patterns.
425. Process Reviewer — sees where the system design itself invited failure.
• Subcommittee 4 — Recovery, Restoration, and Post-Incident Reform
426. Recovery Coordinator — understands how systems move from disruption back to function.
427. Restoration Manager — knows what it takes to bring damaged operations back online.
428. Project Manager — turns recovery into sequenced, finishable work.
429. Program Evaluator — tests whether the reform actually solved the failure.
430. Operations Analyst — sees whether restored systems are truly stable or just patched.
431. Builder — understands physical restoration and rebuild reality.
432. Service Manager — knows whether user-facing recovery is actually being honored.
433. Policy Drafter — turns failure lessons into better rules.
434. Trainer — helps translate reforms into real operating behavior.
435. Community Manager — sees whether trust is actually restored after the incident.
Appendix B. Senate Seats and Committee Assignments
Senate 100.
Senate Recognition and Expansion Committee — 10
Founder
Operator
Governance Lawyer
Auditor
Risk Manager
Platform Architect
Infrastructure Director
Business Development Director
Industry Executive
Public Affairs Director
Senate Bucket Standards, Disclosures, and Records Committee — 10
11. Standards Engineer
12. Disclosure Counsel
13. Records Manager
14. Internal Controls Director
15. Communications Director
16. Program Director
17. Information Architect
18. Compliance Director
19. Reporting Manager
20. Public Records Officer
Senate Participation, Rights, and Fulfillment Committee — 10
21. Product Director
22. Rights Counsel
23. Access Control Manager
24. Licensing Manager
25. Fulfillment Operations Director
26. Fulfillment Director
27. Dispute Resolution Counsel
28. UX Director
29. Service Operations Director
30. Claims Manager
Senate Builder, Apps, and Integration Committee — 10
31. Chief Technology Officer
32. Developer Relations Director
33. Integration Manager
34. API Architect
35. Applications Director
36. Identity and Access Manager
37. Developer Tools Lead
38. Security Architect
39. UX Director
40. Partnership Director
Senate Shared Assets, Infrastructure, and Capacity Committee — 10
41. Infrastructure Director
42. Facilities Manager
43. Production Director
44. Operations Director
45. Technical Director
46. Asset Manager
47. Resource Planning Manager
48. Procurement Director
49. Finance Director
50. Program Director
Senate YES Sale, Proceeds, and Treasury Supervision Committee — 10
51. Treasurer
52. Capital Allocation Director
53. Securities Lawyer
54. Proceeds Oversight Director
55. Financial Controls Director
56. Financial Reporting Manager
57. Reserve Manager
58. Liquidity Risk Manager
59. Infrastructure Finance Director
60. Budget Director
Senate Elections, Qualification, and Chamber Administration Committee — 10
61. Credentialing Director
62. Election Director
63. Election Lawyer
64. Election Auditor
65. Parliamentarian
66. Terms and Vacancies Administrator
67. Legislative Operations Director
68. Records Manager
69. Member Services Director
70. Chamber Administrator
Senate Oversight, Audit, and Public Record Committee — 10
71. Oversight Counsel
72. Audit Director
73. Investigations Counsel
74. Records Manager
75. Forensic Accountant
76. Inspector General
77. Compliance Director
78. Reporting Director
79. Archivist
80. Performance Auditor
Senate Ethics, Conflicts, and Anti-Capture Committee — 10
81. Ethics Director
82. Conflicts Counsel
83. Disclosure Director
84. Antitrust Lawyer
85. Internal Auditor
86. Fraud Investigator
87. Public Integrity Director
88. Intelligence Analyst
89. Internal Controls Director
90. Enforcement Director
Senate Emergency, Continuity, and Incident Review Committee — 10