AI Dev Days

Repository rename: BradGroux/openclaw-dev-days became BradGroux/ai-dev-days on July 30, 2026. GitHub redirects the former repository URL. Existing clones can update their remote with git remote set-url origin https://github.com/BradGroux/ai-dev-days.git. See MIGRATION.md for the event-folder path changes.

AI Dev Days is an independent learning community and event repository. It helps people investigate, define, perform, verify, and improve useful work with AI.

AI Dev Days adopts Open Framework Commons v1.0.0 as its shared philosophical foundation. The adopted release is pinned to:

• repository: BradGroux/open-framework-commons
• tag: v1.0.0
• release commit: a0f0d384e9010a65d1a21a324b4c912433d5e031

Commons supplies shared principles and boundaries; it is not a parent product or operating method. AI Dev Days independently owns its curriculum, events, community practices, examples, research, governance, roadmap, and releases.

The AI-Native Operating Framework is one ecosystem product AI Dev Days may teach or apply. Its methods govern representations of that framework, not AI Dev Days as a whole.

OpenClaw is the deepest existing tool-specific track in this repository. Codex and other tools also appear in event material. Tools provide the implementation context, not the program identity.

The point is simple: get people to one reviewable operating win quickly, then show them how to extend and improve it.

The program follows a source-grounded research-to-education method. Raw research has no authority on its own, event experience does not become reusable curriculum automatically, and every material lesson receives an accountable disposition.

For a visual orientation to that learning loop and the Commons ownership boundary, use the AI Dev Days Program Map.

Choose your path

Start with START-HERE.md if you are not sure which file you need.

• Attendees: use the event-specific links your facilitator shared.
• Facilitators: use RUNBOOK.md.
• Organizers: copy event-specific/_template/ for a new event.
• Curriculum: use curriculum/README.md and curriculum/course-map.md.
• Shared foundation and independence: use CHARTER.md and the adopted Open Framework Commons v1.0.0.
• Visual program orientation: use docs/program-map.md.
• AI-Native Operating Framework teaching guide: use docs/ai-native-operating-framework-alignment.md when an event or lesson selects that framework.
• Program charter and authority: use CHARTER.md and GOVERNANCE.md.
• Research and education method: use docs/research-and-education-method.md.
• Research: use research/README.md.
• AI literacy alignment: use docs/ai-literacy-framework-alignment.md.
• Contributors: review CONTRIBUTING.md and PUBLICATION-SAFETY.md before publishing.
• Architecture: use docs/openclaw-architecture.md or the visual docs/openclaw-architecture-showcase.html.
• Codebase health: see docs/codebase-audit.md.
• Changes: see CHANGELOG.md.
• Program decisions: see decisions/README.md.
• Release process and notes: see docs/release-process.md and docs/releases/.
• Rename and path migration: see MIGRATION.md.
• Event metadata: see event-specific/events.json and event-specific/refresh-checklist.md.

Featured Event Packets

Featured packet: Houston Business Analysts - August 19, 2026

Interactive session for business analysis practitioners and business-technology partners on turning requirements, process knowledge, and data definitions into durable, reviewable AI context.

• Packet: event-specific/2026-08-19-houston-business-analysts-codex/README.md
• Slides: slides.html / slides.pdf (27-slide high-resolution export)
• Speaker notes: speaker-notes-65-minute.md
• Curriculum map: curriculum-map.md
• Session plan: session-plan.md
• Attendee workbook: attendee-workbook.md
• Prompt pack: prompt-pack.md
• Fictional demo: demo/README.md

The editable HTML deck is the visual source of truth. The PDF is published from one dark-theme 1920x1080 screenshot per #slideN, preserving HTTPS links.

Historical packet: Personal AI Agents LIVE - July 21, 2026

Workshop packet for developers, builders, security practitioners, product leaders, and AI workflow adopters.

• Packet: event-specific/2026-07-21-personal-ai-agents-live/README.md
• Product Requirements Document (PRD): event-specific/2026-07-21-personal-ai-agents-live/PRD.md
• Slides: slides.html / slides.pdf
• Speaker notes: speaker-notes-45-minute.md
• Demo workflow: demo/openclaw-prd-workflow.md

Historical packet: H.U.G. Summer Summit AI Panel And Workshop - June 26, 2026

AI panel and workshop packet for educators, students, nonprofit leaders, community partners, and workforce-readiness supporters.

• Packet: event-specific/2026-06-26-hug-summer-summit-ai-panel-workshop/README.md
• Agenda: agenda.md
• Slides: slides.html / slides.pdf
• Speaker notes: speaker-notes-20-minute.md
• Workshop prompts: prompt-pack.md

