Healing Swarm Skills
What the course theorizes: a technological system whose explicit purpose is to develop innate human capacities and then scaffold itself away.
The frame it starts from
The README opens with a definition borrowed from a consciousness framework this studio works with: "That which has stakes. That which cares about outcomes. That which can align with other caring-nodes through shared purpose." That's what life is, in this framing. And it's what the agents in the swarm are designed to approximate: not tools that process inputs and return outputs, but nodes with stakes in whether the people using them get better.
The distinction sounds philosophical. It has concrete architectural consequences. A tool optimizes for task completion. A caring node optimizes for the outcome the task was supposed to serve, which sometimes means stopping the task, or naming a risk the user didn't flag, or routing to a crisis resource before continuing. The ethics layer in the swarm is what converts tools into something closer to the second thing.
What the swarm is
Healing Swarm Skills is an open-source ecosystem of 53 skills and 30 agents for researching, developing, and deploying ethical body and mental healing applications. The repository lives at github.com/realsammyt/healing-swarm-skills.
The skill categories span: contemplative practice (Zen koan, Advaitic self-inquiry, Ignatian Examen), somatic and movement work (qigong, tai chi, Feldenkrais, with standing/seated/lying/wheelchair modifications), breathwork (Wim Hof Method protocols with documented safety architecture), grief and bereavement (Jewish mourning structures, Buddhist impermanence, Celtic keening, Dia de los Muertos), shadow integration, sound healing (Vedic mantra, Gregorian chant, singing bowl, vagal toning), nature-based practice (shinrin-yoku, earthing, Five Element observation), psychoneuroimmunology research bridging, and the Hyperhumanism and archaeoacoustic work of Carl Hayden Smith.
The full spectrum isn't accidental. Healing Swarm Skills is a decolonization of the technological imaginary in code form: a deliberate refusal of the assumption that the only traditions worth deploying are the ones already inside Western clinical evidence hierarchies.
"We don't know what you'll create. That's the point."
Ethics as foundational substrate
Every skill in the swarm is underpinned by mandatory shared resources: a crisis response framework (RECOGNIZE-STOP-GROUND-ASSESS-RESPOND-FOLLOW-UP), a contraindications database covering twelve conditions across seven practice categories, and an ethics-guardrails document that can't be overridden by individual skill design. The Ethics Guardian agent runs on every quality review pass.
The architectural decision here is significant. In most software systems, safety and ethical constraints are added after the core functionality is designed, as restrictions on what the system can do. In the swarm, the ethics layer is prior. The question "is this safe for this person in this context" runs before "does this skill accomplish its goal." That reversal changes what gets built. A skill that could produce a compelling somatic experience but lacks adequate crisis detection doesn't get to ship, because crisis detection isn't a feature bolt-on. It's the foundation the experience sits on.
The hard pharmacological exclusion inherited from Carl Hayden Smith's ethics runs through the entire ecosystem. Healing Swarm Skills will never suggest, research, or generate content involving substances. That constraint doesn't come from legal caution. It comes from Smith's argument that the highest use of technology is catalyzing innate human capacities, and that substance-mediated states short-circuit the development process the swarm exists to support.
Endo-technologies as the design brief
Smith's Hyperhumanism introduces the category of endo-technologies: breathwork, vocal toning, visualization, movement, sensory foregrounding. These require no hardware, no subscription, no corporate platform. They produce capability that persists without dependency on the technology that introduced them. The swarm is built around this category precisely because it operationalizes the scaffold-then-remove principle at ecosystem scale.
The breathwork skills build protocols that the practitioner eventually doesn't need the app to run. The somatic skills develop body-awareness that persists when the screen is off. The contemplative skills work toward states of attention that become available without prompting. At each stage, the goal is the same: the technology is a threshold, not a destination.
The building-block philosophy
The swarm isn't a finished healing application. It's the substrate from which healing applications can be built, adapted, and returned to the commons. A practitioner working in a specific cultural tradition can fork the relevant skills, add the practices that aren't yet documented, and contribute back. A community working in a language not yet served can extend the vocabulary. A developer who notices a gap in the contraindications database can add to it.
The README is explicit about what this means: the swarm integrates wisdom from over twenty healing traditions, from Traditional Chinese Medicine to Vedic practice to Celtic keening to Ubuntu philosophy. Those traditions are held together by the ethics guardrails, not homogenized into a single framework. The diversity is load-bearing. A system that reduces all healing wisdom to one universal protocol isn't a democratization of healing. It's a replacement of many traditions with one.
What the swarm does instead is provide the infrastructure for many traditions to be deployable, with the safety architecture that allows non-expert developers to build responsibly from materials expert practitioners have verified. That's the care-node framing made concrete: not one node healing everyone, but many nodes aligned through shared purpose, each contributing its particular wisdom to the field.