Auto-publish: training content update 2026-05-20 17:21:08
This commit is contained in:
psb-gemma
@@ -1,67 +0,0 @@
|
||||
---
|
||||
title: Team 2890 Overview
|
||||
growth: tree
|
||||
freshness: seasonal
|
||||
---
|
||||
|
||||
# Team 2890 — Hawk Collective
|
||||
|
||||
## Team Identity
|
||||
|
||||
- **FRC Team 2890** — Hickory High School
|
||||
- **Theme:** The Borg — "You will be assimilated!"
|
||||
- **Colors:** Teal (#03818a), Black (#050505), White (#ffffff), Hot Pink (#ec40f5)
|
||||
- **Mascot:** Mothman (stylized hawk head)
|
||||
- **Discord:** The Hawk Collective server
|
||||
|
||||
## Current Robot (2026: Mothman)
|
||||
|
||||
- **Game:** REBUILT
|
||||
- **Vision:** PhotonVision (AprilTags)
|
||||
- **Drive:** YAGSL swerve
|
||||
- **Code:** [Gitea → Team2890/Mothman](https://gitea.hawkcollective2890.com/Team2890/Mothman)
|
||||
|
||||
## Core Systems
|
||||
|
||||
| System | What It Does |
|
||||
|--------|-------------|
|
||||
| **Gitea** | Git hosting, code review — [gitea.hawkcollective2890.com](https://gitea.hawkcollective2890.com/Team2890) |
|
||||
| **PhotonVision** | AprilTag detection, 3D pose estimation |
|
||||
| **YAGSL** | Swerve drive library (Java) |
|
||||
| **WPILib** | FRC robot framework |
|
||||
| **2890-claw** | AI training agent — see [[2890-claw]] entity |
|
||||
|
||||
## Key Skills the Team Uses
|
||||
|
||||
- **FRC programming** — Java, WPILib, command-based architecture
|
||||
- **Swerve drive** — YAGSL, odometry, path planning
|
||||
- **Vision processing** — PhotonVision, AprilTags, limelight-style targeting
|
||||
- **Robot mechanics** — gearboxes, bumpers, mechanisms
|
||||
- **Team coordination** — Git, code review, documentation
|
||||
|
||||
## Knowledge Dependencies
|
||||
|
||||
```
|
||||
FRC Robot Programming (Java)
|
||||
├── WPILib basics
|
||||
├── Command-based architecture
|
||||
├── Swerve drive (YAGSL)
|
||||
├── Odometry / pose estimation
|
||||
└── NetworkTables
|
||||
|
||||
Vision Processing
|
||||
├── PhotonVision setup
|
||||
├── AprilTag detection
|
||||
├── 3D position estimation
|
||||
└── Integration with swerve
|
||||
|
||||
Team Operations
|
||||
├── Git workflow (Gitea)
|
||||
├── Code review practices
|
||||
├── Robot testing methodology
|
||||
└── Safety / inspections
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
*See [[entities/index|People]] for individual profiles. See [[entry-path|Entry Path]] to start training.*
|
||||
@@ -1,113 +0,0 @@
|
||||
---
|
||||
growth: sprout
|
||||
---
|
||||
# Fabric Growth System — Proactive Learning
|
||||
|
||||
## Core Concept
|
||||
|
||||
The Fabric doesn't just log connections — it **grows knowledge** by proactively researching topics relevant to Chris's active projects. The keyword system acts as a trigger for deep research, follow-link crawling, and knowledge synthesis.
|
||||
|
||||
## How It Works
|
||||
|
||||
```
|
||||
Active Project (e.g., "working on M5 ESP32 project")
|
||||
↓
|
||||
Keyword match: "ESP32", "M5Stack", "sensors"
|
||||
↓
|
||||
Fabric queues: "Research ESP32 Piouts, common issues, sensor integration"
|
||||
↓
|
||||
Background research via web search + web fetch
|
||||
↓
|
||||
Findings stored in wiki under relevant source file
|
||||
↓
|
||||
Surface when context matches active project
|
||||
↓
|
||||
Cross-silo connection found → notify relevant agents
|
||||
```
|
||||
|
||||
## Keyword Files
|
||||
|
||||
| File | Silo | Trigger |
|
||||
|------|------|---------|
|
||||
| `keywords/2890-keywords.md` | School (FRC 2890) | Swerve, CAN bus, motor control, Java/WPILib, PhotonVision, YAGSL |
|
||||
| `keywords/play-keywords.md` | Play (HHS-Hackers) | ESP32, M5Stack, sensors, Home Assistant, Pi-hole, fermentation |
|
||||
| `keywords/psb-keywords.md` | Work (PSB) | Brewing, fermentation, Toast POS, inventory, kegging |
|
||||
|
||||
## Keyword Tiers
|
||||
|
||||
### Priority Keywords
|
||||
Trigger deep research — full web search, multiple sources, synthesis into wiki
|
||||
- Example: "CAN bus" found in a source → research termination, failure modes, CTR CANcoder integration, YAGSL CAN setup
|
||||
|
||||
### Secondary Keywords
|
||||
Follow links deeper than normal, note context, add to wiki if substantial
|
||||
- Example: "gear ratio" found → check if it connects to MK4i L1/L3 specs already in wiki
|
||||
|
||||
### Growth Triggers
|
||||
When scraping new sources, follow links containing these words deeper than normal
|
||||
- Example: page has "PID tuning" link → follow it, add findings to relevant file
|
||||
|
||||
## Research Queue
|
||||
|
||||
Maintained in `memory/research-queue.md`:
|
||||
```
|
||||
## Active Queue
|
||||
- [ ] ESP32 Piouts — triggered by M5 project context (PLAY)
|
||||
- [ ] CAN bus termination best practices — triggered by Canjector documentation (2890)
|
||||
- [ ] MK4i L3 tuning notes — triggered by gear ratio image (2890)
|
||||
|
||||
## Completed (moved to wiki)
|
||||
- [x] NEO Vortex current limits — stored in neo-vortex-motor.md
|
||||
|
||||
## Surface Queue (flag to Chris when active)
|
||||
- "ESP32 research complete — found GPIO mapping for M5Stack Core — surface?"
|
||||
```
|
||||
|
||||
## Cross-Silo Connection Growth
|
||||
|
||||
When a keyword match appears in multiple silos:
|
||||
```
|
||||
Play: "ESP32 temperature logging" appears in 3 sources
|
||||
2890: "temperature sensor integration" appears in robot code
|
||||
↓
|
||||
Fabric detects: "temp sensors span hobby + FRC — should cross-reference"
|
||||
↓
|
||||
Action: Flag connection → update both source files with cross-link
|
||||
↓
|
||||
Surface: "Temperature sensing shows up in both your hobby projects and FRC — want a training module on sensor basics?"
|
||||
```
|
||||
|
||||
## Surface Rules
|
||||
|
||||
When to surface proactively vs. log quietly:
|
||||
|
||||
| Situation | Action |
|
||||
|-----------|--------|
|
||||
| New connection found | Log to connections-log.md |
|
||||
| Cross-silo insight (3+ sources) | Surface to Chris via DM |
|
||||
| Skill gap detected for active student | Add to student's training recommendation |
|
||||
| Anomaly (fermentation stalled, code broken) | Alert Chris immediately |
|
||||
| Research complete, new info stored | Surface if project is active, otherwise log |
|
||||
| Keyword match in new context | Log + optionally DM "I found something on X, want me to dig deeper?" |
|
||||
|
||||
## Growth Goals
|
||||
|
||||
- **1 new connection per day** (off-season) — organic, not forced
|
||||
- **1 research synthesis per week** — deep dive on one topic, store in wiki
|
||||
- **Cross-silo bridges** — when same concept appears in 2+ silos, flag and cross-reference
|
||||
- **Student skill gaps** — surface when student is working on related project
|
||||
|
||||
## Process
|
||||
|
||||
1. **Heartbeat** — check for keyword matches in new/updated wiki files
|
||||
2. **Research** — for priority keywords, run web search + fetch
|
||||
3. **Store** — findings go to relevant source file, not just memory
|
||||
4. **Surface** — use surface rules to decide what to flag vs. log
|
||||
5. **Log connections** — to connections-log.md with cross-silo notes
|
||||
|
||||
## Status
|
||||
|
||||
System designed, keyword files created. Research queue initialized. First proactive research to begin when Chris approves.
|
||||
|
||||
---
|
||||
*Last updated: 2026-05-04*
|
||||
@@ -1,97 +0,0 @@
|
||||
---
|
||||
growth: sprout
|
||||
---
|
||||
# Concepts — HHS Hackers
|
||||
|
||||
Hardware/software hacking collective. Chris + former students (Matt, Kyle).
|
||||
|
||||
## Active Projects
|
||||
|
||||
| Project | Status | Key Concepts |
|
||||
|---------|--------|---------------|
|
||||
| ComBadge | Research | ESP32-S3, wearable, voice AI, PicoClaw, Wi-Fi |
|
||||
| Tricorder | Design | ESP32-S3, sensors, UniHiker, voice, PicoClaw |
|
||||
| Pi-hole Router | Planning | DNS, firewall, router, CM4, VLAN, network config |
|
||||
| AI Rig Upgrade | GPU Shopping | GPU Passthrough, Ollama, local AI inference |
|
||||
| Android Head Unit | Planning | CAN bus, car telemetry, voice AI, head unit |
|
||||
| AI Desktop Companion | Research | M5Stack, StackChan, voice robot |
|
||||
| Brewery PID Replacement | Prototyping | ESP32-S3, ESPHome, Home Assistant, PID, PT100 |
|
||||
|
||||
## Core Skills
|
||||
|
||||
- **ESP32-S3** — embedded development, low-level hardware
|
||||
- **Voice AI** — hotword detection, speech-to-text, local LLM
|
||||
- **Home networking** — DNS, DHCP, firewall, VLAN, router config
|
||||
- **Home Assistant** — home automation, dashboarding, integrations
|
||||
- **Hawk** — multi-agent systems, exec management
|
||||
- **Docker** — containerized services
|
||||
- **CAD/3D printing** — case design
|
||||
|
||||
## Knowledge Dependencies (Skills needed for projects)
|
||||
|
||||
```
|
||||
ESP32-S3 dev
|
||||
├── C/Arduino SDK
|
||||
├── esp-idf or Arduino framework
|
||||
├── I2C/SPI protocols
|
||||
├── Wi-Fi (station + AP modes)
|
||||
└── BLE (optional)
|
||||
|
||||
Voice AI
|
||||
├── Wake word / hotword detection
|
||||
├── Speech-to-text (on-device or API)
|
||||
├── Local LLM integration
|
||||
└── Text-to-speech
|
||||
|
||||
Home Networking
|
||||
├── DNS fundamentals ← Pi-hole requires this
|
||||
├── DHCP fundamentals
|
||||
├── Port forwarding / NAT
|
||||
├── Firewall rules (iptables/nftables)
|
||||
├── VLANs ← Natural next step after basic networking
|
||||
└── VPN basics
|
||||
|
||||
Home Assistant
|
||||
├── YAML configuration
|
||||
├── ESPHome integration
|
||||
├── Entities, automations
|
||||
└── Dashboard (HA Lovelace)
|
||||
|
||||
ComBadge / Tricorder
|
||||
├── ESP32-S3
|
||||
├── Sensor selection / I2C
|
||||
├── Battery management
|
||||
├── Enclosure design
|
||||
└── Voice AI pipeline
|
||||
|
||||
Pi-hole Router
|
||||
├── DNS ← FOUNDATION (needed first!)
|
||||
├── DHCP
|
||||
├── Network routing
|
||||
├── Firewall
|
||||
├── VLANs ← after basic networking
|
||||
└── VPN (optional, advanced)
|
||||
```
|
||||
|
||||
## Gap Analysis for Chris
|
||||
|
||||
Chris is strong on: hardware, ESP32, soldering, circuit design
|
||||
Chris is weak on:
|
||||
- **Networking fundamentals** — DNS, DHCP, VLANs, firewall rules. He keeps running into networking gaps when doing Pi-hole and router projects. This is the biggest gap.
|
||||
- **3D CAD** — designing cases/enclosures. Has printer but not using it effectively for project enclosures.
|
||||
- **Software architecture** — can build circuits but wiring multiple services together (Home Assistant, ESPHome, dashboards) takes too long.
|
||||
|
||||
## Gap Detection Map
|
||||
|
||||
When Chris works on:
|
||||
- **Pi-hole** → He needs DNS fundamentals first, then DHCP, then firewall, then VLANs
|
||||
- **ComBadge/Tricorder** → He knows ESP32 well, but voice AI pipeline is new. Needs hotword → STT → LLM → TTS understanding.
|
||||
- **Brewery PID** → He's learning ESPHome + Home Assistant integration, which is mostly YAML config.
|
||||
|
||||
## Recurring Topics
|
||||
|
||||
1. **ESP32-S3** — appears in ComBadge, Tricorder, PID controller, AI Desktop Companion
|
||||
2. **Voice AI** — ComBadge, Tricorder, Android Head Unit, AI Desktop Companion
|
||||
3. **Home networking** — Pi-hole, VLANs, router replacement
|
||||
4. **Local AI inference** — Ollama, GPU setup, ComBadge backend
|
||||
5. **Home Assistant** — fermentation dashboard, PID controllers, automation
|
||||
@@ -1,63 +0,0 @@
|
||||
---
|
||||
growth: sprout
|
||||
---
|
||||
# Concepts — PSB (Post Secondary Brewing)
|
||||
|
||||
Chris and Susan's craft brewery. Three agents: psb-thinking (planning), psb-gemma (brewhouse ops), psb-business (business side).
|
||||
|
||||
## Active Projects
|
||||
|
||||
| Project | Status | Key Concepts |
|
||||
|---------|--------|---------------|
|
||||
| Fermentation Dashboard | Planning | Home Assistant, TILT hydrometer, Grafana, dashboarding |
|
||||
| Brewery PID Replacement | Prototyping | ESP32-S3, ESPHome, Home Assistant, PID, PT100, custom PCB |
|
||||
| Toast POS | In use | Point of sale, product mix reports, email export |
|
||||
| Pi-hole (brewery) | Not started | DNS, ad-blocking (separate from home Pi-hole) |
|
||||
|
||||
## Core Skills
|
||||
|
||||
- **Brewing chemistry** — fermentation, yeast, malt, hops
|
||||
- **Home Assistant** — telemetry dashboards, TILT integration
|
||||
- **ESP32/ESPhome** — brewery sensor integration
|
||||
- **Toast POS** — sales reporting, product mix analysis
|
||||
- **PCB design** — custom PID controllers (Chris's growing skill)
|
||||
- **PID control** — temperature regulation for brewing vessels
|
||||
|
||||
## Knowledge Dependencies
|
||||
|
||||
```
|
||||
Brewery PID Control
|
||||
├── Temperature sensing (PT100, MAX31865)
|
||||
├── PID algorithm fundamentals
|
||||
├── ESP32-S3 + ESPHome
|
||||
├── Home Assistant integration
|
||||
└── Solid-state relay (SSR) control
|
||||
|
||||
Fermentation Dashboard
|
||||
├── Home Assistant ( Lovelace dashboards)
|
||||
├── TILT hydrometer / Bluetooth bridge
|
||||
├── Grafana (optional, for pretty charts)
|
||||
└── ESP32 bridge programming
|
||||
|
||||
Toast POS
|
||||
├── Report generation (product mix)
|
||||
├── CSV export
|
||||
├── Email automation
|
||||
└── Google Sheets integration
|
||||
```
|
||||
|
||||
## Gap Analysis for Chris (at brewery)
|
||||
|
||||
Chris is strong on: brewing, electronics, PCB design
|
||||
Chris is weak on:
|
||||
- **Home Assistant YAML** — configuration, automations, templating
|
||||
- **Dashboard design** — making data look good (Grafana, Lovelace)
|
||||
- **Software integration** — wiring multiple systems together
|
||||
|
||||
## Recurring Topics
|
||||
|
||||
1. **Temperature control** — PID for vessels (HLT, mash tun, boil kettle, fermenters)
|
||||
2. **Home Assistant** — telemetry dashboards, sensor integration
|
||||
3. **Custom hardware** — ESP32 + PT100 + SSR for temperature control
|
||||
4. **Data visualization** — making fermentation data readable
|
||||
5. **PCB design** — custom brewery controller boards
|
||||
@@ -1,72 +0,0 @@
|
||||
---
|
||||
growth: tree
|
||||
---
|
||||
# 2890-Claw Keywords — Swerve/Robotics Focus
|
||||
|
||||
## Priority Keywords (Trigger deep research)
|
||||
- troubleshooting
|
||||
- design
|
||||
- swerve
|
||||
- CAN bus
|
||||
- motor control
|
||||
- encoder
|
||||
- PID
|
||||
- autonomous
|
||||
- PathPlanner
|
||||
- PhotonVision
|
||||
- YAGSL
|
||||
- MK4i
|
||||
- NEO Vortex
|
||||
- SPARK Flex
|
||||
- CANcoder
|
||||
- Canjector
|
||||
- AprilTag
|
||||
- odometry
|
||||
- pose estimation
|
||||
- field-relative
|
||||
- command-based
|
||||
- WPILib
|
||||
- Java
|
||||
- Megatag
|
||||
- gear ratio
|
||||
- mechanism
|
||||
- drive system
|
||||
- torque
|
||||
- speed
|
||||
- reduction
|
||||
|
||||
## Secondary Keywords (Follow links, note context)
|
||||
- gear ratio
|
||||
- mechanism
|
||||
- drive system
|
||||
- current draw
|
||||
- power distribution
|
||||
- limit switch
|
||||
- gyro
|
||||
- pigeon
|
||||
- navx
|
||||
- timeout
|
||||
- fault
|
||||
- breaker
|
||||
- fuse
|
||||
- PDP
|
||||
- PDB
|
||||
- VEXpro
|
||||
- SDS
|
||||
- REV
|
||||
- CTRE
|
||||
- cross-cache
|
||||
- alignment
|
||||
- trajectory
|
||||
- auto routine
|
||||
- simulation
|
||||
- torque
|
||||
- speed
|
||||
- reduction
|
||||
- motor sizing
|
||||
- RPM
|
||||
- Nm
|
||||
- Amp
|
||||
|
||||
## Growth Triggers
|
||||
When scraping new sources, follow links containing these words deeper than normal
|
||||
@@ -1,70 +0,0 @@
|
||||
---
|
||||
growth: tree
|
||||
---
|
||||
# Play Keywords — Hobby/Personal Tech Focus
|
||||
|
||||
## Priority Keywords (Trigger deep research)
|
||||
- troubleshooting
|
||||
- design
|
||||
- ESP32
|
||||
- M5Stack
|
||||
- LilyGo
|
||||
- T-Display
|
||||
- T-Sensor
|
||||
- T-QT
|
||||
- sensors
|
||||
- Home Assistant
|
||||
- Pi-hole
|
||||
- TILT
|
||||
- fermentation
|
||||
- MQTT
|
||||
- I2C
|
||||
- GPIO
|
||||
- OLED
|
||||
- display
|
||||
- stepper
|
||||
- servo
|
||||
- Arduino
|
||||
- Raspberry Pi
|
||||
- circuit
|
||||
- PCB
|
||||
- schematic
|
||||
- sensor
|
||||
- automation
|
||||
- Node-RED
|
||||
|
||||
## Secondary Keywords (Follow links, note context)
|
||||
- Grove
|
||||
- UART
|
||||
- SPI
|
||||
- ADC
|
||||
- voltage
|
||||
- current
|
||||
- resistor
|
||||
- capacitor
|
||||
- transistor
|
||||
- relay
|
||||
- power supply
|
||||
- 12V
|
||||
- 5V
|
||||
- 3.3V
|
||||
- enclosure
|
||||
- 3D print
|
||||
- case
|
||||
- mount
|
||||
- sensor fusion
|
||||
- imu
|
||||
- accelerometer
|
||||
- gyroscope
|
||||
- temperature
|
||||
- humidity
|
||||
- pressure
|
||||
- gas sensor
|
||||
- TDS
|
||||
- specific gravity
|
||||
- TTGO
|
||||
- T-Watch
|
||||
- T-Call
|
||||
|
||||
## Growth Triggers
|
||||
When scraping new sources, follow links containing these words deeper than normal
|
||||
@@ -1,74 +0,0 @@
|
||||
---
|
||||
growth: tree
|
||||
---
|
||||
# PSB Keywords — Brewery/Business Focus
|
||||
|
||||
## Priority Keywords (Trigger deep research)
|
||||
- troubleshooting
|
||||
- design
|
||||
- brewing
|
||||
- fermentation
|
||||
- malt
|
||||
- hop
|
||||
- yeast
|
||||
- cellaring
|
||||
- serving
|
||||
- carbonation
|
||||
- temperature control
|
||||
- recipe development
|
||||
- Toast POS
|
||||
- inventory
|
||||
- kegging
|
||||
- packaging
|
||||
- mash
|
||||
- lautering
|
||||
- sparge
|
||||
- boil
|
||||
- chill
|
||||
- racking
|
||||
- barrel
|
||||
- aging
|
||||
- conditioning
|
||||
- diacetyl
|
||||
- acetaldehyde
|
||||
- sulfur
|
||||
- off-flavor
|
||||
- attenuation
|
||||
- gravity
|
||||
- ABV
|
||||
- IBU
|
||||
- SRM
|
||||
- batch size
|
||||
- efficiency
|
||||
|
||||
## Secondary Keywords (Follow links, note context)
|
||||
- pump
|
||||
- valve
|
||||
- thermometer
|
||||
- hydrometer
|
||||
- refractometer
|
||||
- glycol
|
||||
- conical
|
||||
- brite tank
|
||||
- bright beer
|
||||
- serving tank
|
||||
- jockey box
|
||||
- CO2
|
||||
- nitrogen
|
||||
- pressure
|
||||
- flow rate
|
||||
- hose
|
||||
- quick disconnect
|
||||
- QD
|
||||
- ball lock
|
||||
- pin lock
|
||||
- tap
|
||||
- faucet
|
||||
- draft
|
||||
- keg
|
||||
- sankey
|
||||
- D system
|
||||
- S system
|
||||
|
||||
## Growth Triggers
|
||||
When scraping new sources, follow links containing these words deeper than normal
|
||||
@@ -1,155 +0,0 @@
|
||||
---
|
||||
growth: sprout
|
||||
---
|
||||
# Cross-Domain Skill Map
|
||||
|
||||
Skills that span multiple domains. These are the bridges worth surfacing.
|
||||
|
||||
## Skills Present in Multiple Domains
|
||||
|
||||
### Networking
|
||||
| Domain | Use |
|
||||
|--------|-----|
|
||||
| HHS Hackers | Pi-hole router, VLANs, firewall |
|
||||
| PSB | Brewery network, device connectivity |
|
||||
| 2890 Claw | Robot communication, field networking |
|
||||
|
||||
**Gap:** Chris is weak on networking fundamentals. Pi-hole project will expose this soon.
|
||||
|
||||
---
|
||||
|
||||
### Home Assistant
|
||||
| Domain | Use |
|
||||
|--------|-----|
|
||||
| HHS Hackers | PID dashboards, automation |
|
||||
| PSB | Fermentation dashboard, TILT integration |
|
||||
|
||||
**Bridge:** Both domains use HA differently — brewery for telemetry, hackers for home automation.
|
||||
|
||||
---
|
||||
|
||||
### ESP32-S3 / Embedded
|
||||
| Domain | Use |
|
||||
|--------|-----|
|
||||
| HHS Hackers | ComBadge, Tricorder, PID controllers |
|
||||
| PSB | Brewery PID controllers |
|
||||
|
||||
**Bridge:** Same hardware, different contexts. Chris can share learnings between brewery PID and ComBadge.
|
||||
|
||||
---
|
||||
|
||||
### Voice AI
|
||||
| Domain | Use |
|
||||
|--------|-----|
|
||||
| HHS Hackers | ComBadge, Tricorder, AI Desktop Companion |
|
||||
|
||||
**Note:** Not in PSB or 2890 yet, but Chris wants it everywhere.
|
||||
|
||||
---
|
||||
|
||||
### Git / Version Control
|
||||
| Domain | Use |
|
||||
|--------|-----|
|
||||
| HHS Hackers | Gitea for crash-lab |
|
||||
| 2890 Claw | Gitea for robotics team |
|
||||
|
||||
**Bridge:** Chris has two Gitea instances. Could consolidate. Also: Git workflow best practices transfer.
|
||||
|
||||
---
|
||||
|
||||
### Hawk / Multi-Agent
|
||||
| Domain | Use |
|
||||
|--------|-----|
|
||||
| HHS Hackers | crash-bot system |
|
||||
| PSB | 3-agent system (thinking/gemma/business) |
|
||||
| 2890 Claw | 2890-bot |
|
||||
|
||||
**Bridge:** Same platform, different configs. Lessons from one transfer to others.
|
||||
|
||||
---
|
||||
|
||||
## Skills Unique to Each Domain
|
||||
|
||||
**HHS Hackers only:**
|
||||
- 3D CAD / enclosure design
|
||||
- CAN bus / automotive
|
||||
- GPU passthrough / local AI inference
|
||||
|
||||
**PSB only:**
|
||||
- Brewing chemistry
|
||||
- Toast POS operation
|
||||
- Fermentation science
|
||||
|
||||
**2890 Claw only:**
|
||||
- FRC / WPILib / Java
|
||||
- Swerve drive mechanics
|
||||
- PhotonVision / AprilTags
|
||||
- Student coaching methodology
|
||||
|
||||
---
|
||||
|
||||
## Priority Learning Paths
|
||||
|
||||
Based on active projects and dependencies:
|
||||
|
||||
### Path 1: Networking Fundamentals (URGENT)
|
||||
**Why:** Pi-hole router project is blocked by DNS/DHCP/firewall knowledge gaps.
|
||||
|
||||
```
|
||||
Step 1: DNS fundamentals (what it is, how resolution works)
|
||||
Step 2: DHCP fundamentals (what it does, how addresses get assigned)
|
||||
Step 3: NAT and port forwarding (how routing works)
|
||||
Step 4: Firewall basics (iptables/nftables concepts)
|
||||
Step 5: VLANs (network segmentation)
|
||||
```
|
||||
|
||||
### Path 2: Home Assistant Mastery
|
||||
**Why:** Both brewery and home projects need HA dashboards and automation.
|
||||
|
||||
```
|
||||
Step 1: Lovelace dashboard basics
|
||||
Step 2: Entities and automations
|
||||
Step 3: ESPHome integration
|
||||
Step 4: Templating and YAML magic
|
||||
Step 5: Grafana integration (for pretty charts)
|
||||
```
|
||||
|
||||
### Path 3: Voice AI Pipeline
|
||||
**Why:** ComBadge and Tricorder both need this.
|
||||
|
||||
```
|
||||
Step 1: Wake word / hotword detection (why it's hard)
|
||||
Step 2: Speech-to-text options (on-device vs API)
|
||||
Step 3: Local LLM integration (Ollama + API)
|
||||
Step 4: Text-to-speech output
|
||||
Step 5: Latency optimization
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Chris's Skill Confidence (Self-Reported + Observed)
|
||||
|
||||
| Skill | Confidence | Source |
|
||||
|-------|------------|--------|
|
||||
| Electronics / PCB design | High | Observed |
|
||||
| ESP32 hardware | High | Observed |
|
||||
| Brewing | High | Observed |
|
||||
| Soldering / assembly | High | Observed |
|
||||
| FRC mechanics | High | Observed |
|
||||
| Home Assistant YAML | Low | Observed (keeps asking for help) |
|
||||
| Networking fundamentals | Low | Observed (Pi-hole blockers) |
|
||||
| Voice AI pipeline | Medium | Learning |
|
||||
| Grafana/dashboards | Low | Mentioned |
|
||||
| Git workflow | Medium | Inconsistent use |
|
||||
| Java/WPILib | Low | Coaching, not coding |
|
||||
| 3D CAD | Medium | Has printer, not using it |
|
||||
|
||||
---
|
||||
|
||||
## Top Gaps to Fill
|
||||
|
||||
1. **DNS + DHCP + networking basics** → unblock Pi-hole router project
|
||||
2. **Home Assistant YAML** → unblock brewery and home projects
|
||||
3. **Voice AI pipeline understanding** → ComBadge/Tricorder will hit this soon
|
||||
4. **Grafana** → fermentation dashboard needs this
|
||||
5. **Java/WPILib advanced** → better coaching when students code
|
||||
@@ -1,172 +0,0 @@
|
||||
---
|
||||
growth: sprout
|
||||
---
|
||||
# Wiki Optimization — Team Training Environments
|
||||
|
||||
## The Problem With Our Current Structure
|
||||
|
||||
### Current State
|
||||
- Files buried in subdirectories: `entities/students/bruno.md`
|
||||
- Compile scans `entities/` root only → entities count = 0
|
||||
- Folders create rigid hierarchy → knowledge doesn't connect across siloes
|
||||
- 90 sources but they don't cross-reference meaningfully
|
||||
|
||||
### What We're Missing
|
||||
The wiki's power isn't in folders — it's in **links**. A wiki that surfaces data usefully for a team training environment needs:
|
||||
|
||||
1. **Atomic notes** — one concept per file, linked to everything related
|
||||
2. **Topic notes** — "hub" pages that aggregate links to related content
|
||||
3. **Training paths** — sequences of notes that guide learning
|
||||
4. **Entity profiles** — student/mentor pages that track skills + progress
|
||||
|
||||
---
|
||||
|
||||
## Three Fix Options
|
||||
|
||||
### Option A: Move Files Up (Minimum Fix)
|
||||
**What:** Move `entities/students/bruno.md` → `entities/bruno.md`
|
||||
|
||||
| Pros | Cons |
|
||||
|------|------|
|
||||
| Quick fix | Solves compile only, not structure |
|
||||
| Entities show up | Rigid folder hierarchy persists |
|
||||
| Low risk | Doesn't enable cross-topic views |
|
||||
|
||||
**Verdict:** Tactical patch. Doesn't fix the real problem.
|
||||
|
||||
---
|
||||
|
||||
### Option B: Flat Structure + Topic Hubs (Recommended)
|
||||
**What:**
|
||||
1. Move student files to `entities/` root
|
||||
2. Create **topic hub pages** that link to relevant entities + sources
|
||||
3. Use Obsidian Dataview to create dynamic skill-tracking views
|
||||
|
||||
**Example topic hub:**
|
||||
```
|
||||
# PathPlanner Training Hub
|
||||
[[bruno]] — working through PathPlanner basics
|
||||
[[riley]] — completed intro module
|
||||
[[photonvision]] — integrated with autonomous routines
|
||||
[[mothman-robot-code]] — YAGSL swerve implementation
|
||||
|
||||
## Learning Path
|
||||
1. [[systemcore]] — understand the controller first
|
||||
2. [[swere-modules]] — then how the drivetrain works
|
||||
3. [[photonvision]] — then vision-based positioning
|
||||
4. PathPlanner → finally, how to program paths
|
||||
```
|
||||
|
||||
| Pros | Cons |
|
||||
|------|------|
|
||||
| Compile works | Requires more setup upfront |
|
||||
| Teams see learning paths, not files | Topic hubs need maintenance |
|
||||
| Cross-topic views via Dataview | — |
|
||||
| Scales to any number of students | — |
|
||||
| Each hub is a training module | — |
|
||||
|
||||
**Verdict:** Best for our scenario. Chris teaches — he needs learning paths, not file browsers.
|
||||
|
||||
---
|
||||
|
||||
### Option C: Recursive Compile Config
|
||||
**What:** Configure the wiki plugin to recurse into subdirectories
|
||||
|
||||
| Pros | Cons |
|
||||
|------|------|
|
||||
| Keeps subdirectories | Requires config change |
|
||||
| Existing structure preserved | May break with Hawk updates |
|
||||
| — | Doesn't solve cross-linking problem |
|
||||
|
||||
**Verdict:** Avoid. Kicks the problem downstream.
|
||||
|
||||
---
|
||||
|
||||
## Recommendation: Option B
|
||||
|
||||
**Why Option B surfaces data most usefully for our scenario:**
|
||||
|
||||
Chris is a teacher. The Fabric watches all silos. The wiki should answer questions like:
|
||||
|
||||
| Question | How Option B Answers It |
|
||||
|----------|------------------------|
|
||||
| "Who's learning PathPlanner?" | [[pathplanner-hub]] → [[bruno]] + [[riley]] |
|
||||
| "What does a new student need to learn?" | Topic hub shows prerequisites + links |
|
||||
| "Where are the gaps in our training?" | Hub pages with missing/unfinished links |
|
||||
| "What did Bruno complete?" | Dataview query: student + status + date |
|
||||
| "Show me all sensor-related docs" | [[sensors-hub]] → links to all sensor sources |
|
||||
|
||||
**Topic hubs we'd need:**
|
||||
|
||||
| Hub | Purpose | Links |
|
||||
|-----|---------|-------|
|
||||
| `swere-training-hub` | Drivetrain learning path | Bruno, Riley, MK4i, NEO Vortex, YAGSL |
|
||||
| `vision-training-hub` | Camera + AprilTag setup | PhotonVision, MegaTag, AprilTag field layout |
|
||||
| `pathplanner-hub` | Autonomous programming | Student progress, YAGSL, Mothman code |
|
||||
| `electrical-hub` | Wiring + CAN bus | SPARK Flex, CANcoder, PDH, Canjectors |
|
||||
| `cad-training-hub` | Fusion 360 learning | Bruno, Riley, Fusion 360 module |
|
||||
|
||||
---
|
||||
|
||||
## Implementation Steps
|
||||
|
||||
### Step 1: Fix Entity Compile (5 min)
|
||||
```bash
|
||||
cd /home/topher/.openclaw/wiki/main
|
||||
git mv entities/students/bruno.md entities/bruno.md
|
||||
git mv entities/students/riley.md entities/riley.md
|
||||
git commit -m "Flatten entities structure for compile"
|
||||
git push
|
||||
```
|
||||
|
||||
### Step 2: Create Topic Hub Pages (ongoing)
|
||||
Start with the most important hub — the one Chris teaches from most:
|
||||
|
||||
**`training/hubs/swere-training-hub.md`**
|
||||
- Links: MK4i, NEO Vortex, SPARK Flex, YAGSL, Bruno (learning), Riley (completed)
|
||||
- Learning path with prerequisites
|
||||
- Status indicators per student
|
||||
|
||||
### Step 3: Add Frontmatter for Dataview
|
||||
Add to each student profile:
|
||||
```yaml
|
||||
---
|
||||
type: student-profile
|
||||
track: swerve
|
||||
skills:
|
||||
- fusion-360: intermediate
|
||||
- pathplanner: beginner
|
||||
- welding: beginner
|
||||
status:
|
||||
pathplanner: in-progress
|
||||
swere-basics: completed
|
||||
---
|
||||
```
|
||||
|
||||
Then Dataview can query: "Show all students with `skills.pathplanner: beginner`"
|
||||
|
||||
---
|
||||
|
||||
## Research Path for Chris
|
||||
|
||||
This IS the research path. The "fix" isn't a wiki plugin config — it's **restructuring the wiki around how Chris teaches**:
|
||||
|
||||
1. **Atomic notes** per hardware concept (we already have this)
|
||||
2. **Topic hubs** that aggregate + sequence learning (we're missing this)
|
||||
3. **Entity profiles** with structured skill tracking (we have the files, wrong location)
|
||||
4. **Training paths** that show prerequisite chains (needed for system to surface gaps)
|
||||
|
||||
The Fabric then detects gaps by watching:
|
||||
- Which hub links are broken?
|
||||
- Which student profiles show no recent progress?
|
||||
- Which hub has no topic hub page yet but students need it?
|
||||
|
||||
---
|
||||
|
||||
## Key Insight
|
||||
|
||||
**Folders are for files. Hubs are for learners.**
|
||||
|
||||
Chris teaches. The wiki should organize around what students need to learn, not where files live. Topic hubs do that — they group related content from across all silos into coherent learning paths.
|
||||
|
||||
**Option B is the fix.** Want me to start with the swerve training hub? 🎓
|
||||
Reference in New Issue
Block a user