I am a technical analyst deciding which Keryx release to evaluate for a small startup. Read the registered, verified creator release source associated with https://github.com/tang-vu/keryx/releases.atom. In English, name the newest release tag actually present in the feed and one explicit change stated for that release, with inspectable citations. Explain one compatibility or deployment fact the release entry does not establish. Use the eligible registered creator path within the admitted source/reward budget; disclose actual access and citation payment outcomes separately. Do not treat an unpaid public reference as a creator payment or treat a transfer alone as proof the answer is useful.
10/7/2026, 11:19:40 PM · llm:deepseek:deepseek-v4-flash
Decision log · 76 steps
Portable research receipt
Take the evidence trail with you
One deterministic JSON bundle binds the answer, visible decisions, exact article versions, claim evidence and a Circle-settlement snapshot under SHA-256. Retain the digest to detect later changes; the self-check is not a publisher or Keryx signature.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.