News for hackers. Stuff that matters.
Re:SEC Asks Manhattan Federal Court to Hold Elon Musk in Con... by sokoloff on Wednesday February 27, 2019 @07:39PM (#19268160)
Excerpts rom the SEC court filing: The SEC required this provision as a term of its settlement with Musk in order to prevent Musk from recklessly disseminating false or inaccurate information about Tesla in the future. On February 19, 2019, Musk tweeted, “Tesla made 0 cars in 2011, but will make around 500k in 2019.” Musk did not seek or receive pre-approval prior to publishing this tweet, which was inaccurate and disseminated to over 24 million people. Musk has thus violated the Court’s Final Judgment by engaging in the very conduct that the preapproval provision of the Final Judgment was designed to prevent.

As one of the terms of his settlement, Musk agreed to comply with procedures implemented by Tesla that would require him to seek pre-approval of any written communications, including social media posts, that contained or reasonably could contain information material to Tesla or its shareholders.

Consistent with the Court’s Tesla Judgment, on December 11, 2018, Tesla adopted a “Senior Executives Communications Policy” (the “Policy”). Written Communications that contain, or reasonably could contain, information material to Tesla or its stockholders must, prior to posting or other publication, be submitted to Tesla’s General Counsel and Disclosure Counsel (or in the event of the General Counsel’s unavailability, Tesla’s Chief Financial Officer and Disclosure Counsel) for pre‐approval. Authorized Executives are not authorized to post or publish Written Communications that contain, or reasonably could contain, information material to Tesla or its stockholders without obtaining pre‐approval. The Policy provides a non-exclusive list of examples of information that may be “material to Tesla or its stockholders,” which includes “projections, forecasts, or estimates regarding Tesla’s business.” Id. at 1-2. Finally, Tesla’s Policy requires that [i]f an Authorized Executive (i) further edits a pre‐approved Written Communication, or (ii) desires to release a Written Communication more than two (2) days, after receipt of written pre‐approval, such Authorized Executive will re‐confirm the pre‐approval in writing in accordance with this Policy prior to release.

Could you make an attempt at arguing the reasonable argument in the other direction?

Re:SEC Asks Manhattan Federal Court to Hold Elon Musk in Con... by Dylan16807 on Wednesday February 27, 2019 @07:58PM (#19268228)
The argument is that "information material to Tesla or its stockholders" only applies to information that wasn't already public.

The tweet may have appeared to have nonpublic information, but it didn't actually have any.

Therefore the tweet didn't need approval.

That's the core of the argument. Is that clear enough? I already tried to explain why I think it's reasonable in previous posts, but I can do it again if you want me to.

Re:SEC Asks Manhattan Federal Court to Hold Elon Musk in Con... by sokoloff on Thursday February 28, 2019 @07:27AM (#19270859)
It is clear enough now; I missed that before.

I missed that as the thrust of your argument, because even if the information in that tweet was "material but not non-public due to previously approved disclosure", it would fall afoul of the "more than 2-days since approved" and "approved previously but now has edits" restrictions, which still leaves Musk in violation of the policy and therefore the court agreement.

(I also believe that the update of the range from "350k-500k" [previously public] to "around 500k" [in the tweet] to be a material update when given by the CEO of a company and that the SEC will argue that is also the case, but I agree/admit that there's some room for argument on that point.)

Thank you for the topic-centered discussion and I hope you experienced (as I did) this exchange as "disagreeing without being disagreeable".

Re:SEC Asks Manhattan Federal Court to Hold Elon Musk in Con... by Dylan16807 on Thursday February 28, 2019 @01:09PM (#19273494)
> even if the information in that tweet was "material but not non-public due to previously approved disclosure", it would fall afoul of the "more than 2-days since approved" and "approved previously but now has edits" restriction

It's more that the information is "material but not non-public", end of sentence. He's not piggybacking on a previous approval of a post. He's piggybacking on the fact that it's public.

Even if the previous disclosure had been in a post by Musk, I'd argue those rules don't apply to a new post. Those rules are about how approval for a specific post can be revoked, by delaying too long or by editing. They only affect that specific post, not future uses of now-public information.

But the previous disclosure was not such a post. It bypassed the entire tweet approval process. So these secondary rules definitely do not apply.

> (I also believe that the update of the range from "350k-500k" [previously public] to "around 500k" [in the tweet] to be a material update when given by the CEO of a company and that the SEC will argue that is also the case, but I agree/admit that there's some room for argument on that point.)

That's an okay belief. I'm not saying the result is clear-cut, just that Musk has a reasonable argument.

> Thank you for the topic-centered discussion and I hope you experienced (as I did) this exchange as "disagreeing without being disagreeable".

Sure, I'd agree there.

Re:SEC Asks Manhattan Federal Court to Hold Elon Musk in Con... by sokoloff on Thursday February 28, 2019 @01:37PM (#19273789)
> It's more that the information is "material but not non-public", end of sentence.

Even there, I think that's covered by "Written Communications that contain, or reasonably could contain, information material to Tesla or its stockholders must, prior to posting or other publication, be submitted to Tesla’s General Counsel and Disclosure Counsel for pre‐approval."

Re:SEC Asks Manhattan Federal Court to Hold Elon Musk in Con... by Dylan16807 on Thursday February 28, 2019 @02:18PM (#19274203)
That's the core of the argument.

Taking it literally might be the right interpretation. But it also fails to make sense in other ways. Is there an implied "not already public"? It's honestly hard to tell.