{
 "source": "the firm's own statements, each sealed at publish; a correction is a dated addendum, never an edit",
 "section": "Statements",
 "origin": "https://jyotishintelligence.com",
 "verify": "sha256 of the file at text_url equals text_sha256; the seal id is the first 16 hex of the leaf on the firm's seal chain",
 "count": 2,
 "statements": [
  {
   "id": "2026-11-15-starship-flight-15",
   "url": "/press/2026-11-15-starship-flight-15",
   "title": "Statement on Starship Flight 15",
   "issued": "2026-11-15T19:11:30.000Z",
   "issued_note": "First posted on LinkedIn by the principal; the time is the capture of the live post.",
   "published": "2026-11-15T20:14:08.461Z",
   "dek": "Starship Flight 15 did most of what it set out to do. The 26 satellites were released near the planned orbit and the ship was caught at the tower. The booster was not: Super Heavy diverted to a splashdown in the Gulf, and SpaceX gave slight engine underperformance and low fuel as the reason.",
   "text": "To the Starship team at SpaceX, and to the underwriters who carry launch risk:\nStarship Flight 15 did most of what it set out to do. The 26 satellites were released near the planned orbit and the ship was caught at the tower. The booster was not: Super Heavy diverted to a splashdown in the Gulf, and SpaceX gave slight engine underperformance and low fuel as the reason.\n\nOn 13 November at 17:59 UTC, about five hours before lift-off, JYOTINT sealed an automated launch-day read for that flight. It said:\n• Count: CLEAN\n• Launch, ignition to payload release: NO-GO\n• Named exposure: engine relight and the tower catches, which lean on Raptor ignition and combustion margins after staging.\n• On the booster, in the read's own words: \"a catch waved off to a water landing is the form it would first take.\"\n\nThe count ran quiet, as read. The booster loss took the form the read named. We also carried risk on the payload release, and that went well. We leave that on the record too.\n\nThe read is one page of decisions for two readers. The launch team gets the mission chain and a short watch list by step. The underwriter gets the same day as exposure by phase: before ignition, launch, and operating life. It is risk management, not a prediction. The team and the underwriter always keep the decision.\n\nThe sealed PDF is attached, exactly as it was sealed. Both editions, the seal and the public grade are here:\nhttps://jyotishintelligence.com/launch/automated",
   "blocks": [
    {
     "p": "To the Starship team at SpaceX, and to the underwriters who carry launch risk:"
    },
    {
     "p": "Starship Flight 15 did most of what it set out to do. The 26 satellites were released near the planned orbit and the ship was caught at the tower. The booster was not: Super Heavy diverted to a splashdown in the Gulf, and SpaceX gave slight engine underperformance and low fuel as the reason."
    },
    {
     "p": "On 13 November at 17:59 UTC, about five hours before lift-off, JYOTINT sealed an automated launch-day read for that flight. It said:"
    },
    {
     "ul": [
      "Count: CLEAN",
      "Launch, ignition to payload release: NO-GO",
      "Named exposure: engine relight and the tower catches, which lean on Raptor ignition and combustion margins after staging.",
      "On the booster, in the read's own words: \"a catch waved off to a water landing is the form it would first take.\""
     ]
    },
    {
     "p": "The count ran quiet, as read. The booster loss took the form the read named. We also carried risk on the payload release, and that went well. We leave that on the record too."
    },
    {
     "p": "The read is one page of decisions for two readers. The launch team gets the mission chain and a short watch list by step. The underwriter gets the same day as exposure by phase: before ignition, launch, and operating life. It is risk management, not a prediction. The team and the underwriter always keep the decision."
    },
    {
     "p": "The sealed PDF is attached, exactly as it was sealed. Both editions, the seal and the public grade are here:"
    },
    {
     "p": "https://jyotishintelligence.com/launch/automated"
    }
   ],
   "text_url": "/press/statements/2026-11-15-starship-flight-15.txt",
   "text_sha256": "0ff8fa0041b95ada1d915d7b4f38f48dfe911bbdc44bf4ef807fec59e859f0b9",
   "seal": {
    "id": "c5d4f5719c6f748a",
    "seq": 953,
    "leaf": "c5d4f5719c6f748aee704e29c74c4f90b3438252b34c3a0feadb9fa612c0904c",
    "sealed": "2026-11-15T20:14:08.465Z"
   },
   "refs": [
    {
     "label": "The public row, its seal and its grade",
     "url": "/launch/automated"
    },
    {
     "label": "Sealed read, underwriter edition, PDF as sealed on 13 November",
     "url": "/auto-advisories/lia_20261113_1ed2bff6999b.pdf"
    },
    {
     "label": "Sealed read, launch edition, PDF as sealed on 13 November",
     "url": "/auto-advisories/lia_20261113_1ed2bff6999b.launch.pdf"
    },
    {
     "label": "Evidence package for the grade",
     "url": "/api/v1/auto-evidence/lia_20261113_1ed2bff6999b.json"
    }
   ],
   "copies": [
    {
     "where": "LinkedIn",
     "url": "https://www.linkedin.com/posts/vijay-jyotish_starship-flight-15-sealed-launch-day-read-ugcPost-7527810547698909184-ng_9/"
    },
    {
     "where": "X",
     "url": "https://x.com/vijayjyotish/status/2122046779848098265"
    }
   ],
   "addenda": []
  },
  {
   "id": "2026-11-15-amazon-leo-lv-01",
   "url": "/press/2026-11-15-amazon-leo-lv-01",
   "title": "Statement on Amazon Leo LV-01",
   "issued": "2026-11-15T19:11:00.000Z",
   "issued_note": "First posted on LinkedIn by the principal; the time is the capture of the live post.",
   "published": "2026-11-15T20:14:08.409Z",
   "dek": "Today is a hard day. Vulcan lifted off from SLC-41 with 40 Amazon Leo satellites, and ULA has confirmed an anomaly about 10 minutes into flight. The payload did not reach orbit. Our respect goes to the people who now have to find the cause.",
   "text": "To the launch teams at United Launch Alliance (ULA) and Amazon Leo, to the underwriters who carry launch risk, and to the mission assurance teams at Space Systems Command and United States Space Force: Today is a hard day. Vulcan lifted off from SLC-41 with 40 Amazon Leo satellites, and ULA has confirmed an anomaly about 10 minutes into flight. The payload did not reach orbit. Our respect goes to the people who now have to find the cause.\n\nWe are posting our own record of this mission, in full, because a record only counts if it is public before and after.\n\nOn 11 November at 17:21 UTC, 48 hours before the first attempt, JYOTINT sealed an automated launch-day read for LV-01 at its planned T-0 of 13 November. That read said:\n• Count: CLEAN\n• Launch, ignition to payload release: NO-GO\n• Course: STAND DOWN. No minute of the 31-minute window read clean for the flight.\n• Named exposure: Centaur V, with thermal margin carried into both of its burns, and an off-target insertion or an incomplete release as the form it would take.\n\nWhat we can and cannot claim:\n• That attempt was scrubbed for a ground nitrogen supply fault. Our read named a slip, but it did not name that cause. We graded it that way in public.\n• The read was sealed for the 13 November mark. The vehicle flew two days later, on a mark we did not read. We make no claim about the cause of today's anomaly. That belongs to ULA's investigation.\n\nThis was Vulcan's return to flight, and national security payloads are waiting on it. That is why we think a forward read of the launch day belongs beside the engineering review, as one more input for the people who decide. It is risk management. It is not a prediction, and the launch team and the underwriter always keep the decision.\n\nThe sealed PDF is attached, exactly as it was sealed. The row, its seal and its grade are public here:\nhttps://jyotishintelligence.com/launch/automated",
   "blocks": [
    {
     "p": "To the launch teams at United Launch Alliance (ULA) and Amazon Leo, to the underwriters who carry launch risk, and to the mission assurance teams at Space Systems Command and United States Space Force: Today is a hard day. Vulcan lifted off from SLC-41 with 40 Amazon Leo satellites, and ULA has confirmed an anomaly about 10 minutes into flight. The payload did not reach orbit. Our respect goes to the people who now have to find the cause."
    },
    {
     "p": "We are posting our own record of this mission, in full, because a record only counts if it is public before and after."
    },
    {
     "p": "On 11 November at 17:21 UTC, 48 hours before the first attempt, JYOTINT sealed an automated launch-day read for LV-01 at its planned T-0 of 13 November. That read said:"
    },
    {
     "ul": [
      "Count: CLEAN",
      "Launch, ignition to payload release: NO-GO",
      "Course: STAND DOWN. No minute of the 31-minute window read clean for the flight.",
      "Named exposure: Centaur V, with thermal margin carried into both of its burns, and an off-target insertion or an incomplete release as the form it would take."
     ]
    },
    {
     "p": "What we can and cannot claim:"
    },
    {
     "ul": [
      "That attempt was scrubbed for a ground nitrogen supply fault. Our read named a slip, but it did not name that cause. We graded it that way in public.",
      "The read was sealed for the 13 November mark. The vehicle flew two days later, on a mark we did not read. We make no claim about the cause of today's anomaly. That belongs to ULA's investigation."
     ]
    },
    {
     "p": "This was Vulcan's return to flight, and national security payloads are waiting on it. That is why we think a forward read of the launch day belongs beside the engineering review, as one more input for the people who decide. It is risk management. It is not a prediction, and the launch team and the underwriter always keep the decision."
    },
    {
     "p": "The sealed PDF is attached, exactly as it was sealed. The row, its seal and its grade are public here:"
    },
    {
     "p": "https://jyotishintelligence.com/launch/automated"
    }
   ],
   "text_url": "/press/statements/2026-11-15-amazon-leo-lv-01.txt",
   "text_sha256": "b6530dd6f67945934e4524cff05810d9a49084934a209450af62d4bdeedc5975",
   "seal": {
    "id": "ebedf722df184b1f",
    "seq": 952,
    "leaf": "ebedf722df184b1fed9ff0567ee7391854cf7c407d7f3c9f66edad8c902a3dd6",
    "sealed": "2026-11-15T20:14:08.414Z"
   },
   "refs": [
    {
     "label": "The public row, its seal and its grade",
     "url": "/launch/automated"
    },
    {
     "label": "Sealed read, PDF as sealed on 11 November",
     "url": "/auto-advisories/lia_20261111_37a5aed58666.pdf"
    },
    {
     "label": "Evidence package for the grade",
     "url": "/api/v1/auto-evidence/lia_20261111_37a5aed58666.json"
    }
   ],
   "copies": [
    {
     "where": "LinkedIn",
     "url": "https://www.linkedin.com/posts/vijay-jyotish_amazon-leo-lv-01-sealed-launch-day-read-ugcPost-7527809910596747265-Te0E/"
    },
    {
     "where": "X",
     "url": "https://x.com/vijayjyotish/status/2122046449810813090"
    }
   ],
   "addenda": []
  }
 ]
}
