Governance · Optimisation · Agentic Coding
The discipline layer on top of AI-assisted development
LLM-based coding agents have fundamentally altered the pace of software production. VibeOps is the framework that ensures this acceleration produces high-quality software at scale — not just fast software.
Governing the agentic coding environment — rather than optimising the agent or the prompt — is the highest-leverage intervention available to engineering teams.
— VibeOps: A Governance and Optimisation Framework for Agentic Coding Environments · Lauchande, 2026 · DOI: 10.5281/zenodo.18741405
The Problem
The difference between high-quality and low-quality agentic output isn't the model. It's the environment.
Framework Architecture
Composable layers that together form a complete governance system for agentic coding environments.
Contribution I · Environment Contract
AGENTS.mdA structured, version-controlled configuration file governing agent behaviour at the repository level. The agent's onboarding document, constraint system, and tribal knowledge base — all in one file. It gives agents the context senior engineers carry in their heads.
Contribution II · Methodology Layer
A portable methodology layer encapsulating reusable engineering knowledge as composable skill modules. Unlike configuration — which is repository-specific — Agent Skills travel across codebases. They encode how a team thinks about problem-solving, not just what tools they use. This is the essence of Factor VIII.
Contribution III · Evaluation Framework
A multi-dimensional evaluation framework treating development sessions as controlled experiments with separable parameters and metrics. VibeEvals moves teams beyond subjective gut-feel toward reproducible, measurable assessments of agent performance — quantified via the Vibecheck Score.
Contribution IV · Design Principles
An opinionated set of design principles for governed AI-assisted development. Inspired by the Twelve-Factor App methodology, the 12 Vibing Factors provide a canonical checklist for teams building and operating agentic coding environments — from reproducibility to observability.
Measurement
A leading indicator of environment quality — computed before a line of code is written. The higher the score, the smaller the gap between your best engineer and your newest one.
Coming in Phase 3. Tracked via MLflow in Phase 4.
As illustrated above, even in technologically advanced hubs like Birnin Zana, optimizing the environment is the key to agentic harmony.
The 12 Vibing Factors
A canonical checklist for engineering teams operating agentic coding environments at scale.
Factor I
Environment Contract
AGENTS.md as single source of truth
Factor II
Version Control
All agent config tracked in Git
Factor III
Declarative Configuration
Explicit over implicit instructions
Factor IV
Skill Portability
Reusable methodology across repos
Factor V
Bounded Execution
Clear always / ask first / never model
Factor VI
Reproducibility
Sessions as reproducible experiments
Factor VII
Architecture Alignment
Measure distance from blueprint
Factor VIII ★
Methodology / Config Separation
Methodology travels. Configuration stays.
Factor IX
Observability
Session logs as behavioural signals
Factor X
Iterative Environment Design
Environments improve through experimentation
Factor XI
Team Ownership
Config is team property, not individual
Factor XII
Human Governance
Agents operate within human-defined bounds
Factor VIII · The Canonical Principle
"Methodology travels. Configuration stays."
Agent Skills encode how your team thinks — problem decomposition, testing philosophy, code style. These travel across every repository. AGENTS.md encodes what your repository is — its stack, conventions, hard constraints, and tribal knowledge. These stay put. Conflating the two is the most common governance failure in agentic environments.
Living System
VibeOps environments don't require manual maintenance. They are designed to improve themselves.
When the agent discovers something worth capturing — a gotcha, a missing rule, a pattern — it proposes an update. You approve. The file is updated. The change is logged. Every session makes the environment stronger. This is not a file you maintain — it is a file that learns.
Reference Implementation
Not a minimal starter. A fully primed VibeOps environment — showing what maturity looks like in practice. The AGENTS.md is the product.
uv run vibecheck .Planned"In this brave new world, the ability to code a system matters less than the taste to know what it should become."
— fastapi-vibeops-template · README · Natu Lauchande
DOI: 10.5281/zenodo.18741405