Work in progress IARPG-OPS-2 2.0.14-wip

Global publication search

Search the operations design system

Type to search standards, missions, roles, authorities, reports, sources, pages, schemas, and UAI memory.

Institutional actors · not alignment stereotypes

Build factions from
interests, limits, and people.

IARPG factions are organizations with public mandates, practical interests, internal disagreement, dependencies, oversight, affected communities, and changing relationships. Recruitment is modeled as access, screening, integration, trust, exit, and safeguards—not psychological manipulation.

Direct answer

What makes an IARPG faction realistic?

A realistic faction is not a logo, nationality, or single ideology. It has an institutional purpose, practical interests, constituencies, internal blocs, a decision process, resources, dependencies, oversight, recruitment pathways, exit routes, community effects, and reasons to cooperate or change course.

Profiles
12 fictional organizations
Required internal tension
At least two documented blocs per faction
Recruitment model
Access → vetting → integration → retention or exit
Machine record
Alliance network JSON

Fictional institutional profiles

Twelve factions.
None of them is a monolith.

Search by purpose, region, interest, or internal bloc. Each dossier exposes the organization’s public position and the practical constraints that may complicate it.

Loading fictional faction profiles…

Faction anatomy

A believable institution
needs more than lore.

These fields make alliance changes, mission access, internal conflict, and player consequences legible without reducing an organization to a moral color or national stereotype.

01

Mandate and interests

What the faction says it exists to do, what it practically needs, and where those two diverge.

02

Decision architecture

Who can authorize action, who can block it, how emergency authority works, and what must remain sovereign.

03

Internal blocs

At least two credible positions with different priorities, constituencies, evidence, and tolerance for risk.

04

Resources and dependencies

Capabilities create leverage; dependencies create vulnerability, bargaining pressure, and possible realignment.

05

Oversight and rights

Audits, courts, assemblies, safeguards, affected communities, and the difference between rules on paper and practice.

06

Recruitment and exit

How people enter roles, gain trust, receive supervision, disengage, appeal decisions, and retain dignity.

Recruitment ecosystem

Recruitment is an organizational lifecycle.
It is not a targeting script.

The site models public pathways, suitability, role-based vetting, supervised integration, reciprocal obligations, burnout, disengagement, and reintegration. It does not tell players how to exploit money pressure, ideology, trauma, diagnosis, isolation, identity, or personal vulnerability.

Different faction types use different lawful structures: public applications, professional credentials, apprenticeships, member secondment, transparent contracts, community nomination, or open contributor pathways. Reliability, accountability, and fit matter more than enthusiasm alone.

  1. 01
    AwarenessPublic mission, lawful eligibility, and realistic expectations.
  2. 02
    AccessApplication, referral, appointment, contract, election, or open contribution.
  3. 03
    ScreeningRole-based competence, integrity, conflicts, rights, and due process.
  4. 04
    IntegrationTraining, supervision, limited authority, and shared norms.
  5. 05
    ReciprocityMembers exchange labor, trust, protection, status, or public service.
  6. 06
    Retention or exitBurnout support, reassignment, appeal, disengagement, and reintegration.

Browser-local faction blueprint

Generate a safer starting brief,
then write the disagreements.

The generator creates an original fictional institutional scaffold from neutral variables. It does not save, upload, or transmit inputs, and it never generates real-world recruitment instructions.

Ready

Choose four structural variables.

The output will include institutional tension, an independent-actor boundary, and an uncertainty rule.

Independent-actor posture

Every faction responds
differently to autonomy.

An independent person may be a public supporter, applicant, contractor, contributor, informant, critic, liability, or falsely attributed actor. The category must be evidenced rather than assumed.

CONTROL

Formal authority required

Military, public safety, and sensitive liaison systems reject unauthorized operational action.

BOUNDED ACCESS

Contract or contributor pathway

Cooperatives and standards groups may accept independent work through clear roles and review.

OPEN SUPPORT

Advocacy without authority

Civic networks may welcome broad sympathy while reserving formal representation to mandated roles.

DISPUTED CLAIM

Praise is not command

Post-event praise, shared language, or a common adversary does not establish prior direction or membership.

Connected tools and standards

Explore the wider AI ecosystem.