The Client Newspaper — System & Concept Diagrams

Figure 1 · System architecture

From ad platforms to a client-ready page — automatically

A scheduled job pulls the figures every day, stores them, drafts the mechanical “reads,” and renders each client’s themed hub. Credentials only gate the connectors on the left — everything to the right is serverless.

Data sources (need access) Cloudflare (serverless) AI — mechanical draft only Client-facing output

Figure 2 · Information architecture

One front page, four sections — cloned per client

The hub is the “front page.” Each report is a section a client can open. Creative and Work-in-progress are placeholders today; the same tree is stamped for every client from a config row.

Figure 3 · Client journey

What the client actually does

The whole point of the “newspaper” feel: a client understands the headline in one glance, then drills only into what interests them.

Figure 4 · The guardrail

Figures are machine-owned; judgment is human-owned — in one document

Martial’s hard line: automate the figure-gathering and the mechanical description, never the analysis. Both live in the same shared report, so it’s never a “my report / your report.”