Technical solution research report

Produce a decision instrument, not a catalog of project descriptions. The invariant is:

user problem → target outcome → constraints → options
→ evidence → semantic fit → ownership/risk
→ validation/exit criteria → recommendation

Read the technical decision brief before ranking options, and read the technical proposal exemplar before a solution-design or multi-repository comparison. The brief fixes the decision frame; the exemplar distills the decision structure of Kubernetes KEP-753 without importing its production-scale depth into early-stage work.

1. Route the task and scale the depth

Classify the request before collecting evidence: