Jobs at ResearchCity#

ResearchCity does not yet exist as an organization. It will begin to exist when sufficient buy-in materializes to start hiring. This page is a public commitment to the kind of work that needs doing — and an invitation to those who want to do it.

Hiring philosophy#

LLoL will hire as soon as resources allow. Who gets hired first depends on who can most help ResearchCity move forward at that moment. There is no fixed sequence. The first colleague might be a web developer, a translator, a formal-methods researcher, or a coordinator — depending on where the need is greatest when funding arrives.

What is certain:

  • ResearchCity needs people who can work across disciplines, cultures, and worldviews with gentle kind reasonable professionalism.

  • Every hire must strengthen the organization’s ability to serve its mission of averting existential disasters through rigorous, transparent, interdisciplinary research.

  • LLoL is at the bottom of the org chart, not the top. Everyone hired is someone LLoL serves.

What kinds of capabilities are needed#

The work spans five broad areas. Within each, specific roles range from research to operations to outreach:

  • Research — formal methods, empirical testing, risk assessment, comparative theology, history and philosophy. The intellectual core.

  • Operations — FeedbackFlow processing, content editing, translation across 10 languages, administration. Keeping the engine running.

  • Community — engagement, fundraising, education and outreach. Converting understanding into participation.

  • Technology — web engineering, data and AI, security and privacy. Building and maintaining the infrastructure.

  • Strategy — strategic planning, communication, partnerships. Ensuring the work reaches those who need it.

Coordinating across all five areas are the ZION Coordinators — four people responsible for Zoning (inter-department communication), Investigating (research coordination), Organizing (matching people to work), and Navigating (ensuring things get done on time). Together they replace a traditional chief-of-staff role with a distributed model that prevents bottlenecks.

Advising from the outside are Legal Advisors and Lived Experience Advisors who bring perspectives LLoL lacks.

For details on all of these, including brief descriptions and rationales for every position, see the 153 FiShFus Positions.

The 153 FiShFus positions#

LLoL has developed a tentative organizational plan for ResearchCity with 153 positions across 6 Zones. The plan is documented in the 153 FiShFus Positions, which was developed with assistance from Claude (Anthropic) and refined through a 5-perspective adversarial review.

The number 153 is deliberate (John 21:11). The plan is very early — every department, position, and description will be refined through review and real-world experience. It exists to show that this vision has been thought through to the level of organizational structure, not just abstract ideas. Real scaling will require real adaptation.

How to express interest#

None of these positions are currently funded. But if you see yourself in any of the capabilities described above or in the 153 FiShFus Positions, LLoL wants to hear from you.

  1. Send an email to FF+jobs@balospe.com with what you could contribute, why you are interested, and links to relevant work.

  2. All applications may be treated as public domain submissions under the Jonah License unless you explicitly request otherwise.

  3. LLoL may not be able to respond until funding allows hiring. Please be patient.

To help make these positions real: buy in to ResearchCity.

Notes

Content stability — Content is variant dv_Auto_MMv1_2026m03d31 (see StayVS). Rebuilt 2026-05-18.

See also on Balospe.com
Epic Fury to Epic Empathy: Fund a ResearchCity for Mathematical Theology

For millennia, Jews, Christians, Muslims, and others have fought wars — and fueled apocalyptic fears — over theological questions that none of them could state precisely enough to resolve. Mathematical theology offers a way out: translate the claims into formal axioms, check them for consistency, and discover where traditions actually agree once ambiguity is removed.

First explorations reveal a striking result: all three Abrahamic scriptures converge on the same pan-en-theistic structure when mapped to formal axioms. If that convergence holds under rigorous scrutiny, it can defuse centuries of eschatological conflict by showing that many disagreements are verbal, not logical.

But this work requires global support to avoid capture by special interests. Refining axioms, engaging scholars across traditions, and running formal consistency checks all require sustained effort — as does real-world testing of what matheology discovers.

If you believe replacing eschatological warfare with mathematical clarity is worth pursuing before it’s too late, please fund this work — every contribution helps evolve a global ResearchCity for finding the narrow path to peace.

FF FeedbackFlow to improve this page: How you can contribute

For the full guide on providing feedback — including how it is handled, licensing, and what to expect — see How to use FeedbackFlow.

Please check if See also on Balospe.com above already addresses your idea. Feedback works best when it targets the most specific page. If none of those pages help, you may have a good case for sending FF here.

To submit your FeedbackFlow:

  1. Click anywhere on the email preview below to open a pre-filled email.

  2. Replace the placeholder text with your feedback.

  3. Send.

To: [email protected] CC: [email protected] Subject: FF k2 s2 AIMS for [jobs] Replace_by_OneLineSummary Body: To make this page [jobs] more gentle kind reasonable for beginners, producers, andOr experts with a background in xyz: Please consider improving this:

The email subject contains k2 and s2 — default codes for impact and urgency. Most contributors can leave these unchanged. To adjust each as independently as they are:

  • Importance of impact: above average k3, average default k2, below average k1.

  • Urgency of speedup: above average s3, average default s2, below average s1.

This allows plotting importance over urgency to help triage FF. For more details see FF System Design.