SCiPNET // PERSONNEL_FILE · OPERATIVE: JOEY OPEN FOR WORK
Operative File · AESRC-24
Clearance: OPEN FOR WORK

JOEY

Community architect & writer

I take a new or dying online community and make it alive — then build the teams, onboarding, moderation, events, and writing that keep it that way after the launch buzz fades.

2,508
peak messages in a single day — reached 14 days after a launch I built and drove (Project Aurora)
7 yrs founding, running & directing communities
6 communities built & staffed · up to ~1,400 members
Cambridge English C2 · Grade A · novelist
Get in touch →
SCROLL ▾
01 / WHAT I DO

Everything a community needs — under one person

01

Community launch

Structure, channels, first events, and the opening momentum most servers never get. Zero to active.

02

Onboarding systems

Turn sign-ups into regulars. New members reach a real first interaction within a day — not never.

03

Governance & moderation

Clear rules, fair enforcement tiers, mod-log discipline, and standards that hold under pressure.

04

Building & leading teams

Recruit, train, and structure a staff team with department heads — one that runs the place without you in the room.

05

Events & engagement

Recurring events and campaigns that give people an actual reason to come back tomorrow.

06

Writing & lore

Announcements, rules, guides, and original worldbuilding that people actually read. I write every word.

07

Marketing & social media

Content planning, scheduling, and multi-platform clip campaigns that pull new members from outside your server.

08

Setup & security

Full server setup, verification, anti-nuke and anti-raid protection, and the infrastructure that keeps it safe.

I'm a writer first.

Author of a 75,000-word science-fiction novel, a national-level writing award, and Cambridge C2 Grade A (Writing 200/200). Every announcement, rule, and lore document in this portfolio is written by me — the tone of a community is the community.

Case File 01

PROJECT AURORA

An 18+ sci-fi roleplay world I've built and directed since day one — from cold launch to a living community.

02 / CASE STUDY — PROJECT AURORA

From day-one consultant to Executive Director

I've been on Project Aurora since day one — first as consultant, then Canon Director, now Executive Director on the Aurora Board. Roughly 99% of the build is my work: onboarding, governance, events, canon, security, and the full visual identity — including the launch that hit thousands of messages a day inside two weeks.

Role: Consultant (day one) → Canon Director → Executive Director
Board: Aurora Board
Scope: canon · systems · onboarding · events · security · brand
Watch the launch teaser
youtu.be/3K1XDHG_QLo · Project Aurora

Launch — messages per day, first 14 days

source: server message log · hover a bar
9D1
42D2
1,289D3
281D4
774D5
1,021D6
683D7
1,201D8
1,210D9
1,910D10
935D11
1,544D12
1,888D13
2,508D14
What this shows: a cold launch I ran from 9 messages on day one to 2,508 on day fourteen — the launch-and-engagement problem most communities fail. Sustaining it long-term is the job of the systems below.

// Visual identity — produced by me with AI tools · click to enlarge

// Real posts, live in the server · click to enlarge

Event announcementLaunching an operation and pulling members into it — Operation: Ironwood.
GovernanceA contested call (AI art) put to a binding one-member-one-vote decision.

// Systems I designed

Canon ops

SCPIP database & operations

SCPs enter play uncontained; members roleplay the containment, run the research, and file after-action reports into a living operational database.

Onboarding

Foundation Handler System

Trusted members claim each new sign-up within 24h, run their first scene, and check in at day 3 and 30. Success = still active after 30 days.

Team

Staff organisation & recruiting

Full staff structure with defined roles and departments, plus recruitment posts, graphics, and application flows to fill them.

Governance

Tiered ruleset & enforcement

Four severity tiers, escalation, a discretion clause, and appeals. Age policy and safety built in from day one.

Security

Moderation & server security

Mod-log systems, anti-nuke and anti-raid protection, verification, and the server setup that keeps the place safe.

Onboarding UX

Orientation packet & cheatsheet

A complete new-member guide plus a one-page reference — confused to posting without asking staff.

Events

Event design & GM playbook

Step-by-step event process and detailed live briefings that keep large group events readable.

Case File 02

CRIMSON NETWORK

An international multi-game network I directed — and the team I built to run it.

03 / CASE STUDY — CRIMSON NETWORK

Directed it, staffed it, handed it off

Crimson Network (Crimson Shield International) is an international multi-game community. I came in as Overseer (general director), moved into Staff Manager, built a self-running staff team — then handed it off to focus on new projects. The mark of a good system is that it runs without you.

Role: Overseer → Staff Manager
Peak: ~1,400 members
Outcome: team built & handed off

// Network branding · click to enlarge

  • Staff structure: recruited and trained a team with department heads that outlived my involvement.
  • Progression & roles: designed the leveling system and role hierarchy that reward activity.
  • Systems: a Trading Karma trust system, a clan, a Steam group, and a private game server.
  • Channel architecture: restructured the network around what members actually use.
  • Responsive management: "you asked, we listened" changes driven by member feedback.
  • Growth: retention analysis, marketing, and a game-studio community partnership.

// My posts & systems, live in the network · click to enlarge

Network systemsSteam group, all-games clan, and leveling — announced as Joey.
Trust systemTrading Karma — a reputation system for member-to-member trades.
Responsive mgmt"You asked, we listened" — a member-driven channel restructure.

Full growth & retention metrics available on request.

04 / MARKETING & SOCIAL

Pulling people in from outside

Running a server is half the job. The other half is the content that brings new members to it — I plan and write recruitment campaigns, cross-platform posts, and in-world social copy that reads like the community, not an ad.

  • Recruitment campaigns & teaser drops
  • In-world social posts (X / Discord) that stay on-brand
  • Clip & media strategy to farm reach
  • Content calendars & scheduling across platforms
05 / TRACK RECORD

Seven years of building communities

2019 – 2021

SCP RP — Site-19 & SCP Universe

Founder and owner. Built structured servers from scratch and organised staff teams. Peak ~300 and ~200–400 members.

2022 – 2023

Site-202 "New World"

Lead developer and organiser. Launched after a teaser campaign; built political structure, lore, and automated systems. Peak ~500 members.

2022

DoomsdayRP — Milsim

Co-owner. Rose through staff to faction co-lead; set staff-management and communication standards. Peak ~100–500 members.

2023 – 2024

The Art of Warfare (TaW)

Contributor to a 3,000+ member military-gaming network. Wrote a strategic analysis and a server-improvement consult focused on user psychology, retention, and growth.

2024 – 2025

Crimson Network

Overseer → Staff Manager. Built the staff team, then handed off to focus on new projects. Featured above. Peak ~1,400 members.

2026

Project Aurora — Executive Director

Consultant (day one) → Canon Director → Executive Director, Aurora Board. ~99% of the build. Featured above.

These are online gaming and roleplay communities — but the craft (cold-start launches, onboarding, moderation, team-building, retention, events, writing, marketing, and security) is exactly what a course, creator, or product community needs.

06 / CREDENTIALS

The receipts

C2 · Grade A
Cambridge English Proficiency — 200/210. Writing 200/200, Listening 210/210. Native-market English.
Award
National-level student research & writing award for a long-form project.
75,000 words
Author of a completed science-fiction novel with deep psychological themes.

Let's launch yours.

Available now for community launches, rebuilds, and ongoing management. Tell me what you're building and where it's stuck.

SCiPNET // END OF FILE · OPERATIVE: JOEYCOMMUNITY ARCHITECT & WRITER · 2026