Application Flow

When to Use

Use this skill when the user asks how to structure an ovstage program end-to-end, what the main steps are, how the pieces (instance, path dictionary, query, write/ordinal/write-floor, read, release) fit together, or which focused skill owns each step.

Inputs

Resolve inputs in this order: existing repository files and referenced snippets, explicit user request, then broader agent context.

• Lifecycle stage in question: instance creation, prim/attribute identity, write, seal (advance write floor), query/read, or release.
• Whether the program ingests existing USD (the population API, ovstage_population.h) or writes attributes directly (the path shown here).
• Whether it's a one-shot write→read or a running producer/consumer loop (CPU running ahead of execution — see cpu-ahead-gpu-async).
• The shipped headers and the referenced example snippets are the authoritative contract.