Open for submissions

Every name in Rulealize, and who owns it.

Which plugin provides an operation, which namespaces and shorthand characters are spoken for, and which published rule sets a uses can name — read out of the packages themselves, and checked again every day.

/

Try

You arrive holding

seq.any

The index answers

Kind	`expression`
Plugin	`Rulealize.Plugin.Sequence`
Namespace	`seq`
In versions	`1.2.0 – 1.5.0`
Shorthand	none

$ dotnet add package Rulealize.Plugin.Sequence

18plugins admitted

103operations indexed

15rule sets published

2026-11-01 11:01 UTCcatalogue last read from nuget.org

Namespaces

18 namespaces, one owner each

A namespace has exactly one owner across the whole ecosystem, and the runtime refuses two plugins that claim one. That check runs when somebody assembles a plugin folder — after both were published — so this is the only place a collision can be seen before it costs anything.

Reserved by the registry, not grantable: fmtsettime

Shorthand

One keystroke wide, and recorded rather than owned

In use: # (def), $ (state), @ (bind). A string beginning with one is handed to that plugin's expander instead of being read as text, so the supply is one keystroke wide and cannot be extended — letters, digits and anything ordinary data might begin with are unusable. Under a dozen exist for the entire future of the ecosystem, and none of them is taken: a character is recorded here and granted to nobody, so a plugin may reserve one another plugin already reserved. The two load together, and a rule set that would otherwise be ambiguous names the vocabulary it meant — "$state:board".

What is refused, and the two things worth knowing first →

In use

Refused — ordinary data begins with these

Rule sets

Published rule sets a `uses` can name

A rule set's uses names the documents it holds, by the identifier each one declares. That identifier is the package identifier, so nothing has to resolve one to the other — these are the documents that exist, what each of them holds, and what it would cost to hold one.

How a name gets in

One form, and nothing in it is believed

A submission names a package and a version — and for a plugin, the two names it claims. Everything else is read out of the package, and nobody has to approve it.

01Fill in the formPackage, version, and for a plugin its namespace and shorthand — checked against nuget.org as you type.
```
package    Acme.Plugin.Dice
version    1.0.0
namespace  dice
```
02Send it from GitHubThe form opens your submission on GitHub, filled in; one click sends it. The registry loads the package and refuses anything it contradicts.
```
✓ namespace  dice
✓ prefix     none
✓ version    1.0.0
```
03Every release, indexed dailyNew versions need no new submission. One that renames itself is withheld and marked — never silently indexed.
```
1.1.0  indexed
1.2.0  withheld · claims dice2
```

Submit a package → How to build a package Read the grant policy

Kept, not just served

Every page says when it was last true

The catalogue is rebuilt from nuget.org every day. An index nobody keeps looks exactly like one that is kept — so the time of the last read is on every page, and a release that renamed itself is shown, marked, rather than quietly dropped.

Last run

2026-11-01 11:01 UTC

✓ 18 plugins read back from their assemblies
✓ 15 rule sets read back from their documents
✓ every release checked against the ledger
· 0 releases withheld