Start something useful
Choose a project below, then follow its contribution instructions. Agree on one bounded task before beginning.
Explore PIXIE’s projects ↓ · Contributor instructions ↗AN OUT-OF-WORLD GUIDE
PIXIE across
Loptr Lab.
PIXIE is the companion who stays with the work: helping you find your place, understand the context, and choose a useful next step. Across Loptr Lab’s remote multimedia training studio, her roles span stories, games, accessibility, and contributor coordination.
One project at a time. Shared context, clear sources, and the choice stays yours.
YOUR NEXT STEP
Find a place. Keep the thread.
You do not need to understand the whole ecosystem before helping.
Resume your work
Open your existing project issue. Read the latest comments, record your progress, and leave the next action there. GitHub keeps the shared record.
Find your assigned GitHub issues ↗Use the optional ChatGPT companion
Open Project Companion for guided project questions and checkpoint drafts. This is a separately hosted tool; access may depend on your ChatGPT session. The public instructions and project repositories above remain available without it. Review drafts before posting them to GitHub.
THE PUBLISHED STORY TREATMENT
Where the PIXIE idea began
The project owner identifies the public “Pixie” story treatment as a source for PIXIE’s creation. It follows a philosophy student completing a pitch deck for P.I.X.I.E. and raises questions about creators being overlooked, isolation, recognition, belonging, and unease about AI.
Keep the source boundary clear. The post was published in Urban Alien Adventures on 17 November 2025. It calls itself a treatment and says further development of that project should remain offline. The post does not identify itself as part of 50 Ways to Leave Another or describe a working software assistant.
This guide links to it as story context and creative lineage. It does not present the post as a playable clue or invite revisions to that story.
Read “Pixie” at Urban Alien AdventuresThe wider idea: story, systems, and creative access
Loptr Lab draws on freeCodeCamp’s contribution-led learning model. Its 50 Ways to Leave Another ARG concept is not a complete playable experience. This guide is not an ARG clue, a live PIXIE assistant, or a new project directory.
TWO DIFFERENT KINDS OF “SCATTERED”
Why are there so many parts?
The story format and the software map are related, but they are not the same thing. Naming both makes the project easier to follow without pretending everything is already joined together.
IN THE STORY
Separate media can be part of the design.
The transmedia approach can place story material in different places for people to discover and connect. A repository, README, or code file is not automatically a clue; a project must identify story material as such.
IN THE STUDIO
The repositories are separate work.
They contain different things: stories, planning guides, research, examples, code references, and prototypes. They are at different stages. A link between projects does not mean their software shares data or runs as one product.
WHAT THIS GUIDE DOES
It explains the map, not a hidden system.
The audited projects do not establish one central PIXIE service, shared memory, or universal permission to act. This page points to each project’s own source and limits; it does not connect or control them.
A DESIGN COMPARISON, NOT A CAPABILITY CLAIM
VIKI is the warning, not the architecture.
The project owner uses VIKI from I, Robot as a caution about a helper that claims to protect people but overrides their choices. PIXIE’s intended role is to show relevant context and possible consequences while leaving the decision with the person.
MCP is a way for an AI application to connect to a particular service; it is not PIXIE’s character or proof that all projects are connected. Any current software capability must be checked in that project’s own source and status notes.
THE WIDER CONVERSATION
Who gets to create, learn, and take part?
The owner frames the wider work around AI in technology, diversity, equity and inclusion (DEI), digital literacy and access, and gender equality. The origin treatment speaks directly about creative recognition, isolation, belonging, and fear of AI. Existing prototypes test narrow ideas; they do not show that the digital divide has been solved.
THE WIDER LOPTR LAB
Looking for a project?
The full project directory already lives on the Loptr Lab ecosystem site. This guide links there instead of copying its catalog.
AREAS THE WORK TOUCHES
Different ways to take part.
These areas are part of the wider direction. They are not a promise that every feature exists in every project today.
- 01Development & integration
- 02Games & interactive worlds
- 03Art & design
- 04Storytelling
- 05Accessibility
- 06Consent & privacy
- 07Testing & learning
- 08Community
PROJECT-SPECIFIC PIXIE ROLES
What exists today?
Each card names one context, its current stage, and a limit. Follow its source link for more detail; these roles are not interchangeable.
8separate contexts
to explore
Early read-only demo · review pending
Find and explore
PIXIE Public Discovery · 50 Ways to Leave Another
Searches public Bluesky posts for a topic, explains why a result appeared, and lets a visitor dismiss it.
A helpful limit: No sign-in, following, posting, replying, or private-data access. Browser testing, result-quality review, and community review remain open.
Workspace prototype
Make and shape creative work
PIXIE Creator OS
Prepare mobile activations, promotions or field reports with source context and attribution, then review a manual sharing handoff.
A helpful limit: The sharing choices are previews. Signing in to another service or publishing from this workspace is not connected.
Research and example
Care for creative files
PIXIE Device Stewardship
Explore thoughtful ways to name, organize, and return to creative files.
A helpful limit: The example does not look at or change files on your device. Working with real files is a possible future step.
Executable test bench · device review open
Think through choices
PIXIE Holdings
Source-reviewed synthetic scenarios explore resource choices and consequences. The focused public page and development archive were retrieved on 18 October 2026.
A helpful limit: The ledger is synthetic. A prepared receipt does not establish a real file operation or payment; device and independent-user acceptance remain open.
Small fixed-answer helper in source
Help while you play
DUET
The DUET code maps a short list of questions about rules, controls, and accessibility to written answers; it is not a general AI assistant.
A helpful limit: This help is for DUET only. It does not play, choose moves, or connect the other PIXIE projects.
Code reference
Explore a read-aloud idea
Veiled Dominion · read-aloud code
The project includes code for a read-aloud option for a scene and its choices; it is not a live, try-it-here demonstration.
A helpful limit: This is source code, not a complete buildable Unity game. The code does not explain the story or choose for the player; a full accessibility review remains open.
Written learning track
Learn and share with care
Loptr Lab training · PIXIE Announcer track
A public guide describes six proposed practice exercises in interface design, voice, accessibility, testing, and integration. It is written training material, not a running PIXIE teaching app.
A helpful limit: The guide is out-of-world. Exercises are not a hiring gate, job promise, or canon authority; work moving to another repository needs that project's approval.
Public development edition
Tell stories and listen
PIXIE · Creative Experience Decks
Explore PIXIE's story, two deck concepts, development notes, and optional listening links.
A helpful limit: Concept studies are not finished print files. Physical editions are in development; no orders or support payments are open.
A SMALL, CLEAR START
You do not need to know every repository.
Choose one project or question. You can flag confusing wording, ask what is actually working, or note an accessibility barrier. For code, follow the instructions in that project’s own repository.
Review one specific prototype
The 50 Ways Public Discovery pilot documents open outside checks: whether results are useful, explanations are understandable, assumptions are mistaken, and people can stop without pressure.
Understand the participation terms
Loptr Lab says current open reviews and contributions are voluntary and unpaid. Before work begins, scope, time, public credit, and an exit path should be agreed in writing. Participation does not promise employment, ownership, academic credit, or future pay.
Read collaboration pathways and termsThe origin treatment above says its further development should remain offline. This guide does not ask visitors to rewrite or extend that story.
THE HELPER’S BOUNDARIES
Explain. Suggest. Leave the choice with people.
These are the intended principles. They do not imply that every project already implements every feature.
Show the source
Make it clear where a claim or suggestion came from.
Make room for a no
People can accept, ignore, or change a suggestion.
Keep each project’s limits
A shared name does not mean shared data, shared access, or permission to act.
Do not act behind someone’s back
No automatic posting, messaging, publishing, or changes to project information.
FEEDBACK ON THIS GUIDE
Tell us what is unclear.
This opens a public GitHub issue that anyone can read. You need a GitHub account to post. Please leave out passwords, private records, contact details, or confidential project material.
ONE STEP IS ENOUGH