Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion data/backlog.json
Original file line number Diff line number Diff line change
Expand Up @@ -181,7 +181,7 @@
{"project":"linux-phone-oco/surya-lab","id":"surya-follows-template","title":"surya-lab follows device-template's release: its copy of the list gone, check.yml and tests/health/README.md taken, the pin a release","status":"open","note":"Migration for decision 2026-11-18-device-template-follows-by-release; no phone. Measured drift today: generic copy 5 entries behind, check.yml without xargs -r, tests/health/README.md missing, devicebase.toml template = 2026-11-17. AGENTS.md outside the idealkb part stays its own until the template:begin part exists, then the general conventions come from the template.","opened":"2026-11-18","waits":null,"blocked_by":"template-releases","hardware":null,"needs":"build","device":"xiaomi-surya","proof":"docs research/device-template/2026-11-18/template-drift.sh device-template ideal-knowledge-base surya-lab: every surya-lab line says ok","rank":null,"about":"device-template"}
{"project":"linux-phone-oco/google-walleye-lab","id":"walleye-follows-template","title":"google-walleye-lab follows device-template's release: its copy of the list gone, its rust job in its own workflow, the pin a release, stale PR 208 closed","status":"open","note":"Migration for decision 2026-11-18-device-template-follows-by-release; no phone. Measured drift today: generic copy 5 entries behind, ffs-acm-rs job inside the template's check.yml, devicebase.toml template = 2026-11-17, PR #208 (the template's #15 by hand) open though main has it.","opened":"2026-11-18","waits":null,"blocked_by":"template-releases","hardware":null,"needs":"build","device":"google-walleye","proof":"docs research/device-template/2026-11-18/template-drift.sh device-template ideal-knowledge-base google-walleye-lab: every google-walleye-lab line says ok","rank":null,"about":"device-template"}
{"project":"linux-phone-oco/docs","id":"bringup-steps","title":"Bring-up steps as data: every step that makes Linux run on a machine, generic in docs, each device's status claimed in its own base, a guidebook and helpers made from it","status":"open","note":"Decided 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base (research bringup-steps-landscape). The pieces are the items about bringup-steps, unranked for the author.","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-schema,bringup-steps-seed,feed-device-steps,walleye-steps-claimed","hardware":null,"needs":null,"device":null,"proof":"research/bringup-steps/2026-11-18/bringup-chain-walleye.sh passes in docs: tad q bringup-chain --device google-walleye lists walleye's steps in order, each proven one with its proof and run, none unknown (fails today: no query bringup-chain)","rank":null,"about":"commons-only"}
{"project":"linux-phone-oco/docs","id":"bringup-steps-schema","title":"The bring-up step tables in docs: bringup_steps, bringup_step_edges, step_status, the records bringup-step and bringup-edge, and the query bringup-chain","status":"open","note":"Ready to land as drafted in research/bringup-steps/2026-11-18 (schema.toml, records/, queries/): tried in a scratch clone at 3596bb3. The owner's to land (AGENTS.md: schema, records, queries).","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":null,"device":null,"proof":"tad check passes with the three tables; tad r bringup-edge refuses an edge that closes a cycle; tad q bringup-chain answers with no device (every status unknown)","rank":null,"about":"bringup-steps"}
{"project":"linux-phone-oco/docs","id":"bringup-steps-schema","title":"The bring-up step tables in docs: bringup_steps, bringup_step_edges, step_status, the records bringup-step and bringup-edge, and the query bringup-chain","status":"done","note":"Landed: tables bringup_stages (the stage list as rows, so it changes with ikb bringup-stage and no schema change), bringup_steps, bringup_step_edges, step_status (declared only; a feed fills it); records bringup-step, bringup-edge (refuses a cycle, a self-edge, a group mixing hard and soft), bringup-stage; query bringup-chain [--device] with a computed ready/waits. Reviewed by the programmer subagent (group-name collision, UNION for the depth walk, stage tie, device guard fixed). tad check: 37 tables; make verify twice clean. Test research/bringup-steps/2026-11-18/bringup-chain-walleye.sh: was 'no query bringup-chain'; with the schema and seed it gets 26 steps in order and fails only for lack of claims (walleye kernel-reaches-init is unknown, not done): walleye-steps-claimed and feed-device-steps make it pass.","opened":"2026-11-18","waits":null,"blocked_by":null,"hardware":null,"needs":null,"device":null,"proof":"tad check passes with the three tables; tad r bringup-edge refuses an edge that closes a cycle; tad q bringup-chain answers with no device (every status unknown)","rank":null,"about":"bringup-steps"}
{"project":"linux-phone-oco/docs","id":"bringup-steps-seed","title":"Seed the generic steps: 26 steps and 37 edges from walleye's real chain, surya's road checked against it","status":"open","note":"sh research/bringup-steps/2026-11-18/seed.sh in docs, through the records","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-schema","hardware":null,"needs":null,"device":null,"proof":"tad q bringup-chain lists 26 steps, bootloader and stock steps at depth 0, health-suite-runs last; tad check passes","rank":null,"about":"bringup-steps"}
{"project":"linux-phone-oco/device-template","id":"steps-contract","title":"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","status":"open","note":"Reaches 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.","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-schema,template-releases","hardware":null,"needs":null,"device":null,"proof":"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 six","rank":null,"about":"bringup-steps"}
{"project":"linux-phone-oco/docs","id":"feed-device-steps","title":"Pull each device base's steps into step_status: records/feed-device-steps.sql and a device-steps-unknown fallback in bin/run-feeds.sh","status":"open","note":"As feed-device-parts: read devicebase.toml (steps = 1) and data/steps.json from the base on main; a step not claimed is unknown, not known yet; a claim of a step docs does not know is dropped and named.","opened":"2026-11-18","waits":null,"blocked_by":"bringup-steps-schema,steps-contract","hardware":null,"needs":null,"device":null,"proof":"run against a base without steps = 1, every step of that device is unknown with the reason; against google-walleye-lab after its claims, research/bringup-steps/2026-11-18/bringup-chain-walleye.sh passes","rank":null,"about":"bringup-steps"}
Expand Down
4 changes: 2 additions & 2 deletions docs/backlog.md
Original file line number Diff line number Diff line change
Expand Up @@ -4556,10 +4556,10 @@ Project
: linux-phone-oco/docs

