Nothing in the console edits the rules that decide which subdomains may be carved #71

New Issue

2026-09-21T07:18:21Z

cgalo5758 commented

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

The question

The registry holds a table of name rules that decides which subdomains a member may carve under the operator's shared domain. It is filled by the seed and by migrations; no operator page reads or writes it, and leaving it out of the console was recorded as a deliberate non-goal. An operator who wants to reserve a word, or release one that was reserved, has to reach the database. Is the table operator-owned, and therefore owed a surface, or is it deployment configuration that only ever changes with a migration?

What depends on the answer

Whether the domains area gains another editing surface and the review that comes with one, and whether a deployment can adjust its own reserved words without a release.

Options known so far

Declare the table seed-only, say so where the carve rules are described, and keep it out of the console.
Give it a small operator surface with the same list treatment the other domains tables use.
Move the reserved words into instance settings, where deployment-wide values are being gathered anyway.

Decided when

The domains model says who owns the name rules and how they change, and the recorded non-goal is either lifted or restated as the decision.

Migrated from status/issues.md at b7a0e15

## The question The registry holds a table of name rules that decides which subdomains a member may carve under the operator's shared domain. It is filled by the seed and by migrations; no operator page reads or writes it, and leaving it out of the console was recorded as a deliberate non-goal. An operator who wants to reserve a word, or release one that was reserved, has to reach the database. Is the table operator-owned, and therefore owed a surface, or is it deployment configuration that only ever changes with a migration? ## What depends on the answer Whether the domains area gains another editing surface and the review that comes with one, and whether a deployment can adjust its own reserved words without a release. ## Options known so far - Declare the table seed-only, say so where the carve rules are described, and keep it out of the console. - Give it a small operator surface with the same list treatment the other domains tables use. - Move the reserved words into instance settings, where deployment-wide values are being gathered anyway. ## Decided when The domains model says who owns the name rules and how they change, and the recorded non-goal is either lifted or restated as the decision. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/domains area/operator-ui labels 2026-09-21 07:18:21 +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#71