ADR 0006: Repository topology¶
- Status: Accepted
- Date: 2026-09-29
Context¶
Two products come out of the research: the software (the Governed Agent Harness) and the thesis document (LaTeX) that designs, implements and evaluates it. They differ in:
- life cycle: the software keeps evolving after the earlier iteration
v0.8.0; the document follows the academic calendar; - visibility: the software can be public; the manuscript is under institutional review and must not be published before it is approved;
- license: the software is Apache-2.0; an academic work must not end up under Apache-2.0;
- CI: Python tests, packaging and supply-chain controls versus a LaTeX build, word limits and citation checks;
- privacy: the research material behind the thesis (interview transcripts, notes, authoring prompts) must never be published in any repository.
Decision¶
Two repositories, one per product:
SebasBarrera/harness-engineering(this repository): the software, public, Apache-2.0, default branchdevelop, releases onmain.- The thesis document: a separate, private repository. It is deferred by decision of the
author: for now the manuscript stays on the author's machine, outside Git, next to this
repository (
Documento/, ignored by.gitignoreand blocked by the privacy denylist in CI).
A monorepo was rejected because it would force one visibility and one license on both products and mix two unrelated CI pipelines. Public visibility for the code also gives, at no cost, code scanning, secret scanning with push protection, branch rulesets, GitHub Pages and SonarQube Cloud.
Consequences¶
- The code repository links to the thesis by its title and institution (see thesis context); it never contains the manuscript, its figures or its sources.
- Privacy is enforced mechanically:
.github/privacy-denylist.txtandscripts/check_denylist.pyfail CI if a denylisted path is committed, and gitleaks scans the whole history. - When the thesis repository is created, it gets its own CI (LaTeX build, word limits, citation
checks, privacy denylist) and links back to this repository and to the
v0.8.0tag. - The repository has a single maintainer, who integrates work branches into
developwith merge commits and no pull requests; CI must be green on the branch before it is merged. Rulesets block force pushes and deletion ofmainanddevelop. With a second maintainer, the flow moves to pull requests with required reviews and CODEOWNERS. Amended 2026-10-05: the single maintainer also integrates through pull requests (merge commit, every blocking check green, no required review), so the checks that only run on pull requests apply to every change.