Radar only
New, noisy, or barely explained tools stay here until their role in the ecosystem is easier to name.
How to use it
Treat the radar like scouting, not truth.
A tool landing here means it is worth watching. It does not yet mean the tool belongs in the catalog, the glossary, or the core curriculum.
The more stable pages stay slower and stricter on purpose.
Public-source workflow
The radar uses public discussion, then human filtering.
1
Collect weak signals. Refresh tracker/tool_radar.json from the Hacker News Algolia API with tracked terms and tool names.
2
Read for category impact. Ask whether a tool introduces a new layer, a new packaging pattern, a new host shape, or just another example in an existing bucket.
3
Promote carefully. Only move something into the catalog or glossary after it has clearer docs, a more stable identity, or broader ecosystem relevance.
Promotion rule
Not every hot repo becomes part of the field guide.
Catalog candidate
Promote a tool when it has a clear category fit, public docs, and a reason someone learning the stack should know it exists.
Glossary candidate
Promote a term or pattern when it starts appearing often enough that readers need a quick definition just to keep reading the site.
Tracked data file: tracker/tool_radar.json.