Pull Max Spevack Spark work into a CIQ-managed repository before the announcement, and define the outbound publication path

Situation

In the group DM with Nathan Blackham and Brett Mastbergen on Sept 9, Peter pointed at Max Spevack NVIDIA Spark work living at github.com/maxspevack/spark-rocky, noted Brett already has access, and said he would like to get it pulled into a CIQ managed repository, asking one of them to make that happen. He paired that with a request to talk about a process for making it available to the world on the heels of the announcement Lindsay Aamodt wants to make in the coming week or so. He did not route the request through Max. In the same window he told Brett he would try to chat with Max but that Max can be hard to reach currently, and told Lindsay and Bjorn that Max is so hit-miss on getting back to him on things like the benchmark publication.

Reasoning

Lindsay is about to announce a capability whose source of truth is a personal GitHub account, which is an unacceptable dependency for something CIQ goes to market on, and the fix has to land before the announcement rather than after. The trigger is availability rather than policy - Peter had already observed the failure mode that week, twice describing Max as hard to reach and hit-miss on responses, so he removed the single point of failure whose failure he had just experienced. Asking Nathan and Brett rather than Max is a deliberate choice to move custody without waiting on the author participation. Pairing the move with a publication process means the outbound path becomes a CIQ decision going forward rather than a side effect of what the author chooses to push.

Additional Context

Brett Mastbergen reproduced Max results on his own Spark testing by Sept 10 and CIQ wins the leaderboard race on the benchmark Max tuned for, so the work is commercially load-bearing. Peter separately had a 1:1 with Mariah Rippee on Sept 11 with the stated agenda of discussing Max.

Observed Evidence

Direct quote giving the instruction and the publication-process ask, plus two separate direct quotes in the same window establishing the availability problem that motivated moving custody without the author in the loop.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis