EVIDENCE BEFORE ENTHUSIASM
Our method
A useful directory should show where a claim came from, when it was observed and what remains unknown.
How we source
Our starting set is the supplied candidates.csv snapshot. We retain editorial summaries and links to original authors and sources. Grok Bot observations come from the public grokbot.dev status, feed and detail APIs. GitHub project metadata comes from the public GitHub repository API. We do not copy repository README files, code or third-party posts. Inclusion is based on the existing research and content task tags, not stars or payment.
How we verify
The refresh job compares successful public observations with the last successful snapshot and checks source and action URLs. A first successful observation establishes a baseline; it is not a new-listing event. API failures and missing feed items are held for review. A failed link is unconfirmed, not proof that a tool was removed. A link failing for seven days receives a stale warning. We have not run or hands-on tested these assistants.
What the labels mean
- Source checked
- A label imported from the supplied snapshot, with its original date and provenance. It does not certify functionality, safety or availability.
- Links work
- The listed URLs returned a successful response at the recorded check time. Their contents and outcomes remain untested.
- Link unconfirmed / stale
- A check failed, or failed continuously for at least seven days. Follow the evidence and check again.
- Lower / technical setup (inferred)
- An editorial estimate based on hosted access versus a software repository. Exact prerequisites and account access need checking.
- New this week
- A real “added” observation in the current UTC ISO week. Imported records and baseline observations do not receive this badge.
- Recently active
- A source activity date within 14 days of the UTC build date, from a saved source snapshot or the original supplied data. Future dates are excluded; activity alone does not establish a recorded change or a new capability.
- Updated
- A real recorded change in changes.json in the current UTC ISO week, excluding simulated events and future dates. Source activity alone never receives this badge. This is not proof of a new capability.
- Unknown price
- No dated pricing evidence has been supplied. A software licence does not establish running costs.
Update cadence and dates
Refresh runs when the operator invokes refresh.py or the weekly job. There is no automatic scheduler bundled with the site. The intended newsletter cadence is weekly; each UTC ISO-week issue is frozen after generation. The home counts come from the current stored listings and real change log. “Last refresh” uses the saved run timestamp, or just the saved date for older reports. If neither is available, the cell is omitted. It is not the build time. Individual link and snapshot timestamps retain their own observation dates, including cached results.
Attribution and honest limits
Grokbot entry text keeps author credit, source links, CC BY 4.0 and modification notices. GitHub licences apply within their own scope. Source claims may be incorrect or outdated. We cannot establish access, cost, regional availability, output quality or safety from metadata alone. The four “Coming soon” sections carry no listings until public sources exist. No platform affiliation is implied.
Corrections
For this directory, give the workspace owner a listing URL and supporting evidence. A public contact channel must be set up before launch.