IN THE SENATE OF THE STATE OF FIRESTONE
OCTOBER 12, 2025
Ms. Automationeer introduced the following:
A JOINT RESOLUTION
To mandate the maintenance of archives.
Be it resolved by the Senate of the State of Firestone,
SECTION 1. EFFECTIVENESS
This resolution shall take effect immediately upon the completion of the constitutionally required processes.
SEC. 2. SEVERABILITY
Should any part of this resolution be struck down or declared unenforceable, then that part shall be considered severed with the rest remaining in full force.
SEC. 3. ARCHIVE SYSTEM
(a) There shall continue to be a Congressional Archive System (hereinafter, the system), to be defined as a GitHub Organization, whichever is the one currently being used for this purpose on the date of effectiveness.
(b) In this resolution, administrators refers to the President of the Senate, the Speaker of the House, the President pro tempore, and any additional citizen agreed by all of the preceding officials. The administrators shall be responsible for the maintenance of the system.
SEC. 4. RECORDS
(a) The following shall be retained in the Congressional Archive System:
(i) original texts of laws proposed, where available – and these texts may or may not be edited to reflect amendments made, but shall never be edited (except for any purely visual or informational edit) once sent to the Governor to be signed (unless amended during a veto override, where procedure allows); and
(ii) original texts of resolutions proposed, where available – and these texts may or may not be edited to reflect amendments made, but shall never be edited once passed and effective,
and to that end the administrators may collaborate with any other person, group, or body, including the Archivist of the State of Firestone.
(b) Nothing in this section precludes the administrators from storing anything else they may consider necessary, which may include for example, journals and election results; and to this end, too, may they collaborate.
(c) Members of Congress shall be obliged to assist the administrators with any reasonable steps, including providing them with any copies they may have of laws they have written.
(d) For greater clarity, the obligation under this section to make records does not apply to anything before the date of effectiveness, but the obligation for secure retention does apply to anything that already exists in the system.
SEC. 5. SECURITY
(a) Reasonable steps shall be taken by the administrators to limit the potential impact of abuse of any privileges.
(b) As concerns the technical operation of the Git repositories within the system, a linear history shall be maintained, and anything which may disrupt this (including “force pushes”) shall be curtailed to the maximum extent possible.
(c) The administrators, and indeed other citizens, are encouraged to personally retain their own copies of the system.
(d) Information is not retained in the system unless it is committed to a Git repository within the system. For greater clarity, subordinate repositories (including GitHub Wikis) shall not constitute a repository for the purposes of the foregoing, nor shall any branch of any repository which is not the default or mainline branch.
(e) Once an item has been placed into the system, it shall not be deleted, unless the item is an identical duplicate of another item in the system or there is limited historical value in the item and its deletion is exceptionally in the public interest, and in either instance all of the administrators must agree to its deletion. Reasonable renaming or relocation of items within a repository is permitted.
(f) There shall continue to be a log of all “push” activity within the system, visible to all members of Congress, and where reasonable steps have been taken to limit manipulation.
(g) Where GitHub rules prohibit the storing of an item, it need not be stored and may be deleted; and anything which may violate this resolution but is necessary to prevent disruption of the system by GitHub is permitted.