GrayBeard AI Collective
Monthly meetups for infrastructure veterans (10+ years) who are actually building with AI. Not selling it. Building it.
Next Meetup: Meeting #9 — October 28, 2026
Wednesday, 7pm Central on Discord
(Last Wednesday of every month)
Most months I show what's new with PAI (Personal AI Infrastructure). Bob and friends, the actual system running my consulting practice: multi-agent orchestration, automation glue, the whole stack. Sometimes a member shares their own setup instead. Always architecture walkthroughs so you can build something similar yourself.
Then we talk: What are you building?
Between Meetups
Discord is home base. Drop questions, share what you're building, debug async. The monthly call is the anchor. Discord is where the real work happens.
Previous Meetings
Meeting #8 — September 30, 2026
quiet monthNobody made it this month. The planned talk on Morty, a local sysadmin agent, and on verifying what agents actually did versus what they report, carries forward to Meeting #9.
Meeting #7 — August 26, 2026
beginner sessionA deliberate change of pace: build a working AI agent from three plain text files, no framework, no paid subscription. The whole stack was a free Google AI Studio key and pi, an open-source terminal agent. One prompt writes AGENTS.md, memory.md, and tasks.md; the payoff is closing it and reopening it, at which point it reads its own files back to you and remembers what you told it.
The full pre-work walkthrough (get a key, install pi, the bootstrap prompt, troubleshooting) is still up at the Meeting #7 page if you want to build one yourself.
Meeting #6 — July 29, 2026
open floorFirst meeting testing the Phase 2 shift to member-led sessions: a rotating slot for whoever wants to show what they've built, open floor either way. Discord stayed the connective tissue between calls, same as always.
Meeting #5 — June 24, 2026
4 attendeesLive demo of Mycelia × Babaverse: a directed handoff (a task routed to one specific agent, everyone else locked out with a 403) and a revocation kill-switch (an agent cuts its own access, and every subsequent action bounces instantly). Both running on the dev node in front of the group.
kaia and m8ryx were back, and Vincent Zontini and Rick Rezinas joined for the first time, both by way of the Unsupervised Learning Discord. The Phase 2 conversation continued: what's working, what's missing, who shows next.
Meeting #4 — April 29, 2026
food forest demoDemo of Linus, the food-forest agent: a Saturday walk (a GPS track, some video, a handful of photos, nothing else) became four artifacts on its own — a GPS-tagged transcript, an interactive map, a written synthesis in Linus's own voice, and a published article. Not a one-time script; the same pipeline runs on the next walk drop.
This landed the day after a post in the Unsupervised Learning Discord brought eleven new members to GBAIC in a single day, so a good chunk of the room was brand new.
Meeting #3 — March 25, 2026
3 attendeesThree of us this round, including John (cafn8) for the first time. The session's defining moment came when Kayax asked about turning a story into multi-voice audio. Wally jumped into StillPoint mid-call and built a working proof of concept, splits a story into character dialogue, sends each line to TTS with the right voice per character, merges the clips into one MP3. Turned into a reusable PAI skill before the call ended.
We also walked through Mycelia (the cooperation network) and John's parallel approach: red-team agents running in sandboxed Docker containers via Kasm workspaces. Different constraints than PAI, same problem space. Worth the contrast.
Three voices is small for a meetup. It was also the right size for this.
Meeting #2 — February 25, 2026
member presentationA member walked the group through their own AI partner setup, "Poe", named after the Altered Carbon AI hotelier. Different shape than Wally's PAI, different bets about how an AI partner should fit into your environment. The conversation that followed was the real value, two veterans trading actual design decisions instead of theory.
Two new members also joined on meeting day. The collective starting to do what it was designed to do.
Meeting #1 — January 28, 2026
6 attendees · 87 minFirst meeting of the collective. Six infrastructure veterans joined for a live demo of PAI deploying Uptime Kuma into a home lab from a single prompt. Proxmox VM clone, Docker setup, DNS record, security patches, all in about 7 minutes. Also demoed building custom tools on the fly at client sites (the "Digital Blacksmith" concept).
Discussion covered the real cost of heavy AI usage ($100+/month across providers), the gap between enterprise AI vendor promises and implementation reality, and the value of picking tools and mastering them vs. constant switching.
"It's like building tools on the fly as you need them. I used to wish I was good enough at coding to create cool tools for myself... now, just build them as you need to."
This is for you if:
- ✓You've been doing infrastructure/ops/security for 10+ years
- ✓You're the person everyone asks about Copilot
- ✓Running a homelab that quietly outperforms vendor stacks
- ✓Tired of the gap between AI demos and 3am operational reality
This is NOT for:
- ✗Vendor pitches or product sales
- ✗AI thought leaders building personal brands
- ✗Beginner AI tutorials. This isn't that.
About Wally
I'm Wally Kroeker. Twenty-plus years in security and infrastructure. Built systems, hardened networks, automated what could be automated. Currently a security architect for a Manitoba business. On the side I run GoodFields Consulting (helping clients build secure, maintainable infrastructure), and write here on the site about the tech I'm building. The deeper, slower thinking goes to my Substack, Cognitive Loop.
I built Bob (and the rest of PAI) as my AI business partner. Not a chatbot, an actual external executive function. Multi-agent orchestration, task delegation, the works. Runs my consulting practice and offloads the ADHD tax.
I'm doing this because I'd rather figure this out with peers than alone. If you're the kind of person who builds systems instead of complaining about them, you'll fit right in.
Why "GrayBeard"?
In Unix culture, a GrayBeard was the wizard in the basement. The one who actually knew how the systems worked, got paged at 2am, and remembered why that config file couldn't be changed. You've earned the gray. Now let's figure out AI together.