How LuAir builds its own software.
We ask clients to put a named owner on every rule, and we hold our own software to the same standard. Every line of code LuAir ships traces to a business rule someone authored, approved, and still owns, including the lines an AI wrote. This page is the record.
From requirement to release, nothing unexplained.
A requirement becomes business rules, each with one owner. Rules become use cases a machine can read step by step. Each step becomes a block of code carrying the step's identifier. Each release is stamped with the source that produced it. An independent check re-reads the whole specification against the code nightly and on demand, and records every violation with its fix and the release it shipped in.
Three things that make this more than documentation.
Specifications a machine can check
Use cases use a fixed vocabulary, so whether the code conforms is a computation, not a meeting.
The same rules for people and AI
An AI drafts specifications, writes code, and runs checks here. Every change it makes traces to an approved rule, exactly as a person's would. Nothing ships until a person approves it.
A check that runs every night
Independent, on a schedule, against every rule as written. Each violation is recorded with its fix, its date, and the release it shipped in.
The same discipline, applied to ourselves.
Solo installs a node in your team. Provenance is the record of how we build the software that serves our own. Want the node? Start with seven questions about your operation.