# RCC-2026-0003: Authorize Public Testing of the Renasca MVP Candidate

Outcome: **PASSED**

I propose that the Renasca MVP candidate enter an organized public testing period.

The current system allows clan representatives to sign in through Discord, import a clan using its Roblox group URL, select public group experiences, and submit a proposed listing for staff review. Approved clans can appear as planets in the Renasca hub with multiple curated locations. Players can search for those clans and travel to approved destinations through server-controlled teleportation.

The website, governance system, clan importer, production registry, registry cache, staff review process, Roblox hub, and secure destination selection are now functioning. Initial technical testing has been completed, but broader use is necessary to identify usability problems, incomplete metadata, unusual clan structures, teleport failures, moderation concerns, and other issues that cannot be fully reproduced internally.

During this period, Renasca may invite interested clans from the greater clanning community to submit listings and test the experience. Participation will remain voluntary. Every submission will continue to require staff review and deliberate registry publication. Unapproved destinations cannot be supplied directly to the hub.

This testing period does not represent a final release or a guarantee of software verification, anti-cheat certification, combat certification, or capturability. Locations may be publicly listed and joinable while displaying an unverified software status. Those certifications will remain separate systems with their own standards.

Feedback, failures, security concerns, duplicate submissions, suspended locations, registry caching, and cross-experience travel should be documented throughout the pilot. Material problems may result in individual listings or the public test being temporarily suspended while corrections are made.

After a representative testing period, the council should receive a summary of participation, significant findings, unresolved risks, and recommended changes before Renasca is presented as fully launched.

---

Published: 2026-08-06T23:08:17.762Z

Payload SHA-256: `2e79440fff703dd7978fdd89de30db9b0977eaf64bbb6230d73208f8aaf4edce`

Signing key: `renasca-records-2026-01`

Signature: `8odd3YMhumCBESuKZIoLqMMLe4kTdbii93ELpffqujitqhTlDlj5d2Ceh3UBFA3NhsSNXQi8Pr9C17fwuno4Bg`