Mastermind Pod Charter

Disciplined cells for building parallel institutions

This charter turns ambitious intent into accountable execution. Pods are strategic design units, not discussion clubs.

Core Principles

A pod culture that favors execution over ego loops.

Expansion over contraction Production over opinion Merit over status Alignment over ego Lawful resilience

Membership Criteria

Disciplined participation: attendance and preparation
Capacity for disagreement without destabilization
Skill, research, or execution capability
Low ideological rigidity and high accountability
Optimal pod size: 5-8 members

Rotating Roles

Facilitator

Maintains structure, pacing, and tactical focus during meetings.

Synthesizer

Translates discussion into coherent strategy outputs and decisions.

Research Lead

Collects comparative models, precedents, and evidence.

Risk Analyst

Stress tests legal, ethical, and structural weaknesses.

Implementation Strategist

Converts strategy into practical deployment pathways.

Role Rotation Rule

Rotate each cycle to prevent hierarchy ossification and skill silos.

Meeting Rhythm + Output Contract

Weekly Tactical Session (60-90 min)

10 min status updates
40 min domain strategy
20 min objections + stress testing
10 min assignments and owners

Monthly Deliverable

Written strategy packet (5-15 pages)
Roadmap, diagrams, and budget outline
Success metrics and integration points
No month ends without output

Required Strategic Document Sections

Executive summary
Strategic premise + model overview
Implementation phases (90 days / 1 year / 5 years)
Risk matrix and capital/talent requirements
Integration with other pods and domains

Inside the Pod

Speak directly and assume good intent
No performative grandstanding
Private grievances handled privately
Energy discipline and mental clarity are explicit values

Anti-Drift Protocol

Reality-test assumptions against evidence
Consult legal expertise for implementation thresholds
Reject cult dynamics and outside-world demonization
Protect dissent within the container

90-Day Pilot Framework

Month 1

Select one domain, map vulnerabilities, and evaluate three real alternatives.

Month 2

Design a minimum viable model, stress assumptions, estimate resources.

Month 3

Produce deployable blueprint, present to coordinating body, identify pilot site.