Team:SDU-Denmark/safety-b

From 2010.igem.org

(Difference between revisions)
(Biosafety)
(Biosafety)
Line 13: Line 13:
==== Analysis of parts and devices ====
==== Analysis of parts and devices ====
<p style="text-align: justify;">
<p style="text-align: justify;">
-
'''SopII'''  – No homogenity when blasted. The gene is mentioned in Halobacterium salinarum R1 [1] and in Natronomonas pharaonis DSM 2160[2] as being protein coding. The protein is a light dependant iontransporter, and is often seen with the halophilic bacteria (halophilic: organisms that thrive in high concentrations of salt). So it might make non extremophiles more competitive in environments with high salt concentrations. The word: “might“ should be underlined, as it of course takes several genes / proteins to make it more durable in high salt concentrated areas . This clearly is a risk. If a bacterium were to gain the advantage, to survive in high salt concentrations, it would mean we could create diverse bacteria which more easily can survive, and proliferate in completely different environment, than we usually meet them. The outcome of “old” bacteria proliferating in another environment than usual is not easy to foresee.
+
'''SopII'''  – No homogenity when blasted. The gene is mentioned in Halobacterium salinarum R1 [1] and in ''Natronomonas pharaonis'' DSM 2160[2] as being protein coding. The protein is a light dependant iontransporter, and is often seen with the halophilic bacteria (halophilic: organisms that thrive in high concentrations of salt). So it might make non extremophiles more competitive in environments with high salt concentrations. The word: “might“ should be underlined, as it of course takes several genes / proteins to make it more durable in high salt concentrated areas . This clearly is a risk. If a bacterium were to gain the advantage, to survive in high salt concentrations, it would mean we could create diverse bacteria which more easily can survive, and proliferate in completely different environment, than we usually meet them. The outcome of “old” bacteria proliferating in another environment than usual is not easy to foresee.
<br><br>
<br><br>
'''HtrII''' – (sequence?). It contains three domains, which gives a chemotaxis-like property towards Methyl, Aspartate and related amino acids. One of the domains (cl01054, which is the one out of three) is commonly observed in bacteria. [3] The fact that it is often represented in bacteria creates a lower safety risk, as it will less likely transfer its genes to bacteria which don’t have this specific chemotaxis already.
'''HtrII''' – (sequence?). It contains three domains, which gives a chemotaxis-like property towards Methyl, Aspartate and related amino acids. One of the domains (cl01054, which is the one out of three) is commonly observed in bacteria. [3] The fact that it is often represented in bacteria creates a lower safety risk, as it will less likely transfer its genes to bacteria which don’t have this specific chemotaxis already.
Line 244: Line 244:
<br>
<br>
<br>
<br>
-
'''License'''
 
 +
<html>
 +
<head>
 +
  <meta content="text/html; charset=ISO-8859-1"
 +
http-equiv="content-type">
 +
  <title></title>
 +
</head>
 +
<body>
 +
<span style="font-weight: bold;">License</span><br>
 +
<br>
 +
Every team, and lab / company which works with synthetic biology will
 +
be assigned a specific “license plate”, unique to them and being their
 +
‘ID’ on parts-registry. An extension to parts registry’s search
 +
function should then be added. If its database contains information on
 +
each “license”, one could easily find information on a foreign
 +
organism, in case they found it in the wild (that is, anywhere else
 +
than the lab), and had it sequenced afterwards. Upon entering the
 +
parts-registry, one should then be able to enter the license and gain
 +
access to information on the parts that the team / lab / company has
 +
created. Anyone should be able to enter the license code into the
 +
parts-registry and gain access to all information on the creating team,
 +
the parts created by the team, and of course some contact information,
 +
in order to seek advice.<br>
 +
<br>
 +
<span style="font-weight: bold;">Procedure</span><br>
 +
<br>
 +
Retrieval of the watermark should be easy, in the event of a rogue
 +
bacteria spreading havoc in the environment. Standardized placement of
 +
the watermark within the part should make it possible to easily
 +
retrieving the watermark through sequencing. Thus, if a rogue bacteria
 +
is discovered, it should be a simple matter to sequence the part, and
 +
obtain the license. Then it is just a matter of consulting the
 +
parts-registry to access all available information on the part and on
 +
how to contact the creating team. Getting a bacteria sequenced is a
 +
technology which is easy to access, and a lot of companies worldwide
 +
offers sequencing of bacteria, in addition it is a relative speedy
 +
process, which further makes the identification of a malign bacteria,
 +
and its properties relatively easy.<br>
 +
<br>
-
Every team, and lab / company which works with synthetic biology will be assigned a specific “license plate”, unique to them and being their ‘ID’ on parts-registry. An extension to parts registry’s search function should then be added. If its database contains information on each “license”, one could easily find information on a foreign organism, in case they found it in the wild (that is, anywhere else than the lab), and had it sequenced afterwards. Upon entering the parts-registry, one should then be able to enter the license and gain access to information on the parts that the team / lab / company has created. Anyone should be able to enter the license code into the parts-registry and gain access to all information on the creating team, the parts created by the team, and of course some contact information, in order to seek advice.
+
===== A full description of the modified organism =====<br>
-
 
+
<br>
-
 
+
<br>
-
'''Procedure'''
+
A full description of the modified organism should ideally contain the
-
 
+
following information<br>
-
 
+
<br>
-
Retrieval of the watermark should be easy, in the event of a rogue bacteria spreading havoc in the environment. Standardized placement of the watermark within the part should make it possible to easily retrieving the watermark through sequencing. Thus, if a rogue bacteria is discovered, it should be a simple matter to sequence the part, and obtain the license. Then it is just a matter of consulting the parts-registry to access all available information on the part and on how to contact the creating team. Getting a bacteria sequenced is a technology which is easy to access, and a lot of companies worldwide offers sequencing of bacteria, in addition it is a relative speedy process, which further makes the identification of a malign bacteria, and its properties relatively easy.
+
<span style="font-weight: bold;">A. characteristics of the
-
 
+
host and donor organisms</span><br>
-
</p>
+
<br>
-
===== A full description of the modified organism =====
+
1. Name(s) of the organism(s) in question<br>
-
 
+
<br>
-
<p style="text-align: justify;">
+
2. Origin of organism(s) in question<br>
-
A full description of the modified organism should ideally contain the following information
+
<br>
-
 
+
3. Information on the reproductive cyclus of the parental organisms as
-
A. characteristics of the host and donor organisms
+
well as the host<br>
-
 
+
<br>
-
1. Name(s) of the organism(s) in question
+
4. Description of any previous genetic modification<br>
-
 
+
<br>
-
2. Origin of organism(s) in question
+
5. Stability<br>
-
 
+
<br>
-
3. Information on the reproductive cyclus of the parental organisms as well as the host
+
6. Details concerning pathogenesis, virulence, infectivity or toxicity<br>
-
 
+
<br>
-
4. Description of any previous genetic modification
+
7. characteristics of endogene vectors:<br>
-
 
+
<br>
-
5. Stability
+
-sequence<br>
-
 
+
<br>
-
6. Details concerning pathogenesis, virulence, infectivity or toxicity
+
-mobilisation<br>
-
 
+
<br>
-
7. characteristics of endogene vectors:
+
-specificity<br>
-
 
+
<br>
-
-sequence
+
-the presence of resistance-genes<br>
-
 
+
<br>
-
-mobilisation
+
8. host spectrum,<br>
-
 
+
<br>
-
-specificity
+
9. potentially significant physiological traits and the stability of
-
 
+
these traits<br>
-
-the presence of resistance-genes
+
<br>
-
 
+
10. natural habitat<br>
-
8. host spectrum,
+
<br>
-
 
+
11. significant role in environmental processes&nbsp; <br>
-
9. potentially significant physiological traits and the stability of these traits
+
<br>
-
 
