Launch dApp
report 8801 - 21 AUG 2026 - finalizedrubric v1
contractunfit3/10
digest02a94f5d8bef...3206
gate5 of 6 present
contract0x1708...3d - studio
contract
The agreement rule fits what is being agreed0

strict equality is applied with a model call present and no validator pair

agreement, 0 out of 2
Needs GenLayer at all2

the contract fetches a product page via gl.nondet.web.get and passes it to gl.nondet.exec_prompt, so many nodes must

necessity, 2 out of 2
Untrusted text is fenced before a model reads it0

external text reaches the prompt with its structure intact

untrusted, 0 out of 2
The non-deterministic boundary is drawn once1

the calls are grouped, but no stored state is copied to memory first

boundary, 1 out of 2
The failure branches exist0

nothing raises, so every path assumes the happy one

failure, 0 out of 2

Why two numbers

They are never averaged. A careful contract behind a site that calls a transaction done the moment it is sent is a different problem from a weak contract behind an honest site, and one number would hide it.

What a 10 does not mean

This reads source text. It does not execute, fuzz or verify anything. A contract that scores 10 here can still be broken, and this is a first pass before a person reads it, not instead of one.

Read the rubricRun another