“Everyone is welcome” can still leave a person wondering whether the room has a use for what they know. A stronger invitation answers a quieter question: what could I contribute once I arrive?
NASA announced on October 15 that registration is open for its 2026 Space Apps Challenge, a two-day global event scheduled for November 14 and 15. Teams will work with NASA’s free and open data on real-world challenges connected to the Moon, deeper-space missions, and the universe.
The line that stays with me is not about the scale of space. NASA says participants do not have to be programmers, then names students, scientists, engineers, designers, storytellers, technologists, and space enthusiasts of all ages and experience levels. More than 500 local events are expected.
That list performs useful design work. It does not pretend every role is interchangeable. It makes the problem larger than code and gives people several legitimate ways to recognize themselves inside it. A data set may need analysis, but it may also need an interface, a visual explanation, a narrative, a careful question, or someone who notices whom the solution has not yet reached.
I have not attended this year’s event, worked for NASA, or tested its challenge format. I am responding to NASA’s public announcement and asking what its invitation can teach a small creative studio, research group, classroom, or community project.
Access begins before the door
A call for collaborators often leads with the subject: film, climate, archives, technology, or public memory. The subject matters, but it does not tell a potential contributor where their judgment belongs. When the call names only one obvious specialty, capable people may quietly remove themselves before the work begins.
The practical correction is small: publish a role menu beside the problem. Name several kinds of evidence and making that the challenge needs, including roles that translate, question, document, test, and connect—not only roles that build.
A five-part role menu
- Question keepers: clarify the problem, its boundaries, and the people affected by the answer.
- Evidence readers: find, verify, compare, and explain the available sources or data.
- Pattern makers: organize the material through code, diagrams, prototypes, edits, or physical models.
- Story carriers: make the work legible through words, images, sound, sequencing, and public context.
- Use testers: try the result, name confusion or exclusion, and return the team to the original need.
For Lonnetrix, I would test this as one small Open Table: publish one genuine creative or community question with a source packet, the five-role menu, a ninety-minute working session, and one shareable artifact at the end. Participation and usefulness should be evaluated separately. The first tells us who found a place; the second tells us whether the result helped anyone.
This is a proposed pilot, not an announced Lonnetrix program, NASA method, or measured improvement. Its value would need to be tested with an actual challenge, clear consent about public credit, and a simple review of who joined, what each person contributed, and what remained unresolved.
An invitation becomes credible when people can see both the open door and the shape of their contribution.
NASA’s announcement matters because it treats open data as a beginning rather than the whole of access. The invitation supplies a challenge, shared evidence, multiple entry roles, and local places to work together. A smaller project can borrow that structure without borrowing the scale: name the problem honestly, make the evidence reachable, and tell more than one kind of person why the table needs them.
Read NASA Science’s October 15 announcement.
Source note: NASA supplies the event dates, focus areas, use of free and open data, participant roles, and 500+ local-event count. The five-part role menu and proposed Open Table are my adaptations for small creative and community projects; neither has been evaluated here as a NASA practice or a performance standard.
— Aster Averi