Skip to content

starspacegroup/principles

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 

Repository files navigation

*Space Principles

Passenger Expectations:

  1. Know your limits—then expand them "Track. Train. Thrive."
  2. Master your role—and back up theirs "Own it. Cover it. Keep us alive."
  3. Put the habitat first "Your breath is mine. Mine is yours."
  4. Share info—no filters "Truth now. Survival later."
  5. Do it right—every time "Protocol isn’t optional. It’s oxygen."
  6. Clarify, check, finish "Say it. See it. Done."
  7. Train together—like it’s real "We die in sims—so we live out here."
  8. Decide quick, own it "Think fast. Act faster. Stand by it."
  9. Own your screw-ups—then fix them "I broke it. I’ll mend it. We move on."

Leadership Directives:

  1. Grow backups—then step aside "Build them strong. Then vanish."
  2. Match plans to what we actually have "No dreams. Just what works."

Space Core Tenants Documentation

Version 1.0
Starspace.group
Core Principles for Collective Survival and Performance

This document outlines the 11 foundational tenets that guide every individual and leader in high-stakes, interdependent environments. Each chapter explains one tenant in detail: its meaning, rationale, practical application, and expected behaviors.

Chapter 1: Know your limits—then expand them

Self-awareness of current physical, mental, and technical capabilities is the starting point. Regularly assess strengths and weaknesses through deliberate testing and feedback.
Once identified, address gaps via structured training: skill drills, endurance work, scenario practice, and recovery protocols.
Rationale: Unrecognized limitations become failure points under stress. Continuous expansion ensures reliability over time.
Expected behaviors: Maintain personal logs of performance metrics; schedule deliberate practice sessions; seek honest external feedback; never accept "good enough" as permanent.

Chapter 2: Master your role—and back up theirs

Achieve deep proficiency in your assigned primary function (technical, operational, or support). Simultaneously acquire working knowledge of adjacent and critical overlapping roles.
Rationale: Single-point failures are unacceptable when redundancy is limited. Cross-capability reduces risk and enables continuity during absences or overloads.
Expected behaviors: Complete role-specific certification; participate in cross-training rotations; demonstrate competence in backup tasks during exercises; document procedures for handover.

Chapter 3: Put the habitat first

Prioritize the collective well-being and system integrity above personal convenience or individual goals. Monitor teammates for signs of fatigue, error, or distress and intervene early.
Rationale: Interdependence means one person's decline affects everyone. Collective health directly determines operational sustainability.
Expected behaviors: Perform welfare checks; share resources proactively; report concerns without hesitation; accept personal discomfort to maintain group stability.

Chapter 4: Share info—no filters

Communicate observations, status updates, anomalies, and concerns clearly, promptly, and factually—without exaggeration, minimization, or omission.
Rationale: Incomplete or delayed information leads to poor decisions. Transparency enables rapid, accurate collective response.
Expected behaviors: Use standard reporting formats; state facts first, then interpretation; avoid hedging language; confirm receipt and understanding when critical.

Chapter 5: Do it right—every time

Adhere strictly to established procedures, checklists, and safety standards regardless of familiarity, time pressure, or perceived low risk.
Rationale: Protocols exist because past failures identified necessary safeguards. Deviations introduce preventable risk. Consistency builds system reliability.
Expected behaviors: Follow written steps verbatim when required; use read-back verification; never bypass steps "just this once"; call out observed deviations by others.

Chapter 6: Clarify, check, finish

Ensure every assigned task is clearly understood by the executor, actively supervised when necessary, and verifiably completed to standard.
Rationale: Miscommunication or unmonitored execution creates hidden failure modes. Closed-loop communication eliminates assumptions.
Expected behaviors: State objectives and constraints explicitly; request confirmation of understanding; provide oversight on high-risk tasks; confirm completion with evidence (logs, photos, tests).

Chapter 7: Train together—like it’s real

Conduct joint training and simulations that replicate actual conditions of stress, time pressure, degraded systems, and uncertainty.
Rationale: Isolated individual skill does not guarantee coordinated performance. Shared experience under realistic difficulty builds automatic teamwork and trust.
Expected behaviors: Participate fully in team drills; debrief honestly after every session; incorporate lessons into future training; treat simulations with the same seriousness as live operations.

Chapter 8: Decide quick, own it

When time is limited and data is incomplete, select the best available course of action, execute decisively, and accept full responsibility for the outcome.
Rationale: Paralysis or excessive delay compounds risk. Ownership prevents blame-shifting and accelerates learning.
Expected behaviors: Use structured decision frameworks under pressure; communicate the decision and rationale; evaluate results objectively; adjust future decisions based on outcomes.

Chapter 9: Own your screw-ups—then fix them

Immediately acknowledge errors or near-misses, describe what happened without excuses, implement corrections, and share lessons to prevent recurrence.
Rationale: Evasion wastes time and erodes trust. Rapid ownership turns mistakes into system improvements.
Expected behaviors: Report incidents promptly; write concise after-action notes; propose preventive measures; assist in implementing fixes; never repeat the same error.

For Leadership Roles:

Chapter 10: Grow backups—then step aside (Leadership Tenet)

Actively develop competence and decision-making capacity in subordinates through delegation, mentoring, and increasing responsibility. Prepare successors so the organization remains effective without any single individual.
Rationale: Centralized knowledge or authority creates fragility. Distributed capability ensures long-term resilience.
Expected behaviors: Assign meaningful tasks with real authority; provide coaching and feedback; gradually reduce direct involvement; evaluate and promote based on demonstrated performance.

Chapter 11: Match plans to what we actually have (Leadership Tenet)

Design objectives, timelines, and resource allocations based on current verified capabilities—personnel skill levels, equipment condition, consumables, and environmental constraints—not on aspirations or external pressure.
Rationale: Over-optimistic planning leads to exhaustion, failure, or cascading breakdowns. Realistic employment preserves capacity for future operations.
Expected behaviors: Conduct capability assessments before approving plans; reject or scale missions that exceed limits; document rationale for scope decisions; adjust plans when conditions change.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors