Research, inference and delivery share infrastructure. Each execution engine retains its own context and permission boundary. Evidence connects a claim to the path and revision that were actually examined.
Inputs retain source, observation time and applicability.
A fixed candidate is evaluated against a declared policy.
Permission has an owner, scope and consuming boundary.
An engine acts inside its own execution context.
Missing or unreadable evidence remains unknown.
Results retain identity, source and the measured population.
This model describes responsibilities and intended handoffs. It does not establish a completed end-to-end deployment across every engine.
Current system descriptions are separate from the archived infrastructure inspection below.
Research and multi-market execution
A research and execution environment covering cryptocurrencies and domestic and overseas equities. Cryptocurrency spot, perpetual futures and options use separate exchange paths; equity orders use broker-specific paths. Data readiness, product admission and execution authority remain separate gates.
Independent domestic equity rotation
A dedicated scheduled rotation engine for domestic stocks and ETFs, with its own execution and account boundary. Its focused mandate does not describe every trading capability available on the desktop host.
Account-scoped execution engine
The reviewed source snapshot contains domestic and overseas equity workers with separate account contexts, permission checks, submission recording and reconciliation. Account separation describes an execution boundary; this source review does not establish current deployment or public service availability.
Coordination and shared market access
A coordination and integration layer supplying state, portfolio controls, release conditions, evidence services and market-specific exchange and broker adapters. Its integrations cover cryptocurrencies, domestic and overseas equities, and domestic and overseas futures and options. Each consuming execution path retains its own permission boundary; this layer is not counted as a fourth independent execution system.
The M3 environment combines research with cryptocurrency and domestic and overseas equity execution. Research is one responsibility of this host, rather than its entire market scope.
The desktop supports cryptocurrencies and domestic and overseas equities alongside the focused KR Rotation engine. Its Control Plane market-access layer also implements domestic and overseas futures and options order paths.
Domestic and US equities; cryptocurrency spot, perpetual futures and options; a separate US equity-option integration.
Path: KIS equity consumers, Binance exchange consumers and the separate Alpaca option branch.
Scope: Generic KIS derivative scaffold branches are sealed. Source integrations do not establish every product is currently enabled.
Domestic stocks and ETFs.
Path: A scheduled KIS cash-order lane with its own arm, lease and submission journal.
Scope: Its domestic mandate is not the desktop host's entire market scope.
Account-scoped domestic and overseas equity workers in the reviewed source snapshot.
Path: Separate worker contexts, live-permission checks, submission recording and reconciliation.
Scope: The local source mirror is not an attested current deployment or a statement that every account is eligible.
Cryptocurrencies, domestic and overseas equities, domestic and overseas futures and options.
Path: Market-specific exchange and broker services, including dedicated KIS derivative order routes.
Scope: This is a shared service layer, not a fourth independent engine or one universal central order-approval switch.
The research source includes LLM routing and AVA bridge clients. AVA server implementation, model residency and current distributed inference were not verified by this source review.
Market coverage reflects reviewed implementation and owner-confirmed host roles. Overseas coverage follows the exchanges and products supported by each broker. Available integrations do not imply that every product is currently enabled for live execution.
Local inference, observation, CI, storage and control services serve different roles. A compute host, a running service and an execution permission are separate facts.
The unified path across all engines remains under verification. A process being present does not establish that every intended handoff is complete.
How authority is represented →Inspected operating footprint
Mesh registration: 9 devices, 9 online. These are network identities, not the physical operating-box count. A dedicated-fabric compute host is outside this mesh; inactive client devices are inside it.
Read-only inspection of the known operating fleet. Point-in-time internal disclosure, not live telemetry or independent attestation.
This is an archived inspection, not live capacity or a current health dashboard.