Request verification

Propose a claim, not a verdict.

A request can come from a maintainer, a vendor, a user nomination, or VeriEnvelope’s own research selection. Its source does not change the Method or buy a result.

Include

• The exact component, version, and source repository.
• One behavior that can be stated as a narrow, observable claim.
• Any required network access, credentials, files, or runtime constraints.
• Why the claim matters and what must remain outside the conclusion.

What influence can—and cannot—buy

Request source, audience demand, or future payment may affect selection, priority, scope, or report format. They cannot purchase demonstrated, widen an Envelope, hide a negative result, or change the frozen decision rule.

No submission backend or payment flow exists today. Use a public GitHub Issue or email for sensitive preliminary context.