Repository-Centric Engineering

Repository-centric engineering treats the repository as the primary surface for implementation truth, workflow contracts, and reusable project knowledge.

Type
Concept
Status
developing
Area
repository systems
Confidence
medium
Maturity
early
Concepts
engineering-memory, operational-truth, workflow-contracts, agentic-engineering-workflows
Updated
2026-07-05

Why This Matters

Repository-centric engineering treats the repository as the primary surface for implementation truth, workflow contracts, and reusable project knowledge.

Current Maturity

status: developing; maturity: early; confidence: medium.

Definition

Repository-centric engineering treats the repository as the primary surface for implementation truth, workflow contracts, and reusable project knowledge.

Working Claim

The repository is not only where code lives. It is where an engineering system can preserve the contracts that make future work safer: setup, tests, architecture, release paths, operating boundaries, and local conventions.

Use

Use this concept when deciding whether a lesson should become repo documentation, automation, tests, templates, or agent guidance.

Boundary

The repository should not absorb every operational fact. Runtime evidence, credentials, incidents, and deployment state still belong to their owning systems.