API and Signal Model

What the frontend reads

According to the documentation, the public frontend data is delivered in a signals / all_links JSON shape.

The key read path is:

GET /api/data
  -> returns the signals/all_links shape to the frontend

This is described in documents such as:

• arkkitehtuuri.md
• yleiskuva.md
• ai-putki-ja-jdbin.md

What a published signal carries

A live product signal is not just a title. The recurring fields in the docs include:

• sourceFact
• editorialSummary
• whyMatters
• evidenceSources
• consensus
• selectionAudit

Important distinction

The frontend does not usually read live JDBIN directly on every request. In practice it most often reads a snapshot-based public JSON response.

Even so, the semantic model comes from the same publish-pipeline design:

pipeline
-> published signal object
-> /api/data
-> frontend cards and modal

What this means for the documentation

Before the editorial pipeline is explained in depth, it should first be clear that:

1. the published unit is signal
2. signal is source-backed, not just AI copy
3. the UI terminology comes from the signal object fields and their derived interpretations