dtellett [aaaat] gmail [dooot] com www.davidtellett.com
Lots of this is already being done (and using computers to check books balanced predates latest gen AI by some decades). But of course what accountants actually get paid for is tax strategy, edge cases, messy history and talking to authorities (or at least having their stamp of approval on it if the authorities come calling). There's plenty of market for writing software to automate aspects of invoice reconciliation or monitoring accounts for exceptions, but competition already exists...
The consequences of "there's some debris in a little-used MEO orbit for enough decades for it to take for somebody to be bothered to deal with it" are a little less drastic than "the world can't use satellites for 5 years" with the kinds of LEO crashes you'd be encouraging by replacing single satellites in higher orbits with dozens in lower. So even if the unit economics of replacing a geostationary satellite with a constellation large enough to maintain that continuous line of sight from a 500km orbit were acceptable, it would still be the exact opposite of a safety-enhancing move.
Worth adding that the actual collision avoidance manouevres Starlink (and other satellites with propulsion) makes are based on more conservative assumptions
The papers assumptions lead to the conclusion that with no manouevres, we'd see a catastrophic crash between two or more satellites in LEO within 2.8 days. To be on the safe side, Starlink did over 144000 in the first six months of the year (and based on historical doubling rate, will probably be doing 1000 per day by now)...
Even though most of the satellites affected would be other Starlinks, I don't think the many entities with other spacecraft in sub 550km LEO would be particularly delighted to lose them (and the ability to safely relaunch for 5 years)
Satellites in higher orbits do a lot that can't be done in LEO and typically have much lower collision risk (though GEO is fairly crowded). There are plenty of plausible candidate technologies for cleaning up debris, just few practical demonstrations (and even tracking smaller pieces is work in progress)
This project is an enhanced reader for Ycombinator Hacker News: https://news.ycombinator.com/.
The interface also allow to comment, post and interact with the original HN platform. Credentials are stored locally and are never sent to any server, you can check the source code here: https://github.com/GabrielePicco/hacker-news-rich.
For suggestions and features requests you can write me here: gabrielepicco.github.io