OAL CORE DEVELOPMENT

Keep ownership, operations and evidence explicit.

Entry point for contributors to the node, core, GUI, protocol, algorithms and build system.

Read order

CURRENT_STATUS → CURRENT_CHECKLIST → ARCHITECTURE → OAL_SPECIFICATION → OAL_API → VALIDATION. Read MOUNT_GEOMETRY before mount transforms.

Core invariants

Node owns device sessions.
Native drivers default; INDI optional.
Mount v9 geometry frozen after HIL.
Main/guide resource locks independent.
Science recording stays upstream of preview/network work.
EN docs canonical with UA mirrors.

Feature workflow

Define ownership/resources, decide query vs operation, publish capabilities, isolate device-specific code, define cancel/failure semantics, add regression coverage, synchronize documentation and record the real qualification level.

Driver and protocol work

Use include/oal/driver_api.h, the driver manifest schema, NATIVE_DRIVER_SDK.md, OpenAPI and the OAL specification. Do not make the GUI a shadow source of protocol state.

Canonical guide: docs/DEVELOPER_GUIDE.md