docs(architecture): define greenfield Rust Oteryn client - #45
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Define one normative, agent-ready architecture for a greenfield Rust Oteryn client while keeping the current C++/Lua/OTUI client operational as a separately documented legacy/reference track.
Greenfield scope
oteryn-client/product directory and nested agent ruleswgpurenderer boundaryGameEvent/GameCommandcontractsAgent program
Legacy preservation
The existing client remains untouched and buildable. Its maintenance knowledge is preserved in:
docs/architecture/LEGACY_OTCLIENT_ARCHITECTURE.mddocs/agents/LEGACY_OTCLIENT_WORKSTREAMS.mdLegacy code is audit evidence only for the Rust track and is not a runtime dependency or architectural template.
Product constraint
A gameplay channel is a parallel instance of one world. It is selected during login or relog; it is not a network multiplexing stream. Seamless in-game channel transfer is out of scope.
Safety and review
Validation
30222662629: passedDetect Build Scope, both Fast Checks, Lua Syntax andCI / Required: passedTask
OTC-20260726-rust-client-architectureReady for squash merge after the final mergeability, changed-file and required-check verification.