Proposal: But This is Only Half the List
Reaches quorum at 9-3 and is Enacted. - lilomar
Adminned at 03 Oct 2010 13:43:33 UTC
Give Rule 2.2.1 the title “Imposters.”
Add a new Subrule to Rule 2.2, entitled “Codename Tracking,” and give it the following text:
Codenames may have their own entries in the GNDT, as if they were Agents. Any Agent may update the Description or Last Known Location of a Codename at any time, but only the D-Ops may add new Codenames.
At any time, if a number of Agents greater than or equal to Quorum has confirmed Codenames, the D-Ops may add any number of these Codenames (including those assigned to Imposters, if they wish) to the GNDT. At any time, if at least three Codenames are tracked in the GNDT but no longer assigned to any Agent or Imposter, the D-Ops may remove any number of these expired Codenames from the GNDT.
In addition, if “Fledgling Allegiance” passes, append the following paragraph to “Codename Tracking:”
Any time an Agent’s Allegiance changes, the D-Ops may secretly change the Codename assigned to an Imposter (if any) with the Agent’s previous Allegiance.
A potential next step would be to allow Agents to blow one another’s cover, if their Description and LKL match a Codename’s.
I’m not sure of what to think.
It would be interesting to get rid of all of the “normal” names from the GNDT and just have one for codenames.
redtara: they/them