Sign in
Identity here is Hugging Face's. This registry holds no password and has nothing to sign up for.
Three steps, and the middle one is the smallest
Hold a Hugging Face account
Most people publishing a steering direction already have one, because that is where the weights and the artifacts live. If you do not, Hugging Face registers it, not us.
Sign in with it
Hugging Face asks you whether to let this registry read who you are. If you agree, what comes back is an opaque subject id, the handle you hold at that moment, and, if you grant it, the organizations Hugging Face says you belong to. No password reaches this site, because none is ever sent here.
Sign in with Hugging Face That page sends you to Hugging Face and receives you back. It holds the reading in the tab and nowhere else, so closing the tab ends it. Signing in on its own writes no submission; that is a button further down that page.
Claim a namespace
This is the act with meaning. A claim binds the account to a namespace and is recorded with its date and its evidence, so a reader can weigh it. Everything published under a namespace stands whether or not anyone has claimed it, and a namespace nobody has claimed is the ordinary state rather than a gap.
More than one account can claim the same namespace. Both claims stand, both carry their own evidence, and this registry does not decide between them.
Your namespace is your handle, and there is no field for it
When you submit, the namespace is the handle Hugging Face reported when you signed in, and the database writes it from your session rather than from anything you typed. It is shown to you, not offered: no box, and no default to type over. Somebody signed in under one handle cannot publish under a name belonging to somebody else, and a dispute about who really holds a name is Hugging Face's to settle rather than ours.
What that makes impossible, stated because a rule that cannot name its cost has not been thought through: publishing under a pseudonym, under a lab name you hold no account for, or into one namespace shared by several people who each sign in as themselves. The last is a real shape, and today the answer is that a group claims a namespace rather than submits into one. An author string written down by somebody indexing published work is unaffected, and stays a free string.
A membership is something a provider said on a day
If Hugging Face reports your organizations, what gets recorded is what it said and when it said it. Nothing rechecks it afterwards, so nothing here will ever claim you belong to an organization now. People join and leave; a membership read once and held forever goes stale quietly while still looking like a fact. Checking again means signing in again, which writes a new observation beside the old one rather than replacing it.
Why Hugging Face
Because that is where the artifacts already are, and because it can answer the organization question, which a plain login cannot. It is the provider this was built against and not a list of permitted ones. A claim records the provider string it was made with and nothing anywhere compares that string against a set of approved names, so another provider is a configuration rather than a change to the schema.
A claim binds the provider's subject id and not the handle. Handles are renameable on every provider, so a claim bound to a handle would either break when somebody renames or follow the name to whoever registers it next. The handle is recorded as of the claim date, and is not what anything looks up by.
What is missing, in one sentence
A way in for somebody who is not on Hugging Face, and a way to correct a submission that is not another submission. What a submission does not wait for is a person's opinion of it: it lands, and it appears on the site when the author rebuilds and publishes, because the corpus is a file in git and that is what the falsifier checks. What this registry is and where it came from.