🌍 World Crumb Policy

Global Framework for Safe, Local-First, Child-Centered Learning Spaces

Version: 1.0
Status: Policy Framework
Scope: Universal
Languages: Multilingual (base: EN/DE)

1. Purpose & Scope

This policy defines the universal principles and operational boundaries for any implementation of child-centered, technology-assisted learning spaces worldwide.

Applies to:
- Schools
- NGOs
- Community centers
- Refugee camps
- Rural education hubs
- Low-resource environments
- Maker spaces
- Research institutions

Does NOT apply to:
- Commercial edtech platforms
- Surveillance systems
- Data-harvesting applications
- Cloud-only services
- Gamified learning apps
- Performance measurement tools

2. Universal Principles (Non-Negotiable)

Every implementation, in every context, must adhere to:

2.1 Child First

Priority Order:
  1. Child safety & wellbeing
  2. System integrity
  3. Adult convenience

Decision Test:
  "Does this protect the child first,
   the system second,
   and the adult last?"

  If YES → Proceed
  If NO → Stop

2.2 Local First

Operation:
  ✅ Offline by default
  ✅ Local network only
  ✅ No cloud dependency
  ✅ Community-controlled
  ❌ No internet requirement
  ❌ No central servers
  ❌ No external dependencies

2.3 No Identity

Zero Data Collection:
  ❌ No names
  ❌ No emails
  ❌ No biometrics
  ❌ No photos
  ❌ No audio recordings
  ❌ No permanent accounts
  ❌ No tracking

Temporary Only:
  ✅ 24h session tokens
  ✅ Local configurations
  ✅ Technical logs (anonymous)

2.4 Structural Safety

Safety Through:
  ✅ Hardware boundaries (FPGA, VLAN)
  ✅ Network isolation
  ✅ Physical supervision
  ✅ Transparent operation
  ✅ Reversible states

NOT Through:
  ❌ User restrictions
  ❌ Data collection
  ❌ Surveillance
  ❌ Performance tracking

2.5 Right to Complexity

Children Have Right To:
  ✅ Direct system access
  ✅ Admin rights (in safe structure)
  ✅ Source code visibility
  ✅ Low-level exploration
  ✅ Error without shame
  ✅ Slow learning pace
  ✅ Exploration without measurement

Children Do NOT Need:
  ❌ Simplified systems
  ❌ "Child-friendly" hiding
  ❌ Protection from complexity
  ❌ Performance pressure
  ❌ Gamification

2.6 Adult Presence

Required:
  ✅ Trained adult always present
  ✅ Support, not control
  ✅ Observation, not judgment
  ✅ Available, not intrusive

Forbidden:
  ❌ Unsupervised sessions
  ❌ Performance pressure
  ❌ Punishment for errors
  ❌ Comparison between children

2.7 Transparency

Must Be Visible:
  ✅ How system works
  ✅ What data exists (minimal)
  ✅ Why rules exist
  ✅ How to reset/undo
  ✅ Where information goes

Must NOT Be Hidden:
  ❌ System operation
  ❌ Data processing
  ❌ Decision logic
  ❌ Safety boundaries

2.8 Reversibility

Everything Must Be:
  ✅ Undoable
  ✅ Resettable
  ✅ Recoverable
  ✅ Non-permanent

No Irreversible:
  ❌ Data storage
  ❌ Account creation
  ❌ Identity linking
  ❌ Permanent consequences

3. Absolute Red Lines (STOP Conditions)

If ANY of these are present → STOP DEPLOYMENT IMMEDIATELY

❌ Long-term user identifiers
❌ Permanent accounts
❌ Cloud-only operation
❌ Internet dependency
❌ Personal data collection
❌ Biometric storage
❌ Photo/video retention
❌ Performance ranking systems
❌ Leaderboards or timers
❌ Adult-only control (no child agency)
❌ Hidden operations
❌ Unsupervised interaction
❌ Dual-use capabilities
❌ Surveillance features
❌ Ideology injection
❌ Political messaging
❌ Religious evangelism
❌ Commercial advertising

