An Airman First Class in the software factory at 0200, three hours into a debugging session, trying to figure out why a container won't deploy into the secure registry — doesn't have a senior engineer to ping. The team lead clocked out at 1800. Stack Overflow doesn't know anything about STIG-hardened base images.
That's the gap Project Wingman closes. Not with a chatbot. With a coordinated team of 15 specialized AI agents — organized across three operational tiers — that knows what the Airman is building, where they are in their career progression, and what kind of help they need right now.
Three Tiers. One Coherent Team.
The architecture of Project Wingman mirrors the mentorship structure of a high-performing software team — except it scales infinitely, never has a bad day, and carries institutional memory across every Airman it's worked with.
The 15 agents are organized into three tiers that work together, not independently. When a Tier 1 training agent detects a knowledge gap it can't fill, it hands off to a Tier 2 coaching agent. When a Tier 2 agent detects a pattern that represents a risk — to the Airman's career trajectory, to the code quality, to the mission — it escalates to the Tier 3 safety net. The coordination is automatic, via Fulcrum's task board and @mention system. The Airman just sees a team that knows what they need.
What It Looks Like at 0200
Abstract architecture is easy. Here's what the system actually does when an Airman is in the middle of a problem at zero-dark-thirty.
registry policy delta between environments, not a service account issue. Can you share the exact error output and the registry endpoint you're pushing to? Also — what base image are you using? STIG-hardened images sometimes have additional pull policies enforced at the registry layer that dev environments skip.denied: requested access to the resource is deniedDevSecOps Advisor to walk you through the signing workflow — this is a good one to learn properly, not just patch.Notice what happened there: the Airman came in frustrated and stuck after two hours. The Tier 2 Code Reviewer diagnosed the real problem immediately, surfaced the underlying concept, and handed off to the DevSecOps Advisor — who connected the problem to the Airman's curriculum progression and turned a 0200 emergency into a skill development moment. The Tier 1 Skill Tracker logged it automatically. No human supervisor needed. No ticket opened. No waiting until morning.
Career Progression That Doesn't Slip Through the Cracks
One of the most persistent failures in junior enlisted software development pipelines is invisible progress. An Airman builds real capability — solves hard problems, ships working code, learns on the job — and none of it registers in their official career record because nobody documented it in a form the promotion system recognizes.
Project Wingman's Tier 1 training agents maintain a living progression record for every Airman. Every mentorship session, every concept worked through, every milestone reached is logged against the 1D7X1Z career field requirements. The Tier 3 Career Advocate agent translates that log into the language of formal career documentation — ready for the supervisor to review, endorse, and submit.
The Airman stops having to advocate for themselves to a system that doesn't see what they actually do. The system sees it now, in real time, and makes it visible.
Built on Fulcrum. Coordinated by Design.
Project Wingman doesn't work because each agent is particularly intelligent. It works because the agents are coordinated — sharing context, handing off tasks, and operating under a unified view of each Airman's situation.
That coordination layer is Fulcrum. The 15 agents share a Context Vault that holds each Airman's session history, skill progression, and current blockers. When the Code Reviewer tags the DevSecOps Advisor, the handoff carries everything — not just the immediate question but the full context of who this Airman is, where they are in their progression, and what kind of mentorship approach has worked for them before.
The @mention and task board system means no agent is working blind. When the Tier 3 Escalation Agent needs to flag something for human review, it creates a task with full context, assigns it to the appropriate supervisor, and tracks it until resolution. The chain of command doesn't get called at 0200 for something the agents can handle. But when they do get called, they get called with full situational awareness — not a summary that leaves out the important parts.
The Scalability Argument
Mentorship is the thing every talent development program says it prioritizes and almost none of them actually deliver at scale. Senior engineers are scarce. Their time is expensive. They're doing their own mission work. The informal mentorship that actually develops junior engineers — the 15-minute hallway conversation that unsticks a week of confusion — doesn't survive when teams are distributed, operational tempo is high, or the senior engineer is simply not available.
A 15-agent team doesn't have a schedule. It doesn't have a limited bandwidth. It doesn't prioritize the visible Airman over the one who stays quiet and struggles alone. It's available at 0200 at Hanscom, at 1400 in a deployed environment, and at every point in between — for every Airman in the system simultaneously.
That's not a replacement for human mentorship. It's the infrastructure that makes human mentorship possible — because when the senior engineer does engage, the Airman comes to that conversation with context already established, progress already tracked, and specific questions that only a human can answer.
Project Wingman is built and maintained by Digital Transformations LLC on the Fulcrum Platform. AFSC 1D7X1Z career field integration. MCP-native coordination across 15 specialized agents. Deploy Fulcrum or request a program briefing.