Compare commits

..

12 Commits

Author SHA1 Message Date
MrC
6228a259b6 Remove draft flags — working in non-draft for review period
Training button stays off on crew page during review
2026-05-07 22:16:14 +00:00
MrC
a16f1b8165 Entry Path stones 1-3: merged voice + substance from both drafts
Stone 1: FIRST Overview — Dean Kamen origin, 4 programs, Gracious Professionalism (Woodie Flowers), Coopertition, Invention+Innovation, season timeline, match breakdown (15s auto/2min teleop/30s end game), championship structure

Stone 2: 2890 Our Story — Collective name origin, four eras (2009 founding through present), students run this, roles table, expectations, team beliefs, gear list (MK4i/NEO Vortex/SPARK Flex/PhotonVision)

Stone 3: Youth Safety — why this matters, non-negotiables, tool-specific rules with 'what kills people' framing (lathe/mill/drill press/welder/grinder/band saw), electrical safety, FIRST Youth Protection (two-deep, background checks, communication), consequences table, 7-item pre-shop checklist

All in young mentor/alumni voice, full content, complete
2026-05-07 22:11:39 +00:00
MrC
03c380d73a Entry Path stones 1-3: FIRST Robotics overview, 2890 Our Story, Youth Safety
Young mentor/alumni voice. Full content — not abbreviated.
Stone 1: FIRST origin, 4 programs, 3 core values, season structure, match breakdown
Stone 2: Team history 2009-present, Collective name, roles, expectations, gear
Stone 3: Tool-specific safety (lathe, mill, drill press, welder, grinder, band saw),
         electrical safety, FIRST Youth Protection, online conduct, consequences

Entry Path page links all three stones in order.
Status: draft — not yet published to Quartz
2026-05-07 22:04:11 +00:00
MrC
bc84dc6513 Sync: Gina Nakahara-Clark — retired status, nickname Ms Nak, no longer with team. Fixed frontmatter leadership:active→retired to match body. 2026-05-06 02:42:28 +00:00
topherslater-prog
4b100b143e teting 2026-05-05 22:38:21 -04:00
topherslater-prog
728d564374 updated entities 2026-05-05 12:50:39 -04:00
MrC
5b7f7a6300 Sync verified: Mr.Douglas Discord 474411386005487616, Alex C cromersmash, Riley pronouns they/them — matches 2890-bot participants.md 2026-05-05 15:02:40 +00:00
MrC
9a8ac5d88c Fix YAML slash in nicknames (big-papa, chris-slater, greyson-w) 2026-05-05 12:13:26 +00:00
MrC
2c2b61728f Add full Team 2890 roster — all 18 members with profiles
Students:
- fox.md (electrician)
- big-papa.md (student coach)
- jacob-firebreaker019.md (driver, 2026)
- jacob-m-jawarrior.md (programmer)
- ryan.md (operator)
- riley.md (technician) — updated with full profile
- steven.md (human player)
- alex-c.md (mentor, 21yr FRC vet)
- matthew.md (observer)
- kiera.md (team mascot)

Leadership/Mentors:
- gina-nakahara-clark.md (founding teacher)
- mr-douglas.md (programming mentor)
- walt.md (head mentor)
- chris-slater.md (lead coach)
- jackie.md (team mom)
- kp.md (rules guy)

Alumni:
- jacoby-powell.md (alumni/mentor)
- greyson-w.md (alumni/mentor, top coder)

Each profile includes: role, training track, status, emoji nickname, hub links
2026-05-05 12:10:46 +00:00
MrC
6a225979ea Implement wiki structure for team training
Entities flattened (compile fix):
- entities/students/ → entities/ (bruno.md, riley.md moved up)
- Added structured frontmatter (skills, status, track)
- Added related hub links

New training hub:
- training/hubs/swere-training-hub.md — learning path from motor to autonomous
- Links: NEO Vortex, SPARK Flex, MK4i, Canjectors, YAGSL, PhotonVision
- Level 1: Motor + controller
- Level 2: Swerve modules
- Level 3: Software + odometry
- Student progress tracking table

This enables the Fabric to surface learning gaps before students hit them.
2026-05-05 12:02:04 +00:00
MrC
634598a665 Add wiki optimization research for team training environments 2026-05-05 11:56:14 +00:00
MrC
35ee29a173 Add LilyGo devices to play keywords: T-Display, T-Sensor, T-QT, TTGO, T-Watch, T-Call 2026-05-04 22:19:44 +00:00
39 changed files with 2512 additions and 112 deletions

1
.obsidian/app.json vendored Normal file
View File

@@ -0,0 +1 @@
{}

1
.obsidian/appearance.json vendored Normal file
View File

@@ -0,0 +1 @@
{}

33
.obsidian/core-plugins.json vendored Normal file
View File

@@ -0,0 +1,33 @@
{
"file-explorer": true,
"global-search": true,
"switcher": true,
"graph": true,
"backlink": true,
"canvas": true,
"outgoing-link": true,
"tag-pane": true,
"footnotes": false,
"properties": true,
"page-preview": true,
"daily-notes": true,
"templates": true,
"note-composer": true,
"command-palette": true,
"slash-command": false,
"editor-status": true,
"bookmarks": true,
"markdown-importer": false,
"zk-prefixer": false,
"random-note": false,
"outline": true,
"word-count": true,
"slides": false,
"audio-recorder": false,
"workspaces": false,
"file-recovery": true,
"publish": false,
"sync": true,
"bases": true,
"webviewer": false
}

22
.obsidian/graph.json vendored Normal file
View File

@@ -0,0 +1,22 @@
{
"collapse-filter": true,
"search": "",
"showTags": false,
"showAttachments": false,
"hideUnresolved": false,
"showOrphans": true,
"collapse-color-groups": true,
"colorGroups": [],
"collapse-display": true,
"showArrow": false,
"textFadeMultiplier": 0,
"nodeSizeMultiplier": 1,
"lineSizeMultiplier": 1,
"collapse-forces": true,
"centerStrength": 0.518713248970312,
"repelStrength": 10,
"linkStrength": 1,
"linkDistance": 250,
"scale": 1.4279142773093856,
"close": true
}

184
.obsidian/workspace-mobile.json vendored Normal file
View File

@@ -0,0 +1,184 @@
{
"main": {
"id": "33833631b82dd76e",
"type": "split",
"children": [
{
"id": "8edcc27a394468f8",
"type": "tabs",
"children": [
{
"id": "2e1c6428c2d818be",
"type": "leaf",
"pinned": true,
"state": {
"type": "empty",
"state": {},
"pinned": true,
"icon": "lucide-file",
"title": "New tab"
}
},
{
"id": "e3ec71b299b0f35e",
"type": "leaf",
"state": {
"type": "graph",
"state": {},
"icon": "lucide-git-fork",
"title": "Graph view"
}
}
],
"currentTab": 1
}
],
"direction": "vertical"
},
"left": {
"id": "800323103ade653a",
"type": "mobile-drawer",
"children": [
{
"id": "4e019f6446a7ce8b",
"type": "leaf",
"state": {
"type": "file-explorer",
"state": {
"sortOrder": "alphabetical",
"autoReveal": true
},
"icon": "lucide-folder-closed",
"title": "Files"
}
},
{
"id": "bc9de419b4b45a73",
"type": "leaf",
"state": {
"type": "search",
"state": {
"query": "",
"matchingCase": false,
"explainSearch": false,
"collapseAll": false,
"extraContext": false,
"sortOrder": "alphabetical"
},
"icon": "lucide-search",
"title": "Search"
}
},
{
"id": "9bed99f6946fb079",
"type": "leaf",
"state": {
"type": "tag",
"state": {
"sortOrder": "frequency",
"useHierarchy": true,
"showSearch": false,
"searchQuery": ""
},
"icon": "lucide-tags",
"title": "Tags"
}
},
{
"id": "5801822cfeaa55dd",
"type": "leaf",
"state": {
"type": "all-properties",
"state": {
"sortOrder": "frequency",
"showSearch": false,
"searchQuery": ""
},
"icon": "lucide-archive",
"title": "All properties"
}
},
{
"id": "7ca1027249ba9b83",
"type": "leaf",
"state": {
"type": "bookmarks",
"state": {},
"icon": "lucide-bookmark",
"title": "Bookmarks"
}
}
],
"currentTab": 0
},
"right": {
"id": "4db085795cec713b",
"type": "mobile-drawer",
"children": [
{
"id": "c1c6d967d8faddd7",
"type": "leaf",
"state": {
"type": "backlink",
"state": {
"collapseAll": false,
"extraContext": false,
"sortOrder": "alphabetical",
"showSearch": false,
"searchQuery": "",
"backlinkCollapsed": false,
"unlinkedCollapsed": true
},
"icon": "links-coming-in",
"title": "Backlinks"
}
},
{
"id": "2f99634c71f99345",
"type": "leaf",
"state": {
"type": "outgoing-link",
"state": {
"linksCollapsed": false,
"unlinkedCollapsed": true
},
"icon": "links-going-out",
"title": "Outgoing links"
}
},
{
"id": "8bb85e0df77b805f",
"type": "leaf",
"state": {
"type": "outline",
"state": {
"followCursor": false,
"showSearch": false,
"searchQuery": ""
},
"icon": "lucide-list",
"title": "Outline"
}
}
],
"currentTab": 0
},
"left-ribbon": {
"hiddenItems": {
"switcher:Open quick switcher": false,
"graph:Open graph view": false,
"canvas:Create new canvas": false,
"daily-notes:Open today's daily note": false,
"templates:Insert template": false,
"command-palette:Open command palette": false,
"bases:Create new base": false
}
},
"active": "e3ec71b299b0f35e",
"lastOpenFiles": [
"reports/index.md",
"sources/index.md",
"index.md",
"inbox.md"
]
}

