ak47andrew/battlesnake

Purpose and entry point

This is a compact Rust application centered on algorithmic processing and movement-related logic. The executable entry point is src/main.rs, with domain code grouped under the stuff module tree.

Application composition

src/main.rs likely initializes settings, constructs domain data, and invokes the primary algorithms. The module root src/stuff/mod.rs defines the internal package boundary and exposes the submodules used by the binary.

Key paths:

• src/main.rs

• src/stuff/mod.rs

Domain model and configuration

src/stuff/datatypes.rs contains the core data structures passed between algorithm stages. src/stuff/settings.rs represents runtime or algorithm configuration, separating tunable parameters from processing code.

Primary flow: startup reads or constructs settings → creates/loads domain data → hands both to algorithms.

Key paths:

• src/stuff/datatypes.rs

• src/stuff/settings.rs

Core algorithm layer

src/stuff/algorithms.rs is the likely general-purpose computation/orchestration layer. It should own high-level algorithm selection, evaluation, or transformation over the domain types rather than embedding those concerns in main.

Key path:

• src/stuff/algorithms.rs

Movement algorithm boundary

src/stuff/move_algos.rs isolates movement, traversal, routing, or state-transition behavior from the broader algorithm layer. This is an important architectural boundary: movement-specific decisions can evolve independently while operating on shared types from datatypes.rs.

Key paths:

• src/stuff/move_algos.rs

• src/stuff/datatypes.rs

• src/stuff/algorithms.rs

Shared operational utilities

src/stuff/tools.rs holds reusable support operations used by algorithm modules. It should remain a dependency leaf where possible: higher-level modules may call it, but it should avoid owning application flow or movement policy.

Key paths:

• src/stuff/tools.rs

• src/stuff/algorithms.rs

• src/stuff/move_algos.rs

Runtime and deployment

The runtime is Rust, defined by Cargo.toml and compiled into the binary rooted at src/main.rs. Container deployment is supported through Dockerfile; stage and production deployment are represented by Windows batch scripts.

Key paths:

• Cargo.toml

• Dockerfile

• deploy_stage.bat

• deploy_prod.bat

No external services, persistence layer, or web/server entry point are identifiable from the supplied tree.