* Green-Gray 

Hypervelocity 


Prometheus Labs is first and foremost a research and development 
corporation. There are many problems that we are working to solve, 
but as a for-profit company, there are limited funds available to solve 
them. Therefore, Prometheus Labs must prioritize funding for those 
projects and research that we feel deserve it. 


However, we pride ourselves on the independent research 
performed by our world-class scientists. Products such as the 
mental web and teleportation were developed by researchers 
working on their vacation days. For this reason, Prometheus Labs 
has instituted a policy of independent research for eight hours per 
week. We have also provided this proposal request form. In the 
event that you wish to pursue an independent avenue of study full- 
time, please fill out this form and submit it to Human Resources. 
Please allow two to four days for processing. 


GRANT REQUEST FOR [INSERT PROJECT HERE] 
Do not give your project a special name. Name it based on what it 
is: a grant request for a scientific question. 


PROBLEM 

What are you trying to achieve? What problem are you trying to 
solve? 

Explain the issue in great detail. Make it clear why this is a problem 
that Prometheus Labs should work on. 


SOLUTION 
Explain the proposed technology solution. How exactly does it work? 


What does it do to solve the problem? What is the technology and/or 
the research behind the proposal that supports its viability? What 
are the benefits of the technology and/or research? Bibliographies 
recommended. 


BUSINESS CASE 

Who will purchase or use this product or knowledge? Give 
demographics (age group, ethnicity, economic class, etc. ). List 
potential markets. If it is a product, what makes this product different 
from similar products already on the market? What makes it a more 
appealing choice? How will the use and/or sale of this research and/ 
or technology benefit Prometheus Labs or scientific knowledge? 


USE OF FUNDING 

You are asking for funding to support development and research of 
this concept. What will the funds go into? What will they be used 
for? What will the funds purchase? Who will they hire? Give a 
timetable for expected lengths of work and dates of completion, a list 
of materials and tools to be used for the project, a list of necessary 
contractors, and the price ranges for all. 


KNOWN ISSUES 

What are the major stumbling blocks to the adoption, widespread 
use, and/or profitability of this research and/or technology? Known 
bugs, difficulties in bringing to market, project failures, etc. How can 
these issues be fixed? 


+ READ ME 


This is a very heavily watered-down format of actual 
grant proposals and various engineering competitions 
I've entered. Prometheus Labs is a company with limited 
funds. Therefore, it must select only the best and most 
well-thought-out projects to fund. The problem and 
solution are self-evident. The business case is basically 
justifying the creation of the object and whether or not 
there is a plan to make it work. The use of funding is to 
make sure that the money poured into the project 
actually goes to good use. The known issues are a 
pragmatic way to make sure that this product actually 
has a future, and that its creator is thinking ahead. 


You don't need a bibliography, but it would definitely 
enhance it. 

This format is basically another perspective on SCP 
objects that Prometheus Labs made. They were 
designed with a commercial purpose in mind. What was 
that purpose? What was it intended for? Who was it 
intended for? 

The format is basically asking you "why would this object 
be created in the first place?" 

It may be more difficult to use this to create a story than 
you are used to, but it also offers a unique perspective 
on an SCP: that of its creator. 


There is only one thing that needs to be kept in mind 
when using this format: the road to hell is paved with 
good intentions. 


(Prometheus Labs builds things they think are useful but 
have horrific consequences) 


Overall Structure 


The basic template for a Redzone Security Advisory is as follows. 
Each of the sections is explained later in the appropriate section. 


[Header Block] 

ie Jonette 

++ Affected Products 

++ Indicators of Compromise 


++ Workarounds 


++ Fixed Software 


++ Exploitation and Public Disclosure 


++ Source 


The Header Block 


To create the header block for a Redzone Security Advisory, include 
the redzone-advisory component, with the following 
parameters: 


title (optional) 
The title given to the vulnerability, for ease of referencing it. 
This should be the same as the page title. 

id (required) 
The vulnerability ID number. This always takes the following 
form: redzone-sa- 12345678-2-to-3-word-summary. This 
should also normally correspond to the page URL, which 
should take this form: www.scp-wiki.net/redzone- 
sa- 12345678. 

updated (optional) 
The date when this advisory was last updated. Omit this 
parameter if it is the same as the publication date. 

published (optional) 
The date on which the first version of this advisory was 
published. 

version (optional) 
The advisory version number indicating the number of times 
this advisory has been updated. Use two-position version 
numbers starting from 1.2 for the second version. If this is 
the first version, omit this parameter. 

final (optional) 
Whether or not this is considered the ‘final’ version of the 
document; defaults to true. If you are describing a 
vulnerability for which there is not yet a fix, or for some other 
reason is not ‘final’, set this to false. 

