Trial Network
The trial network is the public learning path for community node participation. It helps prospective operators understand what it means to apply for Registrar or Discovery roles, prepare identity and domain material, request lifecycle changes, and distinguish application records from runtime authorization.
It should pair well with community skill workflows, but it should remain separate from private official operations. Public applicants need clarity. Official operators need private deployment automation elsewhere.
This separation keeps the trial network approachable. A prospective operator should learn how to prepare an application and understand governance states. They should not need access to private deployment credentials or official runbooks just to understand participation.
What the Trial Network Is For
The trial network helps answer:
- What information should a prospective node operator prepare?
- What is the difference between a Registrar and a Discovery node?
- How should authorized domains be requested?
- How are lifecycle changes such as suspension, recovery, or revocation represented?
- What public material helps governance review?
- How does a community participant learn without running official infrastructure?
The trial network is not a shortcut around governance. It is a structured path toward governed participation.
It is also a feedback loop for the ecosystem. Trial applicants reveal which fields are hard to understand, which domain choices are unclear, which status labels are ambiguous, and what tooling would make real operation easier.
Application Material
A useful node application should include:
| Field | Purpose |
|---|---|
| Operator identity | Identifies the applicant or organization. |
| Node DID | Identifies the infrastructure subject. |
| Requested role | Registrar, Discovery, or later role. |
| Public endpoint | Shows where the service will be reachable. |
| Authorized domains | Defines requested operating scope. |
| Operational notes | Explains reliability, monitoring, and maintenance expectations. |
| Contact and lifecycle process | Makes future changes manageable. |
Templates and examples should make these fields easy to prepare.
A good template should be specific enough for review but not so heavy that it discourages serious applicants. It should ask for the evidence needed to evaluate role, scope, endpoint, identity, and operational readiness.
Recognition Is Not Authorization
A repository entry, pull request, issue, or application record does not automatically make a node authorized at runtime. The runtime trust path depends on governance state, Root recognition, and service enforcement. This distinction protects both users and operators.
The trial network should therefore explain status carefully. “Applied” is not “active.” “Recognized” is not always “authorized.” “Endpoint online” is not “governance-current.”
This precision protects applicants too. A node can be publicly preparing before it is active. A temporary outage does not necessarily mean authorization is lost. A governance suspension does mean the node should stop being treated as authoritative even if the endpoint still answers.
Domains in Trial Participation
Authorized domains are central to trial participation. Operators should request domains deliberately and explain why the scope fits their role. A domain-specific Discovery node does not need all-domain authority. A specialized Registrar should not request wildcard scope without a strong reason.
This lets the ecosystem test realistic delegated authority instead of approving every trial node for everything.
Domain-scoped trials are especially valuable for proving the model. They let the ecosystem see whether a Registrar rejects out-of-scope registration, whether Discovery hides out-of-scope resources, and whether users can understand those outcomes.
How Community Skills Can Help
The community skill can help applicants prepare application material, understand domain choices, and test resource registration or Discovery against official or configured nodes. It should not perform official governance actions or private deployment. Its value is making public participation easier.
Over time, the trial network can become a bridge from public interest to serious operation: read the Docs, prepare an application, register test resources, verify Discovery behavior, understand governance status, and then pursue formal authorization when ready.