Bounded collection.
A private AWS worker, persistent research checkpoints, explicit feeds, cached searches and typed Jev decisions. Runs have request allowances and input bounds.
Discover early.
Investigate carefully.
A collection system should find useful signals, avoid repeat work and leave an evidence trail. It should also say clearly which parts still need an operator.
Research & review.
Local researcher, challenger, evaluator and editor roles prepare dossiers. Exact-revision approval and edition publication remain human-owned.
Measured confidence.
A trusted experiment registry, operational evidence, calibrated detection recall and useful notifications are further work. No autonomous production endorsement is claimed.
THE REPEAT-WORK PROBLEMCheck for change.
Check for change.
Then spend attention.
The same persistent database keeps source metadata, caches, decisions and provider-attempt counters. A cloud checkpoint preserves these between worker invocations.
Conditional HTTP
ETag and Last-Modified validators can turn unchanged feed checks into a 304 response.
Content identity
Canonical URLs and fingerprints avoid treating tracking links or identical text as fresh evidence.
Metadata first
A bounded relevance gate can fetch, defer or skip. Uncertain leads remain available for review.
Exact-input caching
Model, question and evidence fingerprints let identical assessments reuse a previous result.
Request allowances are per research store, not a hard monetary cap across all copies of the database. Provider limits remain separate.
Different areas.
Different places to listen.
Engineering blogs & releases
Explicit RSS/Atom feeds, project release notes, GitHub and arXiv collectors. Official documentation anchors creator claims.
Hacker News & the open web
Bounded official Hacker News API scans and Brave searches surface leads. Coverage is constrained by keywords, rotation and budgets.
X & Reddit
Optional official API connectors. They require configured access and entitlements; Reddit also requires approved use. No social HTML scraping fallback.
Enterprise & community sources
Project-owned sites, Apache projects, permitted search metadata and manually supplied LinkedIn links. Newly found sources enter a reviewable registry.
THE PUBLISHING BOUNDARYPrivate research.
Private research.
A public point of view.
The Lambda worker reads its API configuration from Secrets Manager and writes a private, versioned research checkpoint. Its permissions do not allow it to write the website bucket.
The public website is a separate static export. It can present an approved edition and its backing references, but does not serve drafts, client records, private samples or API keys.
PRIVATE
Sources · samples · model decisions
Research database · API configuration
HUMAN REVIEW + APPROVED EXPORT ↓
PUBLICEdition · recommendations · approved sources
Methodology · portfolio · project notes
Measure the misses, too.
The quality of discovery needs testing against a dated set of relevant launches. Useful measures include discovery delay, shortlist relevance, worthwhile leads missed, source diversity, duplicate rate and cost per useful dossier. The current pilot does not claim a measured one-day detection guarantee.
LET’S MAKE IT PRACTICAL
A clearer next move.
Bring a question, a shortlist or a difficult trade-off. We’ll start there.