Supplied-record evaluation
Inspect the supplied-record candidate-to-issue boundary.
Deton models a pure AppSec evaluation contract. A signal remains a candidate unless an identity-matching supplied result carries the required schema value. Acceptance does not attest live execution, and customer-source transport is unavailable.
The evaluator-eligibility boundary
Confirmed means only that the pure evaluator accepted the supplied result and may make the builder eligible for an in-memory issue. It establishes no execution, authenticity, persistence, custody, delivery, canonical publication, or confirmed customer vulnerability.
From supplied signal to bounded in-memory eligibility
1. Candidate
Normalize the source signal into an explicit, reviewable hypothesis.
2. Proof plan
Describe the intended family contract, oracle, safety ceiling, and prospective replay inputs.
3. Pure evaluation
Evaluate an identity-matching supplied result without treating it as proof of live execution or turning missing input into certainty.
4. In-memory issue eligibility
The builder may construct an in-memory issue value; no persistence, GitHub delivery, or canonical publication is established.
What the current public materials establish
Repository tests and hand-authored synthetic fixtures exercise pure contracts. They authenticate no runner execution, provenance, custody, persistence, GitHub delivery, canonical publication, or customer-repository scan.