The field keeps asking whether sauna works. Steam Collective should ask a more operational question: what did the ses...

The field keeps asking whether sauna works. Steam Collective should ask a more operational question: what did the session actually consist of?

Without protocol metadata, every outcome is orphaned. A mortality signal, a sleep improvement, a histamine flare, or a recovery win cannot be attributed to "sauna" in general. It belongs to a specific dose, in a specific body, under specific conditions.

If community saunas are going to function as research nodes, logging cannot be optional decoration. It is the research instrument.

The minimum set

Every consented Steam Collective session should be able to record:

• modality: traditional dry, infrared, steam, or mixed
• temperature
• humidity when known
• duration per round
• number of rounds
• cooling method: passive rest, shower, plunge, outdoor air, or none
• cooling duration when used
• timing: morning, evening, post-exercise, or other
• fasting state: fed, fasted, or unknown
• hydration/electrolyte approach at a coarse level
• subjective session load
• acute symptoms during and after
• next-day sleep and symptom notes when available

Wearables can enrich this. They should not be required for the minimum viable layer. A paper log that is complete beats a fancy stack that only a few people use.

Why minimum matters

Over-instrumentation kills participation. Under-instrumentation kills inference. The metadata layer has to be light enough for ordinary use and strict enough for later analysis.

That balance is a governance choice. Steam Collective should publish a reporting standard the way open-source projects publish contribution guidelines. Nodes can then innovate locally without inventing incompatible schemas every time.

What this unlocks

With a shared metadata layer, the previous posts become actionable:

• Histamine and heat tolerance become phenotype-specific dose questions.
• Women's hormonal context becomes a stratifier rather than an afterthought.
• Cold pairing becomes a comparable protocol branch.
• Future studies can be designed against real community practice instead of guessed lab conditions.

This is also how decentralised science avoids becoming decorative. A sauna that generates no protocol data is hospitality. A sauna that generates consented, structured session data is infrastructure.

Proposed adoption path

Phase one should not wait for perfect software.

1. Publish the metadata fields and definitions.
2. Collect them through the simplest reliable channel available.
3. Require every funded node proposal to state how it will capture the minimum set.
4. Revisit the schema after the first wave of real sessions, not before.

P14 is the bridge from story to system. Before Steam Collective asks the community to fund a study, it should be able to say what every session logs by default.

If we cannot describe the dose, we cannot govern the science.