TorchLean API

NN.Backend.Profile

Backend Profiles #

Named backend profiles bundle the choices that should move together: build availability, kernel-selection policy, and the ordered capsule modules. This gives downstream APIs one object to pass around instead of separately threading flags such as "CUDA", "LibTorch enabled", and "trusted external allowed".

A named kernel-selection profile for one device.

  • name : String

    Human-readable profile name used in diagnostics and reports.

  • policy : KernelPolicy

    Device, provider preference, assurance policy, and VJP ownership.

  • availability : Availability

    Devices and providers the build declares available to planning.

  • capsuleModules : Array Registry.CapsuleModule

    Capsule modules used to construct and validate the profile's planning registry.

Instances For

    Extend a profile with operation/provider capsule modules without changing model semantics, availability, or assurance policy.

    A new contribution replaces an existing module with the same name. Duplicate names within modules are still rejected when the profile is planned.

    Instances For

      Capsule registry selected by the profile.

      Instances For

        Select capsules using the profile registry, availability, and kernel policy.

        Instances For

          Select a capsule for every runtime-relevant IR node.

          Instances For

            Plan, group, and contract-check a graph under the profile.

            Instances For

              Maintained portable CPU/reference profile with runtime guards and regression evidence.

              Instances For

                Checked native CUDA profile. External trusted providers are not admitted.

                Instances For

                  LibTorch forward scaling profile.

                  LibTorch is allowed to provide selected forward values, but TorchLean still records the graph/tape boundary and does not hand local backward ownership to LibTorch autograd.

                  Instances For

                    Maintained execution profile for a device, when TorchLean currently provides one.

                    Other named devices remain expressible through caller-supplied profiles. They are not silently converted into profiles with empty registries.

                    Instances For

                      Whether this profile registers at least one capsule for its selected device.

                      Instances For