Workbench
Exocore platform
A public pre-alpha orientation shell and the beginning of a local-first cognitive workbench.
Inspect the public record ↗Scott Rallya, still learning how to do the work.
Independent researcher and systems builder, working across cognitive architecture, AI, knowledge systems, creative practice, and a self-directed research life serious enough to earn scrutiny and alive enough to sustain curiosity.
FoundationB.S. Computer Science + Psychology, RPI, 2007
PracticeSelf-directed research, systems building, and public work
Current statusGrowing a research practice and early product exploration
The degree says Computer Science and Psychology, and it is true that those subjects have been tangled together for me for a long time, but the more important part of the record is what came after: graduate attempts in Game Design and Data Science & Machine Learning, quiet exits, a long search for a way of learning that could keep research, systems, play, and the slow work of making something in contact with one another.
I learned from formal programs, and I also learned that the usual containers did not give me a durable home for the work I wanted to do. This site is part of the response. Working with AI lets me set more of the middle down, inspect it, argue with it, and keep moving long enough to see whether an idea can become something real.
The throughline
Following the connection between mind and machine, even when the route is not tidy.
What carries forward
Cross-domain thinking.
Computer science and psychology were never separate interests. Together they became a way of asking how people reason, what systems make possible, and why an interface can be the difference between knowing something and being able to do anything with it.
What remains visible
The rough edges.
I can get absorbed by a question, see four more questions inside it, and then discover that I have built a useful piece of infrastructure before I have returned to the thing that started the whole detour. The route here includes stalled work and interrupted plans. They are part of the context for why returnability matters so much in the design.
Current practice
What the work looks like from the inside.
- 01 / NoticeKeep the questions that have heat. Research questions, technical problems, sound, learning design, and philosophical questions often arrive together here. I try to see the connection before forcing them into separate boxes.
- 02 / BuildMake something real before defending it. A small shell, a public artifact, a working note, or a method record gives a question somewhere to stand while it is still being tested.
- 03 / ReturnLeave a trail for the future version of me. The practice keeps asking how a person can recover the state of a difficult project after time, friction, or a change in capacity has broken the flow.
- 04 / CorrectLet the work push back. AI can help shape, retrieve, question, and draft. I keep the responsibility to accept, reject, and revise, especially when an easy answer feels too neat.
Selected evidence
A few places to inspect the work directly.
Research record
Field Journal
Reviewed public notes on the work as it changes. Read the record in time, or use the Field Map to follow the connections between notes.
Creative work
Exocore music
A separate creative thread where AI collaboration, sound design, and the larger storyworld meet.
Inspect the public record ↗“I want to grow into the kind of researcher who can follow a question all the way down, make something from what I learn, and leave enough of the trail for someone else to inspect.”
Shaped from Scott’s authoring materialRecognition, if it comes, has to come after a thoughtful reader can see the ambition, the work ethic, the gaps, and the evidence that exists today. This file gives the work somewhere to be met on its own terms.