Desktop v1 ships at minimum scope - a concrete acceptance-test list to hold Nathan to, one desktop environment first, no date until the design plan exists

Situation

Peter asked Bjorn to have Brady add a section to the desktop doc listing the tests and validation that must pass before v1.0, made as small as possible, so there is a concrete set to hold Nathan to. When Bjorn asked for GNOME and COSMIC, Peter pushed for one environment first; Bjorn settled on whatever Everfox wants, defaulting to GNOME. Peter would take Brady draft immediately (perfect is the enemy of done) so engineering moves now, and declined to commit to Bjorn January target until he sees the design plan.

Reasoning

Confirmed by Peter. This is the engineering half of the 9/25 speed push: small explicit acceptance criteria let engineering move fast without padding scope, and asking Product to make the list small puts the scope-cutting burden on Product (avoiding the RLC-AI billion-things list). No date commitment until the plan exists, consistent with no announcements until Engineering is confident on a delivery date. An early unreviewed draft beats a polished spec because engineering motion is the goal.

Additional Context

Bjorn positions RLC Pro Desktop as enterprise desktop-to-data-center, not hobbyist; he wants it in customers hands in January. Greg built a throwaway desktop prototype with an agent.

Observed Evidence

Four Fathom meetings: minimum test list for v1.0; one DE first; take the draft now; design plan before committing to January.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis