Just make everything TOP SECRET like a real governmentNow one can make their own system up - just need some logic behind it and it should also be sorta straight forward in application. You don't want people to mix up secrecy levels after all.
Just make everything TOP SECRET like a real governmentNow one can make their own system up - just need some logic behind it and it should also be sorta straight forward in application. You don't want people to mix up secrecy levels after all.
The thing is, leaks spread. So if it's something that Kyubey can't be allowed to know, then we need to put very careful restrictions on who can be told to ensure that it isn't said carelessly. There really couldn't be any BLUE or GREEN or even YELLOW information that needs to be kept from Kyubey, because anything that widespread he will hear. Likewise, ULTRAVIOLET information may only be specifically damaging to Homura, but telling anybody else exponentially increases the risk of it getting back to either Homura or Kyubey.
Time Sensitive nature would be priority rather then classification. Two different and separate things that should be kept separate.
Well more or less this. The coverterms are not meant to be for everything rather they signal special handling instructions. The general baseline would/could be the normal Top Secret, Secret, Classified system which is based off how much damage a leak would cause.
The extra portions are modifiers to how one handles it. I was just trying to make a joke AND avoid making a whole new system. Which is why I used CHRONO for time travel related stuff since it IS on the ball in terms of names. the handling term can't spell out the secret but its not like anyone not in the know would get the connection.
Now one can make their own system up - just need some logic behind it and it should also be sorta straight forward in application. You don't want people to mix up secrecy levels after all.
So for example you could have a handling caveat that FORBIDS risking disclosure to KB since the base system is a general disclosure to anyone not read in. So something could be Secret/NOKB since its only a major issue if it links to say the Tokyo Council but it CANNOT be leaked to KB ever.
Threatcon. REDCON, Priority and Classification should all be separate systems - you don't want to mix those systems together since they all do VERY different jobs. That and I don't want some people to be at a different thretcon then others since they are not read in. They might not KNOW why everyone is loading for bear but they know they need to load for bear.
Information at ORANGE level (e.g. the metabomb) and higher is when we start using timestop and privacy spheres to keep Kyubey from learning it, and sharing with only trusted people.I was using the keep it from KB thing as an example. Most information that we can't let KB know would likely also be VERY unwelcome in anyone elses hands
Actually I wonder if Sayaka's clones 'transmit' over means KB can't hear. So if we whsiper to Sayaka clone A, Sayaka Clone B can report what was heard or Sayaka Prime can listen in.
Secure Sayaka Based Comms!
I say we codename it angel : P
You know guys it was a joke at first - since Sabrina has all these secerts.
Hence the semi-serious caveats. - I did not expect anyone to make a semi-proper system. -__-
Actually I wonder if Sayaka's clones 'transmit' over means KB can't hear. So if we whsiper to Sayaka clone A, Sayaka Clone B can report what was heard or Sayaka Prime can listen in.
Secure Sayaka Based Comms!
I say we codename it angel : P
And my first question is how do we test to see if it is affected by lightspeed?Actually I wonder if Sayaka's clones 'transmit' over means KB can't hear. So if we whsiper to Sayaka clone A, Sayaka Clone B can report what was heard or Sayaka Prime can listen in.
Secure Sayaka Based Comms!
METAPHYSICS/GRIEF/WITCHES/ACTIVE/W_287
Warning! This file is CLASSIFIED: LIME SLICE.
Please verify credentials to access. Unauthorized access or distribution of this material is prohibited.
Account: SVee_O1
Password: aDf1905yS7eM41nUcurRyFirnagZ3N
SVee_O1 Access Attempt Logged
Location: Mitakihara_Prime_003
Time: 2019/05/19 @ UTC 14:54:32.928
Standby for secondary identity verification.
Failure to verify within _1_ minute(s) will result in immediate enaction of countermeasures.
...
Complete.
Soul Gem Harmonics Confirmed.
===============
Alert: This file is a CLASS M1 INFOHAZARD. Precaution DISCO PANTHER is in effect.
Are you certain you wish to proceed? [Y/N]
Witch Case Number 287: Mnemnosyne
Puella Magi ID: UNKNOWN
Active Since: UNKNOWN (Earliest verified 1982, See Hanover_1982.07.11)
Region of Activity: Global
Threat Level: Moderate
Priority: C Class
The Witch of Regret, Mnemnosyne longs to fade away, such that noone in the world knows of her existence.
This takes the form of an aggressively spreading effect that initially targets those with information about the witch and removes those memories, but then spreads to removing memories of the initial targets from secondary infectees, and memories of secondary targets from tertiary affiliates. No spread past three degrees of separation has yet been noted.
The effect is global in scope, and extremely potent - only Class A* memory augments or antimagic applied immediately are effective, and after 16 hours full restoration of lost information is impossible with any currently known ability set. (See: Moscow_2017.12.03)
The inability to recover lost information with Postcognition or Temporal Intervention implies a mechanism operating on a deeper level then mere memory modification. Some degree of retrocausal event alteration may be occuring, though the inconsistencies between memories of affected and unaffected individuals complicate this hypothesis.
Beyond this, there is also a marked tendency for any physical evidence of the witch to be lost or destroyed at a significantly abberant rate - this is speculated to be the result of the witches familiars. This particular file needed to be reconstructed at least 3 times prior to the creation of DISCO PANTHER protocols.
The abberant power of the witch may indicate it is a conglomerate, although due to its abilities no confirmation of this has yet been made - it may instead have spawned from a single magical girl of exceeding potential.
The Incubator claims to have no information on contractees that could spawn such a witch, but it is unclear if this is intentional misdirection or if the Incubator has also had its memory altered. (See: Transcript I_W4091)
At the present moment, with no confirmed location and no actable information about Mnemnosyne, there are no active efforts to capture her for LAZARUS. When PROJECT SCANTRON reaches completion, further developed reality/memory/time anchoring effects may make capture and phase change plausible.
=====
See: Full Mnemnosyne Incident List
See: List of Active Witches
METAPHYSICS/GRIEF/WITCHES/ACTIVE/W_287
Warning! This file is CLASSIFIED: LIME SLICE.
Please verify credentials to access. Unauthorized access or distribution of this material is prohibited.
Account: SVee_O1
Password: aDf1905yS7eM41nUcurRyFirnagZ3N
SVee_O1 Access Attempt Logged
Location: Mitakihara_Prime_003
Time: 2019/05/19 @ UTC 14:54:32.928
Standby for secondary identity verification.
Failure to verify within _1_ minute(s) will result in immediate enaction of countermeasures.
...
Complete.
Soul Gem Harmonics Confirmed.
===============
Alert: This file is a CLASS M1 INFOHAZARD. Precaution DISCO PANTHER is in effect.
Are you certain you wish to proceed? [Y/N]
Witch Case Number 287: Mnemnosyne
Puella Magi ID: UNKNOWN
Active Since: UNKNOWN (Earliest verified 1982, See Hanover_1982.07.11)
Region of Activity: Global
Threat Level: Moderate
Priority: C Class
The Witch of Regret, Mnemnosyne longs to fade away, such that noone in the world knows of her existence.
This takes the form of an aggressively spreading effect that initially targets those with information about the witch and removes those memories, but then spreads to removing memories of the initial targets from secondary infectees, and memories of secondary targets from tertiary affiliates. No spread past three degrees of separation has yet been noted.
The effect is global in scope, and extremely potent - only Class A* memory augments or antimagic applied immediately are effective, and after 16 hours full restoration of lost information is impossible with any currently known ability set. (See: Moscow_2017.12.03)
The inability to recover lost information with Postcognition or Temporal Intervention implies a mechanism operating on a deeper level then mere memory modification. Some degree of retrocausal event alteration may be occuring, though the inconsistencies between memories of affected and unaffected individuals complicate this hypothesis.
Beyond this, there is also a marked tendency for any physical evidence of the witch to be lost or destroyed at a significantly abberant rate - this is speculated to be the result of the witches familiars. This particular file needed to be reconstructed at least 3 times prior to the creation of DISCO PANTHER protocols.
The abberant power of the witch may indicate it is a conglomerate, although due to its abilities no confirmation of this has yet been made - it may instead have spawned from a single magical girl of exceeding potential.
The Incubator claims to have no information on contractees that could spawn such a witch, but it is unclear if this is intentional misdirection or if the Incubator has also had its memory altered. (See: Transcript I_W4091)
At the present moment, with no confirmed location and no actable information about Mnemnosyne, there are no active efforts to capture her for LAZARUS. When PROJECT SCANTRON reaches completion, further developed reality/memory/time anchoring effects may make capture and phase change plausible.
=====
See: Full Mnemnosyne Incident List
See: List of Active Witches
Thirdly- ... did Sabrina collaborate with techguca and soulguca to make a magical classified grief internet computer network?
METAPHYSICS/GRIEF/WITCHES/ACTIVE/W_287
Warning! This file is CLASSIFIED: LIME SLICE.
Please verify credentials to access. Unauthorized access or distribution of this material is prohibited.
Account: SVee_O1
Password: aDf1905yS7eM41nUcurRyFirnagZ3N
SVee_O1 Access Attempt Logged
Location: Mitakihara_Prime_003
Time: 2019/05/19 @ UTC 14:54:32.928
Standby for secondary identity verification.
Failure to verify within _1_ minute(s) will result in immediate enaction of countermeasures.
...
Complete.
Soul Gem Harmonics Confirmed.
===============
Alert: This file is a CLASS M1 INFOHAZARD. Precaution DISCO PANTHER is in effect.
Are you certain you wish to proceed? [Y/N]
Witch Case Number 287: Mnemnosyne
Puella Magi ID: UNKNOWN
Active Since: UNKNOWN (Earliest verified 1982, See Hanover_1982.07.11)
Region of Activity: Global
Threat Level: Moderate
Priority: C Class
The Witch of Regret, Mnemnosyne longs to fade away, such that noone in the world knows of her existence.
This takes the form of an aggressively spreading effect that initially targets those with information about the witch and removes those memories, but then spreads to removing memories of the initial targets from secondary infectees, and memories of secondary targets from tertiary affiliates. No spread past three degrees of separation has yet been noted.
The effect is global in scope, and extremely potent - only Class A* memory augments or antimagic applied immediately are effective, and after 16 hours full restoration of lost information is impossible with any currently known ability set. (See: Moscow_2017.12.03)
The inability to recover lost information with Postcognition or Temporal Intervention implies a mechanism operating on a deeper level then mere memory modification. Some degree of retrocausal event alteration may be occuring, though the inconsistencies between memories of affected and unaffected individuals complicate this hypothesis.
Beyond this, there is also a marked tendency for any physical evidence of the witch to be lost or destroyed at a significantly abberant rate - this is speculated to be the result of the witches familiars. This particular file needed to be reconstructed at least 3 times prior to the creation of DISCO PANTHER protocols.
The abberant power of the witch may indicate it is a conglomerate, although due to its abilities no confirmation of this has yet been made - it may instead have spawned from a single magical girl of exceeding potential.
The Incubator claims to have no information on contractees that could spawn such a witch, but it is unclear if this is intentional misdirection or if the Incubator has also had its memory altered. (See: Transcript I_W4091)
At the present moment, with no confirmed location and no actable information about Mnemnosyne, there are no active efforts to capture her for LAZARUS. When PROJECT SCANTRON reaches completion, further developed reality/memory/time anchoring effects may make capture and phase change plausible.
=====
See: Full Mnemnosyne Incident List
See: List of Active Witches
Adfligosystema inu curry firnagzen.
And my first question is how do we test to see if it is affected by lightspeed?
... Sabrina: *classifies stash of Mami pictures as ULTRA TOP SECERT*
Later
METAPHYSICS/GRIEF/WITCHES/ACTIVE/W_287
Warning! This file is CLASSIFIED: LIME SLICE.
Please verify credentials to access. Unauthorized access or distribution of this material is prohibited.
Account: SMiki_01
Password: t07al1Yn0t4Nan9E1
SMiki_01 Access Attempt Logged
Location: Mitakihara_Prime_008
Time: 2020/07/23 @ UTC 14:54:32.928
Error: Insufficient Security Clearance
Request Denied
---
Sayaka narrowed her eyes at the words on the screen.
"One day Sabrina," she mumbled. "One day."
"But not today," said a quiet voice behind her. Turning, she saw Homura standing, a raised eyebrow.
Sayaka pouted. Stupid security clearance.
Yes, I'm saying that the codewords should be firnbot commands.
[X] Kaizuki
Alas, I'm a bit too out of it right now to continue working on my own vote.
------------
As far as codewords go, I feel they should probably be pretty far removed from the subject matter, such that no one listening in on a conversation will immediately know what they mean or, ideally, even that they refer to some secret at all.
Joking names are okay, but it should be fairly removed or abstracted from the subject matter. As it turns out, we actually have a reference for that kind of removed joke, from our own author even.
Yes, I'm saying that the codewords should be firnbot commands.