Manual Lifecycle and Decorators¶

These APIs are supported for integrations and framework glue, but are not part of the quickstart preferred execution path.

Manual lifecycle APIs¶

Use Tracker.begin_run(...) / Tracker.end_run() when start/end boundaries are controlled externally (for example framework hooks in separate call sites).

Use Tracker.start_run(...) when you still want the same low-level lifecycle surface but can keep it in one context-managed call site:

• Tracker.start_run(...)
• Tracker.begin_run(...) / Tracker.end_run()

Prefer run(...) and trace(...) when you can keep each step in one call site.

Step decorators¶

Use when you want reusable callable metadata defaults:

• @define_step(...)
• @tracker.define_step(...)

Decorator metadata can be useful in large shared step libraries, but introduces extra concepts compared to explicit run(..., outputs=[...], config=...).