Application in development or planning

Thirteenfold Community

Planned workspace for community operations, moderation support, permissions, automation, and accountable human review.

Planned application identity; product qualification is separate.

Why it is planned

A practical role in the family.

Who it is for

Community owners and moderators coordinating review, permissions, and bounded automation.

Example use

A moderation issue or repeated operational task needs context, a proposed response, and accountable human review.

Intended benefit

Could reduce coordination overhead while preserving human responsibility for moderation and external communication.

Intended workflow

How the work would flow.

This describes the planned experience. It does not establish that these capabilities are available.

  1. Collect only the permitted community, channel, role, and event context.

  2. Assemble a moderation-support packet or preview a scoped automation.

  3. Route the proposal to a human reviewer and, when separately authorized, the relevant integration.

Scope and relationships

Clear ownership of the work.

Data and authority boundaries

Would use explicitly connected community content and role metadata within configured scopes; it would not silently reuse private content, infer crisis or diagnosis states, or publish autonomously.

How it fits with the family

Community would own domain-specific moderation context; Relay would coordinate declared workflows without deciding moderation outcomes.

Explore Thirteenfold Relay