OSE Dogfooding Core Product Policy

OSE Dogfooding Core Product Policy — Implementation (On-site, Hybrid, Remote)

https://chatgpt.com/share/69d38b60-04c4-8327-93c2-16ae3c1e9bf0

1. Policy Objective

Ensure all contributors maintain embodied contact with OSE’s core production system (build → learn → design → replicate), regardless of location.

2. Applicability

Applies to:

• On-site staff
• Hybrid staff
• Fully remote staff
• Contractors with decision-making or system-design responsibilities

3. Acceptable Participation Pathways

Pathway	Description	Who Uses It	Minimum Requirement	Verification
On-Site Build Embedding	Participate in active OSE builds	On-site / hybrid roles	Per role table cadence (e.g., 1–2 days every 2–6 weeks)	Attendance logs + crew lead sign-off + output artifact
Hosted Crash Course (OSE Site)	Full immersion at OSE facility	All roles (onboarding + refresh)	Within first 90 days; then every 12–24 months	Completion certificate + competency checklist
Local Replication Build (Remote)	Build OSE modules locally using open designs	Remote staff	1 approved module per quarter (or equivalent hours)	Build log + photos/video + BOM + time/cost report
Micro-Build / Module Sprints (Remote)	Short, kitted exercises from Rapid Learning Facility	Remote / constrained roles	2–4 modules per quarter	Module checklists + media + mentor review
Partner Site Embedding	Embed at approved partner build site	Remote / traveling staff	Equivalent to on-site cadence	Partner sign-off + artifact output
Constrained Participation (Short Duration)	1–2 hour embedded sessions or remote analysis	Physically constrained roles	Every 4–6 weeks (or equivalent)	Observation notes + improvement proposal

4. Remote Staff Requirements

4.1 Baseline (Non-Negotiable)

• Complete Builder Crash Course (on-site) within 90 days of start
• Complete Rapid Learning Facility intro modules
• Complete introductory Iconic CAD training

4.2 Ongoing Participation (Choose One Primary + One Secondary)

• Primary (per quarter):
  • Local Replication Build OR Partner Site Embedding
• Secondary:
  • Micro-Build Modules OR Remote Documentation from observed builds

4.3 Minimum Quarterly Standard

A remote participant must deliver at least:

• 1 completed build/module (physical or partner-verified), AND
• 1 system improvement artifact (design, SOP, training, or media)

Failure to meet both = non-compliance.

5. Standard Artifacts (Proof of Participation)

All pathways must produce verifiable artifacts:

• Build Log:
  • Scope, steps, time spent, issues encountered
• Bill of Materials (BOM) + sourcing notes
• Media:
  • Photos/videos of key steps
• Reflection:
  • Bottlenecks, errors, improvements
• Output:
  • One of:
    • Design improvement (CAD change)
    • SOP / instruction update
    • Training module
    • Replication guide
    • Throughput improvement proposal

6. Competency Levels (Verification Gates)

Level	Description	Evidence Required
L1 Operator	Can execute basic tasks/modules	Completed modules + checklists
L2 Skilled Builder	Works independently with low error rate	Build logs + supervisor/mentor sign-off
L3 Builder–Designer	Improves systems/designs based on builds	CAD updates + measured impact
L4 System Architect	Creates reusable modules and trains others	Replication by others + documented systems

Advancement requires **measurable impact**, not course completion.

7. Cadence & Scheduling Rules

• Participation must be **scheduled in advance** (quarterly plan)
• Remote builds must be **approved for scope** before starting
• High-leverage roles may batch participation (e.g., 3–5 day immersion) instead of weekly cadence
• Core build crews remain stable; remote participation must not disrupt throughput

8. Output Accountability

Each participation cycle must answer:

1. What bottleneck did you observe?
2. What change do you propose?
3. What is the expected impact (time, cost, quality, replication)?

No artifact = no credit.

9. Tooling & Infrastructure

OSE will provide:

• Standardized module kits (RLF)
• Build documentation templates (logs, BOMs)
• Media capture guidelines
• Review/approval workflow (mentor or crew lead)
• Repository for artifacts (CAD, SOPs, training)

10. Exceptions & Adaptations

• Physical constraints: use Constrained Participation pathway
• Geographic limits: use Local Replication or Partner Sites
• Temporary waivers (≤90 days) require leadership approval and a make-up plan

11. Enforcement

Non-compliance results in:

• Loss of decision authority (for leadership/system roles)
• Restricted scope of work
• Performance review or reassignment

12. Summary Rule

No contributor may operate purely abstractly. All roles must maintain **verifiable, periodic engagement with the production system** and produce **measurable system value**.

Why Remote Staff and Participants Must Complete Builder Crash Course

Priority	Reason	What It Means	Why It Matters (Impact on OSE System)
1	Shared Ground Truth (Embodied Understanding)	Direct, hands-on experience of tools, materials, sequencing, and constraints	Eliminates abstraction error; ensures all decisions are based on real system behavior rather than assumptions
2	Decision Quality	Ability to make informed strategic, operational, and design decisions	Prevents unrealistic planning; improves allocation of time, money, and labor; reduces systemic inefficiency
3	Design Integrity	Understanding what is actually buildable, repeatable, and efficient	Avoids elegant but unbuildable designs; ensures CAD and systems translate directly into successful builds
4	Replication Capability	Ability to reproduce or support reproduction of OSE systems independently	Enables scaling through distributed production; turns participants into node creators rather than passive contributors
5	Credible Communication (Ambassadorship)	Ability to accurately represent OSE work in media, outreach, and teaching	Builds trust and adoption; prevents overpromising; produces instructional, not just promotional, content

Summary

Builder Crash Course for remote participants is required not primarily for branding, but to ensure:

• Alignment with real-world production constraints
• High-quality decisions and designs
• Scalable replication of OSE systems
• Credible and effective communication