Enhancement: Review distinction between Verification Requests and claims

[LuizFNJ]

Background Information

There is confusion between Verification Requests (PT: “Denúncias”) and the Repository.

Currently, we handle two different but related types of content:

• Verification Request: A submission made by a user or through active monitoring asking for something to be verified.
• Repository: The structured collection of content items such as speeches, debates, images, or general information.

All repository items (speeches, debates, images, general information) are treated as claims, meaning they can be fact-checked. However, before a claim is created and verified, there is first a verification request.

The intended flow is:

1. A user or the active monitoring system submits a Verification Request (a request to verify something).
2. The actual content to be checked is structured as a Claim (stored in the Repository).
3. The Fact-checking process is performed on that claim.
4. Once verified, the claim becomes a Reviewed Claim (a claim that has already been fact-checked).

This distinction is currently not clear enough in the user experience, which creates confusion about what is being submitted, what is being stored, and what is being verified.

---

How

• Clearly define the conceptual difference between:
  • Verification Request (the request to verify something).
  • Claim (the actual content to be verified).
  • Reviewed Claim (the claim after it has been verified).
  • Repository (where claims and reviewed claims are stored and managed).
• Improve terminology and UI copy to make the flow explicit.
• Visually and structurally reinforce the sequence:
  • Request → Claim → Verification.

---

Expected Behavior

• Users clearly understand the difference between submitting a verification request and viewing repository content.
• The platform makes the flow (Request → Claim → Verification) intuitive and transparent.
• Terminology is consistent across UI, documentation, and internal references.