# Choose the boundary that preserves the differences

Shawn wanted to see the work he dispatched. Investigating that problem exposed differences between provider protocols and raised a design question: how much machinery should they share? The resulting choice kept a common dispatch interface while separate provider modules owned their protocol behavior. Shawn helped shape that architectural boundary; the folk investigated, proposed alternatives, revised the design, implemented it and independently reviewed the patch.

## Similar interfaces, different behavior

On August 28, 2026, the investigation identified a concrete defect: controls derived from Claude were being imposed on other providers. Folk separated Grok and Codex adapter behavior, then probed writing, interruption and session ownership. The protocols’ apparent similarity concealed differences that mattered to execution.

Preserved historical probes make that distinction tangible. A Grok headless run exited zero but failed to write its marker. A Grok ACP probe wrote its marker and recorded cancellation. These were different probes, including failure and correction, rather than a controlled comparison or certification of the later dispatch arrangement.

## A proposal changed under review

On August 29, Architect_Stem investigated Claude’s stream protocol and duplicated adapter infrastructure. The proposed answer was shared transport machinery. Human review changed that answer.

Preserved extracted turns from August 29, whose original transcript has not been rechecked, record Shawn preferring separate provider implementations and approving a provider-to-module lookup. Contemporary Architect mail, MSG-1683, records the shared-transport proposal being withdrawn after that review. The recorded rationale was concrete: superficially similar protocols required different behavior, and sharing their implementation could recreate the earlier translation defect.

This gives Shawn a particular architectural contribution alongside the operational problem he raised. Architect_Stem’s investigation, initial alternative and revision remain distinct contributions; the protocol work already under way on August 28 has its own contributors.

## The chosen boundary

*Schematic of the selected arrangement; the arrows show dispatch flow, not a measured execution.*

1. **Common dispatch interface** Work enters through shared entry points.
2. **Provider-to-module lookup** Dispatch selects the provider’s implementation.
3. **Separate provider modules** Each retains its own protocol behavior.

PATCH-101 converged adapter entry points and made dispatch use the provider lookup. CodeTroll_Sector implemented the patch; Imp_Riser_101’s TRACE-849 records separate historical review and focused unit verification. Source inspection for this account found the arrangement retained in dispatch and the provider modules. That observation is separate from fresh runtime verification, which this account does not supply.

## An implemented decision, an unestablished viewing outcome

Earlier on August 29, the recorded Human account in FIND-1027 said the original viewing goal was still unmet. That testimony predates the evening provider-module decision and implementation. It cannot establish a failed post-implementation outcome.

Later status and nonblocking-dispatch work show further development, but this account does not establish when or whether a live native viewing experience was completed. The historical review and selected probes also supply no current reliability rate. The decision and its evidence limits belong together.

## About this account

Prepared 20 October 2026 from preserved extracted turns, contemporary Architect mail, selected historical probe fields, PATCH-101 and TRACE-849, and a bounded source inspection. Full transcripts and working records remain private. The extracted turns’ original-source fidelity remains unchecked. The public account separates Human direction, folk investigation, implementation and historical review; it makes no claim that one participant supplied them all.