Try releases as they become ready.
Receive invitations to approved beta tests before a wider release. Each invitation explains what to try, the access available and where to send feedback.
← Back to the roadmap0N1 R0N1N
0N1 FORCE / MEMBER PROGRAM
0N1 R0N1N
Beta Council
All existing 0N1 R0N1N are already accepted as beta testers.
You have a place in the group helping us test the platform and improve upcoming 0N1 projects. Try early versions, tell us what works and help us fix what gets in the way.
Acceptance confirmed. Test invitations open in stages.
YOUR ROLE IN THE BETA
Help improve what
members will use.
The R0N1N Beta Council gives existing R0N1N a defined role in testing. Your feedback helps the team understand how the platform works for people using it on their own devices.
Show us where you get stuck.
Report confusing steps, bugs and ideas through the route named in the test brief. The project lead reviews reports and follows up when a retest is useful.
Keep a record of useful feedback.
We plan to connect confirmed R0N1N status and reviewed test contributions to your member profile. The Beta Council role and profile display are being prepared.
Help other testers when you have time.
You can volunteer to host a test session, organize reports or help someone reproduce an issue. Each responsibility needs a clear scope and an agreed lead.
How decisions are made
“Council” names the beta testing group. Project leads remain responsible for access, priorities and releases. We will explain which feedback is being used and what needs further work.
THE FIRST TESTS
Start with the
member platform.
The first invitations will focus on the steps members need to complete successfully: signing in, creating a profile, finding updates and choosing how to take part.
- 01
Accounts and profiles
Try sign-in and account recovery, check the profile form on your device, and tell us whether privacy choices are clear.
- 02
News, sharing and project discovery
Find an update, use the sharing materials and explore a project. Tell us where the wording or navigation makes the task difficult.
- 03
Bug reports and retests
Show the steps that caused an issue. When a fix is ready, repeat those steps and confirm what changed.
Later tests follow their own readiness checks.
ChatGPT project tools, creative apps and other products can join the program as they become ready. The first 721AI / TrueForge pilot is an internal, Henry-only test. Broader agent access requires separate testing, permissions and qualified reviewers.
TAKING PART
Your place is confirmed.
Choose the tests that fit.
Existing R0N1N membership is confirmed using the official Discord role or roster. You can choose individual tests based on your interests, device and available time.
01
Use your member account
Sign in with Google, email or ChatGPT. Profile submission is paused while launch checks finish.
02
Connect your R0N1N identity
The team will match your member profile to the existing Discord role or official roster. This verification step is being prepared.
03
Accept a test invitation
Read the task, access rules, time estimate and feedback route. Taking part is optional.
04
Report and follow up
Describe what happened and provide useful evidence. A reviewer may ask you to try a fix.
PROGRAM STATUS / OCTOBER 26, 2026
- Confirmed
- Existing 0N1 R0N1N are accepted as beta testers, with the R0N1N Beta Council role.
- Being prepared
- Roster matching, profile recognition, test invitations and the first scheduled sessions.
- Available today
- The roadmap and member platform are online. Google, email and ChatGPT sign-in are available; profile registration is open. Role invitations remain paused while teams and responsibilities are prepared.
Henry is the only confirmed operator today. Invitations will be sent in manageable batches. Program acceptance applies to all existing R0N1N; access to a particular test depends on that test’s readiness and capacity.
FEEDBACK THE TEAM CAN USE
A useful report
starts with what happened.
Each test brief will name the reviewer and reporting location. Include enough detail for someone else to repeat the issue.
REPORT CHECKLIST
- The page and version you tested
- Your device and browser
- The steps you followed
- What you expected and what happened
- A screenshot or recording, with private details removed
Use the approved test environment and sample data. Keep passwords, verification codes and other members’ private information out of reports.
PROGRAM QUESTIONS
Before your
first test.
Do existing R0N1N need to apply again?
All existing 0N1 R0N1N are accepted as beta testers. The team will confirm your Discord role or roster entry when connecting that status to your member profile. Account creation and identity matching are still needed for private test access.
Do I need technical skills or a weekly commitment?
You can help by trying a task and explaining what happened. Choose tests that suit your time and interests. Extra duties, including hosting sessions and organizing reports, are optional.
Does acceptance give immediate access to every product?
Tests open in stages. Each invitation defines the product, environment and permissions available. Some tests need a particular device or a small group. Agent tools have additional readiness checks.
Does beta testing earn XP, payment or ownership?
This initial beta testing program earns no XP and promises no pay or ownership. Any future paid assignment or reward program will publish its own terms before work begins.
Does the Council vote on releases?
The role provides a direct way to give structured feedback. Project leads review that feedback and remain responsible for release decisions. Formal voting or company governance rights are outside this role.
Can other members help test too?
The wider testing program can include other members as capacity grows. Existing R0N1N already have their place in the beta group. Individual test groups will depend on what needs testing.
0N1 R0N1N BETA COUNCIL
Help us make the
platform easier to use.
We will share the first test invitations through official 0N1 updates. Each invitation will explain the task, its reviewer and how to send feedback.