FBA Programs Nomenclature

Intent

We train civilization engineers, form new enterprises, and upgrade existing ones to build open, regenerative infrastructure at planetary scale.

New concept emerges - OSE Doctrine: Capability Induction

Sequencing

Nothing launches that requires founder to be the bottleneck. We launch programs in the order that reduces founder load fastest.

Advancement

Never advance someone because they want it. Advance them because they are ready.

Canonical Program Tracks

Civilization Engineering Track (CET)

Engineer civilization-scale systems

• Replaces “Civilization Design”
• Focused on rigor, constraints, and accountability
• Core activities:
  • Systems architecture
  • Research → abstraction → schemas
  • Product definitions
  • Interface standards
  • Documentation canon
  • Pre-enterprise productization
• Audience:
  • Researchers, deep generalists, system builders
  • People seeking high-consequence work on hard global problems
• Key message:
  • This is not a design program. This is where civilization-scale systems are engineered.

Enterprise Formation Track (EFT)

Form new civilization-aligned enterprises

• For builders transitioning into entrepreneurship
• Emphasizes difficulty, discipline, and market contact
• Purpose:
  • Launch new ventures grounded in open, civilizational infrastructure
• Clear signal:
  • This is enterprise formation, not ideation theater

Enterprise Advancement Track (EAT)

Upgrade existing enterprises into civilization-grade infrastructure

• For operating businesses with real revenue
• Supports conversion to open-source, GVCS-grade systems
• Examples:
  • Farms, factories, utilities
  • Existing manufacturers opening designs
• Key framing:
  • This track upgrades what already works into civilization-scale infrastructure

Civilization Builder Orientation (CBO)

Explore before committing

• Lightweight gateway layer (2–4 weeks)
• For:
  • Curious or early-stage participants
  • Those unsure or intimidated by engineering language
• Introduces:
  • Civilization-scale problems
  • Open source as strategy
  • Systems thinking
  • Moral intelligence
• Outcomes:
  • Self-selection into CET, EFT, or EAT — or exit

More about Civilization Builder Orientation

Sequencing

• See FBA Rollout

Fandom

Civilization Commons — “The Civilization Commons is the public layer of participation for people who want to follow, learn from, and support civilization-scale open engineering without enrolling in formal tracks.”

Why a Fandom Layer Is Legitimate (and Necessary) =

At civilization scale, you will always have:

• People who resonate deeply with the mission
• People who want to watch, learn, follow, and support
• People who are not ready (or able) to commit to engineering or enterprise
• People who should not be allowed into core tracks yet

If you do not provide a proper container for this group, they will:

• Lurk noisily
• Demand access
• Drain explanation energy
• Create parasocial founder load

Therefore, a fandom layer is not optional. It is required.

However, it must operate on a one-way value flow by default. The system provides insight, visibility, and narrative. The core does not absorb obligation, debate, or emotional labor.

“Civilization Design (CD)” Name Is Not Correct

“Civilization Design” name fails in three ways:

• “Design” is culturally corrupted
  • Implies aesthetics, UX, CAD, architecture-as-style
  • Suggests low consequence, subjective output
  • Attracts people optimized for slides, not systems

• It undersignals rigor
  • Does not clearly imply engineering discipline
  • Does not imply accountability to reality
  • Sounds adjacent to speculative futurism

• It undersignals economic seriousness
  • Not obvious that outputs feed enterprise
  • Sounds “pre-business” rather than “proto-industry”