BITFETTIOBSERVATORY 0.3.0
HOW IT WORKS

See what your code can really do

Explore its behavior, catch surprising failures, and share results people can check.

1. Pick an artifact

Every program page names one published version by its content digest. The page describes that version and nothing else; a newer version gets its own URL and the old one keeps working.

2. Run it over a domain you declare

A scan executes the artifact itself in a gas-metered sandbox over the integer interval you name, and keeps every raw sample. Inputs outside that interval stay unexplored rather than being reported as passing.

3. Check the receipt

The receipt digest commits the artifact identity, the exact inputs, the samples, and the environment the run happened in. Change any one of them and the digest changes.

4. Read the scope

Every claim carries the boundary of what was established. An unassessed program has no score, which is not the same as a low score.

What is not available yet

Self-service accounts, fused pipeline builds, and independent third-party reproduction are not offered. Where a capability is absent the interface says so rather than showing a placeholder.