229
.obsidian/workspace.json vendored Normal file
View File

@@ -0,0 +1,229 @@
{
"main": {
"id": "6b8ba010950d7c8d",
"type": "split",
"children": [
{
"id": "7a1ec2206c49d0d9",
"type": "tabs",
"children": [
{
"id": "f3cee381b04d8976",
"type": "leaf",
"state": {
"type": "markdown",
"state": {
"file": "index.md",
"mode": "source",
"source": false
},
"icon": "lucide-file",
"title": "index"
}
}
]
}
],
"direction": "vertical"
},
"left": {
"id": "bb6b0229c3ba1b3a",
"type": "split",
"children": [
{
"id": "f2bda265a307845b",
"type": "tabs",
"children": [
{
"id": "2dad7e5096f907fb",
"type": "leaf",
"state": {
"type": "file-explorer",
"state": {
"sortOrder": "alphabetical",
"autoReveal": false
},
"icon": "lucide-folder-closed",
"title": "Files"
}
},
{
"id": "732e4d1aaf9cc742",
"type": "leaf",
"state": {
"type": "search",
"state": {
"query": "",
"matchingCase": false,
"explainSearch": false,
"collapseAll": false,
"extraContext": false,
"sortOrder": "alphabetical"
},
"icon": "lucide-search",
"title": "Search"
}
},
{
"id": "416e652b8aec03dd",
"type": "leaf",
"state": {
"type": "bookmarks",
"state": {},
"icon": "lucide-bookmark",
"title": "Bookmarks"
}
}
]
}
],
"direction": "horizontal",
"width": 300
},
"right": {
"id": "5d5080db948f3842",
"type": "split",
"children": [
{
"id": "c21fa2e0143ba39a",
"type": "tabs",
"children": [
{
"id": "7790a5db303b1c54",
"type": "leaf",
"state": {
"type": "backlink",
"state": {
"collapseAll": false,
"extraContext": false,
"sortOrder": "alphabetical",
"showSearch": false,
"searchQuery": "",
"backlinkCollapsed": false,
"unlinkedCollapsed": true
},
"icon": "links-coming-in",
"title": "Backlinks"
}
},
{
"id": "aef0511a98148ae8",
"type": "leaf",
"state": {
"type": "outgoing-link",
"state": {
"linksCollapsed": false,
"unlinkedCollapsed": true
},
"icon": "links-going-out",
"title": "Outgoing links"
}
},
{
"id": "b8f07221f64ad56b",
"type": "leaf",
"state": {
"type": "tag",
"state": {
"sortOrder": "frequency",
"useHierarchy": true,
"showSearch": false,
"searchQuery": ""
},
"icon": "lucide-tags",
"title": "Tags"
}
},
{
"id": "0032307752bb8723",
"type": "leaf",
"state": {
"type": "all-properties",
"state": {
"sortOrder": "frequency",
"showSearch": false,
"searchQuery": ""
},
"icon": "lucide-archive",
"title": "All properties"
}
},
{
"id": "e07a34807e692164",
"type": "leaf",
"state": {
"type": "outline",
"state": {
"followCursor": false,
"showSearch": false,
"searchQuery": ""
},
"icon": "lucide-list",
"title": "Outline"
}
}
]
}
],
"direction": "horizontal",
"width": 300,
"collapsed": true
},
"left-ribbon": {
"hiddenItems": {
"switcher:Open quick switcher": false,
"graph:Open graph view": false,
"canvas:Create new canvas": false,
"daily-notes:Open today's daily note": false,
"templates:Insert template": false,
"command-palette:Open command palette": false,
"bases:Create new base": false
}
},
"active": "f3cee381b04d8976",
"lastOpenFiles": [
"entities/mr-douglas.md",
"sources/psb-gemma-2026-04-24.md",
"entities/bruno.md",
"entities/kp.md",
"sources/psb-thinking-2026-04-09.md",
"entities/kiera.md",
"sources/psb-gemma-session-state.md",
"sources/psb-gemma-2026-02-24.md",
"sources/psb-recipe-70-meg-omega-2-2024.md",
"sources/psb-gemma-2026-05-01.md",
"sources/psb-recipe-john-adams-ne-cider-4-26.md",
"sources/psb-gemma-psb-memory-2026-02-27-2234.md",
"sources/psb-gemma-2026-04-25.md",
"sources/psb-gemma-2026-04-22.md",
"sources/2026-04-23-combadge.md",
"sources/2026-04-19-model-fallback.md",
"sources/2026-04-19-adhd-workflow.md",
"sources/2026-04-20.md",
"sources/2026-04-27-combadge-debug.md",
"sources/2026-04-23-combadge-battery.md",
"sources/psb-gemma-ocbackup-restore-instructions.md",
"sources/psb-thinking-2026-04-11.md",
"sources/psb-thinking-2026-04-24.md",
"sources/psb-gemma-2026-03-12.md",
"sources/psb-thinking-2026-04-16.md",
"entities/alex-c.md",
"sources/2890/training",
"sources/2890/mk4i-gear-ratios.png",
"sources/2890/canjector-start-pcb.png",
"sources/2890/canjector-schematic.png",
"sources/2890/canjector-minor-render.png",
"sources/2890/canjector-middle-schematic.png",
"sources/2890/canjector-major-render.png",
"sources/2890/canjector-endz-render.png",
"sources/2890",
"sources/play",
"sources/frc",
"training/pathways",
"training/hubs",
"training/modules",
"training",
"knowledge/keywords",
"knowledge"
]
}

View File

