"Okay, you know what, I am not actually going to be able to focus on math until I get this out of my system.  We're just going to put everything about logarithms and bags of factors of 2 and prediction-scoring rules on hold, to be resumed later."

"Instead I'm going to deliver a talk that had better be transcribed and delivered accurately to everyone who is trying to manage Project Lawful."

"Project Lawful is a terrible name, by the way.  The moment I heard it, I knew that the decision-making processes behind it were going to be correspondingly terrible.  I wasn't going to say this until after I'd covered the concepts of probabilistic updating, probabilistic entanglement, and mutual information - those being the Law which would allow me to explain exactly why this was a terrible idea."

"Absent that Law, consider an adversary pondering two alternative hypotheses based on evidence they've managed to collect, one of which is that a certain Chelish project is investigating a mysterious source of knowledge not previously existent in Golarion, and one of which is that Cheliax is making a massive effort to scale up metalworking for some other reason.  If you give your projects cool names, one of these possibilities will sound much more than the other like something that you'd call Project Lawful, even if they can't deduce the first hypothesis just from the name.  You should call your amazing top-secret project Project Doorknob or something else chosen completely at random which carries no information whatsoever about what the project actually does, except, of course, that if all your other top-secret projects also have cool names, the one with a sane name will stand out as being the only one with any sane thinker in it.  Project Dragon, maybe."

"The password to the Forbiddance on the previous project site is also terrible and completely insecure and whoever set it should never be allowed to invent any passwords again, and if you're thinking that I'm an idiot for not thinking to mention that before they set the password here, you're right.  For the record, a slightly better password for a Forbiddance might be, for example, 'escape copper shore'.  It's not very hard to remember, but very difficult for an adversary to guess unless they get a quite large number of tries."

"But I digress."

"Basic project management principles, an angry rant by Keltham of dath ilan, section one:  How to have anybody having responsibility for anything."

"Okay, you know what, I am not actually going to be able to focus on math until I get this out of my system.  We're just going to put everything about logarithms and bags of factors of 2 and prediction-scoring rules on hold, to be resumed later."

"Instead I'm going to deliver a talk that had better be transcribed and delivered accurately to everyone who is trying to manage Project Lawful."

"Project Lawful is a terrible name, by the way.  The moment I heard it, I knew that the decision-making processes behind it were going to be correspondingly terrible.  I wasn't going to say this until after I'd covered the concepts of probabilistic updating, probabilistic entanglement, and mutual information - those being the Law which would allow me to explain exactly why this was a terrible idea."

"But absent that Law, consider an adversary pondering two alternative hypotheses based on evidence they've managed to collect.  One theory is that a certain Chelish project is investigating a mysterious source of knowledge not previously existent in Golarion.  One theory is that Cheliax is making a massive effort to scale up metalworking because they expect to be invaded.  If you give your projects cool names, one of these possibilities will sound much more than the other like something that someone might've called Project Lawful, even if they can't deduce the true answer just from the name.  You should call your amazing top-secret project Project Doorknob, or something else chosen completely at random by a true randomness source, which carries no information whatsoever about what the project actually does.  Except, of course, that if all your other top-secret projects also have cool names, the one with a sane name will stand out as being the only one with any sane thinker in it.  So this should be Project Dragon, maybe."

"The password to the Forbiddance on the previous project site is also terrible and completely insecure and whoever set it should never be allowed to invent any passwords again, and if you're thinking that I'm an idiot for not thinking to mention that before they set the password here, you're right.  For the record, a slightly better password for a Forbiddance might be, for example, 'escape copper shore'.  It's not very hard to remember, but very difficult for an adversary to guess unless they get a quite large number of tries."

"But I digress."

"Basic project management principles, an angry rant by Keltham of dath ilan, section one:  How to have anybody having responsibility for anything."

"Okay, you know what, I am not actually going to be able to focus on math until I get this out of my system.  We're just going to put everything about logarithms and bags of factors of 2 and prediction-scoring rules on hold, to be resumed later."

"Instead I'm going to deliver a talk that had better be transcribed and delivered accurately to everyone who is trying to manage Project Lawful."

"Project Lawful is a terrible name, by the way.  The moment I heard it, I knew that the decision-making processes behind it were going to be correspondingly terrible.  I wasn't going to say this until after I'd covered the concepts of probabilistic updating, probabilistic entanglement, and mutual information - those being the Law which would allow me to explain exactly why this was a terrible idea."

