Fuzzball plus Stratum - one identity and one pane of glass, no duplicated functionality, Engineering owns the developer experience

Situation

At the 10/23 Fuzzball plus Stratum alignment session, Bjorn locked the product split (Fuzzball for R&D, training and research; Stratum for production and inference) and Peter agreed. Peter own calls were architectural invariants: (1) one identity and one set of permissions across both products, with views varying by role and the Stratum UI living within the Fuzzball UI if they coexist; (2) no duplicated functionality - anything both platforms use lives once, in Stratum or in a third shared repo, and Fuzzball reaches through to Stratum hooks; (3) Engineering, not Product, owns the CIQ developer experience of building these products. Process: Jonathon writes the vision for a second review, Wolford draws stock K8s versus Stratum with shared components broken out, Bjorn and Jonathon build an environment by use-case matrix to prune with, and a follow-up next week. Whether Fuzzball requires Stratum stays open between Greg and Bjorn.

Reasoning

Two identity systems and two copies of shared objects create a permanent maintenance and support tax and force customers to manage the same object twice, the opposite of what the combined offering should sell. Peter fixes what must be structurally true regardless of how the product debate lands, leaving the product question in Bjorn and Greg lane. Developer experience is how CIQ engineers build, not what customers buy, so it stays with Engineering rather than becoming a roadmap trade-off.

Additional Context

Peter confirmed the hypothesis as presented.

Observed Evidence

Direct quotes at 12:06, 13:39, 23:59 and 48:35 of the recorded transcript; Bjorn stated the product split at 12:46 and Peter said Great.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis