- Toolkit configuration for your room and your hardware
- Facilitator training — a half-day makes a staff member confident to run a session
- Workshop scripts and a public-showcase format
- Consent and privacy templates, written for a board and a parent to read
- The measurement kit, and support running it
- A Replication Pack you keep — so you can run it again without us in the room
A program you can run,
and prove you ran.
Performia is best understood not as an app but as a program: movement- and-music sessions your community can take part in, with the measurement designed into the activity rather than bolted on at the end. The joy is the surface. The evidence is underneath it.
Before anything else: where this actually stands
No Performia session has run. There is no pilot, no partner site, and no participant data. If you are reading this as a funded organization deciding where to point an AI mandate, you deserve that sentence before the pitch, not after it.
What is built and working: movement-to-sound for a single person, with no controller and nothing worn; a living-chart teleprompter; an AI band that plays in time and in key; a voice companion that can always stop everything; and a local-first posture with a privacy switch that cuts cloud egress.
What is not built: multi-person ensemble rooms, the lesson mode, band avatars, and the one-button measurement export. Those are described here as designed, and nowhere as working.
The co-design is the public benefit, not hidden R&D.
During an award period, your facilitators and your participants shape what the toolkit becomes — what accessible, consent-safe, culturally-grounded AI arts practice actually requires in a trusted local room. Nobody knows that yet. It cannot be discovered in our office.
The product improves through real deployment in your community, and that co-design is a legitimate public good in its own right. It is the line that lets an organization say yes without us overclaiming — and it is why we would rather tell you plainly that nothing has run than pretend otherwise.
Who does what.
- Program leadership and community recruitment
- Venue, staffing, and artist or facilitator compensation
- Participant consent management
- Final approval of anything public
- Participation in your own local evaluation
Your data is yours. The organization owns its participant and community data. We may use de-identified learnings to improve the toolkit, within limits we agree in writing. Any public case study needs your approval as well as ours.
The measurement is designed in, not added after.
Most monitoring and evaluation is added at the end. That is why it fails: participants experience it as paperwork, staff forget to collect it, the data arrives incomplete, and good programs struggle to renew. We design the program and the evidence layer together, so that taking part is what generates the evidence.
The instruments are standard, validated, and free to use — not something we invented to flatter ourselves. And there is a hard line about what each number is allowed to claim.
If you are an organization with an AI mandate and no obvious thing to actually do with it, that is the conversation we want to have — including the part where we tell you what does not exist yet.