"But absent that Law, consider an adversary pondering two alternative hypotheses based on evidence they've managed to collect.  One theory is that a certain Chelish project is investigating a mysterious source of knowledge not previously existent in Golarion.  One theory is that Cheliax is making a massive effort to scale up metalworking because they expect to be invaded.  If you give your projects cool names, one of these possibilities will sound much more than the other like something that someone might've called Project Lawful, even if they can't deduce the true answer just from the name.  You should call your amazing top-secret project Project Doorknob, or something else chosen completely at random by a true randomness source, which carries no information whatsoever about what the project actually does.  Except, of course, that if all your other top-secret projects also have cool names, the one with a sane name will stand out as being the only one with any sane thinker in it, meaning, someone not from Golarion, if anybody like Lrilatha knows what that should look like.  So this should be Project Dragon, maybe."

"The password to the Forbiddance on the previous project site is also terrible and completely insecure and whoever set it should never be allowed to invent any passwords again, and if you're thinking that I'm an idiot for not thinking to mention that before they set the password here, you're right.  For the record, a slightly better password for a Forbiddance might be, for example, 'escape copper shore'.  It's not very hard to remember, but very difficult for an adversary to guess unless they get a quite large number of tries."

"But I digress."

"Basic project management principles, an angry rant by Keltham of dath ilan, section one:  How to have anybody having responsibility for anything."

"Okay, you know what, I am not actually going to be able to focus on math until I get this out of my system.  We're just going to put everything about logarithms and bags of factors of 2 and prediction-scoring rules on hold, to be resumed later."

"Instead I'm going to deliver a talk that had better be transcribed and delivered accurately to everyone who is trying to manage Project Lawful."

"Project Lawful is a terrible name, by the way.  The moment I heard it, I knew that the decision-making processes behind it were going to be correspondingly terrible.  I wasn't going to say this until after I'd covered the concepts of probabilistic updating, probabilistic entanglement, and mutual information - those being the Law which would allow me to explain exactly why this was a terrible idea."

"But absent that Law, consider an adversary pondering two alternative hypotheses based on evidence they've managed to collect.  One theory is that a certain Chelish project is investigating a mysterious source of knowledge not previously existent in Golarion.  One theory is that Cheliax is making a massive effort to scale up metalworking because they expect to be invaded.  If you give your projects cool names, one of these possibilities will sound much more than the other like something that someone might've called Project Lawful, even if they can't deduce the true answer just from the name.  You should call your amazing top-secret project Project Shoemaker, or something else chosen completely at random by a true randomness source, which carries no information whatsoever about what the project actually does.  Except, of course, that if all your other top-secret projects also have cool names, the one with a sane name will stand out as being the only one with any sane thinker in it, meaning, someone not from Golarion, if anybody like Lrilatha knows what that should look like.  So this should be Project Dragon, maybe."

"The password to the Forbiddance on the previous project site is also terrible and completely insecure and whoever set it should never be allowed to invent any passwords again, and if you're thinking that I'm an idiot for not thinking to mention that before they set the password here, you're right.  For the record, a slightly better password for a Forbiddance might be, for example, 'escape copper shore'.  It's not very hard to remember, but very difficult for an adversary to guess unless they get a quite large number of tries."

"But I digress."

"Basic project management principles, an angry rant by Keltham of dath ilan, section one:  How to have anybody having responsibility for anything."

"Okay, you know what, I am not actually going to be able to focus on math until I get this out of my system.  We're just going to put everything about logarithms and bags of factors of 2 and prediction-scoring rules on hold, to be resumed later."

"Instead I'm going to deliver a talk that had better be transcribed and delivered accurately to everyone who is trying to manage Project Lawful."

"Project Lawful is a terrible name, by the way.  The moment I heard it, I knew that the decision-making processes behind it were going to be correspondingly terrible.  I wasn't going to say this until after I'd covered the concepts of probabilistic updating, probabilistic entanglement, and mutual information - those being the Law which would allow me to explain exactly why this was a terrible idea."

"But absent that Law, consider an adversary pondering two alternative hypotheses based on evidence they've managed to collect.  One theory is that a certain Chelish project is investigating a mysterious source of knowledge not previously existent in Golarion.  One theory is that Cheliax is making a massive effort to scale up metalworking because they expect to be invaded.  If you give your projects cool names, one of these possibilities will sound much more than the other like something that someone might've called Project Lawful, even if they can't deduce the true answer just from the name.  You should call your amazing top-secret project Project Doorknob, or something else chosen completely at random by a true randomness source, which carries no information whatsoever about what the project actually does.  Except, of course, that if all your other top-secret projects also have cool names, the one with a sane name will stand out as being the only one with any sane thinker in it, meaning, someone not from Golarion, if anybody like Lrilatha knows what that should look like.  So this should be Project Dragon, maybe."

