Independent ownership research on U.S.-listed companiesMethodology  ·  Disclosures

SpaceX company research

SpaceX & xAI Daily Briefing — 2026-11-15

Sources checked: 2026-11-15 06:35 EST (America/New_York)

Developments after the November 14 evening edition, written as of this Sunday morning check: a recap of Starship Flight 15's first ship catch, with no official Flight 16 date announced; ULA's Vulcan Leo 1, reset for 12:11 p.m. Eastern today after Friday and Saturday scrubs; reported Grok Bot usage-efficiency changes and official documentation that Grok API text watermarking is now opt-in; a further day of the Starshield dispute, including a Ukrainian denial of a purely technical explanation; and Google's November 12 introduction of Gemini 4 Hydrogen. This is a selective briefing, not an exhaustive daily news feed. Nvidia's Friday close and week, as reported by CNBC, and Anthropic's still-unpriced offering with an expected Nasdaq first trade on November 19, were covered in the November 14 edition and are not treated here as new facts. A short, clearly dated note added on November 16 records that Vulcan later lifted off on November 15 and failed; the outcome is covered in the November 16 edition.

Official recap · no Flight 16 date announced as of this morning

Flight 15's first ship catch stands; SpaceX has not announced a Flight 16 date

As recorded in the November 14 edition, SpaceX's Flight 15 recap says Starship lifted off from Pad 2 at Starbase on November 13, deployed 26 Starlink V3 satellites, and, about 22.5 hours later, was caught by Mechzilla for the first time. The booster catch was aborted after the boostback burn ended early because of low fuel mass, with the root cause under investigation; an automated abort diverted the booster offshore, and the flight termination system was triggered after the landing burn cut off while hovering over the Gulf. The company's recap page does not name the vehicles. The SpaceX webcast referred to the returning ship as Ship 42, and press accounts including Space.com and Spaceflight Now identified the first stage as Booster 22. Those designations are from the webcast and reporting, not from the recap text reviewed here. As of this Sunday morning check, SpaceX had not announced a date for Flight 16. A Space.com preview published later on November 15 likewise records work still ahead on reuse and does not state a Flight 16 date.

Analysis · opportunity and risk
Opportunity: the first official ship catch remains the main near-term evidence that a returning ship can be recovered at the tower. Risk: the booster was not caught, the early boostback cutoff is still under investigation, and the absence of a Flight 16 date means the next reuse attempt is not yet on a public calendar.

Source: SpaceX — Starship Flight 15 (recap dated November 13–14, 2026). Vehicle names from the SpaceX webcast, as reported by Space.com and Spaceflight Now. Flight 16 calendar also checked against Space.com, November 15, 2026.

Launch plan as of this morning · later failure recorded in a dated note

Vulcan Leo 1 is reset for 12:11 p.m. Eastern today after two scrubs

As of this Sunday morning check, United Launch Alliance had retargeted its Vulcan return-to-flight Leo 1 mission for 12:11 p.m. Eastern on November 15 from Cape Canaveral, carrying 40 Amazon Leo satellites. Aviation Week reported the reset on November 14 after a second ground-systems issue; Friday's attempt had been delayed by a power interruption at a nitrogen plant, and Saturday's window was lost to a ground-to-rocket network communications problem, as recorded in the November 14 edition. The vehicle and payload had been reported healthy. The mission remained the first of 38 Vulcan flights Amazon has purchased and the first flight of a redesigned solid-rocket-booster nozzle, with Space Force use of Vulcan still paused pending review of this return to flight. Note, added November 16: Vulcan later lifted off on the afternoon of November 15 and failed to deliver the satellites to orbit. The outcome is covered in the November 16 edition.

Analysis · opportunity and risk
Opportunity: a Sunday attempt, if it occurred as then planned, would have been the first flight data point on the redesigned nozzle. Risk: two prior scrubs showed the window could slip again, and even a successful commercial flight would have left the Space Force pause dependent on later review. The later failure, recorded in the dated note, does not change this morning status.

Source: Aviation Week — Vulcan Return-To-Flight Launch Reset For Nov. 15 (November 14, 2026). The November 16 dated note records the later launch and failure; see the November 16 edition.

Reported product change · team comments, not a verified changelog entry in this review

Grok Bot team comments put usage-efficiency gains at about 7%, and up to 15% on routines

TeslaNorth reported on November 14 that Grok Bot's team had described new harness optimizations as delivering roughly 7% more usage from a plan, with gains of up to 15% on routine runs. The article said Sam Sokolin, who works on Grok Bot, made those comments on November 13, and that Elon Musk highlighted the changes on November 14 as improvements to Grok Bot efficiency. The figures are team comments as relayed by the press, not independently measured results in this review, and they describe stretching existing plan allowances rather than a change in advertised plan prices. This review did not open the underlying social posts. A broader official launch of Grok 4.8 was still unconfirmed as a general or API release in this morning's check; a November 13 post from the official Grok account describing a limited soft rollout to Bot users is addressed, with that distinction, in the November 16 edition.

