Launch Determinism Challenge Corpus and Public Scorecards

[dgenio]

Description

Users need public, repeatable evidence beyond one benchmark script.

Use case

Teams comparing orchestration tools want trusted determinism proof points.

Proposed solution

• Define challenge corpus with seeded deterministic and adversarial cases.
• Publish scorecards: correctness, repeatability, and latency variance.
• Version the corpus and document update policy.
• Add CI job that regenerates scorecards on schedule.
• Add contribution guide for new corpus cases.

Alternatives considered

• Keep private benchmark cases.
• Publish one-time blog metrics.
• Depend on raw CI logs only.