Practical AI literacy for Fulshear students.
The club is shaping a small, practical AI literacy pilot for Jr. High+ students and parents. The first step should be modest: one workshop that teaches students how to ask better questions, test AI outputs, protect privacy, and decide when not to use AI.
The starting point
AI tools are already part of search, writing, coding, design, tutoring, and everyday software. Students need more than shortcuts. They need judgment.
Fulshear AI Club is exploring a student education program that starts small enough to run well. The recommended first pilot is a 90-minute parent-and-student workshop called Prompt, Test, Reflect.
Pilot options compared
| Option | Length | Min volunteers | Feasibility | Educational value | Parent trust | Status |
|---|---|---|---|---|---|---|
| Four-Week Student Workshop Series | Weekly 90-minute sessions | 4 | 3/5 | 5/5 | 4/5 | |
| Parent and Student Orientation Night | 60-90 minutes | 2 | 5/5 | 3/5 | 5/5 | |
| One-Session AI Literacy Workshop | 90-120 minutes | 3 | 5/5 | 3/5 | 5/5 | |
| Builder Studio Model | Recurring open studio (2-3 hours) | 3 | 3/5 | 4/5 | 3/5 | |
| Summer AI Camp Pilot | Half-day or multi-day format | 6 | 2/5 | 5/5 | 3/5 |
Program principles
The program is built on repeatable patterns, not one-off plans. Each pattern describes a problem, the forces at play, a practical solution, and a test to see if it worked.
ethics-in-the-loop
Ethics in the Loop
Problem: Ethics added at the end feels optional.
Solution: Put a brief ethics question inside every activity.
Validation test: Does every student artifact include a risk or responsibility note?
Related:safety-boundary-before-exploration,student-artifact-portfolio
public-demo-as-learning-center
Public Demo as Learning Center
Problem: Learning fades if students only complete private exercises.
Solution: End with a low-pressure share-out of what students tested, corrected, or learned.
Validation test: At least three students can explain a finding or revision in plain language.
Related:student-artifact-portfolio,parent-trust-first
recap-notes-as-institutional-memory
Recap Notes as Institutional Memory
Problem: Volunteer programs forget what they learned.
Solution: After every session, publish or archive concise recap notes: what happened, what worked, what changed, and what remains open.
Validation test: The next facilitator can improve the session using the recap.
Related:feedback-loop-after-every-session,validation-loop
student-artifact-portfolio
Student Artifact Portfolio
Problem: Attendance alone does not show learning.
Solution: Each session produces a small artifact with a reflection note.
Validation test: Students leave with evidence of their own thinking.
Related:public-demo-as-learning-center,prompt-test-reflect
feedback-loop-after-every-session
Feedback Loop After Every Session
Problem: Programs drift when feedback is informal.
Solution: End with three feedback prompts: useful, confusing, concerning.
Validation test: The team records at least one change to make before the next session.
Related:recap-notes-as-institutional-memory,validation-loop
mentor-pairing
Mentor Pairing
Problem: One facilitator cannot support mixed ages and skill levels during hands-on work.
Solution: Pair mentors with small groups and give mentors role cards.
Validation test: Students can describe their own decisions after mentor help.
Related:volunteer-role-cards,safety-boundary-before-exploration
safety-boundary-before-exploration
Safety Boundary Before Exploration
Problem: Students may test tools with private, risky, or inappropriate prompts unless boundaries are explicit.
Solution: Begin every session with a short boundary statement: what not to enter, what not to ask, and when to get an adult.
Validation test: Students can name at least two things not to put into an AI tool.
Related:parent-trust-first,ethics-in-the-loop
tool-before-theory
Tool Before Theory
Problem: Abstract AI lectures can lose students before they build judgment.
Solution: Teach one useful tool workflow, then introduce theory as needed to explain limits.
Validation test: Can students name both what the tool helped with and what it could not be trusted to do?
Related:prompt-test-reflect,ethics-in-the-loop
local-venue-as-civic-anchor
Local Venue as Civic Anchor
Problem: A program without a trusted place can feel abstract or commercial.
Solution: Start in a civic venue if approved, and treat the venue as a partner to respect rather than a backdrop.
Validation test: Families understand where to go, who is hosting, and what is approved.
Related:parent-trust-first,feedback-loop-after-every-session
low-friction-equipment
Low-Friction Equipment
Problem: Requiring expensive hardware or paid accounts narrows access and complicates logistics.
Solution: Design activities that can run with a facilitator demo, shared devices, printed prompts, or student-owned laptops.
Validation test: The session still works if only half of students have devices.
Related:smallest-launchable-workshop,parent-trust-first
smallest-launchable-workshop
Smallest Launchable Workshop
Problem: A large education program is tempting, but too much scope can collapse under volunteer, venue, and safety demands.
Solution: Start with one 90-minute workshop that teaches a single practical workflow and produces one student artifact.
Validation test: Could two to four volunteers run it again next month with modest improvements?
Related:repeatable-session-spine,feedback-loop-after-every-session,parent-trust-first
prompt-test-reflect
Prompt, Test, Reflect
Problem: Prompting alone can train students to accept fluent answers.
Solution: Use a three-step workflow: prompt clearly, test the output, reflect on whether and how to use it.
Validation test: Students can show one check they performed before using an answer.
Related:tool-before-theory,recap-notes-as-institutional-memory
volunteer-role-cards
Volunteer Role Cards
Problem: Volunteers need clear jobs, especially around minors.
Solution: Create role cards for facilitator, logistics lead, mentor, recorder, and validator.
Validation test: A new volunteer can understand their role in two minutes.
Related:mentor-pairing,repeatable-session-spine
parent-trust-first
Parent Trust First
Problem: Families may reasonably worry about privacy, cheating, overreliance, and unsafe tools.
Solution: Invite parents into the first layer of the program and explain safety boundaries plainly.
Validation test: Can a cautious parent explain what the program will not do?
Related:safety-boundary-before-exploration,low-friction-equipment
repeatable-session-spine
Repeatable Session Spine
Problem: Every session designed from scratch increases volunteer burden.
Solution: Use a recurring structure: welcome, boundary, demo, hands-on work, reflection, feedback.
Validation test: Volunteers can swap in a new activity without redesigning the whole session.
Related:smallest-launchable-workshop,feedback-loop-after-every-session
What students would do
Students would complete a small, low-risk activity such as:
- Compare an AI answer against two source snippets.
- Create a study guide from a short public article.
- Turn rough notes into a project plan.
- Generate research questions, then reject weak or misleading ones.
- Draft a simple explainer and mark what still needs verification.
Each student would leave with a short artifact showing the prompt, the checked output, and one reflection about what needed human judgment.
Guardrails
The pilot is built around clear safety boundaries. Every guardrail has a severity level and an enforcement method.
-
No public posting of student work without parent permission
No photos, screenshots, or excerpts of student work are shared on the website, social media, or pitchbook without a signed permission form. Default is private.
-
No grading, ranking, diagnosis, therapy, or private counseling
Explicitly stated in boundary statement and parent handout. Facilitator intervenes if any activity drifts into these domains.
-
Parents may observe or participate
Parents are invited to observe the first pilot. A separate parent orientation may be offered before student sessions. Parents who observe are asked not to interfere with student work unless asked.
-
No sensitive personal information in prompts
Explicit boundary statement at the start of every session. Facilitator monitors demo prompts. Printed handout lists examples of what not to enter.
-
No claim that AI output is correct until checked
Every student artifact must include a verification note. Facilitator checks that students performed at least one check before considering an activity complete.
-
No student accounts required for the first pilot
Activities designed to work with facilitator demo, shared devices, or printed exercises. No account creation required for the first pilot.
Parents and students
Parents are welcome in the first layer of the program. That is intentional. Families should understand the tools, the limits, and the club’s safety posture before the program grows.
Students should expect a practical session, not a lecture about the future. The work will be hands-on, careful, and honest about what still needs to be verified.
Volunteers
A small pilot needs a small, clear team. Each role has defined responsibilities and explicit boundaries.
lead-facilitator
Lead facilitator
Owns:
- Session agenda
- Slide deck
- Pacing
- Instruction delivery
Does not do:
- Handle check-in
- Collect student data
- Manage social media
logistics-lead
Logistics lead
Owns:
- Check-in
- Timing
- Room needs
- Parent questions
- Sign-in process
Does not do:
- Deliver instruction
- Mentor student work
validator
Validator
Owns:
- Reviews public materials for claims
- Checks safety language
- Checks feasibility
- Reviews tone before publication
Does not do:
- Deliver instruction
- Mentor student work
- Handle check-in
- Write content (reviews others' work)
mentor
Mentor
Owns:
- Support student groups
- Ask questions before giving answers
- Monitor for guardrail violations
Does not do:
- Do the work for students
- Deliver instruction
- Handle check-in
recorder
Recorder
Owns:
- Captures feedback
- Records open questions
- Writes improvement notes
- Archives session recap
Does not do:
- Deliver instruction
- Mentor student work
- Handle check-in
Sponsors and partners
Potential partners or sponsors could help with room access, printed materials, snacks if allowed, loaner devices, accessibility support, or mentor volunteers.
The club should not name a partner, sponsor, venue approval, or school relationship until it is confirmed. Any support should preserve student privacy, curriculum integrity, and the club’s practical, evidence-driven stance.
What needs confirmation
Before announcing a date, the club needs to confirm:
- Venue approval and room rules.
- Youth supervision expectations.
- Whether parents should stay for the whole workshop.
- Device and Wi-Fi availability.
- Whether library or shared devices may be used with AI tools.
- What policy applies to students under 13.
- Which volunteers are available.
Next step
The next practical step is to confirm venue rules, choose an age range, recruit two to four volunteers, and prepare a parent-facing workshop notice.