Public and Private Reasoning Layers — The Abstraction Architecture of This Case
This case study is a public-layer artifact. It preserves the reasoning structure — the causal logic, the corrections, the reversals, the post-event findings — without including the full-fidelity private-layer operational detail. The public layer (structural arguments, reasoning method, decision logic) is transferable and is the case's intended contribution. The private layer (specific word candidate sets, calibrated benchmarks, geometric routing analysis) remains with the operator. The distinction is structural: the public layer's value is in its transferability; the private layer's value is in its specificity. An orchestration system that operates between these layers is noted as a conceptual pattern; no implementation detail is part of this record.
Capture
This case study is itself a public-layer artifact. It captures the causal structure and reasoning logic of a complete preparation-and-execution cycle, including corrections, reversals, and post-event findings. It is designed to be read by anyone. It is not designed to be a complete transfer of the optimization system it describes.
Two distinct layers of reasoning exist within this case:
Public layer: The structural arguments — premium square exhaustion as a scoring invariant, expected-value framing over theoretical-maximum framing, the one-sentence theme test, pre-play rule clarification, clean-play standards, the solvability finding and its structural implications. These arguments are transferable. A reader can learn the reasoning method from them. The value is in the logic, not in the specific optimization data.
Private layer: The full-fidelity preparation artifacts — the specific word candidate sets, the calibrated scoring benchmarks, the exact geometric routing analysis, the empirical benchmarks from competitive execution. These remain with the operator. Their value is in their specificity, which is exactly what makes them non-transferable without dissolving their advantage.
Why
The two-layer architecture is not accidental or evasive — it is structural. The YY Method's core purpose is to preserve reasoning chains as durable artifacts. A reasoning artifact that includes its own full operational detail is a different kind of artifact from one that preserves the reasoning structure. Both have value; they serve different purposes.
The public layer serves the reasoning-artifact purpose: a reader can extract the method, apply it to their own domain, and understand how the operator navigated from an unexpected result to a revised strategy to a post-event structural finding. That is the case's intended contribution.
The private layer serves the operator's competitive purpose: it is the current state of the optimization system that produced the result. Publishing it would convert a competitive asset into a public resource. Whether to do that is a separate decision — one that is deferred.
The distinction also applies to the role-transition context (C8-034): the coaching relationship transmits private-layer content selectively, to a specific person, in a specific context. It is not public-layer disclosure. The coached participant receives the operational detail that the operator has developed; the event's general participant population does not.
An orchestration system that operates between these two layers — able to reason from private-layer inputs while producing public-layer outputs — would be valuable in principle. The conceptual architecture is noted; no implementation detail is part of this record.
Why-Not
Why not publish the private layer as well — full transparency, maximum value? Full transparency is appropriate in contexts where the private layer's value is not reduced by disclosure. In this case, the private layer is a competitive asset in an ongoing event. Its value to the operator depends partly on other participants not having it. After the operator has retired from competing — or after the event format changes enough to make the current optimization system obsolete — full disclosure becomes available. The timing decision is deferred.
Why not keep the case private as well, since it documents a real competitive advantage? The public layer does not transfer the competitive advantage. A reader who learns that "premium square exhaustion is the core scoring invariant" and "9x expected-value plays outperform 27x theoretical-maximum plays" has learned a structural argument they could have derived independently. The operational detail that makes that argument executable — the specific word lists, the routing analysis, the calibrated benchmarks — is not in the public record.
Commit
Decision: The case is published as a public-layer artifact. The reasoning structure is fully preserved. The private-layer operational detail is not included and is not described. The two-layer architecture is made explicit in this ADR so that future readers understand the distinction is deliberate, not a gap.
Confidence: High. The two layers are structurally distinct and the boundary is clear.
Timestamp
2026-04-26