CANON PAGE NOTES: These are all the notes I've dug up on Task Forces, Security, & Facilities, including on the proposed writing guides. Lemme know if you have any issues/questions; most of this stuff isn't mandatory.
------------------
TASK FORCES:
These are just the notes on Task Forces that I had when I was drafting the project.
* The goal is a set of good, solid examples of MTFs which users can use as a guide to create their own MTFs for their own purposes.
* Don't be afraid to expand entries where necessary, to create.
* This includes creating new MTFs that can creatively inspire people.
* Anything can be cut, except Omega-7 (which can be altered). (I'd like to keep the Silencers)
-----------
Logs from PF discussion between you, me, Mann:
[14:26] DrMann When you go through it, 'Lanna, rather than necessarily going for ones that /are/ used a lot...
[14:26] DrMann Go for ones that look like they /could/ be used a lot.
[14:26] thedeadlymoose I'd say work like this -- again, assuming you want to take on Task Forces, too -- Do like Facilities and cut shit using the same methods. (Leave in The Silencers and anything you think is legitimately fun/cool/inspiring.) Then add in some things to fill in gaps -- to be representative.
------------
For the Task Forces OOC Writing Guide:
Again, these are the notes Troy gave me. They are just suggestions.
**If you want**, include a short explanation of /why/ certain MTF examples are good examples of what writers should aspire toward, including linking to one or two examples of their use in a positive manner.
[2013-03-03 16:36:12] <TroyL> You might consider sitting down and creating a list of reasons to actually have an MTF in existance.
[2013-03-03 16:36:25] <TroyL> Then using that list, have a single example of each.
[2013-03-03 16:36:38] <TroyL> "This is an MTF used for containing an SCP"
[2013-03-03 16:36:48] <TroyL> "This is an MTF used for utilizing an SCP in some way."
[2013-03-03 16:37:01] <TroyL> "This is an MTF used for tracking an SCP's activity"
Here are notes I took based on information from Echo. It's also excessively combat-orienated.
You can discard or use this as you see fit:
"Small task forces of 3 - 10 members would likely handle investigation, infiltration, assassination, or occasionally grabbing a single SCP object under tricky circumstances. Fewer people to arouse fewer suspicions.
Direct assault would tend to involve larger task forces. For a typical "home invasion" example (to contain an SCP in a location approximately the size of a house), a 40 - 50 member task force might be typical: a third to maintain a perimeter and security, a third to act as support, and a third to perform the assault. Larger task forces would be mobilized for larger buildings (though, naturally, the task force will divide up once inside). To blend in, task forces of this size might pose as paramedics, firefighters, police offers, or the national guard.
[...] Don't make an extremely tiny task force assigned to job that would take many members. Especially don't make a task force specifically dedicated to something as basic as "desert survival" or "close-quarters combat in a biohazard situation". [...] If it could be handled by literally any element of a basic response team, it probably doesn't need a specific task force.
If it could be handled by literally any element of a larger group, it probably doesn't need a specific task force."
I'd also suggest adding tips for alternate canon versions that aren't ridiculous. For example, the page assumes a default canon of a decent-sized Foundation. The writing guide could also suggest "An very small Foundation might have only small Mobile Task Forces, and would need to coordinate with (or manipulate) outside military forces to accomplish larger goals."
Also potentially mention standards for adding an MTF to the list (or disregard if we want to discourage that for now)
...and whatever else you want in there.
-----OTHER WRITING GUIDES
All the writing guides should probably also specify multi-canon in some way; the idea is to create sensible, useful, inspiring writing guides, not straitjackets. Staff could add general disclaimers to the writing guides, but it may work better to try to work some version of that in. "This is the default assumptions, and here's some tips if you go outside that default assumption -- how to do it well."
------------------
FACILITIES:
For Facilities this is as simple as saying, say, that a really small Foundation wouldn't realistically be able to run all these sites.
Optionally, we could estimate the real-world numbers of people who work at these sites (Just For Funsies).
Potentially also note the multiple canon ideas re: whether the Foundation has "magical" tech to cut down on numbers (or clones, or whatever)
Also potentially mention standards for adding a Facility to the list.
...and whatever else you want in there.
Notes from chat:
[13:33] DrMann I think the non-authoritative bit on Facilities could be made a little stronger. Other than that, looks good.
[13:33] thedeadlymoose Might that not be taken care of by an attached writing guide, though?
[and eventually I think we agreed on that :P]
-------------
SECURITY:
A general overview of how clearance levels / etc have been classically used on the site. Example text from the previous draft:
"Security and staff levels are used throughout the website, with ranks from 0 to 5. Other than 5 being reserved for the highest ranking staff and most classified material, and 0 for the lowest ranking, like janitors and secretaries there is no unbreakable consensus on what the numbers mean.
For example, the "classic" organizational system entirely merges rank & clearance level into "Level 0 - 5", exchanging real-world accuracy for simplicity of use. Another interpretation might hold that zero through five denotes a simplified pay grade range."
(You don't need to use that text.)
Could optionally talk about common theories on D-Class like clones or whatever. Up to you.
I believe we talked about explaining some of the differences between security guards, tac response teams, & MTFs elsewhere.
Plus whatever else you want to add.
--------------
