Introduction

Welcome to the Operational Framework — a concise, role‑driven guide for running a coordinated organization. While the examples and nomenclature are inspired by large‑scale online strategy play, the structure applies to any distributed team that needs reliable information flow, resilient logistics, and decisive operations.

Purpose

Define clear divisions of responsibility so people know what to own and how to escalate.
Provide lightweight processes that keep the team fast while staying aligned.
Offer ready‑to‑use role descriptions, checklists, and interfaces between teams.

How to use this book

Start with Key Design Principles to understand the underlying philosophy and constraints.
Review Divisions to see how work is grouped and how information flows across the org.
Review Roles to assign responsibilities and set expectations for communication and outputs.

Key principles: see Key Design Principles.
Divisions: Intel, Logistics & Infrastructure, Social, Training.
Roles: Commander, Chief Operations Officer, Chief Offense Officer, Chief Defense Officer, Chief Logistics Officer, Intel Director.

Conventions

“Division” = a functional team with a clear mission and interfaces.
“Role” = a responsible owner with explicit duties and outputs.
Communication flows up for analysis and down as directives. See Chain of Communication.

Key Design Principles

Separation of Concerns

Every division has one function. Intel gathers information; Operations uses it. Logistics fuels Operations; Command coordinates them all.

Chain of Communication

Information should always flow up from Scouts/Logistics → Intel → Command, and down as directives to Operations and Divisions. Upward flow = raw data and status. Downward flow = decisions, priorities, and standards.

Redundancy

Each critical role (Defense, Intel, Logistics) should have at least one assistant or understudy—so one offline player does not cripple the system.

Transparency

Pseudo‑public threads for reports; private threads for analysis. Everyone should be able to see the data, even if only officers interpret it. Reports and dashboards should default to visible to all members unless there’s a concrete counter‑intel risk.

Standard Interfaces

Input/Output expectations must be explicit for each Division and Role. See Divisions pages for interfaces and SLAs.
Decisions should reference an intel report or a design principle; avoid purely ad‑hoc choices.

Cadence and Rhythm

Use predictable cycles: daily check‑ins, weekly reviews, and event‑driven alerts for emergencies.
Keep ops tempo sustainable; surge only with clear objectives and end‑conditions.

Divisions

Divisions are functional teams with clear missions, inputs, outputs, and interfaces. Use these pages to understand how work is grouped across the organization and how information and resources should flow between teams.

Division Index

Intel Division — Collects, verifies, analyzes, and disseminates information for decision‑makers.
Logistics & Infrastructure Division — Provides supply, transport, and rebuild capacity to sustain operations.
Social Division — Builds cohesion and retention through onboarding, comms, and community programs.
Training Division — Accelerates effectiveness with role‑aligned curricula, drills, and refreshers.

Intel Division

Mission

Gather, verify, analyze, and disseminate information to enable fast, informed decisions.

Key Processes

Recon collection: scouts gather activity, capabilities, and terrain/infra data.
Counter‑intel: vet recruits, monitor anomalies, minimize information leakage.
Analysis and reporting: convert raw sightings into assessments and actionable targets.

Inputs

Field reports from Recon Scouts and allied sources.
Operational requirements from Chief Offense Officer and Chief Defense Officer.

Outputs

Daily/weekly situation reports (SITREPs).
Target dossiers with priority and risk.
Early warning alerts and threat assessments.

Interfaces

Up: summaries and risk to Chief Operations Officer and Commander.
Across: targeting support to Offense; threat assessments to Defense; feasibility feedback to Logistics.

Logistics & Infrastructure Division

Mission

Provide dependable supply, transport, and rebuild capacity to sustain operations at any tempo.

Key Processes

Pooling and allocation of resources (e.g., silver, materials) with clear priorities.
Transport planning: routes, timings, and surge capacity management.
Infrastructure standards: production hubs, storage, and critical rebuild playbooks.

Inputs

Operational requirements from Chief Operations Officer.
Demand signals from Chief Offense Officer and Chief Defense Officer.

Outputs

Fulfillment schedules and ETAs.
Capacity dashboards (transport, production, reserves).
Rebuild plans for post-incident recovery.

Interfaces

Across: aligns with Intel Division to anticipate demand and avoid exposure during moves.
Up: constraints and risks reported to Chief Operations Officer.

Mission

Foster cohesion, culture, and member retention through community management and communications.

Key Processes

Onboarding and orientation for new members.
Community events and recognition programs.
Internal comms: announcements, summaries, and digest delivery.

Inputs

Strategic updates from Commander and Chief Operations Officer.
Training needs from the Training Division.

Outputs

Clear announcements, event calendars, and periodic digests.
Onboarding checklists and buddy assignments.

Interfaces

Across: collaborates with Training for learning pathways; signals morale risks to Operations leadership.
Up: reports engagement metrics and retention risks to leadership.

Training Division

Mission

Accelerate member effectiveness with practical, role‑aligned training and refreshers.

Key Processes

Curriculum design mapped to Roles and SOPs.
Live drills and tabletop exercises (offense waves, defense incident command, logistics pooling).
Knowledge base upkeep and quick‑reference checklists.

Inputs

SOP updates and lessons learned from AARs led by Operations.
Skill gaps and onboarding needs from the Social Division.

Outputs

Role-aligned training paths and schedules.
Drill results and competency checklists.
Quick-start guides and reference cards.

Interfaces

Across: partners with all role owners to keep materials current with reality.
Up: reports readiness and skill coverage to the Chief Operations Officer.

Roles

Roles are accountable owners with explicit responsibilities, communication patterns, and outputs. Use these pages to assign responsibilities, set expectations, and understand how work moves Up/Across/Down the organization.

