About F.O.R.G.E

The Problem

Everyone is building with AI agents. Nobody agrees on how.

Vendors ship runtimes and APIs. Researchers publish theoretical frameworks. But practitioners - the people actually deploying agentic AI into production - have no shared vocabulary, no structured methodology, and no way to evaluate whether their approach will survive contact with reality.

When an AI agent nearly force-pushed to a production repository, there was no playbook for what governance should look like. When a ten-agent team needed to coordinate across domains, there was no established pattern for parallel dispatch. When sessions reset and context evaporated, there was no standard for knowledge persistence.

We built all of it from scratch. Then we organized what we learned so nobody else has to.

Why a Framework?

I swore I would never write a framework. Frameworks are what happens when someone with a whiteboard and a title decides to solve a problem they've never actually had. I've sat through enough of those meetings to know better.

But here's what changed: I watched the results. Teams without operational methodology, without governance, without structured context recovery, without defined authority, produce dangerous output. Agents that force-push to production. Hallucinated facts that ship to customers. Scope that expands until the project collapses under its own weight. These are not theoretical risks. They are the stories that make the news, the ones where the headline is "AI breaks everything" when the real headline should be "team deployed AI without a methodology."

If you're not getting good results with AI agents, there is a point where it stops being the model's fault and starts being an operational problem. The models are good enough. The tooling is good enough. What's missing is the discipline, the same discipline that any high-performing team in any domain has always needed. This framework exists because proven engineering principles from QA, military operations, red teaming, and systems architecture transfer directly to AI collaboration, and the teams that apply them are getting dramatically better results than the teams that don't.

I built this because it worked for us, and I'm publishing it because it will work for you.

What F.O.R.G.E Is

F.O.R.G.E (Framework for Organized, Resilient, Governed Engineering and Development of Agentic AI) is an Agentic AI Creation Framework. It provides 73 methods organized across 8 tactical pillars - a structured, navigable taxonomy for building, governing, and scaling AI agent systems at any level of application.

Modeled after MITRE ATT&CK - the framework that gave cybersecurity a common language for adversary behavior - F.O.R.G.E gives agentic AI a common language for building behavior. Each method is specific, actionable, and comes with implementation guidance, success indicators, and failure modes.

This is not theory. Every method exists because something went right - or more often, because something went wrong and we built the system to prevent it from happening again.

Who It's For

F.O.R.G.E scales to any level of agentic AI application:

• Solo practitioners running 1-3 AI agents: Start with Foundation and Knowledge (~10 core methods)
• Teams of 2-5 humans with multiple agents: Add Governance and Team Design (~25 methods)
• Organizations running scaled AI operations: Implement the full framework (all 73 methods)

If you are using AI agents in production - or planning to - F.O.R.G.E gives you the vocabulary and the playbook.

The Eight Pillars

Origin

F.O.R.G.E was developed by Pete McKernan, drawing from 20 years of operational experience: military command (92 Marines in combat operations), red team operations at the highest classification levels, QA engineering, adversarial security research, and game design.

The methodology was forged - literally - during the first two weeks of running a production agentic AI team: 10 specialized agents, 463,000 words of output, a patent filing, multiple software products, and a governance system built because an agent almost destroyed a repository.

Every structure in F.O.R.G.E maps to proven patterns from domains where getting it wrong has real consequences. Trust tiers are security clearances. Mission briefings are agent invocations. Standing orders are persistent directives. Session handoffs are shift-change briefs. The patterns transfer because the underlying problem - coordinating distributed teams under uncertainty - is identical.

Framework Structure

F.O.R.G.E uses a matrix structure inspired by MITRE ATT&CK:

• Tactics (columns) represent the 8 strategic pillars of agentic AI development
• Methods (cells) represent 73 specific practices within each tactic
• Each method includes a description, implementation guide, success indicators, and failure modes
• Methods are identified by ID (e.g., FG-0101) for precise cross-referencing

Version History

Contribute

F.O.R.G.E grows from real experience. If you've found a pattern that works, a method that's missing, or a sub-method that would make an existing technique more concrete, we want to hear about it.

• Propose a sub-method: Open an issue with what you've learned
• Propose a technique: Open an issue for new methods the framework doesn't cover
• Read the guide: CONTRIBUTING.md explains the process and standards

Contact

F.O.R.G.E is maintained by Pete McKernan. For questions or feedback: [email protected]. Read more at itsbroken.ai.