CareerOS-02.Works — How Education Connects to Career (Phase-3 Corridor)

# ======================================================================
# CareerOS-02.Works — How Education Connects to Career (Phase-3 Corridor)
# Version: MasterOS.v1.0 (Consolidation Protocol compliant)
# Twin Pair: CareerOS-02.NegVoid  <->  CareerOS-02.Works
# Scope: reconnect mechanism: assessment → execution; curriculum → corridors
# ======================================================================
META:
  ModuleID: CareerOS.02.Works.EducationCareerReconnect
  Slug: /how-education-connects-to-career/
  Status: CANONICAL
  Vocabulary: FROZEN (no new primitives)
  Requires:
    - CareerOS.00.Foundation
    - CareerOS.01.Master.NegVoid
    - CareerOS.02.NegVoid.EducationCareerDisconnect
  Twin:
    NegVoid: CareerOS.02.NegVoid.EducationCareerDisconnect
    Works:  CareerOS.02.Works.EducationCareerReconnect
  Roles:
    - Operator: student (practice loops), parent (support), teacher/tutor (coaching)
    - Oracle: mentor/career coach (mapping + diagnostics)
    - Visionary: school leader (system design + incentives)
    - Architect: pathway designer (corridors + gates + portfolio routes)
# ----------------------------------------------------------------------
# 1) Classical Foundation Block (mainstream)
# ----------------------------------------------------------------------
CLASSICAL_FOUNDATION:
  Alignment principles:
    - competencies + authentic assessment + experiential learning
    - internships/projects + career guidance
    - transferable skills + reflection
  Common models:
    - project-based learning, work-integrated learning, apprenticeships
# ----------------------------------------------------------------------
# 2) Civilisation-Grade Definition (locked)
# ----------------------------------------------------------------------
CIV_GRADE_DEFINITION:
  Connection:
    - Education connects to career when it outputs reliable execution capability
      under load, not only knowledge under test conditions.
  Corridor:
    - a repeated loop that stress-tests: brief → draft → feedback → revise →
      document → reattempt, until reliability stabilizes (P3 corridor).
  Core Law:
    - stability when RepairSpeed >= DriftRate under rising load.
# ----------------------------------------------------------------------
# 3) Phase Map (P0–P3) — what the connected system produces
# ----------------------------------------------------------------------
PHASE_MAP:
  P0: "Needs external rescue" (no reliable loop)
  P1: "Can execute with explicit instructions" (fragile transfer)
  P2: "Can execute standard workflows" (moderate autonomy)
  P3: "Corridor-ready" (frames, executes, updates, repairs, scales)
# ----------------------------------------------------------------------
# 4) Inequality Locks (connection guarantees)
# ----------------------------------------------------------------------
INEQUALITY_LOCKS:
  L1: ExecutionTrainingTime >= AssessmentTrainingTime   # shift objective
  L2: FeedbackLoopRate >= SkillDriftRate
  L3: TransferStrength >= ContextVariation
  L4: (Clarity × OwnershipExplicitness) >= CoordinationFriction
  L5: RepairSpeed >= DriftRate
# ----------------------------------------------------------------------
# 5) Connection Mechanism (the 7 required parts)
# ----------------------------------------------------------------------
CONNECTION_MECHANISM:
  C1_ObjectiveFunctionShift:
    From:
      - grades as primary output
    To:
      - reliable execution artifacts as primary output
    Implementation:
      - every term must produce portfolio artifacts (>= 3)
  C2_CurriculumAsCorridorRouting:
    Principle:
      - curriculum must route learners through repeated execution corridors,
        not only content coverage
    Minimum corridor:
      - brief → draft at 20% time → feedback → revise → document → reattempt
  C3_AuthenticTasksUnderLoad:
    Tasks must include:
      - ambiguity (what exactly is needed)
      - constraints (time/resources)
      - stakeholders (audience expectations)
      - evaluation (acceptance criteria)
    Reason:
      - this matches career load structure
  C4_OperationalEnglishEmbedding:
    Every project must require:
      - 6-line brief
      - weekly update with evidence
      - escalation note when blocked
      - final documentation (SOP/checklist + lessons)
  C5_ModelAndEstimateEmbedding (MathOS coupling):
    Every project must include:
      - variable list + units
      - bounding estimate
      - sanity check
      - interpretation to decision statement
  C6_InstrumentationAndSensors:
    Schools must track:
      - rework ratio
      - time-to-clarity
      - escalation latency
      - update quality
      - portfolio coverage
    Purpose:
      - detect drift early (pre-collapse)
  C7_RepairCorridor (FenceOS coupling):
    When sensors go red:
      - truncate (stop full-solution push)
      - stitch (iterate + SOP + reattempt within 7 days)
# ----------------------------------------------------------------------
# 6) Standard Corridor Loop (copy-paste runnable)
# ----------------------------------------------------------------------
STANDARD_CORRIDOR_LOOP:
  Step1_Brief:
    - goal
    - constraints
    - output
    - metric
    - owner
    - deadline
  Step2_Draft_20percent:
    - smallest viable draft delivered early
  Step3_Feedback:
    - receive critique; list changes
  Step4_Revision:
    - apply changes; improve clarity/accuracy
  Step5_Document:
    - SOP/checklist (10 lines max)
    - lessons learned (3 bullets)
  Step6_Reattempt:
    - repeat on similar task inside 7 days
    - goal: lower rework ratio; faster clarity
# ----------------------------------------------------------------------
# 7) Sensors + Thresholds (connection health)
# ----------------------------------------------------------------------
SENSORS:
  S1_ReworkRatio:
    green: < 0.20
    yellow: 0.20–0.35
    red: > 0.35
  S2_TimeToClarity:
    green: < 0.15
    yellow: 0.15–0.30
    red: > 0.30
  S3_EscalationLatency:
    red_if: "escalation occurs after deadline risk is visible"
  S4_UpdateQuality:
    green: >= 0.85
    yellow: 0.60–0.84
    red: < 0.60
  S5_PortfolioCoverage:
    green: >= 3 artifacts/term
    yellow: 1–2/term
    red: 0
# ----------------------------------------------------------------------
# 8) Collapse Prevention (3-mode guard)
# ----------------------------------------------------------------------
COLLAPSE_PREVENTION:
  Against_Amplitude_KO:
    - early drafts + validation checks + escalation scripts
  Against_Slow_Attrition:
    - artifact growth requirement + career map visibility
  Against_Fast_Attrition:
    - repair corridor (truncate + stitch) + workload calibration
# ----------------------------------------------------------------------
# 9) Output Blocks (publish)
# ----------------------------------------------------------------------
OUTPUT_BLOCKS:
  - CoreLaw: "Education connects to career when it trains repeated execution corridors under load, measured by artifacts and repair speed, not grades alone."
  - CorridorLoop: STANDARD_CORRIDOR_LOOP
  - Sensors: S1–S5 table
  - Repair: FenceOS truncation + stitching triggers
# END MODULE