Role Index

Commander — Sets overall strategy and arbitrates major trade‑offs.
Chief Operations Officer — Turns strategy into executable operations and standards.
Chief Offense Officer — Leads offensive operations and targeting waves.
Chief Defense Officer — Owns defensive posture and incident response.
Chief Logistics Officer — Manages resources, movement, and sustainment.
Intel Director — Runs the intel lifecycle and delivers assessments.

Commander

Department of Strategic Command

Description

Sets overall strategy, diplomatic posture, and political commitments. Empowers the Chief Operations Officer to execute, and arbitrates trade-offs when resources or priorities conflict.

Responsibilities

Set strategic direction and success criteria.
Decide on wars, mergers, treaties, and high-stakes commitments.
Appoint and evaluate senior officers; ensure succession and redundancy.

Communication

Down: strategic guidance and constraints to the Chief Operations Officer.
Outward: diplomacy with external groups; unify messaging.
Inward: periodic reviews of intel summaries and operational dashboards.

KPIs / Outputs

Strategy memos and decision records.
Alignment reviews and org health assessments.

Chief Operations Officer

Department of Strategic Command

Description

Translates strategy into executable operations. Coordinates divisions, sets operational standards, and ensures tempo and priorities are maintained across campaigns and routine activity.

Responsibilities

Turn strategic goals into logistics-backed, actionable plans and timelines.
Chair operations briefings and after-action reviews.
Supervise sub-officers (Defense, Offense, Logistics, Intel) and resolve cross-team blockers.
Set readiness levels, surge criteria, and exit conditions for operations.

Communication

Up: regular status and risk summaries to the Commander.
Down: clear directives and standards to all divisions with deadlines and success criteria.
Across: synchronize with Intel Director for targeting and with Chief Logistics Officer for resource feasibility.

KPIs / Outputs

Operation briefs and tasking orders.
Readiness dashboard and risk register.
After-action reports (AARs) with decisions and follow-ups.

Chief Offense Officer

Department of Operations

Description

Leads offensive operations. Plans raids and coordinated expansion waves, sets standard troop compositions, and selects strategic targets informed by Intel Division reports.

Responsibilities

Maintain and publish standard operating procedures (SOPs) for offensive actions.
Build target lists with the Intel Director and validate feasibility with the Chief Logistics Officer.
Schedule and lead waves/raids; assign roles (timers, breakers, follow-ups).
Track readiness: siege tools, fast movers, time‑zone coverage, contingency forces.
Run after‑action reviews and roll findings into SOP updates.

Communication

Up: operational status and risk to the Chief Operations Officer.
Across: targeting sync with Intel Director; supply checks with Chief Logistics Officer.
Down: tasking and timelines to participating squads.

KPIs / Outputs

Published OP brief with timings, targets, and composition.
Target list with priority and justification.
AARs with outcomes and SOP adjustments.

Chief Defense Officer

Department of Operations

Description

Owns defensive posture and rapid response. Sets defensive readiness standards, builds support bridges, and manages emergency response pings and triage.

Responsibilities

Publish defense SOPs: wall levels, support composition, alarm criteria.
Maintain support networks and bridge routes for fast reinforcement.
Run incident command during sieges: assignment, escalation, relief rotation.
Track readiness: support stacks, timing coverage, and critical infrastructure.

Communication

Up: defense status and incident summaries to the Chief Operations Officer.
Across: coordinates with Intel Director for threat assessments and early warnings.
Across: coordinates with Chief Logistics Officer for supplies and rebuilds.

KPIs / Outputs

Defense readiness dashboard and alerting matrix.
Siege incident logs and post-incident reports.
Support bridge directory and upkeep schedule.

Chief Logistics Officer

Department of Operations

Description

Owns resources, movement, and sustainment. Oversees silver pooling, cart coordination, and resource movement so production hubs reliably feed operations.

Responsibilities

Plan and run silver/resource pooling; maintain transparency and auditability.
Manage transport capacity (carts, timings, routes) and prevent bottlenecks.
Validate operational feasibility and timings with Chief Offense Officer and Chief Defense Officer.
Maintain rebuild pipelines and reserve stocks for surge events.

Communication

Up: logistics status, constraints, and ETAs to the Chief Operations Officer.
Across: resource feasibility checks with Offense/Defense; early warning to Intel Director when shortages affect targeting.

KPIs / Outputs

Pooling plans and fulfillment reports.
Capacity dashboard (transport, production, reserves).
Rebuild and resupply schedules.

Intel Director

Department of Intelligence

Description

Owns the intel lifecycle: collection, verification, analysis, and dissemination. Ensures decision‑makers have timely, relevant, and reliable information, and that counter‑intel risks are actively mitigated.

Responsibilities

Manage regional scouts and coverage maps.
Run counter‑intelligence processes and access hygiene.
Maintain activity maps and risk heatmaps.
Produce and distribute SITREPs and target dossiers.
Direct targeted reconnaissance and special collection.

Direct Reports

Recon Scouts

Gather intel on forces, logistics, and infrastructure.
Track activity patterns and local conditions.
Collect field data for reports and verification.

Counter Intel

Vet new recruits and guard privileged access.
Monitor anomalies and investigate leaks.
Ensure sensitive information is protected.

Communication

Up: deliver summaries, risks, and confidence levels to Chief Operations Officer and Commander.
Across: provide targeting and threat assessments to Offense/Defense; feasibility context to Logistics.
Down: tasking and standards to Recon and Counter‑Intel teams.

KPIs / Outputs

Coverage and freshness metrics for intel feeds.
SITREPs with clear confidence ratings and sources.
Target dossiers with priority, risk, and recommended actions.

Keyboard shortcuts

Operational Framework