OXYGEN GTM

Use OXYGEN as a CLI/MCP/API-first GTM engineering workspace and AI CRO surface. Start from the product primitives and surfaces — workspace context, tables, schemas, columns, enrichments, action runs, workflows, sequencer, approvals, credits, and provenance — then choose commands. Prefer schema discovery and explicit table/column/workflow commands over one-off provider calls.

The product doctrine is: CLI/MCP executes; web and ui:// widgets visualize, approve, retry, and explain.

Primitive And Surface Default

For GTM work, first decide which OXYGEN primitive or surface should own the state. Formal primitives are organizations, tenant databases, tables, the tool/enrichment catalog, workflows, and observable runs; the column and sequencer surfaces below sit on top of those primitives. Do not start from a provider tool unless the task is truly a one-off probe.