What's new

Small product notes from the 3signals build log.

2026-06-11

Vibe Check section

3signals now has a Vibe Check section for surfacing community-validated momentum alongside the system's curated signal picks.

  • The newsletter format can now separate deterministic Curated Signals from Vibe Check picks, making it clear what came from structured discovery versus public community momentum.
  • Vibe Check scans public engagement across sources such as Reddit, Hacker News, and GitHub, then runs candidates through the same quality gates before they can appear in a 3signals issue.
  • Each Vibe Check item carries a short "what's the vibe" note, giving readers quick context on why builders are talking about it now.

Source: session · X note pending

2026-05-18

Interactive wiki graph view

The 3signals wiki now includes an Obsidian-style graph for exploring how signals connect to topics, concepts, authors, and source evidence.

  • Open the graph from the wiki card to see signals and topic clusters arranged as an interactive map.
  • Use the graph filters to show signals, topics/concepts, and authors together or one layer at a time.
  • Hover a node to reveal its headline, click once to focus nearby labels, and click a signal node again to open the full newsletter-style signal card.

Source: session · X note pending

2026-05-17

Front-end and back-end split for faster site delivery

3signals now serves the public website from Vercel while Railway keeps running the API, cron jobs, and content generation pipeline.

  • The public web experience now loads from Vercel-hosted pages instead of waiting on the Railway server container to wake up.
  • Railway remains responsible for stateful work: ingestion, publication jobs, newsletter delivery, wiki artifacts, signup, login, unsubscribe, and feedback endpoints.
  • The split keeps the site fast for readers while preserving the existing production pipeline behind api.3signals.ai.

Source: session · X note pending

2026-05-09

Daily and weekly subscription controls

3signals now lets readers choose daily signals, the weekly digest, both, or wiki-only access without losing premium wiki login.

  • New signups default into both daily and weekly email streams, while confirmed readers can still choose neither and keep wiki access.
  • Existing verified subscribers are opted into both streams when the new preference fields are added.
  • Newsletter footers now include separate daily and weekly unsubscribe links.

Source: session · X note pending

2026-05-09

Wiki date horizons and scoped Obsidian vaults

The premium wiki now supports recent-history filters and matching Obsidian downloads, using pull date by default with source publication date available as an alternate lens.

  • Readers can open filtered views such as the last 5, 7, 30, or 90 days from the wiki and signals index.
  • Scoped Obsidian vault downloads preserve the same date horizon, so personal notes can focus on the window a reader cares about.
  • Pull-date filtering answers what 3signals recently retrieved, while source-date filtering answers what original authors recently published.

Source: session · X note pending

2026-05-09

Daily and weekly process modes

3signals now has a unified process endpoint with daily and weekly behaviors plus send and operator-only test options.

  • Daily send remains the default production behavior.
  • Weekly send builds a digest from the last seven days, selecting up to 21 deduplicated signals.
  • Test mode forces delivery to the configured operator email, skips X posting, skips presentation recording, and disables external delivery sync.

Source: session · X note pending

2026-05-09

Editor headline presentation layer

3signals now treats presentation as a first-class pipeline concern, with prompts and guards that turn derived signals into punchy factual headlines instead of source summaries.

  • Extraction summaries are now explicitly requested in headline form: specific, attention-getting, and factual.
  • The Editor persona avoids phrases like 'The article discusses...' or 'The author claims...' and makes the same general claim the source evidence supports.
  • Deterministic title guards now catch additional source-referential language before it reaches the newsletter or wiki.
  • The finalized Editor headline is reused across the newsletter, wiki, homepage feature cards, and X posts so public surfaces stay aligned.

Source: session · X note pending

2026-05-08

Daily broadcast send lock

3signals now has a hard server-side gate that prevents the full subscriber newsletter from being sent more than once per campaign day.

  • The lock lives in the send path itself, so duplicate cron, Railway, n8n, or manual broadcast calls are rejected before any email is sent.
  • Resetting generated content does not clear the broadcast lock, which prevents accidental resend storms after operator maintenance.
  • Test sends remain available for QA, but recipient overrides are restricted to the operator email.

Source: session · X note pending

2026-05-08

Calibrated extraction for better signals

3signals now uses a stronger extraction model and an explicit score calibration rubric so novelty, authority, and signal quality are grounded in evidence rather than hype.

  • Extraction now runs on gpt-4o so summaries, entities, scores, and signal grouping get higher-quality structured inputs.
  • The novelty rubric reserves high scores for concrete new evidence such as releases, benchmarks, papers, datasets, product launches, implementation details, policy decisions, and first-hand operational reports.
  • Commentary, recaps, promotional material, memes, merchandise, administrative notes, and engagement bait are now pushed lower before they can become featured signals.

Source: session · X note pending

2026-05-08

Claim-aware novelty rotation

3signals now rotates featured signals using evidence fingerprints, newly supported claims, unseen authors, and new entity mixes instead of relying only on broad topic freshness.

  • The daily top three now targets at least two signals that are new or newly supported by fresh evidence.
  • Manual test sends can avoid recording presentation history so they do not make the next real briefing look stale.
  • Operator reports now explain novelty reasons, fingerprint diversity, and when the new-signal target is missed.

Source: session · X note pending

2026-05-08

Secure 3signals.ai domain and cleaner browser trust

3signals now runs from the canonical 3signals.ai domain with HTTPS redirects, security headers, and a hardened browser delivery path.

  • The site now redirects to the canonical HTTPS domain and sends HSTS plus browser security headers.
  • The public pages were checked from a clean Chrome context for valid certificates, secure context behavior, and mixed-content regressions.
  • The setup keeps old links working while steering readers to the trusted 3signals.ai experience.

Source: session · X note pending

2026-05-08

Reset, rebuild, and test-send controls

The system now has secured reset and async job controls for wiping generated content, rebuilding from seed configuration, and sending operator-only test newsletters.

  • The reset flow clears retrieved content, vector data, generated wiki files, markdown vault artifacts, and newsletter cache while preserving seed configuration.
  • Long-running jobs can be dispatched asynchronously and checked through secured status endpoints.
  • Targeted recipient overrides make it possible to run production-like newsletter tests without mailing the full subscriber list.

Source: session · X note pending