The default comes back as a new grant each time, while a marked grant comes back as itself: two mechanisms for one idea #154

New Issue

2026-09-28T08:37:29Z

cgalo5758 commented

2026-09-28 08:37:29 +00:00

This is an exploration, not a decided change. It needs confirming before anything is written, because it gets at how the grants system is designed.

What exists

The default floor. When an organization's ladder is left vacant (a subscription ends, a grant is revoked or expires, an org-type migration runs), the console restores the org type's default by issuing a new grant with reason default (ReapplyDefaultsIfVacant). Every restoration adds another grant row. The earlier default grants stay in the ledger, replaced.
Resumption (in specification). An operator marks a grant "Resumes when the plan that replaced it ends". When that plan ends, the same grant row delivers again. No grant is issued.

Where the two meet

Both answer the same question: what does an organization receive when the plan on its ladder ends? And they get in each other's way:

A default grant cannot be marked. The floor would compete with the mark for the same rung.
A marked grant of the default product never delivers while the default holds that rung. So it is never replaced, and its mark never matters.

The idea to explore

Treat an org type's default as a standing grant that always resumes:

issued once per organization;
replaced whole by a plan that is bought or granted over it;
delivering again when that plan ends, like any marked grant.

The floor would stop issuing grants, the mark would be the one mechanism, and a default would be a grant that resumes by nature.

Questions it raises

How a change of the org type's default reaches organizations whose default grant is standing. Today the migration ends default positions and issues new grants.
What an operator's revoke of a default grant would mean.
The ledger: one default grant per organization, instead of one per restoration.
The rule that a default grant is authored by the system, not by an operator.
Organizations created before such a change, and their accumulated default grants.
Whether the floor does jobs the mark could not, for example refilling a ladder after a tier is removed.

Related: #153 (a default ladder whose lowest rung confers nothing makes every restoration fail).

This is an exploration, not a decided change. It needs confirming before anything is written, because it gets at how the grants system is designed. ## What exists - **The default floor.** When an organization's ladder is left vacant (a subscription ends, a grant is revoked or expires, an org-type migration runs), the console restores the org type's default by issuing a new grant with reason `default` (`ReapplyDefaultsIfVacant`). Every restoration adds another grant row. The earlier default grants stay in the ledger, replaced. - **Resumption** (in specification). An operator marks a grant "Resumes when the plan that replaced it ends". When that plan ends, the same grant row delivers again. No grant is issued. ## Where the two meet Both answer the same question: what does an organization receive when the plan on its ladder ends? And they get in each other's way: - A default grant cannot be marked. The floor would compete with the mark for the same rung. - A marked grant of the default product never delivers while the default holds that rung. So it is never replaced, and its mark never matters. ## The idea to explore Treat an org type's default as a standing grant that always resumes: - issued once per organization; - replaced whole by a plan that is bought or granted over it; - delivering again when that plan ends, like any marked grant. The floor would stop issuing grants, the mark would be the one mechanism, and a default would be a grant that resumes by nature. ## Questions it raises - How a change of the org type's default reaches organizations whose default grant is standing. Today the migration ends default positions and issues new grants. - What an operator's revoke of a default grant would mean. - The ledger: one default grant per organization, instead of one per restoration. - The rule that a default grant is authored by the system, not by an operator. - Organizations created before such a change, and their accumulated default grants. - Whether the floor does jobs the mark could not, for example refilling a ladder after a tier is removed. Related: #153 (a default ladder whose lowest rung confers nothing makes every restoration fail).

cgalo5758 added the

kind

design

area/entitlements labels 2026-09-28 08:37:29 +00:00

cgalo5758 commented

2026-09-28 21:02:47 +00:00

Resumed grants make one question here concrete. Today the default returns only when an organization holds nothing on any ladder. So a marked grant that resumes on one ladder keeps the default off the others: an organization whose resumed Plus sits on "Wiki plans" gets nothing back on "Forum plans". Resuming a grant keeps that rule and leaves the floor untouched. Whether the default belongs per ladder is part of this exploration.

cgalo5758 referenced this issue

2026-09-28 21:03:06 +00:00

A retired product can return only to the exact row that delivered it, so each new way of writing grant rows needs its own exception #155

cgalo5758 referenced this issue

2026-10-06 21:25:01 +00:00

Ending a plan's delivery runs the same four steps in three places, with the pool locked at different points #180

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#154