The tree · Access · My own decision · Could be decided within 5 to 20 years

Stay in my current career when the first chance to leave comes

Not yet Current plan

One option at the first fork in the pathway: stay in my current career when the first chance to leave comes, for as long as it keeps expanding capability in ways that serve the longer goal. Marked as the current plan because the sketch in definitions.md leans this way; I was explicitly hesitant, and the decision comparison exists to test it.

The test: what counts as it having happened

A dated record that I stayed in my current career past the first point at which I could have left it, in my employment record.

Settled by: my employment record

The odds, by how long I live

This one is my own decision, not something that happens to the world, so it is never given a probability. A normal run of the tree assumes the current plan. To compare options, the tree is run once per choice and the change in the headline number is what gets reported. The other option at this fork: Leave my current career for civilian work in or near the space industry.

Revisions

DateFieldFromToWhy
2026-09-25 name Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history Decided September 25th, 2026 (definitions.md decision log): no public surface names my current career until I complete my training in May 2027. Same meaning; no probability or link moved.
2026-09-25 description Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history Decided September 25th, 2026 (definitions.md decision log): no public surface names my current career until I complete my training in May 2027. Same meaning; no probability or link moved.
2026-09-25 resolution Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history Decided September 25th, 2026 (definitions.md decision log): no public surface names my current career until I complete my training in May 2027. Same meaning; no probability or link moved.
2026-09-25 source Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history my employment record Decided September 25th, 2026 (definitions.md decision log): no public surface names my current career until I complete my training in May 2027. Same meaning; no probability or link moved.
2026-10-03 id see data/snapshots/renamed-ids.toml see data/snapshots/renamed-ids.toml Id only, and with it the page's address: the old id described my current career, which no public surface does until May 2027 (decided September 25th, 2026; the rename I approved October 3rd, 2026 on Claude's proposal). Name, criterion, numbers and links are unchanged. Saved runs keep the old id and are read through data/snapshots/renamed-ids.toml.
2026-11-14 name Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history Stay in my current career when the first chance to leave comes Decided September 25th, 2026 (definitions.md decision log): no public surface describes my current career until May 2027. This wording still pointed at it, so it was reworded on November 14th, 2026 after a review of the live site. Same meaning; no probability or link moved.
2026-11-14 description Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history One option at the first fork in the pathway: stay in my current career when the first chance to leave comes, for as long as it keeps expanding capability in ways that serve the longer goal. Marked as the current plan because the sketch in definitions.md leans this way; I was explicitly hesitant, and the decision comparison exists to test it. Decided September 25th, 2026 (definitions.md decision log): no public surface describes my current career until May 2027. This wording still pointed at it, so it was reworded on November 14th, 2026 after a review of the live site. Same meaning; no probability or link moved.
2026-11-14 resolution Wording that named my current career; withdrawn from public copy until May 2027 and kept in the repository's history A dated record that I stayed in my current career past the first point at which I could have left it, in my employment record. Decided September 25th, 2026 (definitions.md decision log): no public surface describes my current career until May 2027. This wording still pointed at it, so it was reworded on November 14th, 2026 after a review of the live site. Same meaning; no probability or link moved.
2026-11-14 id see data/snapshots/renamed-ids.toml A-stay-in-current-career Id only, and with it the page's address: the old id still pointed at my current career, which no public surface describes until May 2027 (decided September 25th, 2026; renamed November 14th, 2026 after a review of the live site, on the same footing as the renames of October 3rd, 2026). Name, criterion, numbers and links are unchanged by the rename. Saved runs keep the old id and are read through data/snapshots/renamed-ids.toml.

Think this estimate is wrong? Here's how to tell me, and what happens next. The record itself is data/A-access.toml in the public repository.