Independent contract review
Challenge command fields, transitions, reset/error precedence, accumulator lifecycle, memory behavior, and ambiguous language.
Open work, clear boundaries
Bring evidence.
01 / Useful now
Work at the current frontier.
The calibrated workload is complete. The first two Conv-SiLU blocks pass; C2f graph lowering and independent contract/conformance review are the next steps.
Conformance scrutiny
Re-derive expected fixture outcomes, inspect provenance and masking rules, and propose missing positive, boundary, or negative cases.
Expand the compiler/runtime
Extend the compiler to C2f split, concat, residual scales, and retained intermediates. Review the experimental package schema and failure cases.
See the next slice →Numerical test vectors
Add adversarial cases, independent comparisons, and minimized regressions for rounding, saturation, layouts, activations, and accumulation.
02 / Find your layer
Many disciplines fit here.
HASLAB is deliberately layered so a contribution can be deep and useful without spanning the complete system.
ML + quantization
Export auditing, operator coverage, calibration, accuracy budgets, preprocessing, and host-tail boundaries.
Compiler + runtime
Deterministic lowering, shape and layout logic, tiling, SRAM planning, packages, errors, and simulator execution.
RTL + verification
Narrow conformance-driven modules, assertions, differential testing, formal properties, and reproducible tool flows.
FPGA + silicon
Resource probes, memory mapping, board evaluation, process assumptions, SRAM, DFT, physical verification, and packaging.
03 / A strong change
Make the reasoning reviewable.
A contribution should explain why the change exists, which contract it affects, and what evidence shows it is correct.
Before proposing
- Identify the specification or interface affected
- State the workload or measurement motivating the change
- Check current milestone dependencies
- Review existing decisions and open evidence gaps
Include with the change
- Tests or verification appropriate to the layer
- Strict reporting of unsupported behavior
- Pinned tools, artifacts, versions, and commands
- Third-party model, dataset, PDK, IP, and tool licensing
04 / Begin
Read, reproduce, then propose.
Start with the contribution guide and current development plan. For interface or numerical changes, expect a short architecture decision record and evidence that keeps the golden oracle independent.