Methods

The post-training methods this deployment offers, and every hyperparameter you can tune.

The catalog as the console renders it: built-in recipes plus anything published as a recipe pack, each with a source badge.

Method catalog with framework versions and tunable parameters.

What you see

Field	What it tells you
Framework version	Which upstream version this method runs, and which others it supports
Roles	The roles it needs — actor, reference, rollout — which is what lets you split pools with --profile
Post-train actions	What --then accepts for this method
Algorithm plugins	Patches loaded by default
Parameters	Every tunable key with its type, range, default, and where it lands in the framework’s own config

That last column is the one worth reading before your first submit. It is the same declaration sf validate checks against, so if a value is not listed here, setting it will be rejected.

What you can do

• Search by name, summary, framework or publisher.
• Copy the submit command for a method, pre-filled.
• Open a published method’s source to see who published it and at which version.

When a method you expect is missing

The catalog is what the platform supports; this screen is what this deployment opens to its users. An administrator narrows it with FORGE_ALLOWED_RECIPES — a cluster without the memory for distillation turns it off there rather than by editing the catalog.

If nothing is listed at all, the allowlist is set to something that matches nothing.