# Ethics and Field-Report Policy

> Version 1.0 — applies to public practitioner field reports submitted to UnPeeragogy.

UnPeeragogy studies friction in collaborative learning and peer production. Those incidents often involve real people, disagreements, workplaces, communities and relationships. Methodological openness does not justify exposing people who did not choose to become research subjects.

This policy therefore applies a simple rule:

> **Preserve enough context to understand the incident; remove context that only makes people identifiable.**

## 1. Scope and status

UnPeeragogy is an independent, open research project. It is not presented as an institutionally reviewed clinical study, human-subject experiment, or statistically representative survey.

The project primarily works with:

- public documentary sources;
- public repository and governance records;
- voluntary, public practitioner field reports;
- first-person accounts supplied by people who choose to contribute.

The project does **not** ask contributors to provide sensitive personal data in order to participate.

## 2. Do not submit sensitive or confidential material

Field reports should not contain:

- real names of private individuals unless they have clearly consented to being identified in this context;
- private email addresses, phone numbers, home addresses or account identifiers;
- passwords, access tokens, private repository content or confidential business information;
- private messages or screenshots that participants did not agree to publish;
- medical, health, sexual, religious, political, biometric or other sensitive personal information that is not strictly necessary and already intentionally public;
- allegations of criminal conduct about identifiable private people;
- information about children or minors;
- information that could create a plausible safety risk if made public.

If such material is essential to understanding an incident, do not post it publicly. Contact the project maintainer first and describe the methodological problem without sharing the sensitive data.

## 3. Data minimisation

Use the least identifying description that preserves the mechanism under study.

Prefer:

- "a small volunteer documentation team" over a unique team name;
- approximate group size over a full participant list;
- "a European university" over a department and city when location is not analytically relevant;
- role descriptions or pseudonyms over real names;
- date ranges over exact timestamps when exact timing is unnecessary.

De-identification is not guaranteed anonymity. A distinctive event can remain identifiable even after names are removed. Contributors should consider whether insiders could reasonably recognise the people involved and remove unnecessary details accordingly.

## 4. Contributor position

Every field report asks the contributor to identify their relationship to the event:

- direct participant;
- direct observer;
- second-hand / documentary knowledge;
- mixed or other position.

This is not a ranking of credibility. It is provenance. A participant may know motives and context that a document cannot show; a document may preserve details that memory does not.

## 5. Observation is not interpretation

Reports separate:

- what happened;
- what surprised the contributor;
- what the contributor thinks it meant;
- plausible alternative explanations.

The project may interpret an incident differently from the contributor. That interpretation must remain visibly distinct from the original report and must link back to it.

## 6. Public submission and consent

GitHub Discussions are public. Before submitting a field report, contributors must acknowledge that:

- the report can be read by anyone;
- the project may analyse, quote in part, link and archive it;
- material incorporated into the project-owned research corpus is intended for open reuse under CC0;
- public Git/GitHub history, caches, archives and third-party forks may preserve earlier versions even after later edits or removal from the active corpus.

Do not submit material for which you cannot make that public-use decision.

## 7. Withdrawal, correction and takedown

A contributor may request correction or removal from the **current maintained corpus** by contacting the project maintainer or opening an appropriate repository request.

The project will make a reasonable effort to remove unnecessary personal data from maintained project surfaces. It cannot guarantee erasure from:

- Git history already distributed to third parties;
- forks;
- search-engine caches;
- web archives;
- copies independently downloaded or republished under applicable terms.

For this reason, data minimisation before publication is the primary safeguard.

## 8. Third-party public records

A fact being publicly accessible does not automatically make every reuse ethically appropriate.

When using public discussions, issues, mailing lists or governance records, UnPeeragogy should prefer claims about **structures, decisions and documented processes** over unnecessary profiling of identifiable individuals.

Names of public actors may be retained when their identity is materially necessary to understand an official role, authorship, public decision or already-public scholarly contribution. Otherwise, structural description is preferred.

## 9. AI-assisted analysis

AI tools may help search, classify, compare or generate provisional interpretations. AI output is never treated as empirical evidence merely because a model produced it.

Research-grade claims must remain traceable to human-readable sources or incidents. Where an AI-assisted pipeline materially affects an interpretation, the relevant method/version should be disclosed when practical.

Do not send confidential field-report material to third-party model providers through this project. Public reports should already be written on the assumption that they are public.

## 10. Counter-evidence and participant dignity

UnPeeragogy studies failure modes without turning people into failure modes.

A report may describe avoidance, free-riding, hidden hierarchy, coordination fatigue or other dynamics. These are analytic descriptions of situations and structures, not diagnoses of a person's character.

Counter-evidence must be retained when it materially challenges an interpretation. The project should prefer revision over defending an earlier claim for reputational reasons.

## 11. Researcher positionality

The maintainer has a history inside the Peeragogy project. This gives access to context and also creates interpretive risk.

The project therefore treats positionality as metadata rather than pretending neutrality. First-person material from the maintainer is labelled as such and should not be silently promoted into independent corroboration.

## 12. Safety threshold

If publication could plausibly cause disproportionate harm to a private person, the incident should be generalised, delayed, withheld, or excluded even when it would be analytically interesting.

Open research is not the same as maximal exposure.

## 13. Contact

For privacy, correction, takedown or research-ethics concerns, use the contact channel published on:

https://unpeeragogy.pyragogy.org/

For methodological challenges that can be discussed publicly, use GitHub Discussions so the reasoning can remain inspectable.

