About
Where AIQT comes from.
AIQT began inside the GRC Library, a public documentation project whose corpus is written under an AI-managed workflow. The disciplines that kept that work honest proved useful well beyond one project, so they became a standard in their own right.
Origin
Proven in practice before it had a name
AIQT started inside the Governance, Risk, and Compliance Documentation Library (the GRC Library), a public project homed at github.com/jposluns/grc_library, whose document library is written under an AI-managed workflow. It arrived in four steps.
- Built where it was needed. The AI-managed workflow needed rules to keep it honest: every claim tied to its source, every check kept at full strength, nothing called done without a check that ran.
- Distilled into a pack. Those rules were distilled into a portable guardrails pack and applied first to the library's own work, in the same repository the pack protected.
- Proven adoptable. Over time the pack grew into something other people could adopt independently of the document library.
- Given its own home. The guardrails are now being separated into a standalone project, AIQT, which the GRC Library will then adopt, replacing its own built-in copies with the standalone pack. This is a deliberate evolution, not a rebrand: the standard proved general, so it earned its own home.
A sibling project
Clean Language
AIQT is not the first project to leave the GRC Library this way. Clean Language separated first: a free editorial standard that keeps AI writing precise, direct, and natural, spun out of the same library and now a project in its own right (its source is on GitHub). AIQT follows the same route, from a discipline proven inside the library to a standard anyone can use.
Direction
How decisions are made
As the projects progress, decisions about AIQT's evolution are made by lead maintainer Jeff Posluns, and they orient toward one question: what will best help the world.
Open source, portable, and shared is the working answer. Contributing an improvement back is Rule 5's voluntary Guardrail-Seed give-back, separate from the software licence, and the direction is chosen for public benefit rather than lock-in. A guardrail that travels between tools and teams helps more people than one that binds you to either.
The maintainer
Jeff Posluns
Jeff Posluns, CGEIT, CISSP, is a Chief Information Officer and enterprise technology executive with thirty years of leadership, driving enterprise-scale transformations across operating models, ERP, data, and platform modernization for global organizations, with particular depth in enterprise AI.
He builds AI capability end to end, from governance councils and lifecycle controls through to production AI and ML adoption across business workflows. His leadership rests on a deep foundation in cybersecurity, risk, and governance, built over CIO, CISO, and consulting mandates in high-trust, multi-jurisdiction regulatory environments, which keeps his decisions grounded in security-by-design, privacy, and operational resilience. He holds the CGEIT and CISSP certifications, has served as a director of an international non-profit, has co-authored several books, and has presented at industry and academic conferences since the late 1990s.
AIQT is created and led by Jeff, distilling the governance lessons of the GRC Library's AI-managed workflow into a standard other teams can use.