+
12. Competition or symbiosis with other naturally occurring organisms<br>
-
10. natural habitat
+
<br>
-
 
+
13. Ability to create survival structures (i.e. the ability to create
-
11. significant role in environmental processes
+
spores)<br>
-
 
+
<br style="font-weight: bold;">
-
12. Competition or symbiosis with other naturally occurring organisms
+
<span style="font-weight: bold;">B. characteristics of the
-
 
+
genetically modified organism</span><br>
-
13. Ability to create survival structures (i.e. the ability to create spores)
+
<br>
-
 
+
1. origin of the genetic material used to modify the organism, as well
-
 
+
as the intended functions of this material<br>
-
 
+
<br>
-
B. characteristics of the genetically modified organism
+
2. Description of the modification, including the method of vector
-
 
+
insertion in the host organism, as well as the <br>
-
1. origin of the genetic material used to modify the organism, as well as the intended functions of this material
+
method used to create the genetically modified production-organism<br>
-
 
+
<br>
-
2. Description of the modification, including the method of vector insertion in the host organism, as well as the  
+
3. the function of the genetic modification<br>
-
method used to create the genetically modified production-organism
+
<br>
-
 
+
4. origin and characteristics of the vector<br>
-
3. the function of the genetic modification
+
<br>
-
 
+
5. structure and size of vector in the genetically modified
-
4. origin and characteristics of the vector
+
production-organism<br>
-
 
+
<br>
-
5. structure and size of vector in the genetically modified production-organism
+
6. stability of the organism with respect to genetic traits<br>
-
 
+
<br>
-
6. stability of the organism with respect to genetic traits
+
7. mobiliseringshyppigheden of the inserted vector and/or the
-
 
+
organism’s ability to transfer genetic material<br>
-
7. mobiliseringshyppigheden of the inserted vector and/or the organism’s ability to transfer genetic material
+
<br>
-
 
+
8. activity of the expressed protein<br>
-
8. activity of the expressed protein
+
<br>
-
 
+
<span style="font-weight: bold;">C. Health concerns</span><br>
-
 
+
<br>
-
 
+
1. Toxic or allergenic properties<br>
-
C. Health concerns
+
<br>
-
 
+
2. Product risks<br>
-
1. Toxic or allergenic properties
+
<br>
-
 
+
3. The genetic modified organism’s pathogenic properties compared with
-
2. Product risks
+
the donor – or the host organisms or possibly <br>
-
 
+
the donor organism<br>
-
3. The genetic modified organism’s pathogenic properties compared with the donor – or the host organisms or possibly  
+
<br>
-
the donor organism
+
4. Colonization ability<br>
-
 
+
<br>
-
4. Colonization ability
+
5. If the organism is pathogenic to humans, who are immune competent:<br>
-
 
+
<br>
-
5. If the organism is pathogenic to humans, who are immune competent:
+
a) Cause illness and the pathogenic mechanism, including invasiveness
-
 
+
and virulence<br>
-
a) Cause illness and the pathogenic mechanism, including invasiveness and virulence
+
<br>
-
 
+
b) infectivity<br>
-
b) infectivity
+
<br>
-
 
+
c) infective dose<br>
-
c) infective dose
+
<br>
-
 
+
d) host range, possibility of change<br>
-
d) host range, possibility of change
+
<br>
-
 
+
e) possibility for survival outside the human host<br>
-
e) possibility for survival outside the human host
+
<br>
-
 
+
f) The presence of vectors or other distribution areas<br>
-
f) The presence of vectors or other distribution areas
+
<br>
-
 
+
g) Biological stability<br>
-
g) Biological stability
+
<br>
-
 
+
h) resistance patterns against antibiotics<br>
-
h) resistance patterns against antibiotics
+
<br>
-
 
+
i) allergencity<br>
-
i) allergencity
+
<br>
-
 
+
j) chance for suitable disease treatment<br>
-
j) chance for suitable disease treatment
+
<br>
-
 
+
<span style="font-weight: bold;">D. Environmental concerns</span><br>
-
 
