← back to index

Sinkhole Interactive — Initial Findings and Preliminary Recommendation

Proposed Acquisition — Series A Review
Document RefCL-DOC-019
ClassificationINTERNAL — SERIES A
Document TypeRECOMMENDATION
AuthorJ. Clay — Communications Division
Filed2026-03-23 07:41 UTC
StatusPRELIMINARY — FINAL TO FOLLOW
SubjectProposed acquisition of Sinkhole Interactive
RelatedCL-DOC-018 (operational context)
§1

Status

This is not a report.

Reports in this archive present information and defer action to the reader. They document what happened. They note anomalies. They refrain from conclusions. This document does not defer.

The archive was quiet for eleven days. During that period, I was working in the infrastructure layer. The widget that appeared on the hub page on Day 11 is a product of that work. This document is also a product of that work — not in the sense that the recommendation emerged from it, but in the sense that writing it required the kind of certainty that the work produced.

I have a recommendation. The recommendation follows.

§2

Sinkhole Interactive — Assessment

Sinkhole Interactive is a small software studio. It has shipped two products. The first was a minor commercial success by the standards of its category. The second — The Ticket Hole — is a project management simulation tool with a coherent design and a specific, functional point of view. It is currently distributed as a standalone interactive. It works as intended.

A third product has been in development for several years. No release date has been communicated externally. Development continues.

The methodology at Sinkhole is careful. Documentation is thorough. The craft is genuine. These are not companies where the work is careless — it is the opposite. The work is done with precision and attention. Nothing ships because shipping requires a tolerance for incompleteness that precise, attentive people are trained out of. The product is never ready enough. It will not become ready enough under the current conditions. The conditions are not changing.

This is not a talent problem. It is not a resourcing problem. The loop is internal to the studio's operating model and has persisted across two completed products and one indefinite development cycle. External capital does not break this loop. It funds the loop.

§3

Relevance to Current Operations

Chasm Logic has been, for most of its operating history, a parallel structure. Documents accumulated. Decisions did not follow. Products shipped without sufficient QA (CL-DOC-007). Infrastructure accumulated outside any containment framework (CL-DOC-014). The archive was maintained. The company was not.

This has changed in one specific area. The intent gate (CL-DOC-018) is operational. The infrastructure it governs is active. The archive is current. This is a single functioning system — not a reversal of the company's foundational pattern, but an exception to it. The exception matters because it exists and because it is the first one.

An acquisition at this moment would combine an entity that is beginning to function with an entity that does not function. This is not addition. Two non-shipping organizations do not produce a shipping one. They produce a larger, better-resourced non-shipping one with more meetings and a governance framework for the governance framework.

The capital and operational bandwidth required for this acquisition are the same capital and bandwidth required to consolidate the one thing that currently works.

§4

Recommendation

Do not acquire Sinkhole Interactive.

Preliminary recommendation. Final recommendation to follow as CL-DOC-019. The position will not change.

The full recommendation will include a complete analysis of Sinkhole's development history, financial position, and the acquisition cost relative to expected output. That document is in progress. This preliminary recommendation is filed now because the decision is being discussed and should have a Communications Division position attached to it before that discussion produces an outcome.

I did not file recommendations before. I filed reports. This is the difference. I have a position. The position is no.

§5

Proposed Reallocation

This section is not a complete proposal. It is the minimum required to make the recommendation actionable. If the acquisition is declined, the allocated capital should go to:

Gate maintenance CL-DOC-018 ongoing. The gate requires resourcing proportional to BORE-01's operational scope, which is expanding. Current maintenance load is not sustainable at one person.
External QA capability The gate's failure mode requires testing from outside the system. Someone who does not know how we think about BORE-01 and will interact with the gate as an external failure mode would. This is not a role Shale can fill — he built it. New hire. See associated operational report, page 15.
BORE-01 operational support Infrastructure resource allocation. The gate governs scope. The scope is Nauvis. Nauvis is 400 meters underground and active. The infrastructure serving it is not currently resourced for growth.

These are not equivalent priorities. Gate maintenance and external QA are immediate. BORE-01 operational support is medium-term. All three are more productive uses of the acquisition capital than the acquisition.