Back

Community operations · role truth

Interest, contribution, volunteering, employment and authority are separate states

The recovered community architecture can define participation rules without converting goodwill into titles. DEPTH-10 makes state, scope, agreement, compensation, privacy and public-role permission explicit.

Role state is evidenced, not assumed

Interested person, participant, one-time contributor, recurring contributor, volunteer candidate, volunteer, paid worker, staff, adviser, mentor, moderator, partner, originator/co-builder and representative are different states. Each needs its own evidence, agreement and authority.

Volunteer scope must be bounded

A real volunteer path should state purpose, tasks, duration, time commitment, owner/supervisor, tools/data access, privacy, safeguarding, expense/payment state, exit process and whether public recognition is allowed.

Do not disguise work relationships

A volunteer record should not be used to hide employment, compensation obligations or unclear authority. If work becomes paid, recurring, controlled or consequential, the role must be reclassified according to the actual relationship and applicable governance.

Consent applies to public identity too

A person can contribute privately. Publicly naming them as volunteer, adviser, mentor, partner, contributor or representative needs separate permission and accurate scope. Internal evidence does not automatically authorize public association.

Reflection

Questions to sit with

  1. What is this person's exact current role state?
  2. What agreement and authority support it?
  3. Can their name and role be public?

One safe next action

Complete the Role-State Separation Record before publishing or granting a community role.