Documentation
¶
Overview ¶
Command aee-verify is the consumer MVP for AEE v0.7 statements: it runs GATE 0 (well-formedness), GATE 1 (coverage validity), the result recompute, derives the per-row evidence tier against a consumer policy, and evaluates the consumer-policy step (expected corpus and substrate anchors; the Admitted conjunction).
Exit codes: 2 on usage or I/O error; otherwise, when any consumer policy is supplied (-keys, -expected-corpus-digest, -expected-substrate-digest), 0 iff the statement is ADMITTED (validity AND tier policy AND supplied anchors); with no policy supplied (bare conformance-replay mode), 0 iff the statement is VALID.
Key policy file (JSON; pinned out of band, never read from the predicate):
{"substrateObservationKeys": [
{"keyid": "<hint, optional>", "publicKeyHex": "<64-hex raw ed25519 public key>"}
]}
The policy path may also arrive in AEE_SUBSTRATE_KEYS instead of -keys. That is the channel the conformance harness uses to hand a rail the pinned key policy without dictating a flag spelling: it runs each vector twice through the same argv, once with the variable set and once with it absent, and compares the two tier columns that come back. An explicit -keys always wins, and an unset variable is bare conformance-replay mode exactly as before.
In -json mode the whole report is written as ONE line, because the harness reads the last line of stdout and parses that line alone. A pretty-printed object ends in a line reading "}", which parses as nothing.
Source Files