Beta

Signal Facet Designer

Signals stay off for launch, but the schema needs to be ready. This page captures the metadata we’ll store in Supabase/Convex and how it maps to filters/UI badges.

Source: Signal spec; Phase 1 migrations live with Supabase schema, Phase 2 ties them into AI/context engine.

Kinds

Controls iconography and influences which prompts or summaries we generate by default.

  • horizon_signal

    Emerging patterns, early indicators.

  • risk_alert

    Negative trend or dependency warning.

  • opportunity_spotlight

    Positive leverage point or enabling condition.

  • stakeholder_voice

    Quotes, testimonies, lived experience.

  • policy_signal

    Legislation, rulemaking, agency actions.

  • tech_milestone

    Capability jumps, deployments, breakthroughs.

  • method_in_use

    Practices observed in the field or labs.

  • counter_signal

    Evidence that challenges the prevailing narrative.

Metadata

Stored under signalMeta (or similar) facet; needs migrations + form controls.

  • confidence0-1 or qualitative (low/med/high).
  • time_horizonNear-term / 1-3y / 3-5y / 5y+.
  • impact_axespeople | planet | profit | power (multi-select).
  • geo_scopeGlobal vs region vs city.

Next steps

  • Draft Supabase migration + Convex schema changes.
  • Update adapters to expose the facet.
  • Wire filters/pills in the UI.