Status
: open
: done

Note
: Ready to land as drafted in research/bringup-steps/2026-11-18 (schema.toml, records/, queries/): tried in a scratch clone at 3596bb3. The owner's to land (AGENTS.md: schema, records, queries).
: Landed: tables bringup_stages (the stage list as rows, so it changes with ikb bringup-stage and no schema change), bringup_steps, bringup_step_edges, step_status (declared only; a feed fills it); records bringup-step, bringup-edge (refuses a cycle, a self-edge, a group mixing hard and soft), bringup-stage; query bringup-chain [--device] with a computed ready/waits. Reviewed by the programmer subagent (group-name collision, UNION for the depth walk, stage tie, device guard fixed). tad check: 37 tables; make verify twice clean. Test research/bringup-steps/2026-11-18/bringup-chain-walleye.sh: was 'no query bringup-chain'; with the schema and seed it gets 26 steps in order and fails only for lack of claims (walleye kernel-reaches-init is unknown, not done): walleye-steps-claimed and feed-device-steps make it pass.

Opened
: 2026-11-18
Expand Down
3 changes: 3 additions & 0 deletions docs/bringup_stages.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
<!-- Generated from data/ by tad. Do not edit by hand. -->

# Bringup Stages
3 changes: 3 additions & 0 deletions docs/bringup_step_edges.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
<!-- Generated from data/ by tad. Do not edit by hand. -->

# Bringup Step Edges
3 changes: 3 additions & 0 deletions docs/bringup_steps.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
<!-- Generated from data/ by tad. Do not edit by hand. -->

# Bringup Steps
4 changes: 4 additions & 0 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,9 @@
The memory of linux-phone-oco, whose goal is Linux phones as good as Android for everyday use, and better: which phone supports which hardware, how we know, why decisions were made, and what is next. Plain versioned data; see AGENTS.md. The plan, and where Linux phones stand against Android and iOS: [the grand picture](picture.md), and the main screen, [features against Android and iOS](feature_support.md).