4. Required Green Lights (GO Conditions)

All must be present for deployment:

✅ Local-only operation
✅ Hardware-enforced limits
✅ No personal data
✅ Temporary access only (≤24h)
✅ Clear safety boundaries
✅ Adult supervision always present
✅ Transparent logs
✅ Zero gamification
✅ Curiosity-driven learning
✅ Cultural neutrality
✅ Everything reversible
✅ Open documentation
✅ Community ownership possible

5. Context Adaptation Matrix

5.1 High-Infrastructure Contexts (EU, North America, etc.)

Requirements:
  ✅ GDPR/COPPA compliance
  ✅ VLAN isolation
  ✅ DSFA (Data Protection Impact Assessment)
  ✅ Formal safeguarding policies
  ✅ Background checks for adults

Optional:
  ○ Integration with school systems
  ○ Parental consent mechanisms
  ○ Regular audits

5.2 Low-Infrastructure Contexts (Sub-Saharan Africa, Rural Asia, etc.)

Requirements:
  ✅ Offline-first (no internet assumption)
  ✅ Solar/battery operation
  ✅ Low-cost hardware (Raspberry Pi, ESP32)
  ✅ Locally repairable
  ✅ Community training simple

Adaptations:
  ○ Simplified rituals
  ○ Pictorial documentation
  ○ Oral tradition integration

5.3 Conflict/Fragile Zones

Requirements:
  ✅ Zero identity exposure
  ✅ No sensitive data logging
  ✅ Physical safety paramount
  ✅ Rapid deployment/teardown
  ✅ No permanent installations

Critical:
  ⚠️ No data that could endanger children
  ⚠️ No tracking of attendance
  ⚠️ No photography

5.4 Indigenous/Cultural Contexts

Requirements:
  ✅ Community consultation BEFORE entry
  ✅ Respect for local knowledge systems
  ✅ Cultural adaptation allowed
  ✅ Language localization
  ✅ Elder involvement

Forbidden:
  ❌ Imposing external values
  ❌ Disrupting social structures
  ❌ Commercial extraction

5.5 Volunteer-Driven Contexts (Hackerspaces, Community Centers)

Requirements:
  ✅ Low technical complexity
  ✅ Volunteer training < 1 day
  ✅ Self-service documentation
  ✅ No specialized equipment
  ✅ Peer support network

Simplified:
  ○ Reduced feature set OK
  ○ "Good enough" acceptable
  ○ Iteration encouraged

6. Dual-Use Boundaries (Absolute)

Based on 23 years of experience (DroneMasters 2015-2025):

6.1 Forbidden Parallel Activities

❌ NEVER run education AND security training in same organization
❌ NEVER teach children X while training adults to defend against X
❌ NEVER use same technology for civilian AND military purposes
❌ NEVER combine child education with law enforcement training

6.2 Technology Restrictions

Forbidden Technologies:
  ❌ Drones (weaponizable)
  ❌ Facial recognition (surveillance)
  ❌ Biometric systems (identity exposure)
  ❌ Targeting systems
  ❌ Dual-use AI (can be weaponized)
  ❌ Tracking devices

Allowed Technologies:
  ✅ LEDs (not weaponizable)
  ✅ Microcontrollers (safe, educational)
  ✅ Local servers (no cloud risk)
  ✅ Simple robotics (if clearly educational)
  ✅ Art tools
  ✅ Music instruments

6.3 The Checklist (Before Building)

☐ Can this technology become a weapon?
   If YES → Don't or change technology

☐ Would military want this technology?
   If YES → Dual-use, reconsider

☐ Can this technology surveil?
   If YES → Only if structurally local + safe

☐ Do we offer "defense" training simultaneously?
   If YES → STOP, doesn't work

