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
23 changes: 16 additions & 7 deletions data/backlog.json

Large diffs are not rendered by default.

1 change: 1 addition & 0 deletions data/decisions.json

Large diffs are not rendered by default.

3 changes: 3 additions & 0 deletions data/research.json
Original file line number Diff line number Diff line change
Expand Up @@ -57,3 +57,6 @@
{"id":"device-template-how-it-stands","brief":"device-template's children follow it by hand and drift unseen; decided: followed by release like idealkb, template-drift failing in CI; 6 items queued, first the classification","project":"linux-phone-oco/device-template","date":"2026-11-18","question":"Where does device-template's inheritance stand, and what is next?","found":"How it stands, 2026-11-18. device-template (a GitHub template, made 2026-11-17 from what surya proved) has two children: surya-lab (re-based by hand) and google-walleye-lab (Use this template). idealkb's slice reaches all three by update-pins; the template's own slice reaches the labs only by hand - its 13 statements are equal today because each change was landed three times, and 8 drifts are named that nothing catches (research device-template-drift-measured: stale list copies, three files with two sources and false-alarm bump PRs each idealkb release, surya's check.yml and tests/health/README.md, a date for a pin, walleye's stale PR 208, the manifest's shape).\nDecided (2026-11-18-device-template-follows-by-release, research device-template-follow-world): the template is followed like idealkb - every file named generic or made-once, a release pinned in devicebase.toml, laid by the same hourly update-pins once idealkb's follow-source-from-pin lands, and template-drift failing CI on drift. Queue, unranked: device-template template-classifies-its-files, template-releases, template-drift-in-ci, template-followed-by-update-pins; surya-lab surya-follows-template; google-walleye-lab walleye-follows-template. The failing test: research/device-template/2026-11-18/template-drift.sh (exit 1 today). device.toml's shape is template-manifest-schema's. The umbrella is docs item device-template-follow (orchestration's), which this carries out.","sources":"rhizoid-repo,idealkb-chain-follow","about":"device-template","material":null,"supersedes":null}
{"id":"bringup-steps-landscape","brief":"No one keeps bring-up steps as data with edges and proofs; walleye's real chain is 26 steps (17 done with proofs), surya's another road; docs' parts join carries step status as is","project":"linux-phone-oco/docs","date":"2026-11-18","question":"How should linux-phone keep every small step of bringing Linux up on a machine - what it needs, what it enables, its proof - generic for any machine, with each device base recording where it stands, so a guidebook, helpers and later a step runner can be made from it; and how do others do it?","found":"What is: the step-level truth of a bring-up lives only in each lab's backlog, session logs and research, folded on the face into \"boots\" or \"kernel\". Walleye's chain, rebuilt from google-walleye-lab: 26 steps from the bootloader read to the health suite, 17 done (each with a host check and a record: y1 alive by gpio-reserved-ranges and no earlycon, y2's gadget, banner2, z6's shell, z7's dmesg-clean and PMIC), 2 partial (stock measure, crash window: pstore yes, UART no), 1 failing (charger: c2 defers on tps61099), 6 open (UART, watchdog, UFS, USB network, rootfs, suite). Surya's chain (27 steps from surya-lab and docs) took another road: a distribution that already booted through U-Boot, systemd-boot and EFI, so its image, dtbo and stock-kernel steps are not-needed and PMIC and charger are not known. lab-tools has helpers for the image (lpoco bringup image pack/check/swap/bisect, initramfs build), fastboot, flash, provision, suite and suspend; none for UART, devicetree, banner, shell, PMIC, charger. The health suite's checks prove only the steps after a rootfs. docs already has the join this needs: components in docs, parts claimed in each device base (contract parts = 1), pulled by feed-device-parts into support_status, unclaimed = not known yet (decision 2026-11-17-commons-and-device-bases).\nOthers: nobody keeps bring-up steps as data with edges and a proof per step. Order is prose (Nura's porting and mainlining guides, UBports, Sailfish HADK, Qualcomm cover letters: boot to shell first); per-device status is a person's tick (Nura's Infobox Cargo table, Asahi's feature pages); proofs are flat lists (bootrr, dropped for unstable names and per-board lists; Collabora's DT probe kselftest; LAVA boot stages and test-case ids); dependencies are data only where machines run them (BitBake typed edges and input-keyed stamps, KernelCI, openQA fatal/ignore_failure, beads and Taskwarrior's computed READY). Nura's categories are levels as sets of checks.\nTried: the three tables, two records and the chain query in a scratch clone of docs: tad check passes, the edge record refuses a cycle, the generic chain orders 26 steps in 13 depths, walleye's claims give the queue walleye's keeper already has as ready (charger, watchdog, UFS, USB network), and the failing test passes with them and fails when one is removed.","sources":"nura-porting-guide,nura-infobox-device,nura-device-categorization,nura-hardware-ci,nura-mainlining-guide,asahi-feature-support,bootrr,collabora-dt-probe-kselftest,yocto-bsp-guide,yocto-compatible,bitbake-task-deps,lava-boot-action,lava-test-definition,kernelci-pipeline-config,openqa-docs,beads-issue-graph,github-issue-dependencies,taskwarrior-virtual-tags,ubports-porting,sailfish-hadk-subsystems","about":"bringup-steps","material":"research/bringup-steps/2026-11-18/","supersedes":null}
{"id":"bringup-steps-how-it-stands","brief":"Bring-up steps: decided (generic in docs, claimed per device base, pulled like parts), not built; 10 items unranked, first the schema the owner lands; the failing test is in the material","project":"linux-phone-oco/docs","date":"2026-11-18","question":"Where do bring-up steps as data stand, and what comes first?","found":"How it stands, 2026-11-18. Decided, not built: decision 2026-11-18-bringup-steps-generic-in-docs-status-in-each-base (research bringup-steps-landscape). Drafted and tried in a scratch clone, in research/bringup-steps/2026-11-18/: the three tables (schema.toml), the records bringup-step and bringup-edge, the query bringup-chain, a seed of 26 steps and 37 edges, walleye's 26 claims (17 done, 2 partial, 1 failing, 6 open), and the failing test bringup-chain-walleye.sh (fails on main: no query). Queue, unranked, for the author: docs bringup-steps-schema (the owner's to land), bringup-steps-seed, feed-device-steps, bringup-guidebook, milestones-step-terms; device-template steps-contract (after template-releases); google-walleye-lab walleye-steps-claimed and surya-lab surya-steps-claimed (after their template follow); lab-tools bringup-steps-helpers, then the research bringup-step-runner. Umbrella: bringup-steps. Open for the author: the stage list and the size of a step (26 for walleye's road so far); whether milestones should be rewritten as step sets; whether a claim should ever lapse by age (decided no: proven_on instead).","sources":"bitbake-task-deps,lava-test-definition,nura-infobox-device","about":"bringup-steps","material":null,"supersedes":null}
{"id":"base-graph-measured","brief":"The graph measured: 12 edges, 3 moved by a job, 6 by hand, 5 behind today; own files are a one-way exit and nothing carries a change up; the parts contract has two homes","project":"linux-phone-oco/docs","date":"2026-11-18","question":"What is the real dependency graph of idealkb, docs, device-template, the device bases, lab-tools and the forks: who pulls what, which way, by which tool, and how does drift show (the author, 2026-11-18)?","found":"Measured at origin/main of each (idealkb v0.16.0, docs 608b61f, device-template d6eae9e, surya-lab 42da677, google-walleye-lab f0e0fc2, lab-machine fb75285), read only.\nFiles go down: idealkb's slice reaches docs, ideal-agent, device-template and both labs by follow.sh/update-pins (hourly, every pin 0.16.0, current; since 0.16.0 a source names its pin and marker, ./sources lists device-template, skipped until it releases; check-one-owner stops two owners). device-template's 10 statements and the 4 device tables (devices, parts, test_runs, test_results - outside any marker) reach the labs by hand; the pin is a date. tad reaches every base by a weekly job whose consumers list lacks the three device bases; docs' CI runs tad 0.6.0, the rest 0.7.1. lab.toml pins lpoco 0.15.0 by hand; 0.17.0 was tagged the same day. sxmo-utils master on grenudi is 4 commits behind sr.ht, nothing fetches it; grenudi/linux is a GitHub fork, current.\nRows go up: docs pulls each lab's parts.json at main by DuckDB (contract parts = 1); component ids agree today by hand (none unknown) and nothing carries docs' catalogue or step ids down.\nChanges go up: nowhere by a tool. A followed file edited below ends follow.sh with 3 and a PR in the follower for a person; nothing reaches the source. own is a one-way exit: docs keeps 7 own files, 6 statements differ from idealkb's (decision.sql lacks --supersedes/--amends/--scope/--tracked-by since 0.14.0, so docs cannot record a superseding decision through its record; 0 decisions carry either), docs' tables.toml has no idealkb part, each device base's own tables.toml lacks 101 lines of idealkb 0.16.0's part; no upstream item names any of it (docs: 0 items to idealkb or the template; labs: 0).\nThe parts contract has two homes: declared by device-template, read by docs; bring-up steps will repeat it (catalogue in docs, claim table in the template). Every contract change is two PRs in two repositories and two release trains.\nIn all: 12 edges, 3 moved by a job (idealkb slice, tad, docs feeds), 6 by hand, 5 behind today. Failing test graph-drift.sh in the material: exit 1, 36 FAIL, 9 ok.","sources":"idealkb-chain-follow,rhizoid-repo,rhizoid-design-log","about":"base-graph","material":"research/base-graph/2026-11-18/","supersedes":null}
{"id":"base-graph-world","brief":"Only copybara (JVM) carries root-level files down and changes up; layered projects share four rules: one owner per file, named overrides with a status, fatal pins, a scheduled integrator report","project":"linux-phone-oco/docs","date":"2026-11-18","question":"What exists in the world for a chain of repositories that share files and must let changes travel both ways - subtree, submodules, josh, copybara, gbp-pq/quilt, stgit, topgit, Nix inputs, Yocto layers, Android repo, Gentoo/Arch overlays, copier/cruft, the kernel's maintainer trees - and what does each cost here (Python refused, Rust with argenv the house way)?","found":"Down and up, root-level files: subtree and subrepo carry a whole directory both ways (split/push) but need a prefix, and tad reads its statements at the root; submodules pin a repository at a path, no files at the root. Android repo copies files outside any project's history (Python). Nix inputs live in the store and cannot be patched in place (nix#3920); update-flake-lock bumps only. copier/cruft: pin + \"behind\" and \"edited\" checks, down only, Python. Renovate, multi-gitter, turbolift, microplane: a pin bump or a script per repo with a PR, down only. copybara alone does both: a follower's PR becomes a change request on the source, GitOrigin-RevId records the import, check_last_rev_state fails when the destination changed, merge_import keeps a destination's own lines - at the cost of a JVM 21 and Starlark per workflow. josh (Rust) selects single files at the root (::f, ::dest=src) and pushes back through a view, but its truth is one monorepo and a follower cannot keep its own variant; push back from separate repositories is unknown. No Rust or shell tool does root-level slices both ways: idealkb's follow.sh is the house's answer and the gap is real.\nLayering: Yocto (oe-core, distro, BSP): one owner per recipe, overrides as named .bbappend files, a dangling append an error, LAYERSERIES_COMPAT fatal, Upstream-Status required on every patch and an error by default, yocto-check-layer forbids a BSP changing others' signatures - the middle layer owns the contract the lowest is checked against. Gentoo: masters non-transitive (each overlay names every ancestor, as each base here pins each source), MasterPackageClobbered an error (check-one-owner). DEP-3: Forwarded/Applied-Upstream on each patch, yet 9.4% forwarded in trixie - a status that only warns moves nothing. Kernel: upstream first, a copy says \"commit X upstream\", linux-next merges every tree on a schedule and mails each conflict to its owners; ACK tags every carried commit UPSTREAM/BACKPORT/FROMGIT/FROMLIST/ANDROID. stgit (Rust 2.7.0) rebases a topic and empties what upstream took; topgit merges along .topdeps, dormant; git cherry finds a landed patch by patch-id with nothing installed. b4, gbp, copier, repo are Python.\nTake: a file has one owner, at the layer that owns its meaning (the contract's reader); an override is named and carries an upstream status, and a missing one fails; upstream first - a change is made at the owner and comes down by the pin; a follower's edit becomes a change request on the source (copybara); a scheduled integrator report names each drift to its owner (linux-next); landed patches retire by patch-id. Set aside every tool as a runtime: the house mechanism already lays slices, the gaps are the rules.","sources":"git-subtree-doc,gitsubmodules,josh-filters,josh-repo,copybara-reference,android-repo-manifest,nix-flake-patch-issue,cruft,copier-updating,dep3,yocto-layers,yocto-patch-status,gentoo-layout-conf,kernel-process,ack-readme,stgit-releases,git-cherry","about":"base-graph","material":"research/base-graph/2026-11-18/","supersedes":null}
{"id":"base-graph-how-it-stands","brief":"How the repository graph stands: decided 2026-11-18-device-layer-from-docs, nothing of it built; graph-drift.sh 36 FAIL; first step idealkb's from-prefix, then the layer moves into docs","project":"linux-phone-oco/docs","date":"2026-11-18","question":"Hand-over: where does the repository graph stand, what is decided, what is the next step and what proves it?","found":"Decided (2026-11-18-device-layer-from-docs, superseding 2026-11-18-device-template-follows-by-release): idealkb -> docs -> every device base; docs gives the device layer from device-layer/ (statements, the device tables' marked part, the skeleton), the template is a follower that keeps its made-once seed files; own needs an upstream item or a reason; a base's edit of a followed file goes up as a PR on the source; graph-drift.sh daily reports every edge; forks tracked by a daily fetch-and-test-merge job; git-rhizoid built after, by conformance (status, follow, send-back, cuttings).\nStands: nothing built. graph-drift.sh (research/base-graph/2026-11-18/) exits 1 with 36 FAIL: docs own-behind x6 and own-part, each device base's own-part and own backlog.sql, layer-pin/owner/follow in the template and both labs, lpoco pin, tad pins and consumers, sxmo tracking.\nNext, in order: idealkb's from-prefix and skip-unchanged (upstream items, idealkb's owner) -> device-layer-in-docs (docs' owner) -> template-follows-docs, surya-follows-template, walleye-follows-template; in parallel docs-own-statements-up, docs-tables-idealkb-part, graph-drift-daily, tad-pins-every-base, lpoco-pin-follows, fork-tracking-job. Done when graph-drift.sh exits 0 (backlog base-graph). Waits on the author: the device layer moving into docs, and git-rhizoid unparked with this scope.","sources":"idealkb-chain-follow,rhizoid-repo","about":"base-graph","material":"research/base-graph/2026-11-18/","supersedes":null}
1 change: 1 addition & 0 deletions data/session_log.json
Original file line number Diff line number Diff line change
Expand Up @@ -119,3 +119,4 @@
{"project":"linux-phone-oco/docs","id":"2026-11-18-research-bringup-steps","entry_date":"2026-11-18","title":"Research: bring-up steps as data","done":"bringup-steps-research.r1 (research lead, from orchestration). Mined google-walleye-lab (161 backlog items, 120 session logs, the bring-up order plan), surya-lab and docs' surya records, lab-tools' lpoco-bringup and lpoco-health tests (a researcher subagent), and docs' tables (components, features, feature_support, support_status, milestones, tests, the parts feed). Looked around at 22 outside sources (a researcher subagent). Drafted the tables, records, query, seed and failing test and ran them in a scratch clone of docs. Recorded 18 sources, the research, the decision, 11 backlog items unranked, the hand-over row; landed data and the material only.","considered":"Landing the schema myself; steps as components; status typed in docs; edges as a list field; an issue tracker; per-driver probe steps; a 30-day expiry","rejected":"Landing tables.toml, records and queries here: AGENTS.md sends them to the owner, orchestration. The rest: see the decision's rejected.","date":null,"about":"bringup-steps"}
{"project":"linux-phone-oco/lab-tools","id":"2026-11-18-host-records-the-root-files-it-installs","entry_date":"2026-11-18","title":"host records the root files it installs","done":"Built host-plan-unreadable-not-new (lab-tools #173): Seen {Absent, Text, Unreadable} in FileChange, install record, plan wording. Programmer review: two findings fixed (only PermissionDenied counts as unreadable; no diff printed for an unreadable file).","considered":"Recording at check time (kept as host-record-from-check); a record keyed per file vs one file (one file, lines HASH DST).","rejected":"Treating every read error as unreadable: a non-UTF-8 readable file would be called up to date unread.","date":null,"about":"host-plan-unreadable-not-new"}
{"project":"linux-phone-oco/lab-tools","id":"2026-11-18-host-record-from-check","entry_date":"2026-11-18","title":"host: record from the share check","done":"Built host-record-from-check (lab-tools #175): a passing share check records the hash of the unreadable polkit rule, unit and helper, so the next plan asks no sudo for them.","considered":"Recording for any unreadable file with a record; gating on ok>0 only.","rejected":"Recording over a recorded hash of other content: the probe shows some rule works, not that it is this one (reviewer finding, fixed). Recording when one of several devices failed.","date":null,"about":"host-record-from-check"}
{"project":"linux-phone-oco/docs","id":"2026-11-18-rhizoid-graph-research","entry_date":"2026-11-18","title":"Research: the repository graph, how changes travel both ways, and git-rhizoid's scope","done":"Measured every edge (12; 3 by a job, 6 by hand, 5 behind); two read-only researchers surveyed subtree, submodules, josh, copybara, Android repo, Nix inputs, copier/cruft, multi-repo bots, gbp-pq/quilt/DEP-3, stgit, topgit, Yocto, Gentoo, Arch, the kernel's trees, ACK; wrote graph-drift.sh (failing, 36 FAIL); decided 2026-11-18-device-layer-from-docs superseding the template follow decision (supersedes, scope and tracked-by set with ikb set: docs' decision record lacks them - itself an instance of the own drift); reshaped the template and lab items; filed idealkb's side and rhizoid's scope as upstream items.","considered":"Keeping the template as the layer's source; josh monorepo; copybara; porting follow.sh to rhizoid now.","rejected":"See the decision's rejected.","date":null,"about":"base-graph"}
Loading
Loading