Arkline documentation

Welcome to the official published documentation for the Arkline Rust engine.

Independent forks, local development and experiments are welcome. Share useful changes through issues and pull requests so the shared engine can improve. P.Industries focuses on the official Arkline network; that operational focus does not make independent worlds second-class projects or require them to use official account infrastructure. See Community and roadmap.

Arkline is an early developer alpha. The current world has one authoritative Rust process with durable SQLite state and independent economic replay. Distributed authority, permissionless node admission and node rewards are not implemented. A build, a deployed endpoint and a verified player journey are separate evidence.

Start here

• Player and developer guide — complete preview, first-flight, local-build and command-client instructions
• Component and deployment map — repository responsibilities, data flow and current authority boundary
• Community and roadmap — independent forks, local experiments and the official network
• Documentation index — versioned documentation overview

Play and understand the client

• Flight and cockpit controls — flight, targeting, drones and surface tools
• Browser client — connection, credentials and browser limits
• Station hangar and quarters — walking, ship boarding and station spaces
• Ship computer and resource jobs — confirmed jobs, worker delegation and manual control
• Sound and voice — audio lifecycle and spoken-command boundaries

Build and extend the engine

• Arkline Editor — local play/inspect/material workflows, contributor tooling and implementation limits

• Game API — implemented JSON requests, snapshots and authentication

• Architecture and economic verification — transactions, conservation and replay limits

• Models and community artwork — current meshes and proposed creator format

• Living-world design — implemented scenery and planned interfaces

• Identity integration plan — configurable standards integration; game login remains separate

Operate and release

• Transport security — verified TLS boundaries, certificates and renewal
• Web origin TLS — operator configuration and scoped rollback
• Private world deployment — one persistent authority and private validation
• Public relays and downloads — WSS, hosting and release paths
• Public transport limits — admission, payload and timeout boundaries
• Self-hosted CI and deployment — runner trust and scoped operations
• Release publication — verified artifacts, publication and recovery

Evidence, history and policies

• Developer alpha readiness — publication boundaries and unresolved work
• Validation history — dated test records, not blanket release guarantees
• Stability audit — reviewed behavior and limitations
• Station assets audit — storage permissions and verifier coverage
• Save and spatial migration — earlier work and persisted-world transitions
• Legacy systems review — historical source review
• Licensing — software and asset obligations
• Security and reporting — responsible reporting and support boundaries

Contribute documentation

The Wiki is the published reader location. The Markdown sources stay in the engine repository so code and documentation changes can be reviewed together. Follow each page's Versioned source link, submit a pull request, and have the reviewed source synchronized to the Wiki. Do not put credentials, private account details or player-world backups in either location.

Source repository · Contributing · Project website

Ship design archive — all seven ships, concept history and proposed interiors. Onboard systems covers proposed power, RF/data, air, water and cooling.

• How ship subsystems work together — power, control, life support, water, cooling, fire response and the mining loop; implemented behavior distinguished from proposals.