Registries
Who runs PRE-GEN today. Registries and AI services are listed here so they can find each other.
Status
| Today | |
|---|---|
| Registry in production | Yes: PRAMPTA |
| Open reference registry | Yes: pregen-registry, Apache-2.0, with a sandbox |
| Signed directory | Yes: registries.json, signed by the steward key; verifiers load it again at least every 24 hours |
| Public test network | Yes: test directory and the test registry at sandbox.pregen.org (codes TOG-TEST-000001N to TOG-TEST-0000123: refusals, a test purchase, a person's terms, a minor, a creator's licence through bind; what each tests) |
| PRAMPTA answers apps by their domain, no account | Yes |
| Second registry | None yet |
| Independent implementation passing the tests | None yet. Build one |
| Revoked registries or keys | None |
| Same person in two registries | The claim the person confirmed on their own channel decides; with none confirmed, the result is not_blocked, which permits nothing (identity) |
| Proof carried with the output | Specified (proof); not yet tested end to end with a platform |
Registries
A registry represents people and works, issues licences and signs answers.
| Name | Role | Prefix | API | Status | Since |
|---|---|---|---|---|---|
| PRAMPTA | First registry | PRAM (listed 2026-10-14); bare codes issued before v5, closed | https://api2.prampta.com | Production | 2026 |
AI services
Services that ask a listed registry before they generate.
| Name | Registry | Status |
|---|---|---|
| None yet. A service appears here once it has made a real request and report with a listed registry. | ||
Getting listed
The directory is what keeps fake registries out: verification accepts a registry's signatures only for the prefix the signed directory gives it. A listing says the registry met the conditions below. It does not certify that everyone the registry represents is genuine. That stays the registry's responsibility.
Registries open a registry application and receive a prefix for their ToG codes. Bring:
- a named operator, a company or a person, with a public address and a contact for complaints;
- a published policy: how you check that someone is who they say and may license the subject, your own refusal rules, answer lifetime, opt-out waiting period, and a public identifier (Wikidata, ISNI or a domain) for every public person you register;
- acceptance of the core rules: the protections no licence can override, the rule for a person held by several registries, and an answer to every complaint within seven days;
- a public API following the core (
POST /v2/requests), a key set at/keysand a document at/.well-known/pregen-registry.json; your key fingerprints given to the steward directly, and your next key announced; - open access for AI services: answer any AI app known by its domain, with no account, on the same terms for all (provider-identity). You may also issue your own credentials, and you may check an app before you answer it fully. Registries listed earlier have 90 days from this rule's publication;
- a passing run of the published test vectors and schemas.
AI services are listed by the registry they work with, after a real request and matching report.
Revocation
The steward can remove a registry that licenses people or works it has no right to, ignores proven complaints, breaks the core rules, or is compromised. A removed registry stays in the directory forever, its prefix is never reused, and nothing signed by its keys permits a generation again. A single stolen key can be removed the same way while the registry keeps its other keys. A removal is never undone, and each one is announced here with its reason. Verifiers see it the next time they load a current directory, at least daily.
Working together
Every code belongs to exactly one registry. Each registry issues codes under its own prefix, so codes never collide. Bare codes issued before version 5 (now written TOG-000042*) keep their meaning; no registry issues new ones. A registry asked about another registry's code points here.
- Who proved it, not who came first. When several registries claim the same public person, a claim the person confirmed on their own official channel wins. Among claims the person confirmed on their own official channel, a refusal of the person in any registry holds in all of them. With no confirmed claim PRE-GEN says nothing: the result is
not_blocked(PG_IDENTITY_UNCONFIRMED), which permits nothing and refuses nothing. An impostor can neither permit nor freeze a person. A matching name is never evidence. - Complaints. A registry answers within seven days: a first response and protective steps such as a freeze, not necessarily a final decision. The steward can record a proven false claim in the directory. Repeated false claims are grounds for removal.
- No middleman. AI services and registries talk directly. Services that make it easier are optional and open to anyone.
Not yet specified: settlement between registries, and profiles for works and characters.