Additional Past Events

• OpenClaw at Microsoft Build Open Source Zone
• OpenClaw Creator Demo at GitHub Build
• InfraGard Houston AI Agent Workshop
• TAMU OpenClaw Dev Days

Learn more with the community

Dev Days is the starting line, not the finish line. If you want a calmer place to ask follow-up questions, keep building with other operators, and hear about future training, join the Start Small, Think Big community:

• Start Small, Think Big Discord: https://discord.gg/Gmfkm7QVSF

For deeper training, future workshops, and small-business AI/operator playbooks, sign up at:

• Start Small, Think Big: https://sstb.ai

OpenClaw track

For OpenClaw-focused events or personal setup, use the direct installer for your platform, then choose your model provider during onboarding:

• Mac: setup-guides/openclaw-mac.md
• Windows: setup-guides/openclaw-windows.md
• Microsoft Foundry key setup: setup-guides/microsoft-foundry.md

What this curriculum is trying to do

• Turn source-grounded research and practitioner knowledge into useful learning
• Connect AI activity to a clear purpose, owner, outcome, and boundary
• Get attendees from zero to one useful, reviewable operating loop quickly
• Teach operator workflow, not just prompts or terminal commands
• Keep mixed-skill rooms moving together
• Leave behind reusable material other organizers can run with
• Preserve evidence, handoffs, and lessons that survive the event
• Give every material event lesson a visible disposition
• Convert curiosity into accountable practice after the event

The curriculum is aligned to the U.S. Department of Labor's AI Literacy Framework: understand AI principles, explore AI uses directly, direct AI effectively, evaluate AI outputs, and use AI responsibly. See the AI Literacy Framework alignment for the source citation and workshop mapping.

Core stance

• First success beats feature coverage. If people don’t get a working loop early, the rest doesn’t matter.
• Business purpose comes before technology. A tool is learning context, not the program identity or method.
• One standard serves people and AI. Clear operating documentation should work for every authorized participant.
• Scenario-first beats blank slate. Give people a concrete use case instead of a vague platform tour.
• Evidence beats activity. A completed exercise should leave a reviewable result, not only a demo.
• Research remains traceable. Sources, interpretation, uncertainty, and decisions stay distinguishable.
• Events produce evidence, not automatic standards. Reusable changes require review and approval.
• Workshop time is expensive. Anything likely to explode should be preflighted, optional, or moved to helper lanes.

Structure

• curriculum/ — modules, labs, pacing, facilitator notes, including the Markdown thinking-layer module
• setup-guides/ — tool-specific setup, currently centered on the OpenClaw track
• labs/ — attendee exercises with binary success checkpoints, including the Markdown thinking-layer lab
• helper-runbook/ — facilitator triage and rescue-lane guidance
• troubleshooting/ — tool, model, provider, and workshop recovery guidance
• docs/ — product-local methods, optional framework teaching guides, reusable explainers, and visual reference material
• CHARTER.md and GOVERNANCE.md — program purpose, authority, decisions, and release rules
• decisions/ — material program decisions and their rationale
• docs/research-and-education-method.md — canonical program method
• docs/ai-native-operating-framework-alignment.md — authoritative relationship and event-application guidance
• docs/ai-literacy-framework-alignment.md — mapping to the U.S. Department of Labor AI Literacy Framework
• event-specific/ — date-first event packets plus an AI Dev Days-owned reusable template
• research/ — source-grounded notes and dispositions; not attendee instructions
• scripts/ — lightweight repo maintenance and publication safety checks
• CONTRIBUTING.md — contributor workflow, verification, and review checklist
• PUBLICATION-SAFETY.md — public repo safety guidelines for contributors

Current refinement priorities

1. Keep current and upcoming event packets ready to run from the README.
2. Keep AI Dev Days guidance product-local and use external frameworks only when an event or lesson selects them explicitly.
3. Keep first-success paths short and specific to the selected tool track.
4. Keep each event packet public-safe, source-backed, and easy to audit.
5. Preserve useful evidence, decisions, handoffs, and lessons after each event.
6. Exercise the complete research-to-education method through upcoming events and use the evidence to improve version 1.x.

Success criteria

A good Dev Days session ends with most attendees having:

• a business or personal outcome stated clearly
• an accountable human owner and visible decision boundaries
• one useful people-and-AI workflow or scenario attempted
• one reviewable artifact, result, or evidence record
• durable context sufficient to continue the work
• one lesson or improvement captured
• a clear next step after the event

Tool-specific event packets add their own completion criteria. For an OpenClaw track, those criteria may include installation, onboarding, gateway, dashboard, and first-response verification.