Engineering Practice

Development methodology, tooling, distributed systems, and operational patterns.

3 papers·October 2026
01

Your CI/CD Pipeline Knows More About Your Codebase Than You Do

TELOSIS-RP-2026-012·October 2026

Continuous integration and continuous deployment pipelines execute every commit, run every test, build every artifact, and log every failure. Over months and years, a CI/CD system accumulates more knowledge about a codebase than any individual developer. It knows which files break most often, which tests are unreliable, which authors introduce the most regressions, and which hours of the day produce the worst code. This data is a surveillance record of engineering behavior. It is unencrypted. It is unregulated. It is accessible to anyone with pipeline admin access. This paper documents what CI/CD systems actually record, who can access that data, and how it could be weaponized against individual developers. It proposes a framework for pipeline data governance that preserves operational value while protecting developer privacy.

Read paper →
02

Exportability as a Structural Property

TELOSIS-RP-2026-007·July 2026

Most software platforms offer data export as a feature - a button in the settings menu that generates a CSV or JSON file. This paper argues that exportability is not a feature. It is a structural property of software architecture that determines whether a user can truly leave a platform without losing their data, their workflows, or their history. We define five conditions for structural exportability, examine common failure modes, and present the export architecture implemented in Covenant and Foundry, products of CODECX.

Read paper →
03

Documentation That Survives

TELOSIS-RP-2026-008·July 2026

Most documentation is written for the present: for the current team, the current architecture, the current understanding of the system. When the team changes, the documentation becomes incomprehensible - or worse, misleading. This paper presents patterns for writing documentation that survives: documentation designed to be understood by someone who joins the project five years after the original authors have left. We define the documentation stack, identify what must be documented and what should not be, and present the documentation standards adopted across TELOSIS brands.

Read paper →