Disputes that arrive with data attached outrank everything else. If you have hardware traces, a workload that behaves unexpectedly, or a number on this site you believe is wrong, write to us.
Contact
What to include
- Hardware traces
Raw JSONL output from
sounding, with the silicon profile and model name in the filename. Anonymised traces are accepted; mock traces are not.- Workload disputes
The model, batch size, prompt length distribution, and the latency or cost figure you observed versus what berth predicted. A single data point with context is more useful than a general objection.
- Collaboration
If you have access to silicon we have not measured, or a workload class the current model does not cover, we want to hear from you.
- Security
Responsible disclosure for the berth codebase: security@reckonresearch.com. PGP key available on request.