Live Product Surface

This section should be read before the Editorial Pipeline section.

The reason is simple: pipeline terms such as Editorial impact, Source confirmation, Selection audit, sourceFact, and whyMatters only become meaningful if it is clear where they appear in the real product.

What exists on the live site

The public live surface is https://blockchainforum.eu, which redirects to the Pages deployment.

The homepage visibly includes at least:

• Latest Blockchain Signals
• All Sources & Links
• individual signal cards
• signal-detail / modal view

Why this should be documented before the pipeline

Otherwise the editorial pipeline stays too abstract. The right reading order is:

1. what the user sees on the site
2. which API feeds it
3. which fields the published signal object contains
4. how the pipeline produces those fields

Compact model

Live site
-> /api/data
-> signals[]
   -> sourceFact
   -> editorialSummary
   -> whyMatters
   -> consensus
   -> selectionAudit
-> frontend labels
   -> Editorial impact
   -> Source confirmation
   -> Selection audit