Institutional Thinking

Organizational design, long-term strategy, and the economics of independent technology.

3 papers·October 2026
01

Software Rot Is a Policy Failure, Not a Technical One

TELOSIS-RP-2026-013·October 2026

The software industry treats software rot as an engineering problem. Code degrades. Dependencies break. Systems slow down. The standard response is technical: refactor the code, update the dependencies, optimize the queries. This paper argues that software rot is not a technical problem. It is a policy failure. Software rots because organizations do not reward maintenance. The engineer who built the system was promoted or left. The team that maintained it was reorganized. The company that owned it was acquired. The code decays not because code inevitably decays but because institutions do not fund, staff, or celebrate the work of keeping old software alive. We trace the lifecycle of abandoned software inside organizations, identify the organizational failures that cause rot, and propose a stewardship model where maintenance is a first class function, not an afterthought.

Read paper →
02

The Economics of Self-Hosting

TELOSIS-RP-2026-009·July 2026

The decision to self-host or use cloud services is often framed as a technical choice. It is not. It is an economic choice with technical consequences. This paper provides a framework for comparing the total cost of ownership of cloud-managed services versus self-hosted infrastructure over one, three, and five-year horizons. We account for visible costs (compute, storage, bandwidth) and hidden costs (operational labor, downtime risk, migration friction, and the cost of lock-in). We conclude that self-hosting is economically favorable for stable, predictable workloads at moderate to large scale, while cloud services are favorable for variable, unpredictable, or very small workloads. We also find that the economic advantage of self-hosting increases over time, while the cost of leaving a cloud provider increases with duration of use.

Read paper →
03

Vendor Lock-In: Structural Analysis and Alternatives

TELOSIS-RP-2026-010·July 2026

Vendor lock-in is the condition where the cost of leaving a software provider exceeds the cost of staying, even when the provider has degraded in quality, raised prices, or changed terms. This paper presents a taxonomy of lock-in mechanisms - technical, contractual, and operational - and analyzes how each creates dependency. We then present strategies for building software products that compete on quality rather than lock-in, drawing on the product architecture of TELOSIS brands. The central argument is that lock-in is not an inevitable consequence of complex software. It is a choice made by the vendor. The alternative is structural independence, where users can leave at any time without losing data, functionality, or continuity.

Read paper →