Analysis · opportunity and risk
Opportunity: if the stated gains hold, paid allowances may last somewhat longer, especially on recurring routines. Risk: the percentages come from reported team comments rather than a published test, and they should not be read as a general Grok 4.8 launch.

Source: TeslaNorth — Grok Bot Gets Up to 15% More Usage After Subscriber Complaints (November 14, 2026), citing team comments on November 13–14

Official documentation · text watermarking off by default, admin opt-in

SpaceXSI documentation now treats Grok API text watermarking as opt-in

SpaceXSI's official output-watermarking documentation says text watermarking is off by default. Team administrators can turn it on per model in the SpaceXSI Console; the setting applies to every API key on the team and takes effect for new requests within five minutes. The guide lists supported text models including grok-4.7, grok-4.6, grok-4.5, grok-4.3 and grok-4.20 variants, and says watermarking, once enabled, covers Responses and Chat Completions outputs, including structured output and tool-call arguments. A response's x-watermark header can be read as true or not. The company says the mark is invisible and uses Google DeepMind's SynthID Text method. Audio from the voice APIs is watermarked by default, with a narrower opt-out that does not apply where a user's location requires a watermark. Earlier public guidance had described a default-on text policy from November 7; the current document states the opposite default. This item records the official documentation now in force, not an independent test of when the service behavior changed.

Analysis · opportunity and risk
Opportunity: a documented opt-in control, with an explicit response header, is clearer for developers than an assumed default-on policy. Risk: earlier public guidance pointed the other way, so integrators should check the current console setting and the x-watermark header rather than rely on older SDK text.

Source: SpaceXSI Docs — Output Watermarking (documentation reviewed November 15, 2026)

Disputed claim · official Ukrainian comments and a company denial, as reported

Ukraine says Starshield restrictions have lasted five days; SpaceX again denies imposing limits

Radio Free Europe/Radio Liberty reported on November 15, citing a November 14 interview, that Denys Sienik, Ukraine's top diplomat in Washington, said restrictions affecting Starshield remained widespread and had persisted for five days of daily tests. He said the limits hindered interception of jet-powered Russian attack drones near the front line. RFE/RL also reported that Ukrainian officials, speaking anonymously, said SpaceX told the Defense Ministry, “We are not imposing any restrictions,” and referred to technical issues without answering a follow-up about temporarily occupied territory. President Volodymyr Zelenskyy, in remarks released by his office on November 14, again described speed restrictions of about 161 kilometers per hour on terminals in temporarily occupied areas and said Kyiv does not believe the disruptions are simply technical problems. This review did not find, in the RFE/RL account, a direct quotation that he accused the company of “lying,” and that stronger wording is not used here. The operational facts remain disputed. The November 13 Shaheen–Coons document-preservation letter is covered in the November 16 edition.

Analysis · opportunity and risk
Opportunity: a named diplomat's on-the-record account, plus a reported company reply to the ministry, keeps both sides of the dispute in official channels. Risk: the company and Kyiv still disagree about whether the disruption is a restriction or a technical issue, and neither account is an independent technical finding.

Source: Radio Free Europe/Radio Liberty — Ukraine Says Starshield Restrictions Persist, Hampering Drone Defenses (November 15, 2026)

Company announcement · Google's stated figures and availability

Google introduces Gemini 4 Hydrogen as a faster model for everyday agentic work

In a November 12 blog post, last updated November 13, Google introduced Gemini 4 Hydrogen, describing it as a faster, more efficient model for everyday coding and agentic workflows, alongside the company's higher-reasoning Gemini 4 Carbon and Argon models. Google said Hydrogen is priced flat across a 1 million-token context window at $1.50 per million input tokens and $7.50 per million output tokens, and that it is rolling out across Google AI Studio, the Gemini API, Gemini for business, the Gemini app, Google Search, and paid Google AI Pro and Ultra subscribers in Google Antigravity. Benchmark scores, speed comparisons and safety figures in the post are the company's own claims and are not independently verified here. This item records the official introduction; it is not a ranking of competing models.

Analysis · opportunity and risk
Opportunity: a dated, official launch with published API prices is a concrete competitive fact for anyone tracking frontier-model availability. Risk: performance and safety claims are the vendor's, and availability by surface and plan can differ from the headline rollout.

Source: Google — Introducing Gemini 4 Hydrogen (November 12, 2026; last updated November 13)

Latest briefing and full archive