Create a Product
Nishad
↻
Om Cortex building one of our own products. The engine is the product β€” here we define Om WMS on the platform the same way a customer defines theirs. Om WMS is Cortex running a warehouse business.
Defining this product
Saved Β· resume anytime
Om WMS
A new product on Om Cortex Β· defined in conversation, no long forms
A Placement Β· Company β–Έ Product Set
Company
Om Supply Chain
β†’
Product
Om WMS
B Charter Β· what this product is for Set

A self-learning warehouse system β€” a customer manages inventory the way their warehouse is physically laid out, with their existing products.

C Workflows to attach Β· the machinery that builds it Confirming
  • Full Software Lifecycleattached
    The build engine β€” features go from request to shipped through the full ladder: design β†’ plan β†’ code β†’ review β†’ test β†’ deploy, with human gates where they belong.
  • Screen Flowattached
    The design engine (D-6) β€” Om WMS's own screens get designed through the Screen-Flow template already in the catalog.
    ↻ Self-referential: the same machinery that designed these very screens designs Om WMS's screens. Cortex, running the workflow, reproduces this very catalog.

Creates Om WMS under Om Supply Chain and wires the two workflows β€” after this it's ready to have seats + capability assigned and the build run as normal work. Saved if you'd rather finish later.

Cortex built-in
We're standing up a new product on the platform. What is it, and which company does it sit under?
Nishad
Om WMS β€” a self-learning warehouse system, under Om Supply Chain.
Cortex built-in
Placed it on the left: Om Supply Chain β–Έ Om WMS. To actually build it, I'd attach two workflows β€” the Full Software Lifecycle (the build engine) and Screen Flow (the design engine). That's the same machinery every product on the platform runs β€” including the one that designed these very screens.
Nishad
Attach both. That recursion is the whole point.
Cortex built-in
Both attached. Create it and Om WMS is ready for seats + capability, then the build runs as normal work. Once it ships, Om WMS packages as a vertical configuration and installs at a warehouse customer β€” the same wheel, one turn further.

What's on this screen

Built from: the product-definition conversation with Cortex, drafted live as you answer, plus the workflow catalog it attaches from.

On screenWhere it comes fromWhat it means to you
Placement (Company β–Έ Product)your answer in the conversation, placed on the spineconfirms which company owns this new product before it's created
Charteryour plain-English description of what the product is forthe one-line explainer other screens will show for this product
Workflows to attachthe platform's workflow catalog β€” the same machinery every product runswhich build/design engine will actually run this product's work
"Set" / "Confirming" tagswhether Cortex has locked in that stage of the draft or is still checking with youtells you what's final vs. still open before you commit
Cortex conversation (right pane)your live back-and-forth with Cortex while it drafts the definitionlets you correct or steer the definition in plain language instead of a form
"Create product & attach workflows" buttonyour final confirmationcommits the draft β€” creates the product and wires the two workflows to it
"Saved Β· resume anytime" chipthe draft's autosave statereassures you it's safe to leave and come back without losing progress