UI Terms on the Live Site

Where the terms come from

The terms visible on the site are not isolated marketing labels. They are grounded in:

1. frontend UI code
2. the /api/data response fields
3. consensus, audit, and editorial pipeline logic

Terms visible live

The frontend code and documentation include, for example:

• Editorial impact
• Source confirmation
• Selection audit
• sourceFact
• whyMatters

Where they can be studied

In the documentation:

• docs/ai-pipeline-tarkka-kuvaus.md
• docs/ai-putki-ja-jdbin.md
• docs/live-smoke-testaus.md
• docs/qa-cheat-sheet-kokous.md

In the frontend code:

• frontend/src/main.jsx

There you can directly see labels such as:

• Editorial impact
• Source confirmation
• Selection audit

Why this is the essential bridge into the editorial pipeline

When moving into the next section about the pipeline, keep this in mind:

• sourceFact is not just an internal field, but part of the published signal meaning
• whyMatters is not just OpenAI copy, but the visible editorial layer in the UI
• consensus is not just backend data, because Source confirmation is derived from it
• selectionAudit is not just a debug log, but part of the product’s transparency layer