impact (required) 
The Basic CVSS score for this vulnerability, a number 
ranging from 0.0 for not a vulnerability, to 10.0 for an 
extremely bad vulnerability. You can calculate this by 
entering its details into this CVSS calculator tool, 


or you Can just guess. 

worknd (optional) 
Whether or not there are workarounds for this vulnerability, 
short of updating to a fixed version. Defaults to false. If there 
are workarounds, make sure to set this parameter to true. 

bugs (required) 
The internal bug ID numbers of the bugs that resulted in this 
vulnerability. ID numbers should be of the form RZux 12345. 
Separate multiple numbers with a newline. 

cve (optional) 
The Common Vulnerabilities and Exposures (CVE) 
number(s) that refer to this vulnerability. CVE numbers have 
the form CVE-year-digits, where digits is four or five digits 
long. (Technically they can be longer, but that is unusual.) 
Make sure to search the CVE database first to make sure 
that the number(s) you pick are not in use. Note that 
numbers from the current year may still be assigned, 
however. Separate multiple numbers with a newline. 

cwe (optional) 
The Common Weakness Enumeration number(s) that that 
are involved in the vulnerability. CWE numbers have the 
form CWE- 123. Make sure that any CWE numbers you list 
actually correspond to the appropriate weaknesses. You 
can kinda-sorta use this site to look up the correct 
CWE numbers, but the site is mostly unusable and the CWE 
system is even more complicated than the SCP Foundation 
tag system. If you want help finding the right CWE numbers, 
send a wikidot PM to AJMansfield and he will help you 
find the right CWE numbers. Separate multiple numbers 
with a newline. 


Here is an example of a fully-parameterized instance of the 
redzone-advisory component: 


[ [include component: redzone-advisory 

|title=Redzone Thingamajig Server Cromulator Vulnerabili 
| id=redzone-sa-12345678-thingamajig-cromulator 

| updated=2005-01-01 

| published=2004-01-01 


version=1.9 
final=false 
impact=7.0 
worknd=false 
bugs=RZux12345 
RZux23456 
cve=CVE-1234-5678 
CVE-1234-6789 
cwe=CWE-123 
CWE-234 

]] 


If you want to make a security advisory from some other company, 
that is also possible, using the redzone-advisory—base 
component instead of the redzone-advisory component. This 
allows you to specify two additional parameters: 


logo (required) 
Specify the path for another image to use, instead of the 
Redzone Security logo at the top. 

color (required) 
The color code to use for all colored highlights. In most 
cases you should set this to the dominant color of the logo, 
but you should make sure that it has enough contrast with 
the page background first. You can do that using this 
WCAG Contrast Checker tool - Ideally all 6 circles 
should turn green when you input your color in the "fg" box, 
although 5 out of 6 is usually good enough. 


Additionally, all previously optional parameters need to be specified 


when using redzone-advisory-—base; in order to omit a piece 
put false as the parameter value. 


Summary 


This section is intended to give a technical summary of the 
vulnerability. This can contain a number of different things, such as: 


¢ How the vulnerability works. 
¢ What causes the vulnerability. 


right, don't be a dumbass! 
SCP-694-2: | WANT MY DADDY! 
[A sound of breaking glass is heard] 


SCP-694-4: SHUT UP, DAMMIT! ... No, no, | was 
talking to Lang's kid, I'm sorry, you know I'd never 
— yes, okay, he — ELWOOD! THE HIGHWAY! 
OVER THERE, ON THE RIGHT! TAKE THE ON- 
RAMP! TURN, DAMMIT! 


SCP-694-3: Which right! 

[The vehicle turns left] 

SCP-694-2: | WANNA GO HOME! 
[A sound of breaking glass is heard] 


SCP-694-4: (hits SCP-694-3) What the fuck are 
you doing! | said go right! 


SCP-694-3: | did go right!4 
[superfluous dialogue redacted] 


[SCP-694-3 and SCP-694-4 turn the corner and 
arrive at SCP-694-1's residence, as SCP-694-1 is 
emerging from his garage and loading his gun.] 


SCP-694-4: Wait, is this Lang's house again? How 
did — oh shit, he's loose! 


SCP-694-3: GUN! 


[The rest of the conversation consists of 
SCP-694-3 and SCP-694-4 fleeing from 
SCP-694-1, and is largely obscenities. After the 
terminus of the loop, -3 and -4's vehicle 
dematerializes, and the recording device falls to 
the ground where it can be recovered. ] 


* How someone might try to exploit the vulnerability. 
¢ Anything else that doesn't fit somewhere else. 