☐ Can we honestly explain to children?
   If "we build X but it can be used for Y" and Y=killing → Don't

☐ Can we sleep at night?
   If NO → Listen to conscience

☐ Would we build it after visiting Kigali Memorial?
   If NO → Then don't build it at all

7. Pedagogy Requirements

7.1 Learning Philosophy

Must Support:
  ✅ Exploration over performance
  ✅ Curiosity over curriculum
  ✅ Understanding over memorization
  ✅ Process over product
  ✅ Questions over answers
  ✅ Error as data, not failure

Must NOT Include:
  ❌ Ranking systems
  ❌ Performance metrics
  ❌ Time pressure
  ❌ Competitive elements
  ❌ External rewards
  ❌ Punishment for mistakes

7.2 The 8 Rights (Universal)

1. Right to Direct System Access
   → See memory, understand internals

2. Right to Admin (in safe structure)
   → Root access in isolated container

3. Right to Exploration Without Measurement
   → No scores, timers, leaderboards

4. Right to Real Complexity
   → Truth, not "child-friendly" hiding

5. Right to Errors (without shame)
   → Crash = learning opportunity

6. Right to Source (not just binary)
   → Read, modify, understand code

7. Right to Low-Level Access
   → Assembly, registers, hardware if desired

8. Right to Slow (without pressure)
   → Own pace, no curriculum stress

7.3 Adult Role

Adults Must:
  ✅ Be present (supervision)
  ✅ Observe without judgment
  ✅ Support when asked
  ✅ Explain when needed
  ✅ Ensure physical safety
  ✅ Maintain boundaries

Adults Must NOT:
  ❌ Direct learning
  ❌ Impose structure
  ❌ Create pressure
  ❌ Compare children
  ❌ Judge performance
  ❌ Solve for children

8. Technical Requirements

8.1 Minimum Standards

Required:
  ✅ Offline capability
  ✅ Local network isolation (VLAN)
  ✅ Hardware boundaries (FPGA or equivalent)
  ✅ Reset capability (<60 seconds)
  ✅ Anonymous technical logs only
  ✅ Open documentation

Optional:
  ○ Internet gateway (heavily filtered, logged)
  ○ External updates (manual, audited)
  ○ Cloud backup (encrypted, no identity)

8.2 Safety Architecture

Layers:
  1. Hardware (FPGA, VLAN, physical isolation)
  2. Network (local only, no WAN)
  3. Software (minimal privileges, sandboxed)
  4. Process (adult supervision, clear rules)
  5. Recovery (full reset always possible)

8.3 Data Minimization

Store ONLY:
  ✅ Temporary session tokens (24h max)
  ✅ Local system configurations
  ✅ Technical logs (IP, timestamp, action)

NEVER Store:
  ❌ Names
  ❌ Birthdays
  ❌ Addresses
  ❌ Photos
  ❌ Audio
  ❌ Biometrics
  ❌ Long-term profiles
  ❌ Behavioral patterns

9. Deployment Checklist

9.1 Before Deployment (Go/No-Go)

☐ All 8 Universal Principles adhered to?
☐ No red lines crossed?
☐ All green lights present?
☐ Context-specific requirements met?
☐ Adult training completed?
☐ Physical space safe?
☐ Technical systems tested?
☐ Emergency procedures documented?
☐ Community consultation done (if applicable)?
☐ Dual-use check passed?

9.2 During Operation

Daily:
  ☐ Adult supervision present?
  ☐ Systems functioning?
  ☐ Children safe and engaged?

Weekly:
  ☐ Technical logs reviewed (anonymous)?
  ☐ Safety incidents logged?
  ☐ Community feedback gathered?

Monthly:
  ☐ Full system audit?
  ☐ Documentation updated?
  ☐ Training needs identified?

9.3 Incident Response

If ANY safety concern:
  1. Stop activity immediately
  2. Ensure children safe
  3. Document incident (no personal data)
  4. Notify coordinators
  5. Review and adapt
  6. Transparent communication

