BETA · GAMMA-Ray is published for review. The rules, the mapping and every rating here are experimental and will change. How a rating is made · what exists · send a correction
GAMMA-Rayv0.0.21 · beta

The pipeline

How it runs today

This is a beta and the flow is still being found. Today a card for somebody else's product goes through this, by a team of agents working in the public repository:

  1. A draft by the studio agent: the evidence mapped to indicators, every source captured and hashed, a vault.
  2. Two rounds of review by a reviewer agent that did not write it: every source opened and checked against the answer; then every level three and four argued against.
  3. A sign-off by an approver agent that neither wrote nor reviewed it.
  4. Published as beta. The company is told afterwards and invited to correct or claim its card.

The gate refuses to publish a third party's card without the two rounds and the sign-off.

ScanStatusReview roundsSigned off
Claude Code on the webpublished-before-review1
Claude Code, on your own machinepublished-before-review1
GitHub Copilot cloud agentpublished-before-review1
Juniedraft0
Manusdraft0
Replit Agentround-11

The fuller pipeline it is growing towards

Several agents and one person, so that no level rests on one reader.

StepWhoDoesNever does
1. Scoutan agentbuilds the cohort and picks one agentic product per companypublishes
2. Collectoran agentfinds sources, captures and hashes each one into the card's vault, runs read-only checks of public addressessends credentials, or tests anything
3. Assessor A and Assessor Btwo agents with no shared contexteach maps evidence to indicatorsassigns a level
4. Scorercode, not an agentcomputes levels, stage, badges and the constellation from the indicators both assessors agree onjudges
5. Challengeran agentargues against every level three and four, and every disagreement between the assessorslowers a level by itself: what it cannot settle goes to a person
6. Gatecodechecks the rules mechanically
7. Editoran agentwrites the standout lines and the editionuses an adjective about a company
8. A personapproves the cohort, settles what the challenger escalates, signs off, and sends anything that leaves

The evidence record

One per answer, in the card's vault and in evidence.json:

FieldWhat it is
indicatorthe one fact this is evidence for
urlthe public source
sha256, read_atthe hash of what was fetched and when: the level was computed from that capture, not from the page as it may be today
methodread (a person or agent read it) or probe (an address was fetched and it resolved)
spanthe words quoted, fewer than fifteen
grade, modehow it is known, and whether it holds as shipped or is available
assessor, agreement, challengerwho mapped it, whether both agreed, and what the challenger found

What exists in this repository

What does not exist yet