Coordinator Territory Change

Status message

Displaying output for plurality voting

Open Votes

Proposal Type: Bylaw Revision
Opened: 18-Oct-2010 1:00AM EDT
Closing: 18-Oct-2010 1:00AM EDT


I Jacob Hoffman CM of Detroit Sabbat propose the following changes to Coordinator Bylaws 3.B. and 3.C.

Seconded by Jason Place

Additions are in Bold.

B. Sect Coordinators
i. Sect Coordinators are responsible for:
1. Monitoring and advising on genre issues regarding the Sect, including but not limited to:
a. Status and Prestation
b. Sect laws, Justice, Politics, and Customs
c. Sect Positions and Designations (Such as Justicars, Princes, Barons, Cardinals as well as such things as the Red list and Black Hand membership)
d. Conflict and Intrigue both within and between the Sects (including Sect Infiltrators and Defectors)
e. Relevant abilities, powers or disciplines specific to a sect or part of a sect (Anarch Combos, Sabbat Rituals, Black Hand Art of Memory etc.)
2. Provide guidance for Storytellers on the goals and activities of the Sect as a whole.
a. Sect Coordinator and Genre Coordinators shall share joint control over NPCs/Territories deemed important to the Sect as a whole, regardless of clan.
b. The Executive Team shall mediate disputes of control and portrayal of these NPCs/Territories.
ii. To this end, Sect Coordinators shall receive all powers outlined to Clan Coordinators in Section 3.C.ii & 3.C.iii as directly related to the duties outlined in Section 3.B.i.
iii. Sect IC Offices, other than those under a single Chronicle's jurisdiction, may not be filled, either by PC or NPCs, without previous approval from that sect's Coordinator. That includes:
1. The Camarilla Inner Circle, Justicars, Warlord, Alastors, Archons and any other publicly known agents of the Inner Circle, Justicars and/or Warlord
2. The Sabbat Regent, Cardinals, Prisci, Paladins, Inquisitors, the Black Hand Seraphim, Dominions, Seconds and any other publicly known agents of those Sabbat Offices, including their Templars, if any.
C. Genre Coordinators
i. Genre Coordinators are responsible for:
1. Providing local STs with informational resources regarding the clan, sect, bloodlines, or species for which they have responsibility.
2. At their discretion, providing local Storytellers with the portrayal of NPCs of that clan, sect, or species, within the bounds of OWBN wide consistency and genre concerns.
3. Providing OWBN with the occasional presence of NPCs of their clan, sect, or species on the OWBN lists, or in person at OWBN events, within the bounds of OWBN wide consistency and genre concerns.
4. Providing OWBN with guidance regarding the general direction of their clan, sect, or species, and with plots which may enhance OWBN’s usage of that clan.
5. Maintaining the consistency and genre appropriateness of the genre resource under their care.
6. Keeping local STs and other appropriate Coordinators appropriately informed of their activities. This includes informing local STs of communications with PCs.
7. Monitoring chronicle adherence to the Character Regulation Bylaws, Section 9.
ii. To this end, Genre Coordinators have the following powers:
1. They may create and portray, or delegate the portrayal of, NPCs as appropriate to their position.
a. [Removed 1/12/08.]
b. Council may remove any of these NPCs/Territories with a majority vote, at which time the Coordinator will be permitted to script a suitable IC disappearance.
c. Delegated NPCs/Territories requested by STs for use by a particular chronicle are primarily subject to the authority of those STs but may be removed at any time by the Coordinator.
d. Coordinator NPCs/Territories cannot be used by any Chronicle without the permission of the Coordinator, his/her delegate, and the local STs.
e. Coordinator NPCs/Territories become subject to local ST authority when they are used by a chronicle, but the Coordinator or his or her delegate shall remain free to refuse to allow any action if it introduces a vital inconsistency of character or a breach in global genre in the Coordinator or delegate’s opinion.
i. If Storytellers feel they require an action, which the Coordinator has refused, they may appeal the matter to Council, whose decision shall be final.
ii. If the Coordinator feels the Storyteller(s) of a chronicle have tampered with, or hampered, the actions of a Coordinator office NPC/Territory in such a way that prevents the Coordinator from enforcing their area of Genre, they may address Council for official Disciplinary action to be taken against said ST(s) or the Chronicle as a whole.
f. Coordinator NPCs are subject to Administrative Bylaws Section 1.D constraint except where otherwise noted in the bylaws.
g. Coordinator NPCs that fall under an R&U category must be passed as normally for that category through Council.
h. Coordinator territory is considered either "Approval" Territory or "Notify" Territory.
i. Use of "Approval" Territory is outlined above.
j. Chronicles may use "Notify" Territory without permission as long as they notify the appropriate coordinator within a week of use. All actions taken within "Notify" Territory are considered under the rule of Administrative Bylaw Section 1. A. iii..
2. Cast a tie-breaking vote on R&U characters they coordinate.
3. Genre Coordinators may collect information on clan/sect/species activities (or in the case of the Justicar Coordinators, on matters which have been brought IC to the Justicar’s attention) from the STs or other Coordinators, who shall not misrepresent such information.
a. Failure to provide necessary information to a Coordinator or intentional misrepresentation of information shall be brought before Council and considered appropriate grounds for punitive measures.
4. They may request permission of the appropriate STs to take any actions directly through clan NPCs towards PCs.
a. The appropriate STs shall be deemed to be the STs with OWBN jurisdiction over the PC at the time and chronicle at which the action is to occur.
b. If the action is foreseeable in advance, permission should also be sought from the PC's home chronicle STs for any direct interaction via NPCs.
i. Permission is not required for indirect interaction (wherein the words, requests, desires, etc. of NPCs are carried to PCs by another PC), only for direct interaction (wherein a PC personally interacts with, or is affected personally by, NPCs without the intermediary of other PCs).
c. If permission is granted, they may take those actions.
d. If permission is not granted, the Coordinator may take their case before Council. Council's rulings will be binding to the Coordinator and the chronicle(s) in question.
e. If Head Storytellers make agreements with Coordinators concerning PCs, those agreements shall be binding on both the Coordinator and the chronicle, regardless of who holds the Coordinator position or the ST positions (though agreements may be altered if both STs and Coordinators agree).
i. Should a formal binding agreement be made between the Coordinator and another party (such as a player and their Storyteller, a Chronicle, or another Coordinator), that formal binding agreement shall be logged with the Archivist and reported to the Executive Team for the purposes of documentation should dispute occur. Any changes to said formal binding agreement shall likewise be logged with the Archivist and reported to the Executive Team.
f. Failure to keep such agreements shall be brought before Council and considered appropriate grounds for punitive measures.
5. Advise Coordinators and STs on ways to leverage R&U related backgrounds and plotlines on a global level, if desired.
a. For example: in the Midwest, it’s quite possible that various PCs in Kenosha, Milwaukee and Green Bay all have a 5-pt. Mentor who is a Samedi. Instead of having 3-5 7th generation Samedi, it would make sense for the various Mentors to be combined into a single NPC, and used as a plot device at ST discretion.
6. They may delegate any of the above powers to one or more Sub-Coordinators, who they will hold responsibility over.
a. They may remove these Sub-Coordinators at will, and Council may remove these Sub-Coordinators with a majority vote.
b. Coordinators are responsible for all disputed issues that are brought before Council.
iii. Genre Coordinators must pass before Council any plot, enforced policy, R&U named characters, or binding edict they wish to use which they can reasonably expect to affect multiple chronicles and these proposals need not be seconded, but go immediately into discussion.
1. If no opposition is voiced during the week of discussion, the proposal is considered passed and enforceable. Once passed these are considered binding to all chronicles and a chronicles refusal to adhere is grounds for OWBN disciplinary measures. Opposition must be in regards to the content of the proposal and must give those reasons why the objection is voiced. This is to allow Coordinator's the opportunity to respond and/or make changes/remove the proposal and its contents.
i. exception to above - Player Character (PC) specific information, such as but not limited to PC's holding regional positions or PC's important enough to have been included in genre documents (i.e. tribal packets, clan packets, status packets etc.) may be updated by notification to council, should the PC specific information change during the duration that the document is current. Adding or removing player characters and their respective information from genre documents is expressly NOT covered by this clause, and should be handled through the normal council approval processes.
2. Those that seem to affect only one chronicle only need local ST approval. In this case, conflicts with the chronicle are subject to point three above.
3. Coordinators may bring before Council any dispute between themselves and another Coordinator or ST in which they feel OWBN wide consistency or global genre is at stake, and Council shall make a timely investigation and judgment.
4. Passing new R&U Named characters before council is to be treated as something which affects multiple chronicles.
5. Passing new Coordinator Territory before council is considered something that affects multiple chronicles. All Coordinator Territory must be designated either "Approval" Territory or "Notify" Territory in the Proposal. After passing Coordinator Territory of any kind that territory should be added to the Territory List which shall be posted to the OWBN website.
6. Any Proposal that utilizes Justicar NPC(s) for the purposes of enforcing genre policy over the Organization requires the consent of either the Camarilla Coordinator or the Genre Coordinator that controls the Justicar NPC in question. Council may not utilize the Justicar NPCs to Propose a Genre Proposal without this consent.
iv. Abuses of the limits of these powers may be addressed with local strikes or brought before Council and considered appropriate grounds for punitive measures. This applies to both Coordinators and their staff, and chronicles and their ST’s.

File / Document: No file attachments for this vote.
Ballot Options
For
Against
Abstain