10. Verification & Compliance

10.1 Self-Assessment

Every implementation must complete:
- GLOBAL_TEST_MATRIX v0.2 (8 dimensions)
- Wald-Testmatrix v0.1 (if German context)
- Context-specific requirements checklist

10.2 External Audit (Optional)

Recommended for:
  - Large-scale deployments
  - Vulnerable populations
  - Funded programs
  - Research contexts

Audit Covers:
  ☐ Technical safety
  ☐ Child protection
  ☐ Data minimization
  ☐ Pedagogical alignment
  ☐ Cultural appropriateness

10.3 Continuous Improvement

Required:
  ✅ Regular safety reviews
  ✅ Community feedback integration
  ✅ Incident learning
  ✅ Documentation updates
  ✅ Shared learnings with network

11. Governance & Ownership

11.1 Open Source + Boundaries

Open:
  ✅ Fork freely
  ✅ Adapt to context
  ✅ Translate to language
  ✅ Share improvements
  ✅ Create variations

Bounded:
  ❌ Cannot remove child protection
  ❌ Cannot add data collection
  ❌ Cannot add cloud dependency
  ❌ Cannot add dual-use features
  ❌ Cannot add gamification

11.2 Community Ownership

Every implementation should strive for:
  ✅ Local ownership (not external dependency)
  ✅ Community control (not corporate)
  ✅ Cultural adaptation (not imposition)
  ✅ Knowledge transfer (not vendor lock-in)
  ✅ Sustainability (not aid dependency)

11.3 Network Support

Implementations can:
  ✅ Join global network (optional)
  ✅ Share learnings
  ✅ Get peer support
  ✅ Contribute improvements
  ✅ Remain autonomous

Network provides:
  ○ Documentation
  ○ Training resources
  ○ Peer connections
  ○ Technical support
  ○ Funding guidance

12. Success Definition

A deployment is successful when:

✅ Children are safe (zero incidents)
✅ Children are curious (engagement high)
✅ Children are learning (visible growth)
✅ Adults are supporting (not controlling)
✅ System is stable (minimal intervention)
✅ Community is owning (sustainable)
✅ No data is leaking (privacy intact)
✅ Boundaries are holding (safety maintained)

Measured by:
- Child safety (zero tolerance for violations)
- Engagement (voluntary return rate)
- Understanding (can explain system)
- System stability (uptime, resets needed)
- Community satisfaction (feedback)

NOT measured by:
- Test scores
- Completion rates
- Performance metrics
- Comparative rankings
- Time on task

13. International Alignment

This policy aligns with and supports:

UNICEF:
  ✓ Child-Friendly Spaces
  ✓ Digital Public Goods
  ✓ Safeguarding Standards

UNESCO:
  ✓ Education for Sustainable Development
  ✓ Global Citizenship Education
  ✓ Digital Literacy

UN Convention on the Rights of the Child:
  ✓ Article 3 (Best interests of child)
  ✓ Article 16 (Privacy)
  ✓ Article 31 (Leisure, play, culture)

GDPR / Data Protection:
  ✓ Data minimization
  ✓ Purpose limitation
  ✓ Storage limitation
  ✓ Privacy by design

Humanitarian Standards:
  ✓ Sphere Handbook
  ✓ INEE Minimum Standards
  ✓ Core Humanitarian Standard (CHS)

14. Conclusion

World Crumb Policy defines the universal framework for safe, local-first, child-centered learning spaces.

It is:
- Non-negotiable on safety
- Flexible on implementation
- Universal in principle
- Adaptable in practice

It protects:
- Children first
- Communities second
- Systems third

It enables:
- Local ownership
- Cultural adaptation
- Global collaboration
- Sustainable impact

Version: 1.0
Status: Active Policy Framework
Scope: Universal (all implementations)
Review: Annual or as needed
Contact: [Your contact method]

💚🌍🌲

For children. Worldwide. Always.