11 changed files with 129 additions and 856 deletions
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@ -1,134 +0,0 @@
 # Contributor Covenant Code of Conduct
 ## Our Pledge
 We as members, contributors, and leaders pledge to make participation in our
 community a harassment-free experience for everyone, regardless of age, body
 size, visible or invisible disability, ethnicity, sex characteristics, gender
 identity and expression, level of experience, education, socio-economic status,
 nationality, personal appearance, race, caste, color, religion, or sexual
 identity and orientation.
 We pledge to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.
 ## Our Standards
 Examples of behavior that contributes to a positive environment for our
 community include:
 * Demonstrating empathy and kindness toward other people
 * Being respectful of differing opinions, viewpoints, and experiences
 * Giving and gracefully accepting constructive feedback
 * Accepting responsibility and apologizing to those affected by our mistakes,
  and learning from the experience
 * Focusing on what is best not just for us as individuals, but for the overall
  community
 Examples of unacceptable behavior include:
 * The use of sexualized language or imagery, and sexual attention or advances of
  any kind
 * Trolling, insulting or derogatory comments, and personal or political attacks
 * Public or private harassment
 * Publishing others' private information, such as a physical or email address,
  without their explicit permission
 * Other conduct which could reasonably be considered inappropriate in a
  professional setting
 ## Enforcement Responsibilities
 The Personnel Committee is responsible for clarifying and enforcing our
 standards of acceptable behavior and will take appropriate and fair corrective
 action in response to any behavior that they deem inappropriate, threatening,
 offensive, or harmful.
 The Personnel Committee has the right and responsibility to remove, edit, or
 reject comments, commits, code, wiki edits, issues, chat messages, and other
 contributions that are not aligned to this Code of Conduct, and will communicate
 reasons for moderation decisions when appropriate.
 This document is maintained by the Personnel Committee. Any change to
 these guidelines must be announced immediately to the collective body.
 ## Scope
 This Code of Conduct applies within all community spaces, and also applies when
 an individual is officially representing the community in public spaces.
 Examples of representing our community include using an official email address,
 posting via an official social media account, or acting as an appointed
 representative at an online or offline event.
 ## Enforcement
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the Personnel Committee at [INSERT CONTACT METHOD].
 All complaints will be reviewed and investigated promptly and fairly.
 All members of the Personnel Committee are obligated to respect the privacy and
 security of the reporter of any incident.
 ## Enforcement Guidelines
 The Personnel Committee will follow these Community Impact Guidelines in
 determining the consequences for any action they deem in violation of this Code
 of Conduct:
 ### 1. Correction
 **Community Impact**: Use of inappropriate language or other behavior deemed
 unprofessional or unwelcome in the community.
 **Consequence**: A private, written warning from the Personnel Committee,
 providing clarity around the nature of the violation and an explanation of why
 the behavior was inappropriate. A public apology may be requested.
 ### 2. Warning
 **Community Impact**: A violation through a single incident or series of
 actions.
 **Consequence**: A warning with consequences for continued behavior. No
 interaction with the people involved, including unsolicited interaction with
 those enforcing the Code of Conduct, for a specified period of time. This
 includes avoiding interactions in community spaces as well as external channels
 like social media. Violating these terms may lead to suspension or expulsion.
 ### 3. Suspension
 **Community Impact**: A serious violation of community standards, including
 sustained inappropriate behavior.
 **Consequence**: A temporary ban from any sort of interaction or public
 communication with the community for a specified period of time. No public or
 private interaction with the people involved, including unsolicited interaction
 with those enforcing the Code of Conduct, is allowed during this period.
 Violating these terms may lead to a permanent expulsion.
 ### 4. Expulsion
 **Community Impact**: Demonstrating a pattern of violation of community
 standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 **Consequence**: Expulsion from the collective. A permanent ban from any sort of
 public interaction within the community.
 ## Attribution
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
 version 2.1, available at
 [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
 Community Impact Guidelines were inspired by
 [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
 For answers to common questions about this code of conduct, see the FAQ at
 [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
 [https://www.contributor-covenant.org/translations][translations].
 [homepage]: https://www.contributor-covenant.org
 [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
 [Mozilla CoC]: https://github.com/mozilla/diversity
 [FAQ]: https://www.contributor-covenant.org/faq
 [translations]: https://www.contributor-covenant.org/translations
--- a/best_practices.md
+++ b/best_practices.md
@ -1,8 +0,0 @@
 # Best Practices Mandate
 This document lists the security practices that the Intrusive Thoughts
 Creative Collective requires its members strictly adhere to in order
 to protect ourselves as an organization from external threats.
 This document is maintained by the Infrastructure Committee. Any
 change to this document should be announced to the collective body.
--- a/business.md
+++ b/business.md
@ -1,7 +0,0 @@
 # Business Committee Charter
 This document defines the procedures, policies, and bylaws specific to
 the Business Committee of the Intrusive Thoughts Creative Collective.
 This document is maintained by the Business Committee. Any changes
 must be announced to the Business Committee body.
--- a/charter_of_directorship.md
+++ b/charter_of_directorship.md
@ -0,0 +1,129 @@
 Whereas we acknowledge the need for a consistent, unified creative
 vision, the undersigned agree to establish the office of Project
 Director as defined by the [terms](#terms) of this document.
 # Terms
 ## Scope
 1. A Project Director is the creative director of a single project, and
   not necessarily any other projects.
 2. Each project may have no more than one creative director. A project
   need not have a creative director.
 3. A Project Director may only be [elected](#election) as defined here.
 4. A Project Director's [role](#role) only applies to the project
   which they direct. Likewise, a Project Director is only beholden to
   the creative body of the project which they direct.
 5. The creative body of a project is the subset of members of the
   Intrusive Thoughts collective who have agreed to work on the given
   project.
 6. A "project" here refers to a single game (or other piece of media) in
   development. A game and its sequel are considered two different
   projects.
 ## Role
 1. A Project Director makes decisions about the creative direction of
   the project which they direct. All members of the creative body are
   asked to abide by the creative decisions made by the Project
   Director.
 2. While other members of the creative body will naturally make
   creative decisions about the project in the course of their work,
   any such decision may be overruled by the Project Director.
 3. The creative body may collectively reject any decision made by the
   Project Director with a two-thirds supermajority veto.
 ## Election
 1. Any member of the creative body may call for the election of a
   Project Director at any time when the project has no acting Project
   Director.
   1. After an election for Project Director is held, another election
      may not be called for a period of three weeks, or until the
      office has been vacated, whichever comes first.
 2. The election shall use
   [ranked-choice voting with instant runoff](https://en.wikipedia.org/wiki/Instant-runoff_voting),
   using an online platform so that every member of the creative body
   may cast their vote regardless of physical location.
   1. We suggest using [RCV123](https://www.rcv123.org/election/open/create/1)
      with the following configuration:
      - Duplicate Vote Deterrence is ON
      - Randomize candidate ballot order
      - Start voting: when voters receive link
      - End voting: election remains open
 3. The election ballot shall be titled "Vote for the Director of
   [project]" where [project] is the name or temporary name of the
   project.
 4. The candidates on the election ballot shall be the names of each
   member of the project's creative body, plus an additional option of
   "None" to indicate the preference that the office remain unfilled.
 5. The link to the election ballot shall immediately be posted to the
   *#announcements* Discord channel.
 6. 48 hours after the ballot is made public, if at least 50% of the
   creative body has voted in the election, then the winning candidate
   shall immediately assume the office of Project Director.
 ## Abdication
 1. A Project Director may choose to abdicate the position of Project
   Director at any time, for any reason, including no reason, by
   posting a message in the *#announcements* channel announcing that
   they are abdicating the position, after which the position of
   Project Director shall immediately be considered vacated.
 2. A Project Director shall automatically abdicate the position of
   Project Director upon leaving (or being removed from) the project's
   creative body and/or the Intrusive Thoughts collective.
 ## Recall
 1. Any member of the creative body may call for the recall of the
   acting Project Director at any time.
   1. After holding a recall vote for an acting Project Director,
      another recall vote for that same Project Director may not be
      called for a period of one week.
 2. The recall vote shall be a simple majority poll with two options,
   using an online platform so that every member of the creative body
   may cast their vote regardless of physical location.
   1. We suggest simply creating a poll in the *#announcements*
      Discord channel with the following configuration:
      - Poll duration: 48 hours
      - Do NOT allow multiple answers.
 3. The poll's title shall be "Should [director] be recalled as
   Director of [project]?" where [director] is the name of the acting
   Project Director in question and [project] is the name of the
   project.
 4. The poll's options shall be "Yes, they should not be Director" and
   "No, they should continue being Director". (Pronouns may be changed
   to respect the director in question)
 5. The link to the poll (or the poll itself) shall immediately be
   posted to the *#announcements* Discord channel.
 6. 48 hours after the poll is made public, if at least 60% of the
   creative body (not just the voting body) has voted "Yes, they
   should not be Director", then the acting Project Director in
   question shall be immediately recalled and the position of Project
   Director shall be considered vacated.
 # Signatures
--- a/constitution.md
+++ b/constitution.md
@ -1,589 +0,0 @@
 # Constitution
 ## Article I. Name
 The name of this organization shall be the Intrusive Thoughts Creative
 Collective. For brevity, it may also be referred to as Intrusive
 Thoughts, Intrusive Games, or simply the Collective.
 ## Article II. Purpose
 We are artists and creators who reject the present capitalist economic
 order based on exploitation of labor for private profit, and we defy
 the regime of violence and terror which enforces it. We reject white
 supremacy, we reject patriarchy, we reject western imperialism, and we
 reject all forms of discrimination based on race, gender identity,
 sexual orientation, disability status, age, religion, and national
 origin. We have come together to show the people that our world does
 not have to be this way. Through our works as artists, we endeavor to
 spread class consciousness, foster resistance against our oppressors,
 and spread our shared vision of a humane social order.
 ## Article III. Membership
 ### Sec 1. Members
 1. The set of all current members of the Intrusive Thoughts Creative
   Collective is known as the _collective body_.
 2. Every individual employed by the Intrusive Thoughts Creative
   Collective is a member of the collective body, and all members of
   the collective body are employed by the Collective.
 ### Sec 2. Recruitment
 1. Membership shall be open to every person who subscribes to the
   principles of the Collective and is willing to make a meaningful
   contribution to the creative work of the Collective.
 2. An individual shall apply to be a member following the procedure
   prescribed by the [Recruitment Mandate][recruitment].
 ### Sec 3. Collective
 1. Every member has a right to vote on decisions made by the
   Collective.
 2. Any decision made by an individual member or decision-making body
   on behalf of any body of the Collective may be overruled by the
   majority decision of a higher decision-making body, except where
   otherwise stated in this document.
 3. The collective body shall be the highest decision-making body of
   the organization.
 4. Members who do not wish to vote on collective decisions may
   temporarily waive their right to vote by expressly declaring their
   intent to the collective body.
   1. Members who have waived their right to vote in the above manner
      are referred to as "non-voting members".
   2. A member may not be coerced into waiving their right to vote.
   3. A member may rescind the waiver of their voting rights at any
      time by expressly declaring their intent to the collective body.
 5. The set of members of the collective body who have _not_ waived
   their right to vote is known as the _voting body_.
 6. A quorum of the collective body shall be half its
   members. Likewise, a quorum of the voting body shall be half its
   members.
 ### Sec 4. Expulsion
 1. A member may be expelled from the Collective by either a two-thirds
   decision by the voting body or by unanimous decision of the
   [Personnel Committee](#sec-2-personnel-committee).
 2. A member facing expulsion must receive a written notice of the
   charges against them and must be given the opportunity to be heard
   before the Personnel Committee or a working group established for
   the purpose of considering expulsion.
 3. A member meeting any of the following criteria may be subject to
   expulsion:
   1. They are in substantial disagreement with the principles or
      policies of the Collective.
   2. They consistently engage in undemocratic, disruptive behavior.
   3. They have violated the [Collective Code of Conduct][coc].
   4. They have been out-of-contact with the collective body for at
      least thirty days without providing an excuse for their absence.
 ### Sec 5. Resignation
 1. A member may choose to resign from the collective by announcing the
   time at which they intend to leave the collective, which shall be
   respected by the collective body.
 ### Sec 6. Organization
 1. The members of the collective body have a right to unionize.
 2. Intimidation or retribution against any member for exercising their
   right to organization, or for discussing organization, or for
   exercising collective bargaining, is recognized as undemocratic
   behavior and is therefore grounds for expulsion.
 ## Article IV. Committees
 1. Committees may be chartered only by this Constitution.
 2. Any member of the collective body may be a member of any committee,
   provided they meet that committee's requirements for membership.
   1. A member of the collective body may be a member of any number of
      committees at the same time, unless otherwise prescribed.
 3. Committees may make internal decisions by holding polls and
   elections exclusive to the voting body of that committee.
   1. Any internal decision of any committee may be vetoed by a
      two-thirds decision of the voting body.
   2. A quorum of any committee shall be half of its voting members,
      unless otherwise stated.
 ### Sec 1. Steering Committee
 1. The Steering Committee shall be responsible for decision-making on
   behalf of the entire collective body in lieu of polling the members
   of the collective body themselves.
 2. The Steering Committee shall meet once every two weeks.
   1. Meetings of the Steering Committee shall be open to all members
      of the collective body.
   2. The Steering Committee may hold a closed executive session if a
      simple majority (one-half) of its members agree to do so in
      order to discuss private matters, such as personnel and related
      financial matters.
 3. The Steering Committee shall be composed of five individuals who
   shall be elected from the collective body by the voting body to a
   term of one year.
 ### Sec 2. Personnel Committee
 1. The Personnel Committee shall be composed of members of the
   collective body who have been individually appointed by the
   Steering Committee.
 2. The Personnel Committee shall be responsible for the recruiting &
   interviewing candidates for collective membership as prescribed by
   the [Recruitment Mandate][recruitment].
 3. The Personnel Committee shall be responsible for ensuring that the
   Collective operates as a safe, equitable, non-discriminatory
   organization in accordance with the principles of the Collective.
 4. The Personnel Committee shall be responsible for periodically
   reviewing member performance.
 5. The Personnel Committee shall be responsible for expelling members
   who meet the criteria for expulsion.
 6. The Personnel Committee shall be responsible for rallying the
   morale of the collective and fostering a sense of _esprit de
   corps_.
 7. The Personnel Committee shall be responsible for maintaining the
   [Personnel Committee Charter][personnel], documenting the
   procedures, policies, and bylaws specific to the Personnel
   Committee therein.
   1. Any changes to the Personnel Committee Charter must be announced
      to the collective body.
 8. The Personnel Committee shall be responsible for enforcing the
   [Collective Code of Conduct][coc] in all Collective spaces,
   including the Collective chat and Git repo.
   1. The Personnel Committee shall also be responsible for
      maintaining the Collective Code of Conduct. Any changes must be
      announced to the collective body.
 ### Sec 3. Infrastructure Committee
 1. The Infrastructure Committee shall be composed of members of the
   collective body who have been individually appointed by the
   Steering Committee.
 2. The Infrastructure Committee shall be responsible for the
   maintenance, upkeep, security, and administration of all Collective
   IT assets and infrastructure, as well as any physical Collective
   assets.
 3. The Infrastructure Committee shall be responsible for defining the
   Collective's security practices, and shall document these practices
   in the [Best Practices Mandate][best-practices].
 4. The Infrastructure Committee shall be responsible for provisioning
   and acquiring new IT assets for the Collective as mandated by the
   other committees and/or the collective body.
 5. The Infrastructure Committee shall be responsible for assisting all
   members of the collective body in the use of Collective IT assets.
 6. Immediately upon discovery of any instance of unauthorized access
   of any Collective IT asset, the Infrastructure Committee shall
   announce the incident to the collective and subsequently begin the
   process of mitigating damages and advising any affected
   members. This damage-control process takes priority over any other
   responsibility of the Infrastructure Committee.
 7. The Infrastructure Committee shall be responsible for maintaining
   the [Infrastructure Committee Charter][infrastructure], documenting
   the procedures, policies, and bylaws specific to the Infrastructure
   Committee therein.
   1. Any changes to the Infrastructure Committee Charter must be
      announced to the collective body.
 ### Sec 4. Engineering Committee
 1. The Engineering Committee shall be composed of any members of the
   collective body who wish to contribute to the works of the
   Collective in a technical capacity.
 2. The Engineering Committee shall be responsible for maintaining the
   [Engineering Committee Charter][engineering], documenting the
   procedures, policies, and bylaws specific to the Engineering
   Committee therein.
   1. Any changes to the Engineering Committee Charter must be
      announced to the Engineering Committee body.
 ### Sec 5. Creative Committee
 1. The Creative Committee shall be composed of any members of the
   collective body who wish to contribute to the works of the
   Collective in a creative capacity.
 2. The Creative Committee shall be responsible for maintaining the
   [Creative Committee Charter][creative], documenting the procedures,
   policies, and bylaws specific to the Creative Committee therein.
   1. Any changes to the Creative Committee Charter must be announced
      to the Creative Committee body.
 ### Sec 6. Business Committee
 1. The Business Committee shall be composed of any members of the
   collective body who wish to contribute to the Collective and our
   works in a business capacity.
 2. The Business Committee shall be responsible for maintaining the
   [Business Committee Charter][business], documenting the procedures,
   policies, and bylaws specific to the Business Committee therein.
   1. Any changes to the Business Committee Charter must be announced
      to the Business Committee body.
 ## Article V. Elections
 ### Sec 1. Procedure
 1. All elected positions shall prescribe a limited term of office.
 2. All elections shall be decided by
   [ranked-choice voting with instant runoff][rcv].
   1. In the event that a clear winner cannot be decided by either the
      normal election nor the instant runoff, the winner shall be
      decided by random selection of the given tied candidates.
 3. All elections shall be held via an online platform so that every
   member may cast their vote regardless of physical location.
   1. Immediately after an election is opened, a link or other means
      of accessing the ballot must be announced to the collective.
 4. All elections shall be open for a period of at least 72 hours after
   being announced to the collective.
 5. Whenever an elected position is vacated, a new election for the
   position shall be held immediately.
 ### Sec 2. Abdication
 1. A member holding any elected office may choose to abdicate that
   office at any time for any reason, including no reason, by
   announcing their intent to the collective.
 2. A member holding any elected office shall automatically abdicate
   that office upon resigning (or being expelled from) the collective
   body.
 ### Sec 3. Recall
 1. A member holding an elected office or an appointed position may be
   recalled from that position with a two-thirds decision of the
   voting body, or the body to which they are beholden.
 ## Article VI. Roles
 ### Sec 1. Internal Roles
 1. A member may be granted a role with respect to any committee they
   are a part of in accordance with the bylaws of that committee.
 ### Sec 2. External Titles
 1. Members should not identify their internal role when representing
   themselves as a past, present, or future member of the Collective
   to anyone outside of the Collective, including (but not limited to)
   a recruiter for another company, on social media, and on their
   résumé or CV.
 2. Members are automatically granted _external titles_ based on
   committee membership. Members are encouraged to identify themselves
   as one or more of their external titles.
   1. All members of the collective body may use the title of "Vice
      President of Research & Development".
   2. Members of the Personnel Committee may use the title of "Vice
      President of Human Resources".
   3. Members of the Finance Committee may use the title of "Vice
      President of Finance".
   4. Members of the Infrastructure Committee may use the title of
      "Vice President of Information Technology".
   5. Members of the Engineering Committee may use the title of "Vice
      President of Technology".
   6. Members of the Creative Committee may use the title of "Vice
      President of Design".
   7. Members of the Business Committee may use the title of "Senior
      Executive Vice President".
 ### Sec 3. Speaker for the Collective
 1. The voting body shall elect a Speaker for the Collective
   (alt. Speaker) from the collective body to a term of one year.
 2. The Speaker shall be responsible for representing the Collective's
   interests publicly in situations that require an in-person
   representative.
 3. The Speaker does not have any executive power, directorial power,
   or decision power beyond that which would be otherwise granted to a
   regular member of the collective body.
 ### Sec 4. Treasurer
 1. The voting body shall elect a Treasurer from the collective body to
   a term of one year.
 2. The Treasurer shall be responsible for the direct management of the
   Collective's financial assets.
 3. The Treasurer shall review the Collective's financial situation
   with the Steering Committee on a monthly basis.
 4. The Treasurer shall prepare an annual budget.
 ### Sec 5. Secretary
 1. The voting body shall elect a Secretary from the collective body to
   a term of one year.
 2. The Secretary shall be responsible for producing and distributing
   minutes of meetings of the Steering Committee and any general
   meetings of the entire collective body.
 3. The Secretary shall be responsible for drafting Collective
   documentation as prescribed by the Steering Committee or the voting
   body.
 4. The Secretary shall be solely responsible for maintaining the
   [Collective documentation repository][doc-repo], including merging
   amendments to this document and revisions to other Collective
   documentation.
   1. Maintenance of the documentation repository shall be conducted
      in a timely fashion, and only in the manner prescribed by this
      document.
 ## Article VII. Working Groups
 ### Sec 1. Working Groups
 1. Any set of members may form a _working group_ for any purpose.
 2. Membership in a working group is inherently open; the members of a
   working group are exactly the members of the collective body who
   identify themselves as members of that working group.
 ### Sec 2. Projects
 1. A _project_ is a working group formed for the specific purpose of
   creating a single distinct game, visual novel, or any other piece
   of media.
 2. A project may elect a Project Director from the project body to the
   term of the project development cycle.
   1. A Project Director makes decisions about the creative direction
      of the project which they direct. All members of the project
      body are asked to abide by the creative decisions made by the
      Project Director.
   2. While other members of the project body will naturally make
      creative decisions about the project in the course of their
      work, any such decision may be overruled by the Project
      Director.
   3. The project body may collectively overrule any creative decision
      made by the Project Director with a two-thirds veto decision.
   4. A project does not need to elect a Project Director. The
      election of a Project Director must include a "None" candidate,
      to indicate the voter's preference that the office remain
      unfilled.
 3. A project may elect a Producer from the project body to the term of
   the project development cycle.
   1. A Producer is responsible for the planning, procurement, and
      execution of a project.
   2. A Producer facilitates communication between the Project
      Director and project body to define & refine engineering,
      creative, and business requirements.
   3. A Producer negotiates a project schedule with the project body,
      and coordinates the project body's labor to ensure the project
      is completed in accordance with that schedule.
   4. A Producer is responsible for advocating for their project's
      labor requirements to the Personnel Committee.
   5. A Producer is responsible for advocating for their project's
      material and technological requirements to the Infrastructure
      Committee.
   6. A Producer is responsible for advocating for their project's
      financial requirements to the Treasurer.
   7. A Producer is responsible for informing the greater collective
      body on any decisions relating to the procurement of project
      requirements.
 ## Article VIII. Collective Ownership
 ### Sec 1. Collective Property
 1. All intellectual property created or discovered by a member of the
   collective body and contributed to a project shall be the
   collective intellectual property of the Intrusive Thoughts Creative
   Collective, with all present and future rights, title, and interest
   assigned to the Collective, unless otherwise stated at the time of
   contribution.
   1. _Intellectual property_ includes, but is not limited to, code,
      graphical assets, sound assets, algorithms, concepts,
      developments, designs, discoveries, ideas, formulas,
      improvements, inventions, processes, software, trademarks, and
      trade secrets, as well as the tangible embodiments
      (e.g. drawings, notes) of any intangible items.
   2. When starting a project, any preliminary intellectual property
      intended to become part of that project must be relinquished to
      the Collective by its owner(s) before the collective body may
      contribute to the project.
 2. All assets owned by the Intrusive Thoughts Game Collective are
   collectively owned by the collective body. This includes virtual
   assets such as intellectual property, as well as material assets
   including servers and databases, as well as any accounts which
   represent the Collective on online platforms.
 3. Collective assets shall be managed and administered by the
   [Infrastructure Committee](#sec-4-infrastructure-committee). Access
   to collective assets in an administrative capacity shall be the
   exclusive responsibility of the Infrastructure Committee.
 ### Sec 2. Core Infrastructure
 1. The Intrusive Thoughts Creative Collective shall collectively
   maintain a set of core infrastructure elements to facilitate the
   basic operation of the collective.
 2. All core infrastructure elements shall be listed in the
   [Core Infrastructure Manifest][core-infrastructure].
   1. Any change to the core infrastructure must be immediately
      reflected in the Manifest.
 3. The [Infrastructure Committee](#sec-4-infrastructure-committee)
   shall be responsible for the administration, upkeep, and security
   of the core infrastructure.
 4. All members must have user-level access to the core infrastructure.
 ## Article IX. Dissolution
 1. In the event of the dissolution of the Intrusive Thoughts Creative
   Collective, all remaining funds and assets shall be released to
   such other organizations that are organized exclusively for the
   promotion of social welfare and that will operate to further the
   common good and general welfare of the community.
 2. In such an event, all Collective source code assets shall be made
   publicly available on gitlab.com. The URLs of any such repositories
   shall be disclosed to every person who was a member of the
   Collective before its dissolution.
 ## Article X. Constitutionality
 ### Sec 1. Constitutional Mandate
 1. This document shall be hosted in a publicly-visible git repository
   on the [Collective document repository][doc-repo].
 2. The version of this document published at the head of the `main`
   branch of the repository shall be recognized as the current version
   of this document.
 3. The git commit history of this document shall not be abridged or
   altered except to add commits when merging an amendment.
 ### Sec 2. Ratification
 1. This document shall be submitted as a pull request to the existing
   [Collective document repository][doc-repo].
 2. After a period of review of at least one week, with the unanimous
   consent of all five founding members of the Intrusive Thoughts
   Creative Collective, this document will be ratified by merging it
   into the `main` branch of the repository.
 3. Upon ratification of this document, the five founding members will
   automatically become members of the Collective.
 4. Upon ratification of this document, there shall be a grace period
   of one week to allow the Collective to form in compliance with the
   procedures of this document.
 ### Sec 3. Amendment
 1. Amendments to this document may be proposed by any member of the
   collective body by submitting a pull request to the
   [Collective document repository][doc-repo].
   1. Any member may have no more than one proposed amendment to this
      document under consideration at any given time.
 2. A proposed amendment must be approved by two-thirds of the voting
   body before it can be accepted and merged.
 3. If a proposed amendment does not meet all acceptance criteria
   within two weeks (fourteen days) of submission, it shall be
   considered rejected and closed permanently.
   1. A rejected amendment may not be re-submitted. However, a new
      amendment with the same text as a previously-rejected amendment
      may be submitted.
 [best-practices]: best_practices.md
 [business]: business.md
 [coc]: CODE_OF_CONDUCT.md
 [core-infrastructure]: core_infrastructure.md
 [creative]: creative.md
 [doc-repo]: https://git.of.the.spectacle.lol/intrusive/docs
 [engineering]: engineering.md
 [infrastructure]: infrastructure.md
 [rcv]: https://en.wikipedia.org/wiki/Instant-runoff_voting
 [recruitment]: recruitment.md
--- a/core_infrastructure.md
+++ b/core_infrastructure.md
@ -1,49 +0,0 @@
 # Core Infrastructure Manifest
 This document enumerates and describes the core infrastructure
 elements necessary for the operation of the Intrusive Thoughts
 Creative Collective.
 This document is maintained by the Infrastructure Committee. Any
 change to the core infrastructure should be reflected in this document
 as soon as possible.
 ## Chat
 An online chat server must be maintained in order to communicate and
 coordinate with the collective.
 This is currently implemented with a Discord server.
 Announcements to the collective are made using the **#announcements**
 channel.
 ## Meeting Service
 An online meeting system allowing voice chat, video chat, and screen
 share must be maintained in order to facilitate Collective meetings.
 This is currently implemented with the same Discord server as our
 [chat](#chat).
 ## Git Host
 A git host must be maintained as a host for Collective source code
 assets.
 This is currently implemented with a [gitea](https://about.gitea.com/)
 instance hosted on a server at 23.239.29.92
 ([git.of.the.spectacle.lol][spectacle])
 ## Document Repository
 A document repository must be maintained as a host for the
 Collective's Constitution & Bylaws.
 This is currently implemented with a repository on the aforementioned
 gitea instance, under [intrusive/docs][docs].
 [docs]: https://git.of.the.spectacle.lol/intrusive/docs
 [gitea]: https://about.gitea.com/
 [spectacle]: https://git.of.the.spectacle.lol/
--- a/creative.md
+++ b/creative.md
@ -1,7 +0,0 @@
 # Creative Committee Charter
 This document defines the procedures, policies, and bylaws specific to
 the Creative Committee of the Intrusive Thoughts Creative Collective.
 This document is maintained by the Creative Committee. Any changes
 must be announced to the Creative Committee body.
--- a/engineering.md
+++ b/engineering.md
@ -1,8 +0,0 @@
 # Engineering Committee Charter
 This document defines the procedures, policies, and bylaws specific to
 the Engineering Committee of the Intrusive Thoughts Creative
 Collective.
 This document is maintained by the Engineering Committee. Any changes
 must be announced to the Engineering Committee body.
--- a/infrastructure.md
+++ b/infrastructure.md
@ -1,8 +0,0 @@
 # Infrastructure Committee Charter
 This document defines the procedures, policies, and bylaws specific to
 the Infrastructure Committee of the Intrusive Thoughts Creative
 Collective.
 This document is maintained by the Infrastructure Committee. Any
 changes must be announced to the collective body.
--- a/personnel.md
+++ b/personnel.md
@ -1,7 +0,0 @@
 # Personnel Committee Charter
 This document defines the procedures, policies, and bylaws specific to
 the Personnel Committee of the Intrusive Thoughts Creative Collective.
 This document is maintained by the Personnel Committee. Any changes
 must be announced to the collective body.
--- a/recruitment.md
+++ b/recruitment.md
@ -1,39 +0,0 @@
 # Recruitment Mandate
 This document describes the process through which an individual may
 join the Intrusive Thoughts Creative Collective.
 This document is maintained by the Personnel Committee. Any changes
 should be announced to the collective body.
 ## Procedure
 ### 1. Petition to Join
 An individual wishing to join the Collective ("applicant") must ask an
 existing member to endorse their application. That member may then
 endorse the applicant by petitioning the Personnel Committee on behalf
 of the applicant.
 ### 2. Application Decision
 The Personnel Committee must accept or reject the applicant's
 application by two-thirds decision no later than three weeks after the
 initial petition.
 ### 3. Application Acceptance
 If accepted by the Personnel Committee, the applicant must agree to
 uphold the policies, procedures, and principles of the Collective as
 defined in the [Constitution][constitution].
 ### 4. Onboarding
 The Infrastructure Committee is responsible for supplying the new
 member with the following:
 - Access to the Intrusive Thoughts Discord server.
 - Access to the Intrusive Thoughts git server.
 [constitution]: constitution.md