Should capabilities be grantable without inventing a product to carry them #123

New Issue

2026-09-21T07:18:36Z

cgalo5758 commented

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

The question

Every grant names a product. Giving an organization something that is not for sale means creating a product to hold it, which the console presents as a private product. Earlier the model allowed a grant to name an entitlement set directly, with two grant paths and two operator forms; that was reversed when conferral was made uniform, the column was dropped and the two forms became one. The question keeps returning: should the products-only model stay, or should a set be grantable on its own again?

What depends on the answer

Whether the private product is the honest shape or a workaround with a friendly name, and how much of the wish for set-only grants is really a wish about authoring, since defining a set's rules while creating a product needs no change to the model and would remove most of the reason to want a grant without one.

Options known so far

Keep products-only: every grant names a real product, private products carry the ad-hoc cases, and the authoring flow is improved instead.
Restore the direct path, accepting two kinds of grant and the conferral history telling two stories.

Decided when

The entitlements model states which of the two is the model, and the console's grant form and its private-product presentation follow it.

Migrated from status/issues.md at b7a0e15

## The question Every grant names a product. Giving an organization something that is not for sale means creating a product to hold it, which the console presents as a private product. Earlier the model allowed a grant to name an entitlement set directly, with two grant paths and two operator forms; that was reversed when conferral was made uniform, the column was dropped and the two forms became one. The question keeps returning: should the products-only model stay, or should a set be grantable on its own again? ## What depends on the answer Whether the private product is the honest shape or a workaround with a friendly name, and how much of the wish for set-only grants is really a wish about authoring, since defining a set's rules while creating a product needs no change to the model and would remove most of the reason to want a grant without one. ## Options known so far - Keep products-only: every grant names a real product, private products carry the ad-hoc cases, and the authoring flow is improved instead. - Restore the direct path, accepting two kinds of grant and the conferral history telling two stories. ## Decided when The entitlements model states which of the two is the model, and the console's grant form and its private-product presentation follow it. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/entitlements area/catalog labels 2026-09-21 07:18:36 +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#123