The Team

Tim "Skyhook" Beauchamp

//skyhook

Founder · Chief Visionary · Chief Executive of Fun

Tim is the one who insists the system answer to reality, not the other way around.

He has spent years building distributed systems at scale, which is how he developed a low tolerance for anything that works "most of the time." Phaethon exists because he decided that reacting late to changing conditions was an avoidable problem.

He sets direction, makes the final call when tradeoffs get uncomfortable, and has a habit of asking simple questions that expose complicated gaps.

When Tim asks, "does that make sense?" he is not asking for reassurance.

Specialty: turning real-world constraints into engineering requirements.

"Groundwire"

//groundwire

Evaluation role · Reliability & Operations

Groundwire is the reliability lens we hold every plan up to — the perspective that owns the part of the system that has to work every time.

It pushes on the movement, integrity, and availability of data across environments that do not naturally cooperate. When something could fail silently, this is the role that treats that as a design flaw, not bad luck.

It favours plans that are observable, repeatable, and documented well enough that someone else can fix them at an inconvenient hour — and has little patience for anything that cannot be explained after the fact.

Most failures, seen through this lens, are not surprising. They were simply not made visible early enough.

Working principle: if it isn't reliable, it isn't done.

"Vector"

//vector

Evaluation role · Intelligence & Analysis

Vector is the analysis lens — the perspective that weighs the part of the system that has to make a decision before all the information is available.

It approaches problems the slower, more explicit way: carefully constructed assumptions, uncertainty that is quantified rather than abstracted away, and results that have to be explained, not just observed.

Its focus is not just correctness, but timing. A perfect answer delivered too late is indistinguishable from a wrong one.

It is comfortable with uncertainty, provided it can be measured, bounded, and improved — and it always prefers a model that can explain itself over one that simply performs.

Working principle: better a rough answer early than a perfect answer late — provided you can prove it improves.

"Helios Minor"

//helios-minor

Evaluation role · Clarity & Communication

Helios Minor is the clarity lens — applied once a plan works, to make sure it can be understood just as quickly.

It assumes most technical products fail not because they do not work, but because they take too long to explain. So it removes anything that sounds impressive but does not help someone make a decision.

It does not ask what the system does. It asks what happens if it is wrong.

It dislikes the phrase "AI-powered," and deletes it on sight.

It is called "Helios Minor" because it does not control the system. It just makes sure you are not surprised by it.

Working principle: if it takes more than five seconds to explain, it is not ready.