An editorial product team building news infrastructure.

• Editorial systems: define story surfaces, source display, topic structure, and reader-facing wording.
• Data and pipeline: collect updates, cluster related items, normalize metadata, and keep source evidence attached.
• Product and design: turn the underlying data into fast, calm, and searchable public pages.
• Operations: monitor availability, feed freshness, and user-visible failures across the stack.

The team treats public pages as the product, not just a dashboard over data. A feature is considered useful only when readers can land on it from search or links, understand the story quickly, and continue into related coverage.

For correction requests, include the page URL, the source being referenced, and the specific wording or metadata that should be reviewed. This keeps fixes tied to verifiable evidence.