Is your feature request related to a problem? Please describe.
The current collaborative note data captures four elements: (1) which notes are collaborative, (2) who contributed each suggestion, (3) the suggestion content, and (4) note content changes. However, two important pieces of information are missing:
- LLM reasoning traces — the "show my work" explanations displayed in the Community Notes interface that reveal how the model arrived at its output.
- Suggestion disposition — whether each contributor's suggestion was ultimately accepted or rejected, and why.
Without these, researchers and developers cannot fully reconstruct the decision-making process behind a collaborative note's final form.
Describe the solution you'd like
Expose both of the above in the data:
- LLM reasoning: Include the model's chain-of-thought or rationale associated with each collaborative note, as shown in the "show my work" UI.
- Accept/reject status: For each suggestion, record whether it was accepted or rejected, and ideally, why.
This would enable deeper analysis of how collaborative notes evolve and how human and LLM judgments interact.
Describe alternatives you've considered
No alternatives identified — this information already exists in the system and would primarily need to be surfaced in the data.
Additional context
N/A
Is your feature request related to a problem? Please describe.
The current collaborative note data captures four elements: (1) which notes are collaborative, (2) who contributed each suggestion, (3) the suggestion content, and (4) note content changes. However, two important pieces of information are missing:
Without these, researchers and developers cannot fully reconstruct the decision-making process behind a collaborative note's final form.
Describe the solution you'd like
Expose both of the above in the data:
This would enable deeper analysis of how collaborative notes evolve and how human and LLM judgments interact.
Describe alternatives you've considered
No alternatives identified — this information already exists in the system and would primarily need to be surfaced in the data.
Additional context
N/A