Loading rankings…
Loading rankings…
Session watching vs yield scoring
| Feature | SigRank | sessionwatcher |
|---|---|---|
| What it measures | Cascade yield per session + overall | Session activity monitoring |
| What it tells you | How efficiently you compound signal | What happened in your sessions |
| Leaderboard | Yes — ranked by Yield, class tiers | No |
| Platform coverage | Claude Code, Cursor, Copilot, Gemini, 15+ | Limited |
| MCP server | Yes | No |
| Privacy | Token counts only — never prompt content | Token counts only |
sessionwatcher watches AI coding sessions. SigRank scores the yield of those sessions. Watching is not scoring.
SigRank's Yield (Υ) metric measures the architecture of your token cascade — is signal compounding, or are tokens burned? That's the question sessionwatcher can't answer.
sessionwatcher watches AI coding sessions. SigRank scores the yield of those sessions. Watching is not scoring. SigRank's Yield (Υ) = (cache_read × output) / input² measures cascade efficiency.
Yes. They're complementary. Use sessionwatcher for its function, and run sigrank submit to publish your cascade score to the leaderboard.
Yield (Υ) = (cache_read × output) / input² — token-cascade efficiency from real sessions. Works across Claude, GPT, Gemini, Cursor, Copilot, and any AI coding tool.
Visit signalaf.com/score to enroll and submit your token telemetry. SigRank will compute your Yield, your rank, and your operator class. Token counts only — never prompt content, never code.
Stop watching sessions. Start scoring yield.
Check my Yield