- [Backlog](backlog.md): 194
- [Bringup Stages](bringup_stages.md): 0
- [Bringup Step Edges](bringup_step_edges.md): 0
- [Bringup Steps](bringup_steps.md): 0
- [Components](components.md): 21
- [Concepts](concepts.md): 10
- [Decisions](decisions.md): 72
Expand All @@ -25,6 +28,7 @@ The memory of linux-phone-oco, whose goal is Linux phones as good as Android for
- [Session Log](session_log.md): 120
- [Shell Releases](shell_releases.md): 2
- [Sources](sources.md): 259
- [Step Status](step_status.md): 0
- [Summaries](summaries.md): 9
- [Support Status](support_status.md): 63
- [Test Results](test_results.md): 0
Expand Down
3 changes: 3 additions & 0 deletions docs/step_status.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
<!-- Generated from data/ by tad. Do not edit by hand. -->

# Step Status
32 changes: 32 additions & 0 deletions queries/bringup-chain.sql
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
-- A device's bring-up, step by step in the order the steps need each other: each step's depth (the longest
-- chain of needs under it, soft ones too: they order the guide), its stage, its status on the device with the
-- proof and the run, what it needs, and whether it is ready (every hard need done, or one of each group).
-- Without --device: the generic chain, every status unknown - the guidebook's order. A step the device's base
-- never claimed is unknown. In needs, ~ marks a soft need and |G the alternatives group it is one of. Within a
-- depth the steps go by stage (bringup_stages.ord), then their own ord.
-- --device string? the device (devices id); omitted: the generic chain
WITH RECURSIVE depth(id, d) AS (
SELECT id, 0 FROM bringup_steps WHERE id NOT IN (SELECT step FROM bringup_step_edges)
UNION
SELECT e.step, depth.d + 1 FROM bringup_step_edges e JOIN depth ON e.requires = depth.id
),
lvl AS (SELECT id, max(d) AS depth FROM depth GROUP BY id),
st AS (
SELECT s.id, coalesce(ss.status, 'unknown') AS status, ss.proof, ss.run, ss.proven_on, ss.updated
FROM bringup_steps s LEFT JOIN step_status ss ON ss.step_id = s.id AND ss.device_id = $device
),
need AS (
SELECT e.step, e.requires, e.kind, e."group", coalesce('g:' || e."group", 'r:' || e.requires) AS g, st.status = 'done' OR st.status = 'not-needed' AS met
FROM bringup_step_edges e JOIN st ON st.id = e.requires
),
ready AS (
SELECT step, bool_and(gmet) AS ok FROM (SELECT step, g, bool_or(met) AS gmet FROM need WHERE kind = 'hard' GROUP BY step, g) GROUP BY step
)
SELECT row_number() OVER (ORDER BY l.depth, sg.ord, sg.id, s.ord, s.id) AS n,
s.id AS step, s.stage, l.depth, st.status,
coalesce(st.proof, s.proof) AS proof, st.run, st.updated,
(SELECT string_agg(requires || CASE WHEN kind = 'soft' THEN '~' ELSE '' END || coalesce('|' || "group", ''), ' ' ORDER BY requires) FROM need WHERE need.step = s.id) AS needs,
CASE WHEN st.status IN ('done', 'not-needed') THEN '' WHEN coalesce(r.ok, true) THEN 'ready' ELSE 'waits' END AS next
FROM bringup_steps s JOIN bringup_stages sg ON sg.id = s.stage JOIN lvl l ON l.id = s.id JOIN st ON st.id = s.id LEFT JOIN ready r ON r.step = s.id
WHERE CASE WHEN $device IS NOT NULL AND $device NOT IN (SELECT id FROM devices) THEN error('no device ' || $device || ' (tad q coverage names them)') ELSE true END
ORDER BY n;
15 changes: 15 additions & 0 deletions records/bringup-edge.sql
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
-- What a step needs before it (an edge of that pair is replaced). hard: it cannot be done first; soft: it can,
-- but blind or at much greater cost. Edges of one step sharing a group are alternatives: one done is enough.
-- --step string the step
-- --requires string the step it needs
-- --kind string hard or soft
-- --group string? the alternatives it is one of (console: UART or the USB gadget)
-- --why string why, in a line - the record that showed it, when one did
SELECT CASE WHEN $step = $requires THEN error('a step cannot require itself') END;
SELECT CASE WHEN EXISTS (
WITH RECURSIVE up(id) AS (SELECT $requires UNION SELECT e.requires FROM bringup_step_edges e JOIN up ON e.step = up.id)
SELECT 1 FROM up WHERE id = $step) THEN error('this edge makes a cycle: ' || $requires || ' already needs ' || $step) END;
SELECT CASE WHEN $group IS NOT NULL AND EXISTS (SELECT 1 FROM bringup_step_edges e WHERE e.step = $step AND e."group" = $group AND e.kind <> $kind AND e.requires <> $requires)
THEN error('the group ' || $group || ' of ' || $step || ' mixes hard and soft: alternatives are all of one kind') END;
DELETE FROM bringup_step_edges WHERE step = $step AND requires = $requires;
INSERT INTO bringup_step_edges (step, requires, kind, "group", why) VALUES ($step, $requires, $kind, $group, $why);
9 changes: 9 additions & 0 deletions records/bringup-stage.sql
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
-- A phase of bringing Linux up on a machine, in the order one meets them: a chapter of the guidebook (a stage of
-- that id is replaced). The list is data, so it changes with this record: a stage added, split, renamed or moved
-- (its ord), with no schema change. A step names its stage (bringup-step --stage).
-- --id string a-short-name: prepare, boot, console ...
-- --ord integer its place among the stages: the order of the chapters (a tie goes by id)
-- --title string the chapter's name
-- --what string what the stage is for, in a line or two
DELETE FROM bringup_stages WHERE id = $id;
INSERT INTO bringup_stages (id, ord, title, what) VALUES ($id, $ord, $title, $what);
22 changes: 22 additions & 0 deletions records/bringup-step.sql
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
-- A step of bringing Linux up on a machine, for every machine it applies to (a step of that id is replaced).
-- Generic: what the step is, when it is done and how that is proven - never one device's state, which its own
-- base claims (its steps table) and docs pulls into step_status. What it needs goes in bringup-edge.
-- --id string a-short-name: kernel-reaches-init, shell-on-console ...
-- --title string what it is, in a few words
-- --stage string its stage: the id of a stage (tad sql "SELECT id FROM bringup_stages ORDER BY ord")
-- --ord integer its place in the stage, where the edges leave two steps unordered
-- --applies string = any any, or the class it holds for: boot:android, boot:uefi, usb:gadget, soc:qcom ...
-- --done-when string what done means, checkably
-- --proof string the test that proves it (a tests id, or the check a device's test must make)
-- --proof-kind string host-check, phone-suite, build-check, witness or research
-- --helper string? the lpoco command that does it; none yet is the gap a helper fills
-- --component string? the part of the catalogue whose first light it is
-- --guide string how it is done, and the traps met so far with the records that met them
-- --sources string? ids of the sources, comma-separated
-- --checked-on date = today when its text was last checked
SELECT CASE WHEN $sources IS NOT NULL AND EXISTS (SELECT 1 FROM unnest(string_split($sources, ',')) AS t(x) WHERE trim(t.x) NOT IN (SELECT id FROM sources))
THEN error('sources names no source of this base: ' || (SELECT string_agg(trim(t.x), ', ') FROM unnest(string_split($sources, ',')) AS t(x) WHERE trim(t.x) NOT IN (SELECT id FROM sources)) || ' (tad r source records one)') END;
SELECT CASE WHEN $stage NOT IN (SELECT id FROM bringup_stages) THEN error('no stage ' || $stage || ' (ikb bringup-stage records one)') END;
DELETE FROM bringup_steps WHERE id = $id;
INSERT INTO bringup_steps (id, title, stage, ord, applies, done_when, proof, proof_kind, helper, component, guide, sources, checked_on)
VALUES ($id, $title, $stage, $ord, $applies, $done_when, $proof, $proof_kind, $helper, $component, $guide, $sources, $checked_on);
Loading
Loading