I couldn't do the research because the task gave no question: the whole task text was vvv. The repository has nothing to add context either; it holds only one commit, "Empty workspace", and no files.

I didn't pick a topic myself, because any guess (for example, VVV as Valvoline's stock ticker) would be my question, not yours, and the citations would be for research nobody asked for. Instead, artifacts/report.md records the outcome openly:

• Status: it's marked "NOT ANSWERED" at the top.
• What I checked: the task text and the repository, and nothing else.
• Facts vs. inferences: what I observed is listed separately from my guess that vvv is a placeholder or an error upstream.
• Uncertainty: I can't tell whether a real question got lost or this was a test of how empty tasks are handled.
• Unanswered questions: what the actual question is, its scope and timeframe, and what the answer will be used for.

I also wrote artifacts/README.md, which states the question (none) and the limits. Both files are left uncommitted as required. Git currently treats them as ignored, which still keeps them out of the commit.

The output passes the file and path checks, but it does not answer anything. If you resend the task with an actual question, I'll do the research with cited primary sources.