How we work
The principles, architectures, practices and concepts the commons works by - kept as data in the canon and the observatory, read by people and agents alike.
Concepts
As good as Android
A phone running Linux that an ordinary person could use as their only phone and not feel they gave something up - counted one feature at a time.
docs
Mainline first, everything upstream
Work is done on mainline Linux and written to be sent upstream: each fix its own series, checkpatch-clean, to the upstream it belongs to; vendor code is read as a specification, never copied.
docs
Measured, not claimed
A feature counts only when a test run has shown it works; what nobody measured is unknown, never broken.
docs
No manual steps outside tools
What a person does twice becomes a command, a record or a test, so that bringing a phone up can run by itself; where hands or eyes are the measurement, the step is a witnessed test, said before and recorded.
docs
Rust, with argenv
linux-phone's tools are Rust, each declaring its command line and environment once with argenv.
docs
One baseline per device
Every check that ever passed is held to; a check outside a run's scope is not asked, rather than kept in a second baseline.
lab-tools
The conveyor refuses what cannot work
Each mistake that cost a try becomes a refusal with a reason: a kernel that is not an EFI program, a listening test without the word that the microphone is placed.
lab-tools
Read the device's own record first
Before cleaning up after an experiment, read what the device itself recorded: a boot entry's try counter, the bootloader's selection, the crash memory.
surya-lab
A placed microphone gives relative levels
A microphone placed by the phone tells which speaker is louder from where it stands, and whether there is sound at all - not absolute loudness.
surya-lab
The phone is the reference
Kept in a known-working state at all times: every experiment is one try that falls back by itself, and the phone is checked well before and after.
surya-lab