What is it?
A publicly accessible collection of browser games, creative experiments, guides, video and community-related features.
Why was it created?
Give people an accessible place to explore finished public artifacts without exposing the private UNITIQX workbench or server.
Who is it for?
- Visitors looking for interactive projects
- Game players
- Creative learners
- Users exploring community ideas
How to use it
- Open Commons.
- Choose a browser experience from the public project cards.
- Use its in-page instructions; for narrated content enable captions or read its transcript.
- If using community features, follow the published guidelines and submission rules.
Available controls or interactions
Public HTML/JS demos and documented community interactions; read-only AI should stick to approved GET resources.
How do you know you succeeded?
Visitor can open a public experience and use its demonstrated features. Community submissions and moderation have separate conditions.
What should you see?
Playable or interactive browser content, published guides and videos.
Play it through your mind
Look at a project card and predict who benefits, which feature to test first and what evidence would establish it works.
You want to evaluate a browser game before sharing it. What do you check first?
Suggested thought move: Define expected controls, win conditions and error states; try a normal session and a failure case.
Reveal the reasoned answer (spoiler)
A supported claim needs a reproducible test result, not just an attractive screenshot.
Illustrative QA planning scenario.
For read-only AI clients
Read public project listings, guidelines, documentation and safe GET content. No server-side authoring or private project access.
Public GET/HEAD resources:
AI responses must distinguish proposed actions and local reasoning from actually executed browser actions; no owner credentials or private APIs are provided.
Errors, limits and privacy
If it fails
Some experiments may be prototypes. If a demo fails, return to the public directory and select another.
Data handling
Public content is intentionally separate from credentials, protected queues and production deployment approval.
Known limitations
- Not every prototype has production-grade feature coverage.
- No public administrative access or arbitrary code execution is granted.
- Community participation may require separate validation and moderation.