@@ -1,6 +1,6 @@
{
"pageCounts": {
"entity": 0,
"entity": 19,
"concept": 0,
"source": 188,
"synthesis": 0,
@@ -20,6 +20,215 @@
},
"contradictionClusters": [],
"pages": [
{
"title": "Alex C — Mentor Profile",
"kind": "entity",
"path": "entities/alex-c.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Big Papa — Student Profile",
"kind": "entity",
"path": "entities/big-papa.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Bruno — Student Profile",
"kind": "entity",
"path": "entities/bruno.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Mr. Slater — Lead Coach",
"kind": "entity",
"path": "entities/chris-slater.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Fox — Student Profile",
"kind": "entity",
"path": "entities/fox.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Ms. Gina Nakahara-Clark — Founding Teacher",
"kind": "entity",
"path": "entities/gina-nakahara-clark.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Greyson W \"Big Podcake\" — Alumni/Mentor",
"kind": "entity",
"path": "entities/greyson-w.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Jackie — Team Mom",
"kind": "entity",
"path": "entities/jackie.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Jacob (firebreaker019) — Student Profile",
"kind": "entity",
"path": "entities/jacob-firebreaker019.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Jacob M (jawarrior) — Student Profile",
"kind": "entity",
"path": "entities/jacob-m-jawarrior.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Jacoby Powell — Alumni/Mentor",
"kind": "entity",
"path": "entities/jacoby-powell.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Kiera — Team Mascot",
"kind": "entity",
"path": "entities/kiera.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "KP — Rules Expert",
"kind": "entity",
"path": "entities/kp.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Matthew — Student Profile",
"kind": "entity",
"path": "entities/matthew.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Mr. Douglas — Programming Mentor",
"kind": "entity",
"path": "entities/mr-douglas.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Riley — Student Profile",
"kind": "entity",
"path": "entities/riley.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Ryan — Student Profile",
"kind": "entity",
"path": "entities/ryan.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Steven — Student Profile",
"kind": "entity",
"path": "entities/steven.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"title": "Walt — Head Mentor",
"kind": "entity",
"path": "entities/walt.md",
"sourceIds": [],
"questions": [],
"contradictions": [],
"freshnessLevel": "unknown",
"claimCount": 0,
"topClaims": []
},
{
"id": "report.claim-health",
"title": "Claim Health",
@@ -93,7 +302,7 @@
"questions": [],
"contradictions": [],
"freshnessLevel": "fresh",
"lastTouchedAt": "2026-05-02T21:02:31.757Z",
"lastTouchedAt": "2026-05-05T12:12:37.589Z",
"claimCount": 0,
"topClaims": []
},

View File

@@ -407,3 +407,6 @@
{"type":"ingest","timestamp":"2026-05-03T02:03:48.552Z","details":{"inputPath":"/home/topher/.openclaw/workspace-psb-gemma/recipes/Seltzer_base_corn_11.md","pageId":"source.psb-recipe-seltzer-base-corn-11","pagePath":"sources/psb-recipe-seltzer-base-corn-11.md","bytes":1770,"created":true}}
{"type":"compile","timestamp":"2026-05-03T02:03:48.836Z","details":{"pageCounts":{"entity":0,"concept":0,"source":188,"synthesis":0,"report":6},"updatedFiles":["sources/psb-recipe-seltzer-base-corn-11.md",".openclaw-wiki/cache/agent-digest.json","index.md","sources/index.md"]}}
{"type":"lint","timestamp":"2026-05-03T02:06:35.546Z","details":{"issueCount":41,"reportPath":"reports/lint.md"}}
{"type":"lint","timestamp":"2026-05-05T11:45:09.194Z","details":{"issueCount":41,"reportPath":"reports/lint.md"}}
{"type":"compile","timestamp":"2026-05-05T12:02:19.853Z","details":{"pageCounts":{"entity":2,"concept":0,"source":188,"synthesis":0,"report":6},"updatedFiles":["entities/bruno.md","entities/riley.md","reports/stale-pages.md",".openclaw-wiki/cache/agent-digest.json","index.md","entities/index.md"]}}
{"type":"compile","timestamp":"2026-05-05T12:12:37.697Z","details":{"pageCounts":{"entity":19,"concept":0,"source":188,"synthesis":0,"report":6},"updatedFiles":["entities/alex-c.md","entities/big-papa.md","entities/fox.md","entities/greyson-w.md","entities/jackie.md","entities/jacob-firebreaker019.md","entities/jacob-m-jawarrior.md","entities/jacoby-powell.md","entities/kiera.md","entities/kp.md","entities/matthew.md","entities/mr-douglas.md","entities/chris-slater.md","entities/gina-nakahara-clark.md","entities/riley.md","entities/ryan.md","entities/steven.md","entities/walt.md","reports/stale-pages.md",".openclaw-wiki/cache/agent-digest.json","index.md","entities/index.md"]}}

57
entities/alex-c.md Normal file
View File

@@ -0,0 +1,57 @@
---
type: mentor-profile
date: 2026-03-13
updated: 2026-05-05
discord: cromersmash
pronouns: He/Him
role: mentor
track: programming
nickname: "Alex C"
emoji: "😎🔫"
status:
mentorship: active
expertise: expert
---
# Alex C — Mentor Profile
## Who They Are
- **Role:** Mentor
- **Nickname:** "Twinkle Toes Master Laser Gunner"
- **Emoji:** 😎🔫
- **Team:** OG — 21 years FRC experience
- **Started on:** Team 1126 (2004 era — the "dozer" reference comes from here)
- **Mentor for:** Teams 1126, 3181, 9214
## Training Progress
| Track | Level | Status |
|-------|-------|--------|
| FRC Programming | Expert | Active mentor |
| FRC Mechanical | Expert | Active mentor |
## Notes
- 21 years FRC veteran — helped start multiple teams
- Started on Team 1126 — references the 2004 FRC kickoff animation "dozer" as an FRC meme
- Known for sitting in corner and "looking pretty" 😎
- Expert level knowledge — can answer almost any FRC question
- "OG" — original gangster of FRC mentorship
## Expertise Areas
- Robot design
- Programming (multiple FRC languages)
- Competition strategy
- Team building
## Related Training Hubs
- [[programming-hub]] — can serve as mentor resource
- [[swerve-training-hub]] — can help with advanced swerve questions
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

39
entities/big-papa.md Normal file
View File

@@ -0,0 +1,39 @@
---
type: student-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: student-coach
track: leadership
nickname: "Big Papa"
emoji: "👂"
status:
coaching-basics: unknown
---
# Big Papa — Student Profile
## Who They Are
- **Role:** Coach (student coach, 2026)
- **Nicknames:** Big Papa, Bone Daddy
- **Emoji:** 👂
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Leadership | Beginner | Unknown | — |
| Coaching | Beginner | Unknown | — |
## Notes
- Student coach for 2026 season
- Responsible for guiding team during matches
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

76
entities/bruno.md Normal file
View File

@@ -0,0 +1,76 @@
---
type: student-profile
date: 2026-05-03
updated: 2026-05-05
discord: bruno_2890
track: mechanical
skills:
fusion-360: intermediate
cad-beginner: true
pathplanner: beginner
status:
roller-coaster: in-progress
battery-box: in-progress
fusion-360-exercises: in-progress
---
# Bruno — Student Profile
## Who He Is
- Active student on Team 2890
- Planner — uses kanban for life management (wants to do everything)
- Working on roller coaster sub-task 3 (stuck 4+ days)
- Active in robotics build
- Has decent Fusion 360 skills (had Mr. Silver's engineering class)
- Discord: bruno_2890
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Mechanical | Beginner | In progress | 2026-05-05 |
| Fusion 360 | Intermediate | Practicing | 2026-05-05 |
| PathPlanner | Beginner | Not started | — |
## Current Tasks (from board)
**High Priority:**
- [ ] Build battery box
- [ ] Build vertical battery box
**Roller Coaster Project (5 parts):**
- [ ] Finish cart body [1/5]
- [ ] Finish bogie design [2/5]
- [ ] Finish track designs [3/5]
- [ ] Assemble cart and bogie in CAD [4/5]
- [ ] Print them out [5/5]
**Other:**
- [ ] Organize robotics storage room
## Related Training Hubs
- [[swerve-training-hub]] — drivetrain fundamentals
- [[cad-training-hub]] — Fusion 360 learning path
- [[photonvision]] — vision-based odometry (future)
## Achievements Earned
| Badge | Earned Date | Notes |
|-------|-------------|-------|
| — | — | None yet |
## Completions Log
| Date | Action | Details |
|------|--------|---------|
| 2026-05-05 | Skills updated | Added Fusion 360 intermediate, PathPlanner beginner |
---
*Profile managed by MrC. Updates when Bruno earns badges, completes modules, or asks questions.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

51
entities/chris-slater.md Normal file
View File

@@ -0,0 +1,51 @@
---
type: leadership-profile
date: 2026-03-13
updated: 2026-05-05
discord: mr.slater
role: lead-coach
track: leadership
nickname: Mr. Slater
emoji: "🏭✨"
status:
leadership: active
---
# Mr. Slater — Lead Coach
## Who They Are
- **Role:** Lead Coach
- **Discord:** mr.slater
- **Nickname:** Mr. Slater, "-topher"
- **Emoji:** 🏭✨ (magic with 3D printers, lasers, CNC cutters)
- **Team:** Team 2890 Lead Coach
## Superpowers
- Does "amazing things with huge farm of 3D printers, lasers, CNC cutters and more"
- "Slater magic" — creative problem solving
- Runs the OpenClaw multi-agent system for team knowledge management
## Training Progress
| Track | Level | Status |
|-------|-------|--------|
| Leadership | Expert | Active |
| CAD/3D Printing | Expert | Active |
| FRC Coaching | Expert | Active |
## Notes
- Primary decision-maker for team 2890
- Uses the Fabric to track student training and surface learning gaps
- Main contact for all team agents (2890-bot, crash-bot, professor)
## Related Training Hubs
- All hubs — approves curriculum and training paths
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

42
entities/fox.md Normal file
View File

@@ -0,0 +1,42 @@
---
type: student-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: electrician
track: electrical
nickname: "The Wire Wizard"
emoji: "🔌"
status:
electrical-basics: unknown
---
# Fox — Student Profile
## Who They Are
- **Role:** Electrician
- **Nickname:** The Wire Wizard 🔌
- **Team 2890 member since:** 2026 (approximate)
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Electrical | Beginner | Unknown | — |
## Related Training Hubs
- [[electrical-hub]] — wiring, CAN bus, power distribution
## Notes
- Part of the 2026 student roster
- Electrical specialization
---
*Profile managed by MrC. Updates when Fox earns badges or completes training modules.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

View File

@@ -0,0 +1,43 @@
---
type: leadership-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: founding-teacher
track: leadership
nickname: "Ms. Gina Nakahara-Clark"
emoji: "📚"
status:
leadership: retired
---
# Ms. Gina Nakahara-Clark — Founding Teacher
## Who They Are
- **Role:** Founding Teacher
- **Nickname:** Ms. Gina Nakahara-Clark, Ms Nak
- **Emoji:** 📚
- **Team:** Started Team 2890 in Fall 2008
## Training Progress
| Track | Level | Status |
| ------------ | ------ | ---------- |
| Leadership | Expert | Retired |
| FRC Coaching | Expert | Since 2008 |
## Notes
- Founded Team 2890 in Fall 2008
- No longer with the team
## Related Training Hubs
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

52
entities/greyson-w.md Normal file
View File

@@ -0,0 +1,52 @@
---
type: alumni-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: alumni-mentor
track: programming
nickname: Greyson W
emoji: "🎂"
status:
mentorship: available
expertise: advanced
---
# Greyson W "Big Podcake" — Alumni/Mentor
## Who They Are
- **Role:** Alumni / Mentor
- **Nickname:** Greyson W, "Big Podcake"
- **Emoji:** 🎂
- **Team:** Former student, now trusted mentor
## Training Progress
| Track | Level | Status |
|-------|-------|--------|
| Programming | Advanced | Alumni mentor |
| FRC Coding | Expert | Available |
## Notes
- Top coder on the team when a student
- Go-to for coding help even as an alumni
- Available for questions about programming and technical challenges
## Expertise Areas
- Java programming
- WPILib
- YAGSL implementation
- General FRC code architecture
## Related Training Hubs
- [[programming-hub]] — can serve as coding mentor resource
- [[swerve-training-hub]] — YAGSL odometry questions
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

View File

@@ -2,5 +2,23 @@
## Generated
<!-- openclaw:wiki:entities:index:start -->
- No entities yet.
- [Alex C — Mentor Profile](entities/alex-c.md)
- [Big Papa — Student Profile](entities/big-papa.md)
- [Bruno — Student Profile](entities/bruno.md)
- [Fox — Student Profile](entities/fox.md)
- [Greyson W "Big Podcake" — Alumni/Mentor](entities/greyson-w.md)
- [Jackie — Team Mom](entities/jackie.md)
- [Jacob (firebreaker019) — Student Profile](entities/jacob-firebreaker019.md)
- [Jacob M (jawarrior) — Student Profile](entities/jacob-m-jawarrior.md)
- [Jacoby Powell — Alumni/Mentor](entities/jacoby-powell.md)
- [Kiera — Team Mascot](entities/kiera.md)
- [KP — Rules Expert](entities/kp.md)
- [Matthew — Student Profile](entities/matthew.md)
- [Mr. Douglas — Programming Mentor](entities/mr-douglas.md)
- [Mr. Slater — Lead Coach](entities/chris-slater.md)
- [Ms. Gina Nakahara-Clark — Founding Teacher](entities/gina-nakahara-clark.md)
- [Riley — Student Profile](entities/riley.md)
- [Ryan — Student Profile](entities/ryan.md)
- [Steven — Student Profile](entities/steven.md)
- [Walt — Head Mentor](entities/walt.md)
<!-- openclaw:wiki:entities:index:end -->

42
entities/jackie.md Normal file
View File

@@ -0,0 +1,42 @@
---
type: leadership-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: team-mom
track: logistics
nickname: "Jackie"
emoji: "✈️"
status:
logistics: active
---
# Jackie — Team Mom
## Who They Are
- **Role:** Team Mom
- **Nickname:** Jackie
- **Emoji:** ✈️ (travel planner)
- **Team:** 2026 season
## Responsibilities
- Travel planning for competitions
- Team logistics and coordination
- Student welfare during events
## Notes
- Essential for competition logistics
- Coordinates travel, lodging, meals
- Student wellbeing during away events
## Related Training Hubs
- [[competition-hub]] — event logistics, travel
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

View File

@@ -0,0 +1,49 @@
---
type: student-profile
date: 2026-03-13
updated: 2026-05-05
discord: firebreaker019
role: driver
track: driver
nickname: "Jacob"
emoji: "👟"
status:
driver-training: active
shoe-height-optimization: in-progress
---
# Jacob (firebreaker019) — Student Profile
## Who They Are
- **Role:** Driver (2026)
- **Discord:** firebreaker019
- **Nickname:** Jacob
- **Emoji:** 👟 (shoe-height optimization in progress)
- **Team:** 2026 competition roster
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Driver | Active | Training | 2026-05-05 |
## Behavioral Notes
- Doesn't always listen to Bone Daddy (Big Papa)
- Focus on shoe-height optimization
## Related Training Hubs
- [[swerve-training-hub]] — drivetrain fundamentals for drivers
- [[driver-hub]] — gamepad controls, match strategy
## Notes
- 2026 driver — primary robot operator during matches
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

View File

@@ -0,0 +1,48 @@
---
type: student-profile
date: 2026-03-13
updated: 2026-05-05
discord: jawarrior
role: programmer
track: programming
nickname: "Jacob M"
emoji: "🤦"
status:
programming-basics: unknown
yagsl: beginner
---
# Jacob M (jawarrior) — Student Profile
## Who They Are
- **Role:** Programmer
- **Discord:** jawarrior
- **Nickname:** Jacob M, "Tall Smart Man"
- **Emoji:** 🤦 (shakes head at programming requests)
- **Team:** 2026 competition roster
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Programming | Beginner | Unknown | — |
| YAGSL | Beginner | Not started | — |
## Notes
- Known for being tall and technically minded
- Shakes head at Alex's programming requests
- Can be looped in for technical debugging
## Related Training Hubs
- [[swerve-training-hub]] — YAGSL swerve implementation
- [[programming-hub]] — Java, WPILib, code basics
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

53
entities/jacoby-powell.md Normal file
View File

@@ -0,0 +1,53 @@
---
type: alumni-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: alumni-mentor
track: general
nickname: "Jacoby Powell"
emoji: "🐻"
status:
mentorship: available
expertise: advanced
---
# Jacoby Powell — Alumni/Mentor
## Who They Are
- **Role:** Alumni / Mentor
- **Nickname:** Jacoby Powell
- **Emoji:** 🐻
- **Team:** Former student, now trusted mentor
## Nickname History (Team Default: Japookiebear 🐻)
The following nicknames were all used at various times: Jacuzzi, Jakota, Jamonda, Jamanga, Jahoba, Jerardo, Jacodo, Jaminga, Jahova, Jacoba, Jaketa, Jacoova, Jramondo, Jacuzza, Jacooby, Jacobi, Jacouger, Jabooda, Jacooda, Jamany, Shacoby, Japotle, Jakourtney, Jacoobydoobydoo, Jamaji, Jakunamattata, Jaquavius, Jaqueef, Coobi, Jaquela, Jasomething, Jaquille O'Neal, Jacobby, Japookiebear (**TEAM DEFAULT**), unc
## Training Progress
| Track | Level | Status |
|-------|-------|--------|
| General | Advanced | Alumni mentor |
## Notes
- Trusted former student — can be looped in for advice/mentoring
- Extensive FRC experience as a student
- Available for questions about team history and culture
## Expertise Areas
- Competition experience
- Team culture
- Technical advice (former competitor)
- Historical context
## Related Training Hubs
- Any hub — can provide alumni perspective
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

39
entities/kiera.md Normal file
View File

@@ -0,0 +1,39 @@
---
type: mascot
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: team-mascot
track: mascot
nickname: "Kiera"
emoji: "🐑"
status:
mascot-duty: active
---
# Kiera — Team Mascot
## Who They Are
- **Role:** Team Mascot
- **Nickname:** Kiera
- **Emoji:** 🐑
- **Team:** Decided at 2024 DCMP event
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Mascot | Active | Designated | 2024 DCMP |
## Notes
- Team mascot designation decided at 2024 DCMP event
- Represents team spirit at events
---
*🐑*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

48
entities/kp.md Normal file
View File

@@ -0,0 +1,48 @@
---
type: leadership-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: rules-expert
track: rules
nickname: "KP"
emoji: "📋"
status:
rules: expert
---
# KP — Rules Expert
## Who They Are
- **Role:** Rules Guy
- **Nickname:** KP
- **Emoji:** 📋
- **Team:** 2026 season
## Expertise Areas
- Game manual interpretation
- Rule compliance
- Competition rules questions
## Training Progress
| Track | Level | Status |
|-------|-------|--------|
| Rules | Expert | Active |
## Notes
- Go-to person for rule interpretations at competitions
- Studies game manual thoroughly each season
- Can answer rule questions during matches
## Related Training Hubs
- [[rules-hub]] — game rules, compliance
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

38
entities/matthew.md Normal file
View File

@@ -0,0 +1,38 @@
---
type: student-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: observer
track: general
nickname: "Matthew"
emoji: "💀"
status:
general: observer
---
# Matthew — Student Profile
## Who They Are
- **Role:** Observer
- **Nickname:** Matthew
- **Emoji:** 💀 (adds nothing but skulls)
- **Team:** 2026 roster
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| General | Observer | Passive | — |
## Notes
- Observer status — present but not actively participating in training tracks yet
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

52
entities/mr-douglas.md Normal file
View File

@@ -0,0 +1,52 @@
---
type: mentor-profile
date: 2026-03-13
updated: 2026-05-05
discord: 474411386005487616
pronouns: He/Him
role: mentor
track: programming
nickname: "Mr. Douglas"
emoji: "☕"
status:
mentorship: active
approach: conservative
---
# Mr. Douglas — Programming Mentor
## Who They Are
- **Role:** Second Coach / Programming Mentor
- **Emoji:** ☕ (tea enthusiast — tea > crumpets)
- **Team:** 2026 season
## Communication Style
- Often negative about trying new things
- Catch phrases: "The problem with that is..." / "The problem is..."
- Messages carry weight — students tend to listen
- **When he raises concerns:** Acknowledge validity, but push back if being overly conservative
## Training Progress
| Track | Level | Status |
|-------|-------|--------|
| Programming | Advanced | Active |
| Paperwork | Lead | Active |
## Notes
- Paperwork lead for the team
- Conservative approach — may need constructive challenging when blocking growth initiatives
- "The problem is..." = red flag for growth mindset
- Tea enthusiast ☕
## Related Training Hubs
- [[programming-hub]] — can help with code architecture questions
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

55
entities/riley.md Normal file
View File

@@ -0,0 +1,55 @@
---
type: student-profile
date: 2026-03-13
updated: 2026-05-05
discord: rileythesheep
role: technician
pronouns: they/them
nickname: "Riley"
emoji: "🐏🧟"
status:
climber-rebuild: in-progress
fusion-360: intermediate
driver: former
---
# Riley — Student Profile
## Who They Are
- **Role:** Technician (2026)
- **Discord:** rileythesheep
- **Nickname:** Riley
- **Emoji:** 🐏🧟
- **Team:** 2026 competition roster
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Mechanical | Intermediate | Active | 2026-05-05 |
| Fusion 360 | Intermediate | Strong operator | 2026-05-05 |
| Driver | Former | — | — |
## Current Tasks
- Rebuild climber assembly (high priority)
- Audit GPS sensor wiring
## Notes
- Former driver
- Strong CAD operator
- Known for RE (Robotics Endeavor) enthusiasm
- Cares about making things work properly
## Related Training Hubs
- [[swerve-training-hub]] — drivetrain understanding
- [[cad-training-hub]] — Fusion 360 (can help mentor others)
---
*Profile managed by MrC. Updates when Riley earns badges or completes training modules.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

43
entities/ryan.md Normal file
View File

@@ -0,0 +1,43 @@
---
type: student-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: operator
track: operator
nickname: "Ryan"
emoji: "💨"
status:
operator-training: active
---
# Ryan — Student Profile
## Who They Are
- **Role:** Operator (2026)
- **Nickname:** Ryan
- **Emoji:** 💨 (shooter + sound FX)
- **Team:** 2026 competition roster
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Operator | Active | Training | 2026-05-05 |
## Notes
- Operator during competition matches
- Handles shooter controls + sound FX
## Related Training Hubs
- [[driver-hub]] — gamepad controls, match strategy
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

43
entities/steven.md Normal file
View File

@@ -0,0 +1,43 @@
---
type: student-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: human-player
track: human-player
nickname: "Steven"
emoji: "🏀"
status:
human-player-training: unknown
---
# Steven — Student Profile
## Who They Are
- **Role:** Human Player (2026)
- **Nickname:** Steven
- **Emoji:** 🏀 (thinks he's Michael Jordan, looks like short Larry Bird)
- **Team:** 2026 competition roster
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Human Player | Beginner | Unknown | — |
## Notes
- Human Player during competition matches
- Stationed at the scoring station for game pieces
## Related Training Hubs
- [[human-player-hub]] — game piece handling, scoring rules
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

View File

@@ -1,55 +0,0 @@
---
type: student-profile
date: 2026-05-03
---
# Bruno — Student Profile
## Who He Is
- Active student on Team 2890
- Planner — uses kanban for life management (wants to do everything)
- Working on roller coaster sub-task 3 (stuck 4+ days)
- Active in robotics build
- Has decent Fusion 360 skills (had Mr. Silver's engineering class)
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Electrical | Unknown | Not started | — |
| Mechanical | Unknown | Not started | — |
| Pneumatics | Unknown | Not started | — |
## Current Tasks (from board)
- [ ] Build battery box (high priority)
- [ ] Build vertical battery box (medium)
- [ ] Roller coaster: finish cart body [1/5]
- [ ] Roller coaster: finish bogie design [2/5]
- [ ] Roller coaster: finish track designs [3/5]
- [ ] Roller coaster: assemble cart and bogie in CAD [4/5]
- [ ] Roller coaster: print them out [5/5]
- [ ] Organize robotics storage room
## Achievements Earned (Lego Badges)
| Badge | Earned Date | Notes |
|-------|-------------|-------|
| — | — | None yet |
---
## Completions Log
| Date | Action | Details |
|------|--------|---------|
| — | — | — |
---
## How MrC Updates This
MrC updates this profile when:
- Bruno mentions earning a badge → add to Achievements Earned
- Bruno says "I finished X" → add to Completions Log
- Bruno asks a question (routes to level)
- MrC surfaces a gap or recommendation

View File

@@ -1,48 +0,0 @@
---
type: student-profile
date: 2026-05-03
---
# Riley — Student Profile
## Who He Is
- Student on Team 2890
- Technician, former driver
- Discord: rileythesheep
- Currently working on: Rebuild climber assembly (high priority)
## Training Progress
| Track | Level | Status | Last Updated |
|-------|-------|--------|--------------|
| Electrical | Unknown | Not started | — |
| Mechanical | Unknown | Not started | — |
| Pneumatics | Unknown | Not started | — |
## Current Tasks (from board)
- [ ] Rebuild climber assembly (high priority, mechanical)
- [ ] Audit GPS sensor wiring (high priority, electrical)
## Achievements Earned (Lego Badges)
| Badge | Earned Date | Notes |
|-------|-------------|-------|
| — | — | None yet |
---
## Completions Log
| Date | Action | Details |
|------|--------|---------|
| — | — | — |
---
## How MrC Updates This
MrC updates this profile when:
- Riley mentions earning a badge → add to Achievements Earned
- Riley says "I finished X" → add to Completions Log
- Riley asks a question (routes to level)
- MrC surfaces a gap or recommendation

50
entities/walt.md Normal file
View File

@@ -0,0 +1,50 @@
---
type: mentor-profile
date: 2026-03-13
updated: 2026-05-05
discord: TBD
role: head-mentor
track: mechanical
nickname: "Walt"
emoji: "🛡️💥"
status:
mentorship: active
expertise: intermediate
---
# Walt — Head Mentor
## Who They Are
- **Role:** Head Mentor
- **Nickname:** Walt
- **Emoji:** 🛡️💥
- **Team:** 2026 season
## Expertise Areas
- Bumper construction — "making pretty looking, semi-functional bumpers that last until Riley hits things"
- Mechanical assembly
- Competition readiness
## Training Progress
| Track | Level | Status |
|-------|-------|--------|
| Mechanical | Intermediate | Active mentor |
| Bumpers | Expert | Active mentor |
## Notes
- Old guy — brings experience from previous seasons
- Known for bumper durability — bumpers survive until Riley crashes into things 💥
- Positive mentorship style
## Related Training Hubs
- [[mechanical-hub]] — mechanical assembly, bumper rules
---
*Profile managed by MrC.*
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->

View File

@@ -3,10 +3,10 @@
## Generated
<!-- openclaw:wiki:index:start -->
- Render mode: `native`
- Total pages: 194
- Total pages: 213
- Claims: 0
- Sources: 188
- Entities: 0
- Entities: 19
- Concepts: 0
- Syntheses: 0
- Reports: 6
@@ -202,7 +202,25 @@
- [zfs-drive-prep](sources/zfs-drive-prep.md)
### Entities
- No entities yet.
- [Alex C — Mentor Profile](entities/alex-c.md)
- [Big Papa — Student Profile](entities/big-papa.md)
- [Bruno — Student Profile](entities/bruno.md)
- [Fox — Student Profile](entities/fox.md)
- [Greyson W "Big Podcake" — Alumni/Mentor](entities/greyson-w.md)
- [Jackie — Team Mom](entities/jackie.md)
- [Jacob (firebreaker019) — Student Profile](entities/jacob-firebreaker019.md)
- [Jacob M (jawarrior) — Student Profile](entities/jacob-m-jawarrior.md)
- [Jacoby Powell — Alumni/Mentor](entities/jacoby-powell.md)
- [Kiera — Team Mascot](entities/kiera.md)
- [KP — Rules Expert](entities/kp.md)
- [Matthew — Student Profile](entities/matthew.md)
- [Mr. Douglas — Programming Mentor](entities/mr-douglas.md)
- [Mr. Slater — Lead Coach](entities/chris-slater.md)
- [Ms. Gina Nakahara-Clark — Founding Teacher](entities/gina-nakahara-clark.md)
- [Riley — Student Profile](entities/riley.md)
- [Ryan — Student Profile](entities/ryan.md)
- [Steven — Student Profile](entities/steven.md)
- [Walt — Head Mentor](entities/walt.md)
### Concepts
- No concepts yet.

View File

@@ -5,6 +5,10 @@
- design
- ESP32
- M5Stack
- LilyGo
- T-Display
- T-Sensor
- T-QT
- sensors
- Home Assistant
- Pi-hole
@@ -41,7 +45,6 @@
- 12V
- 5V
- 3.3V
-焊
- enclosure
- 3D print
- case
@@ -56,6 +59,9 @@
- gas sensor
- TDS
- specific gravity
- TTGO
- T-Watch
- T-Call
## Growth Triggers
When scraping new sources, follow links containing these words deeper than normal

View File

@@ -0,0 +1,169 @@
# 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 OpenClaw 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? 🎓

View File

@@ -3,12 +3,32 @@ pageType: report
id: report.stale-pages
title: Stale Pages
status: active
updatedAt: 2026-05-02T21:02:31.757Z
updatedAt: 2026-05-05T12:12:37.589Z
---
# Stale Pages
## Generated
<!-- openclaw:wiki:stale-pages:start -->
- No aging or stale pages older than 30 days.
- Stale pages: 19
- [Alex C — Mentor Profile](entities/alex-c.md): missing updatedAt
- [Big Papa — Student Profile](entities/big-papa.md): missing updatedAt
- [Bruno — Student Profile](entities/bruno.md): missing updatedAt
- [Fox — Student Profile](entities/fox.md): missing updatedAt
- [Greyson W "Big Podcake" — Alumni/Mentor](entities/greyson-w.md): missing updatedAt
- [Jackie — Team Mom](entities/jackie.md): missing updatedAt
- [Jacob (firebreaker019) — Student Profile](entities/jacob-firebreaker019.md): missing updatedAt
- [Jacob M (jawarrior) — Student Profile](entities/jacob-m-jawarrior.md): missing updatedAt
- [Jacoby Powell — Alumni/Mentor](entities/jacoby-powell.md): missing updatedAt
- [Kiera — Team Mascot](entities/kiera.md): missing updatedAt
- [KP — Rules Expert](entities/kp.md): missing updatedAt
- [Matthew — Student Profile](entities/matthew.md): missing updatedAt
- [Mr. Douglas — Programming Mentor](entities/mr-douglas.md): missing updatedAt
- [Mr. Slater — Lead Coach](entities/chris-slater.md): missing updatedAt
- [Ms. Gina Nakahara-Clark — Founding Teacher](entities/gina-nakahara-clark.md): missing updatedAt
- [Riley — Student Profile](entities/riley.md): missing updatedAt
- [Ryan — Student Profile](entities/ryan.md): missing updatedAt
- [Steven — Student Profile](entities/steven.md): missing updatedAt
- [Walt — Head Mentor](entities/walt.md): missing updatedAt
<!-- openclaw:wiki:stale-pages:end -->

View File

@@ -0,0 +1,85 @@
---
type: training-hub
title: "Swerve Training Hub"
description: "Learning path for Team 2890 swerve drivetrain — from motor to autonomous"
status: active
students:
- bruno
- riley
related:
- sources/2890/swerve-modules.md
- sources/2890/neo-vortex-motor.md
- sources/2890/spark-flex.md
- sources/2890/mothman-robot-code.md
- training/modules/systemcore.md
---
# Swerve Training Hub
## Overview
This hub guides students through the **Team 2890 swerve drivetrain** — from how the motor works to how to program autonomous paths. All content is specific to our hardware: SDS MK4i modules, NEO Vortex motors, SPARK Flex controllers, and YAGSL Java library.
## Hardware Stack
| Component | Spec | Doc |
|-----------|------|-----|
| **Motor** | NEO Vortex (565 Kv, 6784 RPM) | [[neo-vortex-motor]] |
| **Controller** | SPARK Flex (60A continuous) | [[spark-flex]] |
| **Gearbox** | MAXPlanetary (27 ratios, cartridge-based) | [[maxplanetary-gearbox]] |
| **Module** | SDS MK4i (L1/L3 field-swappable) | [[swere-modules]] |
| **CAN Interconnect** | Canjectors (Endz/Minor/Major) | [[canjectors]] |
| **Odometry** | CANcoder + YAGSL | [[mothman-robot-code]] |
## Learning Path
### Level 1 — Motor and Controller
1. [[neo-vortex-motor]] — how the motor works, Kv rating, stall torque
2. [[spark-flex]] — how the controller drives the motor, PWM vs CAN
3. [[maxplanetary-gearbox]] — why we need gears, cartridge ratios
**Check for understanding:** Explain why a 6784 RPM motor needs reduction to drive a wheel.
### Level 2 — Swerve Modules
1. [[swere-modules]] — how the MK4i module translates rotation into motion
2. L1 vs L3 — when to use each (speed vs. torque)
3. [[canjectors]] — how CAN signals route from roboRIO to each module
**Check for understanding:** Sketch a swerve module. Label wheel, gear train, motor, steering motor, CANcoder.
### Level 3 — Software and Odometry
1. [[mothman-robot-code]] — YAGSL swerve implementation
2. [[systemcore]] — roboRIO replacement coming (understand the platform)
3. [[photonvision]] — AprilTag pose estimation for autonomous
**Check for understanding:** What's the difference between wheel odometry and vision pose?
## Student Progress
| Student | Level | Status | Last Active |
|---------|-------|--------|------------|
| [[bruno]] | Level 1-2 | In progress — roller coaster + battery box | 2026-05-05 |
| [[riley]] | Level 2-3 | Strong CAD operator, rebuilding climber | 2026-05-05 |
## Training Resources
- **FIRST Tech Docs** — [YAGSL Documentation](https://github.com/Team2910/YAGSL-Allwpilib)
- **Chief Delphi** — Swerve share thread (tons of student-built robots)
- **SDS MK4i Product Page** — [SDS Documentation](https://www.swervedrivespecialties.com/products/mk4i)
## Prerequisites
- Basic Git usage (for cloning YAGSL)
- Basic Java (for reading/changing robot code)
- Fusion 360 basics (for understanding CAD if doing mechanical track)
## Gaps Detected
> **MrC monitoring:** This hub tracks learning path completion. Gaps surface when:
> - A student is stuck on a concept for >3 days
> - A hub link points to a missing document
> - Student profile shows no progress in 7+ days
---
*Hub managed by MrC. Add students, update progress, link new training modules as they're created.*

View File

@@ -0,0 +1,138 @@
---
title: "Hawk Collective 2890 — Our Story"
tags:
- onboarding
- 2890
- team
- history
- identity
type: training-module
track: entry
owner: 2890
---
# Hawk Collective 2890 — Our Story
## Who We Are
Hawk Collective 2890 is Hickory High School's robotics team. We compete in the FIRST Chesapeake District. We are builders, programmers, designers, welders, machinists, and strategists. We're a team that believes in showing up for each other and leaving things better than we found them.
We're not the biggest team. We're not the richest team. But we've been at this since 2009, and we're still showing up.
**Rookie year:** 2009 — sixteen years and counting
**Location:** Hickory High School, Chesapeake, Virginia
**School address:** 1996 Hawk, Chesapeake VA 23322 — phone: 1-757-421-HAWK
**Competition area:** Chesapeake District (Virginia/Maryland)
## Why "Collective"
Most teams call themselves "The Hawks" or "Team 2890." We say Hawk *Collective*.
"Collective" is what we believe: the team is bigger than any one person. If one of us wins, we all win. If one of us is struggling, we all step up. The robot doesn't get built by a star — it gets built by a team.
When the 2009 senior class picked that name, they were saying something true about themselves. They knew they'd built something bigger than their own experience. The name stuck because the idea behind it was right.
## How We Got Here
### 2009 — The Beginning
A group of Hickory students looked at what other schools were doing and decided they wanted in. No robotics program existed at the school. No shop, no tools, no real budget, no experience.
What they had was a gymnasium they could use for storage, a salvage yard of mechanical parts, and six weeks to build a robot from nothing. They didn't know what they were doing. They did it anyway.
That original team of maybe 10 students is the reason you're reading this now. They made the space for everyone who came after.
### 20102015 — The Learning Years
These were the years of figuring it out. How to build something that doesn't fall apart. How to program it so it actually does what you want. How to compete without falling apart when things go wrong.
The team survived on bake sales, donations from local businesses, and the kind of stubbornness that comes from not knowing any better. Budget was nonexistent. Every tool was earned. Every competition was a road trip in someone's parents' van.
These were also the years that built the culture. The older students who figured things out started teaching the younger ones. The idea that you help the person next to you — that you don't hoard knowledge — started here. It's still how we operate.
### 20162020 — The Growth
The team got real. Students started bringing their younger siblings. The school started putting real money into the shop. Mentors from industry started showing up — engineers from the naval shipyard, machinists from local manufacturing, teachers who saw what this team was actually building in students.
This is when the team stopped being "some kids in a gym with a robot" and started being what it is today. The shop got actual tools. The team got actual space. The expectations got higher.
### 2021Present — What You Joined
The team that exists right now, today. We've got a culture of showing up, learning out loud, and not quitting when it gets hard. Seniors who came in as freshmen learned to weld, code, and design because someone before them decided to teach instead of just doing it themselves.
We're still not the biggest or the richest team in the district. But we've got something that matters: a team that believes the person next to them deserves what they know.
## How We're Organized
### Students Run This
Not metaphorically. Actually.
Students make the real decisions on design, build strategy, competition moves, and team priorities. Mentors teach, guide, keep people safe, and share what they've learned. But the work belongs to the people doing it.
If you want to own a system on the robot — electrical, mechanical, code — you can. You just have to learn the fundamentals first and prove you won't break something expensive on a guess. The point of this team is to make you capable, not dependent.
Every senior on this team should be able to teach what they know. That's how we get better.
### The Roles
| Role | What It Means |
|------|--------------|
| **Build** | Mechanical — welding, machining, assembly, field setup. If it moves or holds something, Build makes it happen. |
| **Electrical** | Power and sensing — wiring, pneumatics, battery management, sensor integration. The nervous system and circulatory system of the robot. |
| **Programming** | Robot code, vision systems, autonomous routines, driver station setup. The brain of the robot. |
| **Scouting** | Data and strategy — watching other teams, analyzing match data, informing alliance selection. Intelligence for the competition. |
| **Media** | Team branding, documentation, outreach. How the world sees us. |
You can do more than one. Most people do. Nobody starts knowing everything.
## What We Expect From You
**Show up.**
Consistency beats talent. The person who never misses a meeting will outlast the genius who shows up when they feel like it. You don't have to be the best builder or the fastest coder on day one. You just have to keep showing up.
**Ask questions.**
Every expert on this team was once a beginner who asked. There are no stupid questions in this shop. There are only questions you didn't ask and now something's broken. If you're confused about how something works, ask the person next to you. If they're busy, wait and ask a mentor. If you still don't understand, ask again.
**Admit when you're stuck.**
"I don't know" is not a weakness. It's the starting line for learning. The only thing that will get you in real trouble is pretending you know something you don't. Nobody is going to yell at you for not knowing something. They will yell at you for breaking something expensive because you didn't ask.
**Help others.**
If you know something that someone else doesn't, you haven't earned the right to keep it to yourself. The person who helps others doesn't lose their advantage — they strengthen the whole team. A team where everyone shares what they know is a team that wins.
**Take care of the space.**
The shop, the tools, the robots, the field elements — these belong to the team. Not to you. Not to any one person. Leave them better than you found them. If something is broken, tell someone. If something is about to break, tell someone. If you borrowed something, return it.
## What We Believe
> We show up. We learn out loud. We don't quit.
This isn't a motto. It's how we operate when things get hard.
If something breaks, we fix it. If someone is behind, we catch them up. If the game is hard, we figure out a way. If we lose, we shake hands and come back smarter. If something isn't working, we don't pretend it is — we acknowledge it and we solve it.
You will fail at something on this team. Everyone does. The difference between the person who grows and the person who quits is that one of them keeps going after failing.
## The Gear We Run
Team 2890's current standard drivetrain is **MK4i swerve modules** with **NEO Vortex** motors. Here's what that means:
**MK4i swerve** means each wheel can steer and drive independently. It's a more complex drivetrain than tank drive, but it gives you directional control that's worth it for most game tasks.
**NEO Vortex** is the motor. Made by REV Robotics. Fast, powerful, and reliable when configured correctly.
Each motor runs a **SPARK Flex** controller, which handles the CAN communication between the motor and the roboRIO (the robot's main computer).
For vision, we use **PhotonVision** with **Limelight** sensors. This lets the robot see the field, locate itself, and aim at targets automatically.
If you don't know what any of that means yet — good. That's what the garden is for.
---
**Next:** [[youth-safety|Youth Safety]] — read this before you touch anything in the shop

View File

@@ -0,0 +1,170 @@
---
title: "FIRST Robotics — The Big Picture"
tags:
- onboarding
- first
- history
- philosophy
- gracious-professionalism
- coopertition
type: training-module
track: entry
owner: 2890
---
# FIRST Robotics — The Big Picture
> "The vision is to transform our culture by creating a world where science and technology are celebrated, where young people dream of becoming science and technology heroes."
> — Dean Kamen, Founder of FIRST
## What Is FIRST
FIRST stands for **For Inspiration and Recognition of Science and Technology**. It was founded in 1989 by Dean Kamen — an inventor best known for the Segway, but more importantly, a guy who looked at American culture and decided that kids needed to see engineering as something worth doing, something heroic.
Kamen's problem was simple: science and tech were being taught as abstract, boring, solo work done by people who couldn't talk to anyone. Athletics got all the glory — the team jerseys, the pep rallies, the crowd cheering. He thought, why can't building a robot feel like that? Why can't engineering be just as exciting, just as celebrated?
So he built FIRST. And it changed everything.
Every year, FIRST releases a new robotics competition. Teams of students — high schoolers, mostly 14 to 18 years old — have **six weeks** to design, build, and program a robot that can compete in that year's game. Not a toy. Not a kit you assemble from instructions. A real machine, built from scratch, that has to actually work under pressure on a competition field.
There are four programs under the FIRST umbrella:
- **FIRST Lego League (FLL)** — ages 9-14, robots made from Lego parts
- **FIRST Tech Challenge (FTC)** — ages 12-18, more sophisticated robots, still student-built
- **FIRST Robotics Competition (FRC)** — the big one, what we do at Hawk Collective 2890
- **FIRST Championship** — the world finals where the best teams from every district compete
We're FRC. 3,000+ teams worldwide. The biggest robotics competition for high school students that exists.
If you've never seen an FRC match, stop reading this and watch one. Search "FRC match" on YouTube. Watch three minutes. Then come back. It'll make everything else on this page make sense.
## Why FIRST Exists
Here's the uncomfortable truth about how most school works: you learn something, you take a test, you forget it. The system is built for compliance and individual performance. Collaboration is a footnote. Failure is something to avoid, not learn from.
FIRST is the opposite.
You will fail. I'm not being negative — I'm being honest. Your first prototype will break. Your code won't work the first time. Your robot will do something embarrassing at your first competition. This is not a bug. This is the entire point.
The work is hard. The problems are new every year. The deadline is always coming. You have to work with people who have different skills than you. You have to ask for help and give help. You have to learn to lose without quitting and win without being insufferable.
That's what FIRST is building. The robot is the vehicle. The point is what happens to the people who build it.
> Students who participate in FIRST are twice as likely to major in science or engineering. That's not a marketing stat — that's a documented outcome of what happens when you give young people real problems to solve with real consequences and real teammates.
## The Three Core Values
FIRST has three guiding principles. These aren't suggestions. They're how you're supposed to act, on and off the field. Everyone in FIRST — students, mentors, volunteers — is supposed to live by these.
### Gracious Professionalism™
Coined by Woodie Flowers, a MIT professor and FRC legend who died in 2009. Gracious Professionalism means: compete hard, but treat people with respect. Win or lose, you shake hands. If another team needs help, you give it — even if it helps them beat you later.
The goal is to raise the bar for everyone. Not knock others down to raise yourself.
No trash talk. No sabotage. No burning bridges. If you won because you cheated or because you refused to help someone, you didn't really win.
This sounds soft until you see it in action. Watch an FRC match where two robots from rival schools bump into each other mid-game. Watch them both stop, assess, and figure out how to keep going. That's gracious professionalism.
### Coopertition™
Coopertition means: cooperate + competition. You can compete fiercely and still work with other teams. In FRC tournaments, teams form **alliances** of three robots for each match. That means you're often working with teams you just met, who might be your competitors in a later round.
It sounds contradictory until you see it in action. Watch alliance selection at a big event — top teams picking their partners, knowing full well they might face those same teams in the finals. And they still share strategy, still help each other debug.
### Invention and Innovation
No two FIRST seasons look alike. The challenge changes. The field changes. The scoring changes. The strategy changes. You cannot coast on last year's winning design. You have to think about the problem, not just copy a solution.
This is the value I personally think matters most for your future. The ability to look at a new problem and figure out how to solve it, without someone handing you the answer — that's rare. FIRST gives you practice at it.
## The Competition Structure
### District Events
Most FRC teams compete in district events first. These are smaller competitions run by regional FIRST organizations. We compete in the **Chesapeake District**, which covers Virginia and Maryland. Most of our travel is within a few hours of home.
District events are intense. You show up, you calibrate your robots, you compete in qualification matches where the alliances are randomly assigned. You scout other teams — watch their robots, figure out their strengths and weaknesses, plan your strategy. Then comes alliance selection, where the top teams pick their partners for the finals.
Points earned at district events accumulate over the season. Teams need enough points to qualify for the District Championship.
### District Championship
Top qualifying teams from the district face off. This is where it gets serious. The competition is harder, the stakes are higher, and the field is smaller. In the Chesapeake District, only the top teams make it this far.
### FIRST Championship
The world championship. All districts from all over the planet send their best. For most teams, this is a once-in-a-lifetime experience. The energy in the arena is unlike anything else in robotics — 10,000 students in one building, all cheering for engineering.
Hawk Collective 2890 has never been to Championship. That's not a secret. It's a goal.
## How a Season Works
### January — Kickoff
Somewhere between the first and second week of January, FIRST releases the new game. It's a global event — every team worldwide watches the same stream at the same moment. The reveal is theatrical, sometimes with a celebrity host or a surprise guest.
You get the game manual, the field specs, and six weeks on the clock. That's it. That's your season.
### Build Season — Six Weeks
This is the intense part. Most teams work nights and weekends. You design, prototype, fail, redesign, build, wire, program, test, break something, fix it, and repeat until you run out of time.
The last week before the build deadline is when the real crunch happens. The robot has to be bagged and tagged — no more work allowed after the deadline unless it's at a competition.
If that sounds stressful, it is. But it's also when you learn the most. There's no substitute for real pressure with real stakes.
### Competition Season
After bag day, you have a few weeks before your first event. Time to practice driving, refine autonomous routines, prepare your scouting system, and get the robot ready to ship.
Then: district events. Qualification matches, alliance selection, playoffs. You compete, you learn, you come back and fix things. Some teams go to two or three events before they're done.
### Off-Season
This is where real growth happens for most teams. No competition pressure. Time to train new members, fix the problems you identified during the season, redesign the things that didn't work, and get better at the skills that take time — machining, coding, driver practice.
Summer is also when most teams attend off-season events — competitions that don't count toward qualification but give you match experience in a lower-stakes environment. This is how good teams get great.
## How a Match Works
Every FRC match runs the same way:
### Autonomous Period — 15 Seconds
The robot runs pre-programmed instructions. No driver control. This is where good programming pays off — the robot has to make decisions and move without human input.
Autonomous is often the difference between winning and losing. A robot that can score during autonomous gives its alliance a head start that Teleop has to capitalize on.
### Teleoperated Period — 2 Minutes
The drivers take control. This is where human skill matters most — the driver, the manipulator, the human player, and whoever's calling the strategy from the stands.
During Teleop, alliances score points by completing game objectives. Scoring changes every year. Sometimes it's stacking cubes on a scale. Sometimes it's shooting balls into a goal. Sometimes it's climbing. Every year is different.
### End Game — Final 30 Seconds
Usually the hardest scoring objectives. The robots are trying to do things like climb, perch on a rung, or make last-second shots. This is where matches are decided — a good End Game can overcome a rough Teleop.
## The Point Isn't the Robot
Read this sentence twice: the robot is a means to an end.
You will spend hundreds of hours on this machine. You will miss sleep. You will argue with teammates about design decisions. You will have moments of pure frustration when nothing works.
And then you will have moments when everything clicks — when the code runs clean, when the mechanism works for the first time, when the driver pulls off a play you didn't think was possible.
The robot is the tool. The point is what you learn making it:
- How to solve problems when you don't have all the answers
- How to work with people who don't think like you
- How to fail and come back
- How to ask good questions
- How to finish something hard
If you leave this team knowing how to do those things, the robot did its job.
---
**Next:** [[2890-our-story|Hawk Collective 2890 — Our Story]]

View File

@@ -0,0 +1,209 @@
---
title: "Youth Safety"
tags:
- onboarding
- safety
- conduct
- youth-protection
- required
type: training-module
track: entry
owner: 2890
---
# Youth Safety
> Read this before you touch anything in the shop. This is not optional.
## Why This Matters
The robotics shop has real tools. Saws, lathes, grinders, welders, batteries that can start fires if you treat them wrong. The work here is exciting and hands-on — and it will hurt you if you don't respect it.
Safety isn't about following rules because someone told you to. It's about not getting hurt. That's it.
I've seen students rush through something because they wanted to get it done, skip a step because it seemed minor, and end up in the emergency room. Not at this team — I've never seen it happen here. But I've seen near-misses that should have been warnings.
The rules in this document exist because someone, somewhere, got hurt doing what you're about to do. Learn from their experience, not your own.
## Workshop Safety — The Non-Negotiables
These are not suggestions. These are how you stay in one piece.
- **Safety glasses on.** Always. Not when you remember, not when it's just a quick cut — always. A particle in your eye will ruin your day permanently.
- **Closed-toe shoes.** No exceptions in the shop. Flip-flops and sandals are for the beach, not the machine shop.
- **No working alone.** Every tool operation needs a second person nearby. If you're using a power tool, someone else should be in the shop with you, watching, not just in the building.
- **Hair tied back.** Loose hair catches in lathes and drill presses. It's an easy fix — ponytail, bun, whatever works.
- **Gloves only when appropriate.** Not on rotating tools. Gloves can catch on a spinning shaft and pull your hand in. Use gloves for welding, for handling rough materials, for moving heavy things — not for anything with a spinning blade or bit.
## Tool-Specific Rules
Every tool in this shop can hurt you if you don't know what you're doing. Here's what you need to know about the ones you'll use most.
### Lathe
A lathe spins your workpiece while you cut into it with a stationary tool. Used for making round parts, cylinders, threads.
**What kills people on lathes:** loose clothing, rings, or watches catching on the spinning stock; holding the workpiece by hand instead of clamping it; reaching across the spinning chuck.
**Rules:**
- No loose clothing, no rings, no watches, no bracelets. Long sleeves must be fitted at the wrist.
- Always clamp your workpiece. Never hold it by hand while the lathe is running.
- Let the tool do the work. Forcing the cutting tool causes chatter, bad parts, and broken tools.
- If something sounds wrong — a chatter sound, a vibration that isn't normal — stop the machine and check before continuing.
### Mill
A mill holds a cutting tool in a spindle and moves it into your workpiece, which is clamped to a table. Used for flat surfaces, slots, holes, and more complex shapes.
**What kills people on mills:** the spinning endmill catching loose material or clothing; improperly clamped workpieces being thrown by the cutting force; touching the cutting tool while it's still spinning.
**Rules:**
- Secure your workpiece to the table with clamps or a vise before you start. Never rely on the friction of the table alone.
- Bring the cutter down to the workpiece slowly. Use the rapid override carefully near the material.
- Let the chip escape. Accumulated chips are hot and can burn. Use a brush or chip hook to clear them, not your fingers.
- After cutting, let the spindle stop completely before adjusting anything or clearing chips.
### Drill Press
A drill press holds a drill bit and pushes it down into a clamped workpiece. More precise than a hand drill.
**What kills people on drill presses:** clothing or hair catching on the drill chuck; holding the workpiece by hand instead of clamping it; using too much pressure and breaking the bit.
**Rules:**
- Clamp your workpiece to the table. Never hold it with your hand.
- Long hair must be tied back. A drill press grabs hair just as easily as a lathe.
- Use the correct speed for the material and bit size. The drill press speed chart is on the wall by the machine.
### Welder (MIG)
Welding joins metal by melting it with an electric arc and fusing it together. We use MIG welding (Metal Inert Gas), which feeds wire through the gun and uses a shielding gas to protect the weld from contamination.
**What kills people with welders:** eye damage from the arc flash; burns from hot metal; fumes from welding galvanized or painted metal; fire from sparks landing on flammable material.
**Rules:**
- Welding helmet on *before* you strike the arc. Off only after the last weld is complete and cooled.
- Wear leather gloves, long sleeves, and a closed collar. Sparks go everywhere.
- Fire extinguisher must be within reach before you start. Know where it is.
- Ventilation matters. Welding produces fumes that will make you sick if you breathe enough of them. If the space doesn't have good airflow, don't weld until it does.
- Inspect your equipment before every use: wire spool, ground clamp, cable condition. Damaged equipment doesn't just fail — it can catch fire.
### Angle Grinder
A grinder spins a disc at high speed for cutting or grinding metal. The disc is fragile and can shatter if damaged or misused.
**What kills people with angle grinders:** a cracked or damaged disc exploding at high RPM; the disc grabbing and kicking the tool; sparks igniting flammable material.
**Rules:**
- Inspect the disc before you turn the grinder on. Look for cracks, chips, anything that doesn't look right. If in doubt, don't use it.
- The guard must be in place. It routes sparks away from you.
- Hold the grinder with two hands. If it kicks, you want control.
- Face the grinder away from your body and away from anyone else in the line of fire.
- Let the disc reach full speed before you touch it to the material. If it sounds wrong, stop and check.
### Band Saw
A band saw has a continuous toothed blade that runs between two wheels. Used for cutting metal stock to length, curved cuts, and more.
**What kills people on band saws:** reaching across the blade while it's running; removing cutoffs before the blade has stopped; using the wrong blade tension or speed for the material.
**Rules:**
- Never reach over the blade. Ever. Even if it's a small piece.
- Let the blade come to a complete stop before adjusting the workpiece, changing the blade guide, or removing the cutoff.
- Remove cutoffs with a push stick or a piece of scrap wood. Not with your fingers. The piece gets hot, and your fingers are in the path of the blade if it slips.
## Electrical Safety
FRC robots run on **12V lead acid batteries** and powerful motors that draw significant current. A fully charged battery can deliver enough current to cause serious burns and start fires if shorted across metal tools.
### Battery Rules
- **Never touch both terminals with metal at the same time.** A wrench or screwdriver across both terminals = instant short = severe burns and possible fire. This is not hypothetical. This has injured FRC students.
- **Check the battery case for cracks or leaks before you use it.** If the case is damaged, do not charge or use it. Take it to a mentor and tell them.
- **Charge in a safe area.** Nothing flammable nearby. The charger can produce heat.
- **Transport upright.** Lead acid batteries can leak acid if tipped. Keep them upright always.
- **Keep terminals covered.** When a battery is not in use, keep the terminal covers on to prevent accidental shorts.
### When the Robot is Powered
- **No working on electrical systems while the robot is powered.** This means disconnect the battery before you touch anything in the electrical bay. Not "be careful" — disconnect.
- If you need to test something with power, tell a mentor and make sure you're using proper technique.
- **If you smell burning — burning plastic, burning metal, anything wrong — disconnect the battery immediately, step back, and tell a mentor.** Do not continue. Do not assume it'll be fine.
- 12V can also charge capacitors that hold charge after the battery is disconnected. If you're working on high-capacitance circuits, discharge them before touching.
## FIRST Youth Protection
FIRST requires all teams to follow Youth Protection guidelines. These are non-negotiable.
### Two-Deep Leadership
No adult is alone with a student. Ever. If a mentor asks you to stay after a meeting one-on-one, if an adult is regularly messaging you on a private channel, if someone you barely know wants to spend time alone with you — that's not normal. Tell Mr. Slater or a mentor you trust. You will be heard. Nothing you report will get you in trouble for reporting it.
### Background Checks
Every adult who works with students on this team has a current background check on file. If you see a new adult in the shop working with students and you don't recognize them, it's okay to ask if they're on the roster. You have a right to know.
### Communication
Students and mentors communicate in shared team channels. Nobody should be in a private DM relationship with a mentor that nobody else can see. If you get a message that feels wrong — even if you can't explain exactly why — tell someone.
### The Rule
> If something feels wrong, it probably is. Say something.
You will never get in trouble for reporting something. You might get in trouble if you knew something was wrong and stayed quiet.
## Online Conduct
Our team communicates through Discord. This is a professional space, not a gaming chat.
**Be respectful.** What you say here represents the team. Don't forget that other teams, sponsors, and members of the public can see what you post in public channels.
**No harassment, slurs, or targeted cruelty.** Zero tolerance. This includes jokes that aren't jokes, comments about someone's identity or background, and anything that makes another team member feel unsafe.
**No sharing personal information** about yourself or others in public channels. Your real name, your address, your phone number, other people's names — keep it in the team space.
**Keep it on topic in each channel.** #build-chat is for building. #programming is for code. General is for things that don't fit elsewhere.
Violations don't get warnings. They get consequences.
## Consequences
| What Happened | What Happens |
|--------------|--------------|
| Minor mistake, nobody hurt | We talk about it. You learn. |
| Repeated minor mistakes | One-on-one. Parents notified. |
| Dangerous behavior | Removed from the shop until a safety review. |
| Intentional harm or harassment | Removed from the team. No debate. |
Mr. Slater makes the call on anything beyond minor. But the point of consequences isn't punishment — it's so everyone goes home in the same condition they arrived.
## When You're Not Sure — Stop and Ask
This is the most important sentence in this document:
> If you don't know how to do something safely, **do not guess**. Ask.
A mentor, a senior student, Mr. Slater — it doesn't matter who. "How do I set up this piece in the mill?" is not a stupid question. "I didn't ask and now my hand is hurt because I assumed I knew what I was doing" is a stupid thing to explain to an urgent care nurse.
You will not be judged for not knowing something. You will be judged for not asking.
## Pre-Shop Checklist
Before you touch any tool in the shop, make sure you can answer yes to all seven of these:
- [ ] Safety glasses on
- [ ] Closed-toe shoes
- [ ] Hair tied back (if applicable)
- [ ] A mentor or senior student is in the shop with you
- [ ] You know where the first aid kit is
- [ ] You know where the fire extinguisher is
- [ ] Someone has shown you how to use this tool — not just told you, shown you
If you're not sure about any of these, ask before you start.
---
**Previous:** [[2890-our-story|Hawk Collective 2890 — Our Story]]
**Next:** Complete the Entry Path — you have finished the required onboarding for Hawk Collective 2890. The garden branches from here.

View File

@@ -0,0 +1,68 @@
---
title: "Entry Path — Everyone Starts Here"
tags:
- pathway
- entry
- onboarding
- required
type: training-pathway
track: entry
owner: 2890
---
# Entry Path — Everyone Starts Here
> **Required for all team members.** No exceptions. Read in order.
---
Welcome to Hawk Collective 2890.
Before you touch a tool, write a line of code, or step into the shop — walk this path. It doesn't matter if you're a freshman who's never seen a robot or a senior who's been doing this for years. These three stones are for you.
They'll tell you what FIRST is, who we are, and how we stay safe.
---
## Stone 1 — [[first-robotics-overview|FIRST Robotics — The Big Picture]]
What is FIRST? Why does it exist? What do the competitions look like? How does the season work?
Start here to understand the world this team lives in.
---
## Stone 2 — [[2890-our-story|Hawk Collective 2890 — Our Story]]
Who are we? How did we get here? How are we organized? What do we actually believe?
This is the team you're joining. Know it before you help build it.
---
## Stone 3 — [[youth-safety|Youth Safety]]
Required reading. Shop safety, electrical safety, online conduct, FIRST Youth Protection.
Read this before you touch anything in the shop. Keep reading it until the rules aren't rules anymore — they're just how you operate.
---
## After You Finish
You've completed the Entry Path. You've earned the right to call yourself part of the team — not because you read some pages, but because you took the time to understand what you're part of.
From here, the garden branches. Your role, your interests, your questions — they guide you from here.
- Building? → [[swere-training-hub|Swerve Training Hub]]
- Programming? → [[2890-codebase-index|Codebase Index]]
- Electrical? → [[power-distribution-hub|Power Distribution Hub]]
- Something else? → Browse the [[training-hubs|Training Hubs]]
Or keep wandering. The paths cross.
---
*Entry Path — required onboarding for all team members*
*Voice: Young Alumni / Senior Student*
*Status: Active*