WBN “Why It Matters” Engine — v1.0

📘 Description

The Why It Matters Engine is a lightweight interpretation system designed to transform raw news into clear, actionable insight for readers. It adds a single, business-focused sentence to each story, helping users quickly understand relevance and impact.

This system balances automation and editorial control, allowing WBN to scale content efficiently while maintaining a strong, consistent voice.

🎯 Purpose

  • Turn headlines into useful insight
  • Help readers understand impact, not just information
  • Maintain a consistent WBN editorial tone
  • Enable fast publishing without sacrificing clarity

⚙️ Core Structure

Each story follows this format:

Headline → Summary → Why It Matters → Source

🧠 How the Engine Works

1. Category-Based Sentence Engine

Each story is assigned a category (e.g., Weather, Transit, Real Estate).

The system inserts a pre-written sentence based on that category.

Example:

  • Category: Transit
    → This matters because transport disruption can affect staffing, customer access, and daily operations.

2. Sentence Library

A small, curated set of reusable responses powers the engine.

  • Start with 6–10 categories
  • Each category has 1–5 variations
  • Keep sentences:
    • Clear
    • Practical
    • Business-focused

3. Optional Modifiers (Future)

Sentences can be enhanced using:

  • Region (Vancouver, Canada, US, Africa)
  • Urgency (Low, Medium, High)
  • Audience (Small Business, Consumer, Investor)

Structure:

Base sentence + optional modifiers

✍️ Custom Override Field

Each story includes a Custom “Why It Matters” field.

Logic:

  • If custom field exists → use it
  • If not → use generated sentence

Example:

const finalWhyItMatters =
story.customWhyItMatters || generatedWhyItMatters;

Purpose:

  • Allows precise editorial control
  • Used for:
    • Breaking news
    • High-impact stories
    • Nuanced topics

🔁 Continuous Improvement Model

The engine improves over time through use.

Process:

  1. Generate default sentence
  2. Edit (if needed)
  3. Save improved version
  4. Add to response library

This builds a growing WBN Editorial Response Bank.

🗂️ Response Storage Options

To keep code lean, responses should be stored outside core logic:

  • JSON file
  • Google Sheet
  • Airtable
  • Lightweight database

Key Fields:

  • Category
  • Region (optional)
  • Urgency (optional)
  • Audience (optional)
  • Response Text
  • Status (active/inactive)

🧩 System Philosophy

  • Keep logic simple
  • Keep language modular
  • Avoid hard-coded complexity
  • Improve through iteration

🚀 Minimum Viable Setup

To launch:

  1. Define 6–8 categories
  2. Write 1 strong sentence per category
  3. Add “Why It Matters” field to each story
  4. Implement simple category → sentence mapping

That is enough for Version 1.

🔒 Editorial Positioning

WBN is not an aggregator.

It is:

An intelligence layer that interprets signals and explains what they mean for real-world decisions.

🧭 Guiding Principle

One clear sentence of insight per story is enough to transform information into value.

📌 Version

WBN Why It Matters Engine v1.0
Date: April 6, 2026
Status: Active — Iterative Build

If you want next, I can turn this into:

  • a Ghost-ready module block, or
  • a database schema + JSON file you can plug in immediately