Writing
Notes on mission autonomy.
Founder-authored notes drawn from primary sources: NASA technology shortfalls, JPL flight heritage, and international agency roadmaps. Every essay is dated, signed, and cites its sources.
Currently · 3 essays
- Why space missions need a trust boundary, not a smarter modelNASA's own ranked shortfalls describe a missing systems layer, not a missing model. The layer that is missing is a trust boundary: a separate mechanism that decides what may execute.
- What thirty years of JPL autonomy actually provedRemote Agent, CASPER, AEGIS, AutoNav, TRN, Ingenuity: what each system solved, what it deliberately did not, and why the strongest were hybrids with a separate mechanism deciding what may execute.
- Permits, not promises: what an assurance kernel doesHow execution permits work, why the assurance kernel is independent, and what deterministic replay actually buys an accident board. References DO-178C, NPR 7150.2, and ECSS as design targets.
New essays are published here and syndicated by RSS.
Barycenter Systems is building a mission autonomy runtime. If this problem is yours too, write to us.