STARHOUND STUDIO / ABOUT
BUILD THE
STRANGE THING.
Starhound Studio is an independent cross-disciplinary studio working across games, fiction, music, and experimental machines.
There isn't a five-year content strategy. There isn't a genre mandate. There isn't a committee deciding whether something fits the brand.
If an idea is interesting enough to become real, we build it.
STUDIO PRACTICE / 01
DIFFERENT MEDIUMS.
SAME IMPULSE.
GAMES
Systems you can inhabit.
FICTION
Worlds that refuse to stay on the page.
MUSIC
Noise with a reason for existing.
EXPERIMENTAL MACHINES
Things we’re not entirely sure what to call yet.
STUDIO PRACTICE / 02
THE WORK
DECIDES THE
MEDIUM.
Starhound doesn't begin with a product category. It begins with a problem, an idea, or something interesting enough that it refuses to leave us alone.
Sometimes that becomes a game. Sometimes a story. Sometimes a record. Sometimes a machine. Sometimes it becomes all four before anyone has the good sense to stop it.
The medium is a consequence of the thing being built.
STUDIO PRACTICE / 03
BUILT FROM
SCRATCH.
Not because everything needs reinventing. Because sometimes the thing we need doesn't exist yet.
Starhound works across disciplines where the boundary between making the work and making the tools for the work tends to disappear.
We don't build from scratch for purity.
We build from scratch when the available assumptions are the problem.
A game may require a new system.
A story may become a world.
A musical idea may become a production experiment.
A computational question may require an architecture built just to ask it properly.
We use existing tools when they fit. We build our own when they don't.
The tool is not the work. But sometimes building the tool is how you discover what the work actually is.
SOFTWARE · SYSTEMS · PROTOTYPES · WORLDS · BAD IDEAS THAT SURVIVED TESTING
STUDIO PRACTICE / 04
FAILURE
IS DATA.
If something only works when nobody tries to break it, it doesn't work.
Starhound treats failure as information.
A prototype that collapses tells us something.
An experiment that contradicts the hypothesis tells us something.
A mechanic that isn't fun tells us something.
A story that refuses its outline tells us something.
The useful question isn't whether an idea failed.
It's what the failure eliminated.
That means testing assumptions, preserving ugly results, attacking things that appear to work, and being willing to throw away an explanation when the evidence stops supporting it.
Success tells you that something survived.
Failure can tell you why.
TEST · BREAK · MEASURE · REVISE · REPEAT
STUDIO PRACTICE / 05
FOLLOW IT
TOO FAR.
The interesting part usually starts after the sensible stopping point.
Starhound projects have a habit of escaping their original boundaries.
A small game acquires a world.
A story develops machinery outside the story.
A song becomes a character, a record, or an entire fictional band.
An experiment asks a question that requires three more experiments to answer.
We don't treat that as scope creep by default.
Sometimes the detour is the project.
There is a difference between adding things because you haven't made a decision and following an idea because it keeps producing consequences.
One is avoidance.
The other is discovery.
Starhound makes room for the second.
FOLLOW · CONNECT · ESCALATE · DISCOVER
STUDIO PRACTICE / 06
THE HUMAN
PROBLEM.
One human. Too many projects.
Starhound is a solo studio.
There isn't a game department, a music department, a research team, or somebody down the hall whose job is to keep any of this sensible.
There's one person moving between them.
That creates an obvious problem:
There is always more work than human.
Projects wait. Ideas accumulate. Some things move quickly. Others sit untouched until the right piece finally clicks into place.
The answer isn't pretending the constraint doesn't exist.
It's choosing what gets attention, letting projects breathe when they need to, and accepting that independent work sometimes moves at the speed of one person having one pair of hands.
The limitation is real.
So is the work.
ONE HUMAN · MANY PROJECTS · QUESTIONABLE SCHEDULING
STUDIO PRACTICE / 07
MAKE THE
STRANGE THING.
The medium changes. The standard doesn't.
Starhound doesn't have a house genre.
A tower-defense game about militarized dachshunds can sit beside a piece of gothic fiction, a record, an experimental machine, or something that doesn't have a useful category yet.
They don't need to look alike.
They need to have a reason to exist.
Strange isn't the objective.
Specific is.
The work should have enough of an idea behind it that changing the medium doesn't make the idea disappear.
Sometimes that means funny.
Sometimes unsettling.
Sometimes beautiful.
Sometimes technically absurd.
Sometimes all four before lunch.
The question isn't whether something fits the studio.
The question is whether there's something there worth following.
And when there is—
we make the strange thing.
SPECIFIC · CURIOUS · UNNECESSARILY COMMITTED
PERSONNEL FILE / 01
THE PERSON
RESPONSIBLE.
Apparently, all of this is one person's fault.
Starhound Studio is the work of Matilda Sparks.
There is no creative department, engineering department, writing room, music division, research group, or deeply concerned project manager.
There is one person moving between code, games, fiction, music, visual work, experimental systems, and whatever problem has become interesting enough to derail the original plan.
That arrangement is occasionally inefficient.
It is also the point.
The same person who writes the story can build the system it needs.
The same person who designs the game can make its propaganda.
A musical idea can become a fictional band.
A technical question can become an experiment.
And discoveries in one discipline have an inconvenient habit of appearing in another.
The boundaries stay deliberately porous.
Starhound isn't multidisciplinary because it collects disciplines.
It's multidisciplinary because the work keeps crossing the lines between them.
No committee is required for this process.
There isn't one.
DESIGN · CODE · FICTION · MUSIC · EXPERIMENTS · POOR SCOPE CONTROL
PERSONNEL FILE / 02
NO FORMAL
DEPARTMENT.
Most of the job titles were assigned retroactively.
Starhound's organizational structure is less a hierarchy than a list of things that eventually needed doing.
So far, this has produced the following departments:
DESIGN
Games, systems, mechanics, interfaces, visual language, and ideas that seemed much smaller when they were written down.
ENGINEERING
Software, prototypes, computational architecture, custom tooling, and occasionally building the thing required to build the other thing.
WRITING
Fiction, worlds, dialogue, articles, documentation, and suspicious quantities of lore.
MUSIC
Songwriting, production, recording, fictional bands, real bands, and noises with paperwork.
ART DIRECTION
Characters, covers, identities, propaganda, visual systems, and making unrelated things look like they were part of the plan.
RESEARCH & EXPERIMENTS
Questions that became prototypes, prototypes that became experiments, and experiments that generated considerably more questions.
There are no departmental meetings.
This is primarily because:
CURRENT
STAFFING LEVEL:
1
Cross-department communication remains excellent.
DESIGN · ENGINEERING · WRITING · MUSIC · ART · RESEARCH