Platform Operations — Internal Orientation

Version: v1.0

Created: 2026-01-19

Audience: Team, Moderation, Stewardship  

Status: Internal reference  

Purpose: Structural clarity, consistency, and long-term continuity  

This document is maintained by the circled.club platform team.

Updates are appended over time.

Decisions and opinions are documented in separate, dedicated posts.

1. What circled.club is (internal definition)

circled.club is a community-driven collaboration ecosystem.

It is not:

• a social feed
• a discussion-first platform
• an attention-optimized growth network
• a general-purpose community forum

It is:

• an infrastructure for structured collaboration
• a system that turns conversations into initiatives
• a place where contribution outweighs attention
• a long-term ecosystem, not a product cycle

Our responsibility is to maintain clarity, integrity, and continuity — not to maximise activity.

2. Core architectural principle

• Orientation before participation.
• Structure before engagement.
• Stewardship before growth.

Every design, permission, and communication decision must support this principle.

3. Two distinct entry journeys (never mixed)

3.1 Public visitor journey (no account)

Goal: Understanding & trust

Allowed actions:

• Read
• Explore
• Observe
• Engage without pressure

Primary surfaces:

• Landing page
• Spaces overview
• Featured Spaces / Circles / Projects
• About pages (Manifesto, Ecosystem, Stewardship, Whitepaper)

Rules:

• Limited commenting (Commenting is available where explicitly enabled.)
• No influence on direction
• No participation pressure

Public visitors are guests with the ability to participate in open contexts,

but not to shape platform governance or direction.

3.2 Member journey (account created)

Goal: Meaningful participation over time

Stages:

1. Profile creation
2. Observation (Spaces & Circles)
3. Light participation
4. Deeper contribution (Circles / Projects)
5. Stewardship & responsibility (earned or assigned)

Members choose where and how much they participate.

4. Structural layers & responsibilities

4.1 Platform Space (constitutional layer)

Purpose: Stability & trust

Function: Reference, not dialogue

Contains:

• Manifesto
• Ecosystem
• Whitepaper
• Stewardship
• Change Logs

Rules:

• No comments
• No debates
• Content is curated and authoritative

This is the source of truth.

4.2 Platform Support Space (orientation layer)

Purpose: Help & routing

Function: Entry point for questions, not escalation

Contains:

• How to get help
• FAQs
• Bug reports (via Circle)
• Contact paths

Rules:

• No individual case handling
• No governance discussions
• Redirect when needed

4.3 circled.club Official Circle (sense-making layer)

Purpose: Platform-level reflection & alignment

Function: Structured dialogue, not a general discussion feed

Used for:

• Platform updates
• Context for decisions
• Invitations to reflect
• Summaries of feedback
• Phase & milestone communication

Posting rules:

• Posts by team only
• Comments open, moderated
• One active topic at a time
• Every thread (discussion) is closed with a summary

This is a logbook and briefing room, not a forum.

4.4 Other Spaces (living ecosystem)

Purpose: Collaboration, projects, communities

Function: Where participation actually happens

Examples:

• Collaboration
• Circled Impact
• Community Projects
• Local / Domain Communities

These spaces are self-organising within the framework.

5. Documentation logic (what lives where)

Type of information – Where what lives

Core values & principles => About => Manifesto

Structure & flow => About=> Ecosystem

Economic/system design => About=> Whitepaper

Responsibility & protection => About => Stewardship

Updates over time => Spaces => Platform => Pages: Change Logs

Context & reflection => Spaces => Platform => circled.club official (Circle)

Help & questions => Spaces => Platform => Platform Support

Practice & experimentation => Spaces => Collaboration => Subspaces, Circles & Projects

6. Engagement policy (important)

• Engagement is invited, not harvested
• Silence is acceptable
• Observation is a valid state
• Growth follows clarity, not the other way around

If something creates noise, pressure, or entitlement — it is misaligned.

7. Role of the team

The team acts as:

• stewards, not owners
• facilitators, not influencers
• maintainers, not growth hackers

Decisions must prioritise:

• long-term continuity
• clarity of structure
• protection of community autonomy

8. When to invite participation in projects

Participation is invited only when:

• structure is clear
• boundaries are explicit
• expectations are set
• moderation capacity exists

Until then:

• observe
• document
• prepare