Hint 1: A result needs a target
Bind evidence to the exact service and source revision under review.
Hint 1 unlocks after your first failed run.
Hint 2: A test name is not all the evidence
This model checks metadata completeness. Human assessment must inspect whether the tests actually establish the required behavior.
Hint 2 unlocks after 2 failed runs.
Reveal the reference patch and explanation
export function missingEvidence(requirements, records, target) {
return requirements.filter(r => !records.some(e =>
e.requirement === r.id && e.service === target.service && e.commit === target.commit
&& e.result === 'passed' && Array.isArray(e.cases)
&& r.requiredCases.every(name => e.cases.includes(name))
)).map(r => r.id).sort();
}Both tenant-policy and replay-policy need records for service=invoices and commit=abc123. An old commit or other service leaves both missing. A record containing owner-allowed without other-tenant-denied leaves tenant-policy missing; a failed replay result leaves replay-policy missing. The output sorts replay-policy before tenant-policy. Under this exercise’s one-complete-run contract, two partial records do not merge into a passing run. Matching metadata still does not prove the assertions were meaningful or that abc123 is deployed.
Compare it with your own fix, then rerun the tests. The editor is not changed when you open this explanation.
The reference patch unlocks after you run code you have edited.
Inspect the actual test harness
The browser and the lab download run the same cases, including cases that catch common wrong fixes, such as comparing with one fixture value instead of the real rule. The download includes the complete test adapter and cryptographic fixtures.
Download cases.mjsHow the browser sandbox runs your code
Your code runs in QuickJS 2025-09-13 (quickjs-emscripten 0.32.0) inside a Web Worker, isolated from the page, with a 32 MiB memory limit and a 2.5-second time limit. The test cases and the pass or fail verdict run outside that sandbox, so changing built-ins such as Array.prototype.push cannot change the result. The lab download runs the same cases under Node.js, where your code runs directly.
The same as in current Node.js:
- ES2025 syntax and built-ins, including Set methods such as intersection, iterator helpers, Promise.try, RegExp.escape and the RegExp v flag
Added to the sandbox so that it behaves like Node.js:
- structuredClone, Array.fromAsync, queueMicrotask, atob and btoa
- URL and URLSearchParams, parsed by your browser’s own URL implementation
- TextEncoder and TextDecoder for UTF-8
- Intl.Collator and a locale-aware String.prototype.localeCompare
- console.log and related methods, whose output appears with your results
Not available in the browser sandbox:
- Timers (setTimeout, setInterval), fetch and other network or storage APIs; the exercises are deterministic and offline
- Node.js modules and globals: import, require, process and Buffer
- Web Crypto (crypto.getRandomValues, crypto.subtle); each workshop supplies the cryptographic operations it needs
- Intl other than Collator: toLocaleString and toLocaleDateString ignore the locale, so numbers have no digit grouping and dates use one fixed format in the device’s time zone
- using declarations, Symbol.dispose and DisposableStack (explicit resource management)
- Uint8Array.fromBase64 and toBase64, JSON.rawJSON, Atomics and Error.captureStackTrace
This exercise uses synthetic requirement IDs, not official ASVS identifiers. Metadata matching cannot prove test quality, evidence authenticity, deployed-build identity, framework compliance or acceptable risk. The accompanying evidence-pack walkthrough addresses human assessment.
Your next task: Which records demonstrate that the tested revision is the one deployed, and who evaluates the adequacy of the tests?