"The password to the Forbiddance on the previous project site is also terrible and completely insecure and whoever set it should never be allowed to invent any passwords again, and if you're thinking that I'm an idiot for not thinking to mention that before they set the password here, you're right.  For the record, a slightly better password for a Forbiddance might be, for example, 'escape copper shore'.  It's not very hard to remember, but very difficult for an adversary to guess unless they get a quite large number of tries."

"But I digress."

"Basic project management principles, an angry rant by Keltham of dath ilan, section one:  How to have anybody having responsibility for anything."

"Okay, you know what, I am not actually going to be able to focus on math until I get this out of my system.  We're just going to put everything about logarithms and bags of factors of 2 and prediction-scoring rules on hold, to be resumed later."

"Instead I'm going to deliver a talk that had better be transcribed and delivered accurately to everyone who is trying to manage Project Lawful."

"Project Lawful is a terrible name, by the way.  The moment I heard it, I knew that the decision-making processes behind it were going to be correspondingly terrible.  I wasn't going to say this until after I'd covered the concepts of probabilistic updating, probabilistic entanglement, and mutual information - those being the Law which would allow me to explain exactly why this was a terrible idea."

"But absent that Law, consider an adversary pondering two alternative hypotheses based on evidence they've managed to collect.  One theory is that a certain Chelish project is investigating a mysterious source of knowledge not previously existent in Golarion.  One theory is that Cheliax is making a massive effort to scale up metalworking because they expect to be invaded.  If you give your projects cool names, one of these possibilities will sound much more than the other like something that someone might've called Project Lawful, even if they can't deduce the true answer just from the name.  You should call your amazing top-secret project Project Doorknob, or something else chosen completely at random by a true randomness source, which carries no information whatsoever about what the project actually does.  Except, of course, that if all your other top-secret projects also have cool names, the one with a sane name will stand out as being the only one with any sane thinker in it, meaning, someone not from Golarion, if anybody like Lrilatha knows what that should look like.  So this should be Project Dragon, maybe."

"The password to the Forbiddance on the previous project site is also terrible and completely insecure and whoever set it should never be allowed to invent any passwords again, and if you're thinking that I'm an idiot for not thinking to mention that before they set the password here, you're right.  For the record, a slightly better password for a Forbiddance might be, for example, 'escape copper shore'.  It's not hard to remember, but difficult for an adversary to guess unless they get a quite large number of tries."

"But I digress."

"Basic project management principles, an angry rant by Keltham of dath ilan, section one:  How to have anybody having responsibility for anything."

"Okay, you know what, I am not actually going to be able to focus on math until I get this out of my system.  We're just going to put everything about logarithms and bags of factors of 2 and prediction-scoring rules on hold, to be resumed later."

"Instead I'm going to deliver a talk that had better be transcribed and delivered accurately to everyone who is trying to manage Project Lawful."

"Project Lawful is a terrible name, by the way.  The moment I heard it, I knew that the decision-making processes behind it were going to be correspondingly terrible.  I wasn't going to say this until after I'd covered the concepts of probabilistic updating, probabilistic entanglement, and mutual information - those being the Law which would allow me to explain exactly why this was a terrible idea -"

"But absent that Law, consider an adversary pondering two alternative hypotheses based on evidence they've managed to collect.  One theory is that a certain Chelish project is investigating a mysterious source of knowledge not previously existent in Golarion.  One theory is that Cheliax is making a massive effort to scale up metalworking because they expect to be invaded.  If you give your projects cool names, one of these possibilities will sound much more than the other like something that someone might've called Project Lawful, even if they can't deduce the true answer just from the name.  You should call your amazing top-secret project Project Doorknob, or something else chosen completely at random by a true randomness source, which carries no information whatsoever about what the project actually does.  Except, of course, that if all your other top-secret projects also have cool names, the one with a sane name will stand out as being the only one with any sane thinker in it, meaning, someone not from Golarion, if anybody like Lrilatha knows what that should look like.  So this should be Project Dragon, maybe."

"The password to the Forbiddance on the previous project site is also terrible and completely insecure and whoever set it should never be allowed to invent any passwords again, and if you're thinking that I'm an idiot for not thinking to mention that before they set the password here, you're right.  For the record, a slightly better password for a Forbiddance might be, for example, 'escape copper shore'.  It's not hard to remember, but difficult for an adversary to guess unless they get a quite large number of tries."

"But I digress."

"Basic project management principles, an angry rant by Keltham of dath ilan, section one:  How to have anybody having responsibility for anything."