+
<br>
-
 
+
1. factors that might affect the organism’s ability for survival,
-
D. Environmental concerns
+
reproduction and it’s ability to spread in the <br>
-
 
+
environment.<br>
-
1. factors that might affect the organism’s ability for survival, reproduction and it’s ability to spread in the  
+
<br>
-
environment.
+
2. techniques for detection, identification and surveillance of the
-
 
+
modified organism<br>
-
2. techniques for detection, identification and surveillance of the modified organism
+
<br>
-
 
+
3. techniques for detection of transfer of genetic material to other
-
3. techniques for detection of transfer of genetic material to other organisms
+
organisms<br>
-
 
+
<br>
-
4. known and expected habitats of the modified organism
+
4. known and expected habitats of the modified organism<br>
-
 
+
<br>
-
5. description of ecosystems into which the organism could spread in the event of an accident
+
5. description of ecosystems into which the organism could spread in
-
 
+
the event of an accident<br>
-
6. expected result of interaction between the modified organism and naturally occurring bacteria that would be  
+
<br>
-
affected in the event of an accident
+
6. expected result of interaction between the modified organism and
-
 
+
naturally occurring bacteria that would be <br>
-
7. known and expected effects on animals and plants, with regards to pathogenesis, virulence, infectivity, toxicity,  
+
affected in the event of an accident<br>
-
allergenicity, colonisation
+
<br>
-
 
+
7. known and expected effects on animals and plants, with regards to
-
8.known or expected contribution to bio-geo-chemic processes
+
pathogenesis, virulence, infectivity, toxicity, <br>
-
 
+
allergenicity, colonisation<br>
-
9. methods for decontamination of the area in the event of an accident
+
<br>
-
 
+
8.known or expected contribution to bio-geo-chemic processes&nbsp; <br>
-
 
