Creating a product means creating something else first, and the product never shows what it delivers #98

New Issue

2026-09-21T07:18:29Z

cgalo5758 commented

2026-09-21 07:18:29 +00:00

The question

An operator who sets out to create a product cannot finish without leaving the form to create an entitlement set (the named collection of rules that says what a product delivers) first. Nobody has named a case where a set is worth authoring on its own, away from the product that will sell it. Is a set an object in its own right, or is it the rules of a product?

What depends on the answer

The product create flow, the product page, which names the set and offers no way to read its rules or reach them, and the entitlement set pages themselves. Rule authoring depends on it too: an operator adding a boolean rule (a yes-or-no capability, such as custom domains) could not tell from the form what the rule would do, and the prose above the form did not close the gap.

Options known so far

Keep the set as its own object and make the relationship legible: author a set from inside the product form, and show the set's rules on the product.
Fold the rules into the product, so a product carries its own rules and a shared set becomes something an operator opts into rather than the only way to author one.
Keep both and change the default: sets stay first-class for reuse, but authoring one is never a prerequisite for creating a product.

Decided when

The catalog model states whether a set is an object of its own or a product's rules, the create flow follows it, and the product page shows what the product delivers without the operator navigating away.

Migrated from status/issues.md at b7a0e15

## The question An operator who sets out to create a product cannot finish without leaving the form to create an entitlement set (the named collection of rules that says what a product delivers) first. Nobody has named a case where a set is worth authoring on its own, away from the product that will sell it. Is a set an object in its own right, or is it the rules of a product? ## What depends on the answer The product create flow, the product page, which names the set and offers no way to read its rules or reach them, and the entitlement set pages themselves. Rule authoring depends on it too: an operator adding a boolean rule (a yes-or-no capability, such as custom domains) could not tell from the form what the rule would do, and the prose above the form did not close the gap. ## Options known so far - Keep the set as its own object and make the relationship legible: author a set from inside the product form, and show the set's rules on the product. - Fold the rules into the product, so a product carries its own rules and a shared set becomes something an operator opts into rather than the only way to author one. - Keep both and change the default: sets stay first-class for reuse, but authoring one is never a prerequisite for creating a product. ## Decided when The catalog model states whether a set is an object of its own or a product's rules, the create flow follows it, and the product page shows what the product delivers without the operator navigating away. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/entitlements area/catalog area/operator-ui labels 2026-09-21 07:18:29 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#98