Intent-Driven Gaming & Development with SAIF Process
Navigate directly to what you need - no scrolling required:
| I want to... | Start Here | Time |
|---|---|---|
| 🎮 Play games on Linux | Gaming Pathway | 15 min |
| 💻 Develop with AI assistance | Development Pathway | 20 min |
| 🔧 Fix system issues | Recovery Pathway | Varies |
| 🚀 Migrate from Windows | Migration Pathway | 1-2 hrs |
| 📖 Learn the framework | Learning Pathway | Self-paced |
| 🤖 AI Agent on repo | Agent Pathway | N/A |
Full guided setup: 📚 GETTING-STARTED.md
# 1. Clone KENL
git clone https://github.com/toolate28/kenl.git ~/.kenl && cd ~/.kenl
# 2. Choose your pathway above (terminal or Obsidian - your choice)
# 3. Follow the guided checklist for your goalPowerShell profile for dynamic banners (optional):
. ~/.kenl/scripts/Install-KenlProfile.ps1KENL transforms your system into a self-documenting, intent-driven platform with:
- 🎮 Shareable game configurations (Play Cards)
- 💻 AI-assisted development (Claude Code, Ollama/Qwen, MCP)
- 🔧 Automated system recovery (BattleMedic)
- 📋 Complete audit trails (ATOM tags)
- ↩️ Rollback safety (every operation is reversible)
Core Belief:
"AI tools should enhance humans, not replace them. Documentation captures intent so humans remain authoritative, even when AI assists."
KENL/SAIF exists because:
- Knowledge is expensive to acquire - Years of expertise shouldn't walk out the door when someone quits
- Intent matters more than actions - "What" without "why" breaks when assumptions change
- Transparency builds trust - Customers/users deserve to know what AI generated and what humans reviewed
- Reproducibility scales expertise - Proven solutions should be shareable, not rediscovered every time
- Confidentiality is real - Not everything should be public. Multi-tier system protects customer privacy
- Rollback is essential - Changes should be reversible. Safety net enables experimentation
HALO wouldn't launch. EA App auth errors, anti-cheat failures, 174ms network latency. After hours of troubleshooting: it works. But how? What fixed it? Can you reproduce it?
KENL captures the why behind every fix, not just the what. If it breaks again, recovery takes minutes instead of hours - because you already documented the solution.
Real example: ATOM-GAMING-001: HALO won't launch → ATOM-RESEARCH-002: ProtonDB suggests GE-Proton 9-20 → ATOM-CFG-003: Applied fix → ATOM-PLAYCARD-006: Created shareable config
Result: Next time HALO breaks, recovery takes <10 minutes instead of hours. Share the Play Card - others skip your pain entirely.
We stand on shoulders, not on toes. KENL doesn't provide better tools - it provides better access to the excellent work already done by the Respective Dev/Contributor communities1.
| Pillar | Purpose | Example |
|---|---|---|
| KENL | Distrobox tooling for Gaming + Development | Isolated dev containers, no system deps |
| ATOM | Intent logging (the why, not just what) | claude-landing/RECENT-WORK.md |
| OWI | Operating-With-Intent (AI + MCP integration) | Play Cards: shareable game configs |
| SAGE | Just-in-time documentation | claude-landing/ orientation docs |
Technical Guarantees:
- Elegant Integration: Distrobox isolation • JSON-RPC MCP • Pure POSIX shell
- Minimal Overhead: ~0.1ms ATOM logging • Static YAML Play Cards • Copy-on-write filesystem
- Breaking-Change Proof: Immutable rpm-ostree base • User-space only (
~/.local) • Atomic GRUB rollback
Every KENL operation includes rollback instructions.
graph TD
User[👤 User] --> Start[📚 GETTING-STARTED.md]
Start --> Pathway{Select Pathway}
Pathway --> |Gaming| KENL2[🎮 KENL2-gaming]
Pathway --> |Development| KENL3[💻 KENL3-dev]
Pathway --> |Recovery| BM[🔧 BattleMedic]
Pathway --> |Migration| KENL0[⚙️ KENL0-system]
KENL2 --> ATOM[🏷️ ATOM Trails]
KENL3 --> ATOM
BM --> ATOM
KENL0 --> ATOM
ATOM --> DB[(SQLite + Cloudflare D1)]
style Start fill:#5865F2,color:#fff
style ATOM fill:#57F287,color:#000
style KENL2 fill:#ED4245,color:#fff
style KENL3 fill:#00AFF4,color:#fff
style BM fill:#FEE75C,color:#000
style KENL0 fill:#845EF7,color:#fff
Detailed pathway documentation: 📁 DOCUMENTATION-PATHWAYS.md
| Pathway | Description | Quick Start |
|---|---|---|
| 🎮 Gaming | Play Cards, Proton optimization | ./modules/KENL2-gaming/research-game.sh "Game" |
| 💻 Development | AI-assisted dev with Ollama/Claude | distrobox create -n kenl-dev |
| 🔧 Recovery | BattleMedic diagnostics | Import-Module BattleMedic |
| 🚀 Migration | Windows → Linux dual-boot | See partition scripts |
| 📖 Learning | Cheatsheets, case studies | Browse KENL7-learning |
| 🤖 Agent | AI Agent system integration | Read AI-AGENT-SYSTEM.md |
14 specialized layers (KENL0-13) that work together:
| Module | Purpose | Module | Purpose |
|---|---|---|---|
| KENL0 System | rpm-ostree, firmware, PowerShell modules | KENL7 Learning | Guides, cheatsheets |
| KENL1 Framework | ATOM + SAGE core | KENL8 Security | GPG, SSH, encryption |
| KENL2 Gaming | Play Cards, Proton | KENL9 Library | Game management |
| KENL3 Development | Distrobox, Claude Code, Ollama/Qwen, MCP | KENL10 Backup | Snapshots, recovery |
| KENL4 Monitoring | Prometheus, Grafana, ATOM DB | KENL11 Media | Streaming, Docker |
| KENL5 Facades | Visual themes, context | KENL12 Resources | Downloads, community |
| KENL6 Social | Sharing, community | KENL13 IWI | Intent-With-Insight |
Each module has its own README - navigate to modules/KENLX-<name>/ and start there.
graph TB
subgraph Gaming["🎮 Gaming Stack"]
KENL2[KENL2 Gaming]
KENL6[KENL6 Social]
KENL9[KENL9 Library]
end
subgraph Development["💻 Development Stack"]
KENL3[KENL3 Development]
KENL7[KENL7 Learning]
KENL8[KENL8 Security]
end
subgraph Operations["⚙️ Operations Stack"]
KENL4[KENL4 Monitoring]
KENL10[KENL10 Backup]
KENL11[KENL11 Media]
end
subgraph Resources["📦 Resources Stack"]
KENL5[KENL5 Facades]
KENL12[KENL12 Resources]
KENL13[KENL13 IWI]
end
subgraph Core["🔧 Core Framework"]
KENL0[KENL0 System]
KENL1[KENL1 Framework]
end
Gaming --> Core
Development --> Core
Operations --> Core
Resources --> Core
Core --> Immutable[Bazzite Immutable OS]
style Core fill:#5865F2,color:#fff
style Gaming fill:#ED4245,color:#fff
style Development fill:#00AFF4,color:#fff
style Operations fill:#57F287,color:#000
style Resources fill:#FEE75C,color:#000
🔍 Complete Audit Trails: ATOM tags track every change with why, not just what. When crashes happen, you know exactly what broke and how to fix it (85% faster recovery2)
📋 Shareable Play Cards: Document game configs as YAML (example config). Share with friends - they skip your troubleshooting pain entirely.
🎮 Linux Gaming Ready: 89.7% of Windows games now run on Linux via Proton3, with 15,855+ games rated playable on ProtonDB and 21,694+ Deck Verified games.
🤖 Local AI Integration: Run Qwen models locally for zero-cost code assistance (Ollama/Qwen setup guide). Integrate Claude with KENL tools via MCP (MCP integration guide).
🛡️ Security-First: ATOM database architecture prevents malicious Play Cards with schema validation, AI safety scoring, and user approval gates.
🎨 Visual Context Switching: Shell themes prevent mistakes (🎮 KENL2 for gaming, 💻 KENL3 for dev, ⚙️ KENL0 for system ops)
🪟 Windows 10 EOL Support: Migration guides for 240M+ PCs affected by Oct 14, 2025 end of support4
🧭 Full Navigation Hub: DOCUMENTATION-PATHWAYS.md 📋 Document Index: DOCUMENT-INDEX.md - 1-line review of all root documents
| Audience | Start Here | Next Step |
|---|---|---|
| Everyone | GETTING-STARTED.md | Choose Pathway |
| AI Agents | AI-AGENT-SYSTEM.md | CURRENT-STATE.md |
| Gamers | Gaming Pathway | KENL2 README |
| Developers | Dev Pathway | KENL3 README |
| Windows Users | Migration Pathway | Partition Scripts |
| Contributors | CONTRIBUTING.md | Governance |
| Category | Location | Purpose |
|---|---|---|
| Pathways | claude-landing/DOCUMENTATION-PATHWAYS.md | Navigation hub |
| Document Index | DOCUMENT-INDEX.md | Root doc review |
| Traceability | ATOM-REGISTER.md | ATOM tag tracking |
| Case Studies | case-studies/ | Real-world scenarios |
| Governance | governance/ | ARCREF + ADR decisions |
| Standards | VISUAL-ELEMENTS-STANDARD.md, SECURITY.md | Guidelines |
Install the KENL profile for dynamic banners and current playcard display:
# Install profile integration
. ~/.kenl/scripts/Install-KenlProfile.ps1
# After installation, these commands are available:
Show-KenlBanner # Display current context, module, playcard
Get-CurrentPlaycard # Show current active playcard
Set-CurrentPlaycard # Set active playcard
Show-Playcards # List all available playcards
kenl-switch <n> # Switch to module (0-13, battlemedic)
kenl-status # Comprehensive statusDynamic banner shows:
- Current platform (Windows, WSL2, Linux, Bazzite)
- Active module context
- Current playcard (game being configured)
- Recent ATOM and SAIF entries
Cross-platform PowerShell modules for KENL operations:
# Install KENL PowerShell modules
.\modules\KENL0-system\powershell\Install-KENL.ps1
# Test network latency
Import-Module KENL.Network
Test-KenlNetwork
# Platform detection
Import-Module KENL
Get-KenlPlatformPSGallery-ready with module manifests (.psd1) for publication. See PowerShell README.
Security-first audit trail system with:
- Prevention Layer: Schema validation, AI safety scoring, user approval
- Execution Layer: Sandboxed operations (Flatpak/Distrobox)
- Audit Layer: Cryptographic integrity (blockchain-style hashing)
sequenceDiagram
participant User
participant KENL
participant Validator
participant Qwen
participant Sandbox
participant DB
User->>KENL: Apply Play Card
KENL->>Validator: Validate schema
Validator->>Validator: Check patterns (rm -rf, sudo, etc)
alt Validation Failed
Validator-->>User: ❌ Rejected: Dangerous pattern detected
else Validation Passed
Validator->>Qwen: Compute safety score
Qwen-->>Validator: Score: 0.85 (GOOD)
Validator->>User: ⚠️ Preview changes + safety score
User->>KENL: Approve
KENL->>Sandbox: Execute in Flatpak/Distrobox
Sandbox-->>KENL: ✅ Success (exit code 0)
KENL->>DB: Log ATOM trail with hash
DB-->>User: ✅ ATOM-PLAYCARD-20251114-001
end
See ATOM Database Architecture for complete design.
Run AI models locally for 60% of KENL's token strategy (Claude 10%, Perplexity 30%, Qwen 60%):
- Zero API costs
- 100% privacy (code never leaves your machine)
- Offline capability
- Integration with VS Code (Continue.dev) and Claude Desktop (MCP)
Enable Claude to interact with KENL tools directly:
- Custom KENL MCP server (rpm-ostree, ujust, ATOM trails)
- Cloudflare integration (Workers, KV, D1, R2)
- GitHub operations (issues, PRs, code search)
- Ollama delegation (offload simple tasks to local AI)
Contributions welcome! See CONTRIBUTING.md for guidelines (Conventional Commits, pre-commit hooks, ARCREF + ADR for architectural changes)
Need help? GitHub Issues • Discussions • Security (private reporting)
License: MIT - Fork it, modify it, share it. See LICENSE
Acknowledgments: This project stands on the shoulders of giants. See ACKNOWLEDGMENTS.md for complete attribution of third-party projects and contributors.
KENL = Knowledge Enhanced Navigation Layer
Every operation builds knowledge → Every knowledge entry enables recovery → Every recovery strengthens the system.
Status: Production | Version: 1.0.0 | Platform: Bazzite (Fedora Atomic) | Made with intent by Bazza-DX 🎮💻🔐
Footnotes
-
See ACKNOWLEDGMENTS.md for comprehensive attribution of Bazzite, Universal Blue, Valve Proton, and all third-party projects that make KENL possible. ↩
-
Based on internal testing comparing recovery time with vs. without ATOM trail documentation. Formal validation study planned for future release. ↩
-
Boiling Steam ProtonDB Analysis (2025) - Community-verified compatibility data showing 89.7% of Windows titles launch on Linux, with 15,855+ games rated playable by at least two ProtonDB reports. ↩
-
Microsoft Windows 10 Support Lifecycle - Windows 10 reaches end of support on October 14, 2025. Enterprise studies show ~240M devices still running Windows 10 as of mid-2025 (ControlUp endpoint telemetry). ↩