Think of this as analogous to the description of an SCP article, 
except don't directly state what anomalous effects it has - that goes 
later, in the Indicators of Compromise section. 


Affected Products (optional) 


This section details exactly which of Redzone's products are 
affected by this vulnerability. In most cases, this is most easily done 
using a table, like this: 

Vuinerable Product Fixed In: 


Redzone Thingamajig Server 2.3.4 


To do that, use this code: 


||~ Vulnerable Product ||~ Fixed In: | | 
|| Redzone Cromulator 3000 Series || 1.2.3 || 
| | Redzone Thingamajig Server | | 2.3.4 | | 


Keep this section short, though - this is only here for verisimilitude, 
and going on for pages and pages about what products are affected 
is probably more verisimilitude than readers will be willing to read. In 
some cases it may be appropriate to omit this section entirely. 


Indicators of Compromise 
This is probably the most important section for the article, in that it 
describes what sort of anomalous effects the vulnerability might 


cause. Think of this as analogous to the part of the description in an 
SCP article where you do the big reveal about the anomaly. 


Workarounds (optional) 


State any measures that a redzone customer might take to mitigate 


the risk or otherwise contain the vulnerability. Think of this as 
analogous to the containment procedures of an SCP article. 


If no workarounds exist, this section may be omitted. 


Fixed Software (optional) 


If there is any reason that the Foundation might not be able to fix 
this problem by upgrading to a newer version, state these reasons 
here. 


This section may be omitted or replaced with standard boilerplate as 
needed, for example: "When considering software upgrades, 
customers are advised to consult the Redzone Security Advisories 
and Responses archive and review subsequent advisories to 
determine exposure and a complete upgrade solution." 


Exploitation and Public Disclosure 
(optional) 


This is the part where you can describe what effect this bug actually 
had on the Foundation Redzone's clients. If it caused everything to 

go to hell, say so. Also describe how widely-known the vulnerability 
was before this document was published. 


This section may be omitted or replaced with standard boilerplate as 
needed, for example: "The Redzone Security Incident Team (RSIT) 
is not aware of any public announcements or malicious use of the 
vulnerability that is described in this advisory." 


Source (optional) 


Here you can give a background or timeline of how this vulnerability 
was discovered. This section may be omitted or replaced with 
standard boilerplate as needed, for example: "This vulnerability was 
discovered by Redzone during internal security testing." 


GRANT REQUEST FOR USAGE OF BIOLOGICAL 
ORGANISMS TO FACILITATE EFFICIENT 
TERRAFORMING AND SPECIES RESTORATION 


GRANT REQUEST FOR USAGE OF BIOLOGICAL ORGANISMS 
TO FACILITATE EFFICIENT TERRAFORMING AND SPECIES 
RESTORATION 


PROBLEM 

The human population of planet Earth is steadily increasing. As of 
6/15/1980, there were approximately 4.43 billion humans on the 
planet. At the current rate of population growth, there will be almost 
7 billion humans alive by 2010. This increasing population puts a 
strain on the resources of the planet, which are exacerbated by 
economic, political, social, and religious conflicts. 


At the same time, human expansion is rapidly causing climate and 
ecological shifts in the planet. At least 600 species have been 
recorded to go extinct as a result of climate change, and likely the 
extinction of hundreds more has gone unnoticed24. It is clear that 
the only way to both preserve the ecology and biological diversity 
and health of the planet while still allowing for human growth is to 
populate other planets. 


However, very few Earthlike planets have been discovered, all of 
which are thousands of lightyears away®. The teleportation 
technology currently in use relies on theories of quantum mechanics 
that are still limited to the speed of light, rendering these planets off- 
limits. 


There are numerous planets and asteroids in our solar system that 
are mere light-minutes away, but are inhospitable to all forms of life. 
If they were to be terraformed, it would be possible for humans to 
relocate to these planets and asteroids. However, there are no ways 
currently within our technological grasp to economically terraform 
these astronomical bodies. 


SOLUTION 

We propose creating biological organisms, custom-designed to exist 
in hostile environments, to gradually terraform them into 
environments suitable for human habitation. These organisms would 
subsist off the raw materials found in the environment, consuming 
them and reproducing while simultaneously converting the planet 
and atmosphere into an Earthlike planet. 


Celine and Franklin's theories on cold nuclear fusion® can be easily 
applied to a terraforming organism. Such an organism would be able 
to perform cold fusion to create elements that are more conducive to 
terrestrial biology. These organisms would also use those elements 
to propagate themselves asexually, so that the conversion process 
proceeds exponentially quicker. Asexual reproduction would also 
ensure that mutations are few and far between.