What's new

Small product notes from the 3signals build log.

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 targeted 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

2026-05-08

Operator analytics, open tracking, and social surface

3signals now records newsletter opens, site access, feedback, and daily social publishing signals so each run can be evaluated as both a briefing and a product loop.

  • The admin console summarizes users, email opens, site access, signups, feedback, and daily activity patterns.
  • Newsletter footer actions collect per-issue thumbs-up/down feedback for future tuning.
  • The site and emails consistently expose @3signalsai, Medium, LinkedIn, and share actions.

Source: session · X note pending

2026-05-07

Freshness grading, reader feedback, and newsletter archive

3signals now grades the current pipeline for freshness, novelty, and impact before publication, stores each issue in a public archive, and adds per-recipient thumbs-up/down feedback links.

  • The freshness gate favors signals backed by a newly retrieved premier article.
  • Reader feedback is tied to the subscriber and issue so votes can tune future signal presentation.
  • New subscribers receive the latest staged issue immediately after confirming their email.

Source: session · X note pending

2026-05-07

Editorial QA for source-backed signal headlines

3signals now checks that every featured signal headline is supported by its premier article and supporting evidence before it appears in the newsletter, website, wiki highlights, or X thread.

  • Mismatched premier articles can be replaced by better evidence from the same signal group.
  • Over-strong wording is softened when the source material does not support it.
  • Weak, promotional, or misleading evidence can hold a signal back from publication.

Source: session · X note pending