verify-layer README: the test table names the complete served verifier set (verify-proof.mjs alone gives 41/45), the negative control from a fresh clone (37/37), and the one adapter check that needs the verifier
This commit is contained in:
1 parent
ac14880703
commit
8c7d72c1a7
2 files changed
+3
-3
No files matched your search
@@ -193,8 +193,8 @@ workload added, and on the same export with environment values planted (`fixturi
|
||||
copies in `fixturi-cloud/surse/`, and compared with them at every run): it requires exactly the running workloads with their
|
||||
identities, no planted value anywhere in the log or the descriptors (and the names present, as the positive control), another CLI's
|
||||
export refused by name, every descriptor re-hashing to the digest in its envelope, and every envelope `VALID` for the reference
|
||||
verifier. `control-negativ-sidecar.mjs` adds three plantings per adapter (the running filter removed, the names replaced by the
|
||||
name/value pairs, the shape check removed) and requires each to turn its named check red: measured 38 of 38 on 2026-10-18. The
|
||||
verifier (looked for at `AERE_VERIFY_PROOF` as above; without it that one check is reported as skipped and the exit code is 2, with 59 run). `control-negativ-sidecar.mjs` adds three plantings per adapter (the running filter removed, the names replaced by the
|
||||
name/value pairs, the shape check removed) and requires each to turn its named check red: measured 38 of 38 on 2026-10-18 in the development tree and 37 of 37 from a fresh clone of the public repository (the case that compares with the pre-review version is skipped there). The
|
||||
adapters are producers, not verifiers, so they name no rule of the conformance suite (`conformance/`), whose rules are those of the
|
||||
log and tree verifiers, unchanged.
|
||||
|
||||
|
||||
Reference in new issue
Block a user