Repository-Centered Engineering
Why the Repository Is Becoming the Engineering System of Record
The repository is becoming the place where an organization turns engineering intent into controlled change—and controlled change into defensible evidence.
Executive Summary¶
Software repositories began as places to preserve source code. They are becoming something more consequential: the operational surface on which engineering organizations express intent, coordinate change, enforce policy, preserve decisions, verify claims, release software, and learn from production.
This shift accelerates in AI-assisted and increasingly agentic delivery environments. Humans and software agents both require authoritative context. Organizations need a durable record of what was requested, what changed, who or what produced it, how it was reviewed, what evidence justified release, and what happened after deployment.
Repository-centered engineering is the disciplined practice of treating the repository and its connected delivery environment as the engineering system of record. It does not mean that every organizational document belongs in Git or that the repository replaces product management, service management, enterprise architecture, governance, or other systems of authority. It means that the evidence needed to understand, challenge, reproduce, release, operate, and improve a system remains connected to versioned artifacts and reviewable workflow.
The paper explains how requirements, issues, branches, pull requests, automated checks, provenance, release records, runbooks, telemetry, incidents, and postmortems form a connected engineering chain. It also examines the repository as executable context for humans and agents, the pull request as an engineering argument, policy as workflow, provenance and supply-chain integrity, the economics of small-batch review, common failure modes, and a maturity path toward a human-agent control plane.
The central conclusion is that code is only one part of the engineering record. The repository becomes professionally valuable when it preserves the chain from intent to operation—not as artifact accumulation, but as a coherent basis for judgment, accountability, automation, and controlled change.
Why Read This Paper?¶
WP-002 provides the operating-model foundation for one of the most important ETIS doctrines: the repository is not merely a code container. It is the environment in which engineering intent becomes reviewable, enforceable, evidenced, and operationally accountable change.
After reading it, you should be able to:
- explain what it means for the repository to serve as the engineering system of record;
- distinguish a connected engineering evidence chain from a collection of disconnected artifacts;
- describe a pull request as a compact engineering argument rather than a merge request;
- explain how repository structure and metadata provide executable context for humans and agents;
- connect governance policy to workflow controls, permissions, reviews, checks, and release gates;
- explain why provenance, SBOMs, and controlled release baselines matter;
- identify common repository-centered engineering failure modes;
- describe an incremental maturity path from code store to human-agent control plane.
Key Topics¶
Intended Audience¶
What the Paper Examines¶
- The evolution from source control to an engineering system of record.
- The engineering record as a connected chain of intent, decision, change, verification, release, operation, and learning.
- Pull requests as professional engineering arguments.
- The repository as executable context for humans and engineering agents.
- Policy as workflow and governance as architecture.
- Provenance, software supply-chain integrity, and controlled release baselines.
- Small batches, fast feedback, and the economics of review.
- Failure modes such as documentation theater, broken traceability, green-check confidence, and process disproportion.
- An operating model and maturity path for repository-centered engineering.
- The ETIS perspective and implications for increasingly agentic delivery environments.
Relationship to ETIS¶
Related Publications¶
- WP-001 — Engineering Trustworthy Software in the AI Era
- WP-003 — Engineering Evidence
- WP-006 — Engineering Governance
- WP-007 — Engineering Review and Readiness
- WP-008 — Operational Readiness
- WP-009 — Context Engineering
- WP-011 — Engineering Trust
- EB-004 — Building an AI Engineering Platform
Citation
IEEE
W. T. O’Connell, “Repository-Centered Engineering: Why the Repository Is Becoming the Engineering System of Record,” ETIS White Paper Series, WP-002, ver. 1.0, July 2026.APA 7th Edition
O’Connell, W. T. (2026). Repository-centered engineering: Why the repository is becoming the engineering system of record (WP-002, Version 1.0). Engineering Trustworthy Intelligent Systems.Chicago
O’Connell, William T. “Repository-Centered Engineering: Why the Repository Is Becoming the Engineering System of Record.” ETIS White Paper Series, WP-002, version 1.0. July 2026.BibTeX
@techreport{oconnell2026repositorycentered,
author = {William T. O'Connell},
title = {Repository-Centered Engineering: Why the Repository Is Becoming the Engineering System of Record},
institution = {Engineering Trustworthy Intelligent Systems},
type = {ETIS White Paper},
number = {WP-002},
year = {2026},
month = {July},
note = {Version 1.0},
url = {https://etisframework.org/publications/white-papers/wp-002/}
}Version History
| Version | Date | Status | Notes |
|---|---|---|---|
| 1.0 | July 2026 | Current | Initial publication. |