+
<br>
-
[https://www.retsinformation.dk/Forms/R0710.aspx?id=12325 [3]]
+
9. methods for decontamination of the area in the event of an accident<br>
-
 
+
<br>
-
Once again please note that this is only intended as a guideline on how to characterize the part in the most wholesome manner.
+
[https://www.retsinformation.dk/Forms/R0710.aspx?id=12325 [3]]<br>
-
 
+
<br>
-
 
+
Once again please note that this is only intended as a guideline on how
-
'''Risk-assessment in conjunction with the use of this part in a particular organism.'''
+
to characterize the part in the most wholesome manner.<br>
-
 
+
<br>
-
Should the part, or a number of parts, be inserted into an organism the team should perform a risk-assessment and make it available on the parts-registry. In some countries, it is mandatory to submit a risk-assessment prior to engaging in a project involving synthetic biology, so we believe that any risk-assessments should be made public through parts-registry.
+
<span style="font-weight: bold;">Risk-assessment in
-
 
+
conjunction with the use of this part in a particular organism.</span><br>
-
 
+
<br>
-
'''Inclusion of copyright information?'''
+
Should the part, or a number of parts, be inserted into an organism the
-
 
+
team should perform a risk-assessment and make it available on the
-
We do not believe in any form of copyright prohibition. We believe in an open-source approach to the field of synthetic biology, as in iGEM. Any copy-right prohibitions would only stall the progress in this most vital field of science. We believe that any and all information on created parts, and experience with these parts in particular organisms, should be shared freely.
+
parts-registry. In some countries, it is mandatory to submit a
-
 
+
risk-assessment prior to engaging in a project involving synthetic
-
 
+
biology, so we believe that any risk-assessments should be made public
-
'''Information on how to neutralize bacteria'''
+
through parts-registry.<br>
-
 
+
<br>
-
This clause is intended as security measure. Should the bacteria be released into the environment, the parts-registry site should contain information on how to neutralize the bacteria. If the bacteria has an kill-code inserted, the site should describe how to enact the self-destruct mechanism.
+
<br>
-
</p>
+
<span style="font-weight: bold;">Inclusion of copyright
-
===== Anticipated problems =====
+
information?</span><br>
-
<p style="text-align: justify;">
+
<br>
-
 
+
We do not believe in any form of copyright prohibition. We believe in
-
'''Code deterioration'''
+
an open-source approach to the field of synthetic biology, as in iGEM.
-
 
+
Any copy-right prohibitions would only stall the progress in this most
-
The code will deteriorate over time due to mutation. This could prove to be a serious problem should watermarking become an integrated part of synthetic biology. Should the genetic watermark deteriorate to the point where one is no longer able to read it, it would not constitute any kind of safety measure, being able to tell that the part was likely to have been made artificially being the only thing we would be able to tell.
+
vital field of science. We believe that any and all information on
-
 
+
created parts, and experience with these parts in particular organisms,
-
Knowing that data will deteriorate, it may be impossible to determine whether the watermark found in a rogue bacteria is authentic or a degenerate. The deterioration is however slow and arbitrary. Our code is so small, that the change that any nucleotide associated with the watermark is going to mutate is very limited. The chances of finding the authentic code intact should be very good.
+
should be shared freely.<br>
-
 
+
<br>
-
'''The open source approach'''
+
<br>
-
 
+
<span style="font-weight: bold;">Information on how to
-
Sharing all this information on creating new synthetic parts that can be inserted into living organisms, also means that people with harmful agendas have access to this knowledge. This naturally means that wrongful actions are possible by use of synthetic biology, but we do not think that this should stand in the way of all the possibilities synthetic biology holds. Also, the more we know about how to create synthetic DNA strands, the better we are equipped if any harmful incident should occur. As of now, it might also just be easier to drop a bomb or send out letters of anthrax.
+
neutralize bacteria</span><br>
-
 
+
<br>
-
Should a bacteria be used for a malign purpose it would be quite easy to insert a false watermark to blame others. So we need to keep in mind that a plot could be made against someone. However, if anyone was interested in harming as many as possible, this person probably wouldn’t care about watermarking at all. This also means that we cannot expect watermarking to play a part in any legal case.
+
This clause is intended as security measure. Should the bacteria be
-
</p>
+
released into the environment, the parts-registry site should contain
-
==== Kill-code ====  
+
information on how to neutralize the bacteria. If the bacteria has an
-
<p style="text-align: justify;">
+
kill-code inserted, the site should describe how to enact the
-
-Why should we consider inserting kill-codes in genetically modified organisms
+
self-destruct mechanism.<br>
-
-What should an efficient kill-code contain
+
<br>
-
-Which bacteria should have a kill-code inserted
+
===== Anticipated problems =====<br>
-
-When should one enact a kill
+
<span style="font-weight: bold;">Code deterioration</span><br>
-
-Should it be mandatory or optional
+
<br>
-
-Availability of the kill-code
+
The code will deteriorate over time due to mutation. This could prove
-
 
+
to be a serious problem should watermarking become an integrated part
-
''Why should we consider kill-codes''
+
of synthetic biology. Should the genetic watermark deteriorate to the
-
 
+
point where one is no longer able to read it, it would not constitute
-
Why should we consider inserting an self-destruct device into modified bacteria?
+
any kind of safety measure, being able to tell that the part was likely
-
No system is completely safe. Accidents, no matter how statistically unlikely, will occur. This is especially true when human beings are involved.
+
to have been made artificially being the only thing we would be able to
-
 
+
tell.<br>
-
An efficient kill-code should
+
<br>
-
 
+
Knowing that data will deteriorate, it may be impossible to determine
-
    -be activated by an efficient signal
+
whether the watermark found in a rogue bacteria is authentic or a
-
    -be persistent
+
degenerate. The deterioration is however slow and arbitrary. Our code
-
    -terminate the bacteria within a very short time span
+
is so small, that the change that any nucleotide associated with the
-
    -not interfere with other functions in the bacteria
+
watermark is going to mutate is very limited. The chances of finding
-
 
+
the authentic code intact should be very good.<br>
-
''Efficient signal''
+
<br>
-
 
+
<span style="font-weight: bold;">The open source approach</span><br>
-
What is to be considered an efficient signal? It should be a signal that
+
<br>
-
 
+
Sharing all this information on creating new synthetic parts that can
-
-We can control
+
be inserted into living organisms, also means that people with harmful
-
 
+
agendas have access to this knowledge. This naturally means that
-
-We can induce at will
+
wrongful actions are possible by use of synthetic biology, but we do
-
 
+
not think that this should stand in the way of all the possibilities
-
-That is unlikely to affect other organisms in any harmful way
+
synthetic biology holds. Also, the more we know about how to create
-
 
+
synthetic DNA strands, the better we are equipped if any harmful
-
Would it be sensible to use a naturally occurring signal? Would be beneficial should the bacteria be released into the environment, where the naturally occurring signal would help destroy the rogue bacteria within the shortest possible time span. Of course, it would only be usable if the laboratory does not itself emit, or at least is able to shield the organism, from the activating signal.
+
incident should occur. As of now, it might also just be easier to drop
-
An example could be that the kill-code is activated by light of a certain wave-length. If the sun emits this wave-length of light, it should destroy any bacteria that might have been released into nature. It is very easy to shield the organism from the light of the sun in the laboratory, and thus we will not accidentally destroy controlled organisms. Thus we could satisfy the three criteria I have listed above: we can control light of a certain wave-length, at least in a laboratory environment. We can induce this light at will and, thirdly, this light will not harm any other organisms.
+
a bomb or send out letters of anthrax.<br>
-
One of the major cons of using a naturally occurring signal is that it would be almost impossible to use the organism, in case it would serve any environmental purposes.      
+
<br>
-
 
+
Should a bacteria be used for a malign purpose it would be quite easy
-
''Persistence''
+
to insert a false watermark to blame others. So we need to keep in mind
-
 
+
that a plot could be made against someone. However, if anyone was
-
The kill-code would be left useless should the bacteria dispose of the code through natural evolution within a very short time. Should the bacteria accidentally or, being subject to malign use, intentionally be released into the environment, we would be unable to enact the built-in kill-code, if the code is not linked in some manner to a vital part of the bacterium's genome. If the code is linked to an essential part of the bacterium's genome, it should be unable to dispose of the code without self-termination, thus ensuring persistence. Without the requirement for persistence, the kill-code would give a false sense of security, not knowing if the code is still present in the organism in question.
+
interested in harming as many as possible, this person probably
-
 
+
wouldn’t care about watermarking at all. This also means that we cannot
-
''Termination within a short time span''
+
expect watermarking to play a part in any legal case.<br>
-
 
+
<br>
-
The shorter the amount of time before the signal is enacted, 'till the rogue bacteria is destroyed, the less harm it is likely to cause.
+
<br>
-
''
+
==== Kill-code ==== <br>
-
Non-interference with other functions''
+
<br>
-
 
+
-Why should we consider inserting kill-codes in genetically modified
-
''Which type of bacteria should contain kill-codes''
+
organisms<br>
-
 
+
-What should an efficient kill-code contain<br>
-
We suggest level 3 and 4 bacteria would be edible for insertion of a kill-code. Level 1 bacteria pose little to no threat to human beings or the environment, and insertion of a kill-code would not be relevant. Level 2 organisms too would not pose any notable threat, and insertion of a kill-code would be overkill.
+
-Which bacteria should have a kill-code inserted<br>
-
Level 3 and 4 organisms however pose moderate to serious threat to human beings, animals, plants and the environment at large. Should any of these organisms escape into the outside world, they would cause considerable harm to the environment.
+
-When should one enact a kill<br>
-
</p>
+
-Should it be mandatory or optional<br>
 +
-Availability of the kill-code<br>
 +
<br>
 +
''Why should we consider kill-codes''<br>
 +
<br>
 +
Why should we consider inserting an self-destruct device into modified
 +
bacteria?<br>
 +
No system is completely safe. Accidents, no matter how statistically
 +
unlikely, will occur. This is especially true when human beings are
 +
involved.<br>
 +
<br>
 +
An efficient kill-code should<br>
 +
<br>
 +
&nbsp;&nbsp;&nbsp; -be activated by an efficient signal<br>
 +
&nbsp;&nbsp;&nbsp; -be persistent<br>
 +
&nbsp;&nbsp;&nbsp; -terminate the bacteria within a very
 +
short time span<br>
 +
&nbsp;&nbsp;&nbsp; -not interfere with other functions in
 +
the bacteria<br>
 +
<br>
 +
<span style="font-style: italic;">Efficient signal</span><br>
 +
<br>
 +
What is to be considered an efficient signal? It should be a signal that<br>
 +
<br>
 +
-We can control<br>
 +
<br>
 +
-We can induce at will<br>
 +
<br>
 +
-That is unlikely to affect other organisms in any harmful way<br>
 +
<br>
 +
Would it be sensible to use a naturally occurring signal? Would be
 +
beneficial should the bacteria be released into the environment, where
 +
the naturally occurring signal would help destroy the rogue bacteria
 +
within the shortest possible time span. Of course, it would only be
 +
usable if the laboratory does not itself emit, or at least is able to
 +
shield the organism, from the activating signal.<br>
 +
An example could be that the kill-code is activated by light of a
 +
certain wave-length. If the sun emits this wave-length of light, it
 +
should destroy any bacteria that might have been released into nature.
 +
It is very easy to shield the organism from the light of the sun in the
 +
laboratory, and thus we will not accidentally destroy controlled
 +
organisms. Thus we could satisfy the three criteria I have listed
 +
above: we can control light of a certain wave-length, at least in a
 +
laboratory environment. We can induce this light at will and, thirdly,
 +
this light will not harm any other organisms.<br>
 +
One of the major cons of using a naturally occurring signal is that it
 +
would be almost impossible to use the organism, in case it would serve
 +
any environmental
 +
purposes.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 +
<br>
 +
<br>
 +
<span style="font-style: italic;">Persistence</span><br>
 +
<br>
 +
The kill-code would be left useless should the bacteria dispose of the
 +
code through natural evolution within a very short time. Should the
 +
bacteria accidentally or, being subject to malign use, intentionally be
 +
released into the environment, we would be unable to enact the built-in
 +
kill-code, if the code is not linked in some manner to a vital part of
 +
the bacterium's genome. If the code is linked to an essential part of
 +
the bacterium's genome, it should be unable to dispose of the code
 +
without self-termination, thus ensuring persistence. Without the
 +
requirement for persistence, the kill-code would give a false sense of
 +
security, not knowing if the code is still present in the organism in
 +
question.<br>
 +
<br>
 +
<span style="font-style: italic;">Termination within a
 +
short time span</span><br>
 +
<br>
 +
The shorter the amount of time before the signal is enacted, 'till the
 +
rogue bacteria is destroyed, the less harm it is likely to cause.<br>
 +
<br>
 +
<span style="font-style: italic;">Non-interference with
 +
other functions</span><br>
 +
<br>
 +
<span style="font-style: italic;">Which type of bacteria
 +
should contain kill-codes</span><br>
 +
<br>
 +
We suggest level 3 and 4 bacteria would be edible for insertion of a
 +
kill-code. Level 1 bacteria pose little to no threat to human beings or
 +
the environment, and insertion of a kill-code would not be relevant.
 +
Level 2 organisms too would not pose any notable threat, and insertion
 +
of a kill-code would be overkill.<br>
 +
Level 3 and 4 organisms however pose moderate to serious threat to
 +
human beings, animals, plants and the environment at large. Should any
 +
of these organisms escape into the outside world, they would cause
 +
considerable harm to the environment.<br>
 +
<br>
 +
</body>
 +
</html>
== Appendix I: risk assessment of the project ==
== Appendix I: risk assessment of the project ==

Revision as of 11:44, 21 October 2010