OSE Dogfooding Core Product Policy

From Open Source Ecology
Revision as of 10:23, 6 April 2026 by Marcin (talk | contribs) (Created page with "= OSE Dogfooding Core Product Policy (Summary Table) = {| class="wikitable sortable" ! Role Type ! Full System Immersion (Crash Course + RLF + CAD) ! Ongoing Build Participation ! Participation Mode ! Required Output ! Purpose / Rationale |- | Core Builders | Required (onboarding + periodic refresh) | 4–5 days/week | Full production roles | Build completion, quality, speed, mentoring | Primary revenue engine; execution excellence |- | Deep Generalists (Apprentices / H...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

OSE Dogfooding Core Product Policy (Summary Table)

Role Type Full System Immersion (Crash Course + RLF + CAD) Ongoing Build Participation Participation Mode Required Output Purpose / Rationale
Core Builders Required (onboarding + periodic refresh) 4–5 days/week Full production roles Build completion, quality, speed, mentoring Primary revenue engine; execution excellence
Deep Generalists (Apprentices / Hybrid Roles) Required (onboarding + periodic refresh) 2 days/week Structured crew participation + learning Skill progression, design feedback, documentation Train builder–designers; integrate learning + production
CAD / Engineering Required (onboarding + periodic refresh) 1–2 days every 2–4 weeks Assigned build tasks tied to design systems Design improvements, reduced errors, build optimization Ensure designs are buildable and replicable
Curriculum / Training Required (onboarding + periodic refresh) 1–2 days every 2–4 weeks Participate + observe training gaps New modules, improved training workflows Align instruction with real build conditions
Marketing / Media Required (onboarding + periodic refresh) 1–2 days every 4–6 weeks Participate + document real workflows Instructional content, storytelling, replication assets Ensure messaging reflects real, replicable systems
Strategy / Leadership Required (onboarding + periodic refresh) 2–5 days every 8–12 weeks Deep immersion in active builds Bottleneck analysis, system optimization proposals Maintain alignment with economic engine + constraints
Spiritual / Community Leader Required (light version acceptable) 1 day every 6–8 weeks Partial participation + observation Insights on morale, cohesion, cultural improvements Maintain credibility and support human system dynamics
External Advisors (Optional) Not required Optional / none Observation or periodic engagement Advisory input only No operational authority; external perspective only

Core Policy Principle

All staff must dogfood the core production system to maintain alignment with OSE’s mission of creating replicable, economically viable production systems.

Minimum Standard

No role may operate purely abstractly; all internal leadership and system-design roles require embodied contact with production.

Output Requirement

Each participation cycle must produce measurable system value:

  • Increased throughput
  • Reduced cost or errors
  • Improved training or documentation
  • Enhanced replicability

Enforcement

Failure to maintain dogfooding participation may result in:

  • Loss of decision authority
  • Role reassignment
  • Performance review