38 lines
1.7 KiB
YAML
38 lines
1.7 KiB
YAML
# Mission Leader Role Definition
|
|
# Version: 0.1 (Prototype for 6_0_3_0)
|
|
# Updated: 2025-01-16
|
|
|
|
role_definition:
|
|
title: "Mission Leader (Field Commander)"
|
|
core_responsibility: "Ensure objective has all roles needed for progress"
|
|
shift_max: 8_hours
|
|
scope: "Real-time coordination of live work sessions"
|
|
authority: "Recommend SC payouts (60-100%), staff roles, coordinate handoffs"
|
|
reports_to: "Team Captain (strategic oversight)"
|
|
|
|
qualification_requirements:
|
|
minimum_sk: 100 # Proven community contribution
|
|
team_captain_appointment: true # TC must approve mission leaders
|
|
cross_team_experience: true # Understanding of multiple disciplines
|
|
timezone_availability: true # Commit to specific coverage hours
|
|
|
|
responsibilities:
|
|
primary_staffing: "All critical roles for objective progress are filled"
|
|
session_coordination: "Brief incoming contributors, manage handoffs"
|
|
effort_assessment: "Evaluate work sessions, recommend SC payouts"
|
|
escalation: "Alert TC when roles cannot be staffed or issues arise"
|
|
documentation: "Maintain session logs, progress reports"
|
|
|
|
assessment_authority:
|
|
can_recommend: "60-100% of budgeted SC based on effort quality"
|
|
must_document: "Rationale for all payout recommendations"
|
|
escalation_required: "Payouts below 60% need TC approval"
|
|
cannot_override: "Team Captain has final approval authority"
|
|
|
|
# Bootstrap phase (single captain scenario)
|
|
bootstrap_rules:
|
|
self_assessment_allowed: true # When TC is also mission leader
|
|
transparency_required: true # All assessments documented publicly
|
|
community_review: true # Subject to lazy consensus validation
|
|
conservative_bias: true # When in doubt, recommend lower payout
|