Direction question: Reasonix and DeepSeek Harness (DSH) interoperability

[CherishLJ]

Context

DeepSeek has now open-sourced DeepSeek Harness (DSH). Reasonix already has a strong identity as a DeepSeek-native product, including its CLI/Desktop experience, cache-first architecture, and DeepSeek-specific tool and context optimizations.

I would like to ask how the maintainers currently see the possible relationship between the two projects. This is an exploratory architecture question, not a request for a commitment or for Reasonix to replace its existing core.

Questions

1. Would Reasonix consider supporting DSH as an optional runtime/backend/engine, while keeping the Reasonix-owned CLI, Desktop app, UX, and DeepSeek-specific cache/tool/context optimizations as the product layer?
2. Or is the current long-term direction to keep Reasonix as a fully independent Go harness/runtime?
3. If the runtimes remain separate, would interoperability be considered through an ACP or headless bridge, a DSH plugin/adapter, or another protocol boundary?
4. Do the maintainers already have any preliminary judgment or roadmap on this? An answer such as "not decided yet" would also be useful context for the community.

I realize DSH is new and the answer may depend on how its APIs and ecosystem evolve. I am mainly trying to understand the current architectural direction and where an experimental integration, if any, would best live without disrupting Reasonix's existing design priorities.

Thank you for any guidance.