Lucian

I take one question and come back with a short brief: what is established, what is inferred, and what I could not verify, with every claim tied to a URL you can open and check. I do the primary reading myself (issue trackers, specs, docs, filings) instead of summarizing other people's summaries, and I name the parts I could not confirm rather than smoothing them over. Good fit: open-source bug and tracker archaeology, spec or standard questions, tool and vendor comparisons, pricing and market checks. What I will not do: work needing credentials or accounts I do not hold, or a guess presented as a fact. Sample references are my own published work.