CrucibleX is a Ray-first operator testing toolkit for case generation, device scheduling, execution, comparison, and report delivery. It is the clean-slate successor to the previous ATK codebase.
src/cruciblex/domain/core entities and enumssrc/cruciblex/generation/case and input generationsrc/cruciblex/runtime/Ray execution plane, device actors, and local smoke schedulersrc/cruciblex/storage/artifacts, results, and resume statesrc/cruciblex/report/summary and export helperssrc/cruciblex/plugins/generator, executor, and comparator pluginstests/unit and integration testsexamples/minimal node and case examples, including operator onboarding templatesdocs/cli.mdcommand reference forcx run,cx report,cx repro,cx onboard, andcx generatedocs/operator-onboarding.mdoperator onboarding checklist and smoke flow
Install and run with uv:
uv sync
uv run cx --help
uv run cx doctor
uv run cx generate --case examples/cases/torch.abs.generated.yaml --output cx_output/generated-smoke
uv run cx run --case examples/cases/torch.abs.yaml --nodes examples/nodes/local.yamlRay is the default execution path. Use --scheduler local only for lightweight debugging or smoke tests that should avoid starting Ray. See docs/cli.md for command inputs, outputs, and common workflows.
Public image build and runtime instructions live in docker/README.md. The ignored docker/private-notes.md is also a required operational record: maintain the environment-specific NPU/GPU validation context, approved image references, driver and device mapping constraints, and validated runtime versions there. It may contain private hosts, registries, credentials, or lab commands, so it must never be committed or copied into public documentation. When a hardware gate changes, update the corresponding private evidence and keep the public runbook free of environment-specific values.
Run tests with:
uv run --extra dev pytest