Backlog
The work ahead and done.
Open · 12
A device base derives its parts' measured fields from its own runs (a derive-parts record that devlab gather runs)
device-templateAfter the move a device's runs are filed into its own base, while parts.measured/measured_run were derived by docs from docs' test_results (derive-support-status) and only seeded at the move. Without…
The device template names bringup and ships a [boot] table in device.toml
device-templateAGENTS.md says where a device's first-boot images are made (lab-tools bringup, followed by pin, never a scripts folder of its own, never an edit of the tool); device.toml gets [boot] in pmOS deviceinf…
device.toml read off a running phone
device-templatedevlab reads a running phone (compatible, sound cards, signal processors, inputs) and proposes its device.toml, [health] included - the onboarding step of the device-template design (linux-phone-oco/d…
A second phone through the template
device-templateThe proof that surya is not the mould: a second postmarketOS phone's lab made by Use this template, reaching healthy with only its device.toml filled.
Switching the phone shell, a word of devlab
device-templatesurya-lab ui/switch.sh switches the shell in place (postmarketOS UI packages, tinydm session, reboot, then the shell, DSP and speaker checked); nothing in it is surya own. As devlab shell switch NAME…
The lab's USB wake lock, carried by devlab
device-templateEvery lab phone on USB needs devlab-usb-awake (a suspend attempt drops the link); surya carries it as its own overlay. It belongs to devlab, written at flash for any phone.
The steps contract in the template: a steps table, the record step, contract steps = 1 in devicebase.toml, data/steps.json empty, in the template's followed files
device-template proven by in the template, tad check passes with an empty steps table; tad r step --step shell-on-console --status done --proof X --run Y writes one row and refuses a status outside the sixReaches labs by the template release (decision 2026-11-18-device-template-follows-by-release), never by hand. A new device starts with no claim: every step not known yet.
device-template names every file it has: generic (followed) or made-once (laid at creation); the skeleton followed, the hardware files left to idealkb
device-template proven by docs research/device-template/2026-11-18/template-drift.sh device-template ideal-knowledge-base: its classified and one-source lines say ok (today 18 unclassified files, 3 with two sources)Decision 2026-11-18-device-template-follows-by-release, step 1. Add a made-once list (device.toml, oco.toml, README.md, devicebase.toml, idealkb.toml, provision/packages.txt, .oco/uncommitted, data/);…
template-drift runs in CI: the template's (classified, one-source) and each lab's (pin, equal, no-copy), from a generic bin/template-drift.sh
device-template proven by a test PR to a lab that edits a template-generic file fails CI with a line naming the file; main of the template and both labs passStep 4. The failing test in docs research/device-template/2026-11-18/ becomes a generic file of the template; a lab's workflow clones the template at its pinned tag and idealkb at its pin, read-only.…
The hourly update-pins moves a lab's template pin as it moves idealkb's: the template lists its consumers, each bump lands through the lab's CI
device-template proven by the first template release after v0.1.0 reaches surya-lab and google-walleye-lab as one bot PR each, landed by their CI, with template-drift exit 0 after waits on grenudi/ideal-knowledge-base item follow-source-from-pin (fo…Step 3. A change to the device layer then lands in the template only; no more parallel hand PRs. idealkb first, then the template, in one run.
The template's device.toml is the generated one, naming the pinned schema, and its CI checks it
device-template proven by device-template CI validates device.toml against the schema of the pinned releaseA new phone's lab then gets completion, hover and the check from its first commit; the header's claim that unknown fields are refused becomes true.
device-template releases by release-please from v0.1.0, and a lab's devicebase.toml names the release it follows
device-template proven by gh release list -R linux-phone-oco/device-template shows v0.1.0, and template-drift's pin line reads it for a lab pinned to itStep 2. release-please as in idealkb; devicebase.toml template = "X.Y.Z" with own = [...] for template files a lab keeps; the template's own devicebase.toml comment says how a new lab sets it. The dat…
In progress · 0
Done · 3
device-template follows idealkb 0.14.0 (pinned at 0.9.1)
device-template proven by idealkb.toml pins 0.14.0 and the base's verify (tad check, make verify) passes on mainDone 2026-11-18: device-template main pins idealkb 0.14.0 (PR #17, build: ideal-knowledge-base 0.14.0, landed by the idealkb update-pins run while this item was in work; read back: idealkb.toml versio…
The template, made from what surya proved
device-templatedevice.toml with every section devlab reads (connection, provision, flash, health) and what to change; tests/health for a phone's own checks; tests/results for its reports; AGENTS.md conventions; CI f…
surya-lab re-based onto the template
device-templatesurya-lab keeps scripts the template no longer needs (lib/phone.sh, tests/run.sh, tests/to-docs.sh, tests/automatic/checks.sh, flash/, provision/provision.sh): each one retires once devlab does its wo…