Open Commons ObservatoryEnglish·Русский

Open Commons Observatory

One living picture of the open commons. Every project keeps its own state as data; the observatory finds the marked ones and gathers what they share - nothing is wired in by hand.

20grand projects
28projects in the picture
281open items, all backlogs
418session log entries

Where the whole is weakest

Read before choosing the next piece of work.

Waiting on a person

  • Ideal agent · The author's canons as one source: software-engineering-canon, the playbook, design-canon the author's word on design-canon
  • Ideal agent · Measure a role-named session's first turn with read-weight on plugin 0.3.0 plugin 0.3.0 installed on the lab and a session started with a Role line
  • Ideal knowledge base · tad: tad r NAME --help from the statement header, and completion of enumerated values (about subjects, project places) tad-engine
  • Linux Phones · The audio DSP sleeps when nothing plays a deeper decision: what on the Apps/AOSS side holds CX and AOSS (sleep set, cluster parameter, the UARTs' CX vote) is unknown
  • Linux Phones · Upstream: tqftpserv >= 1.2 in Alpine v3.24-stable the author: a request to Alpine is made in his name
  • google walleye lab · Boot image: header v0, base 0, kernel 0x8000, ramdisk 0x1000000, tags 0x100, page 4096, dtb appended walleye's stock boot.img header (android-reference-walleye) to confirm the offsets
  • google walleye lab · Remove the C probe of the ffs helper (build/ffs-acm/ffs-acm.c and what only builds n3 from it) once n3r is tried walleye-ffs-rust-try (the keeper's first try of n3r)

Steps nothing delivers

  • Linux Phones · 5: Calls and messages, Connected: data, Wi-Fi, Bluetooth, GPS, The daily basics
  • lpoco · 1: Built on postmarketOS

Work gone quiet

Nothing here.

Manual work worth a tool

  • take a screenshot of a page and look at it · 28× · 23 effort-minutes · Observatory
  • compare our device tree with the vendor kernel's · 5× · 20 effort-minutes · The lab of the Xiaomi POCO X3 NFC (surya)
  • place the microphone and listen to the speakers · 3× · 6 effort-minutes · The lab of the Xiaomi POCO X3 NFC (surya)
  • ran two fastboot boot tries · 3× · 3 effort-minutes · google walleye lab

Loose ends 12

Everything left in progress anywhere, oldest first. Settle each: done, open with its next step, or parked with a reason.

  • Ideal agent · Measure a role-named session's first turn with read-weight on plugin 0.3.0 since 2026-11-17
  • Linux Phones · docs holds only what helps every device; each device has its own open base; docs derives progress from them since 2026-11-17
  • Linux Phones · How a device repository takes later changes of device-template beyond idealkb's generic files since 2026-11-17
  • Linux Phones · The audio DSP sleeps when nothing plays since 2026-11-17
  • Linux Phones · Upstream work is kept as records: upstreams and upstream_items (idealkb 0.8), the upstream-* items headed in them since 2026-11-17
  • google walleye lab · Measure Android on the Pixel 2 before anything is flashed since 2026-11-17
  • google walleye lab · Boot image: header v0, base 0, kernel 0x8000, ramdisk 0x1000000, tags 0x100, page 4096, dtb appended since 2026-11-17
  • google walleye lab · First fastboot boot of the walleye kernel: the phone leaves fastboot and its gadget answers since 2026-11-17
  • google walleye lab · Initramfs that brings up a USB gadget (ACM console + RNDIS/ECM) and telnet/ssh on 172.16.42.1 since 2026-11-17
  • lpoco · lpoco-health: the one health suite on the phone, with switches and run-time detection since 2026-11-17
  • lpoco · lpoco host: the lab host prepared from the lab's and each device's declarations - udev access for gadget serials, host modules, the host's own tools at their pins; plan by default, prepare now to change since 2026-11-17
  • The lab of the Xiaomi POCO X3 NFC (surya) · surya's own cluster sleep parameters in its device tree since 2026-11-17

Grand projects

Linux Phones

phones running Linux, as good as Android - and how close we are

Working
0/4Calls and messages
0/4Connected: data, Wi-Fi, Bluetooth, GPS
0/8The daily basics
Perfection
0/46Everything a phone does
0/6Apps and services as good as Android's
Ongoing perfection
0/6Secure and kept up to date
0/1Tested on real devices
1/4Fixes upstream
Readinesslevel 0 of 9

0 / 46 features known to work on Linux phones (best current), 5 partly, 4 missing, 37 still to measure · 7 projects

Rhizome

stop managing software, start growing it

Working
2/2The idea, whole
0/4Identity works
0/2The round trip
0/2Real code, synced by difference
Perfection
0/3Conjuring
0/3Visible, running, changing live
Ongoing perfection
0/1It grows itself
0/1The first user, ahead on day one
Readinesslevel 1 of 9

3 projects

Mnemonic Vocabulary

an interactive engine for all mnemonic techniques - and the memory kingdom they build

Working
1/1The idea, written down
0/2Designed
0/2Encodes and recalls
0/1The memory kingdom, seen
Perfection
0/1Memories that last
0/1On a PC and a phone
Ongoing perfection
0/1And maybe Android
Readinesslevel 1 of 9

2 projects

Package distribution

one conveyor, called not copied

2 projects

Discovered lenses

Grand views the observatory found, made by anyone - drawn the same way as its own.

as-steps

0 projects

at-a-glance

0 projects

canon

0 projects

curated

0 projects

documents

0 projects

face

0 projects

front

0 projects

held-back-by-the-author

0 projects

people

0 projects

practices

0 projects

site

0 projects

site

0 projects

still-showing

0 projects

surfaces

0 projects

the-perfect-form

0 projects

waiting-on-the-author

0 projects

The observatory itself

Observatory

one living picture of the open commons

Working
2/2Finds and gathers every project
2/2Shows the picture
Perfection
2/3Every project's path
0/1Boards beside the paths
0/1tad in Rust
Ongoing perfection
1/1Agents instruct themselves
1/1Still perfecting
Readinesslevel 7 of 9

4 / 7 milestones done · readiness 7 / 9

✓ why✓ what○ how✓ now

ocoeco

the information ecosystem - data made by work, chained and propagated

Working
2/2One language for all data
1/1Data rises by itself
1/2Data made by work, not by hands
1/5Every change recorded
Perfection
0/1Data chains
1/2Its own core, in Rust
0/1A rhizcut everywhere
Ongoing perfection
0/1The principle lived
Readinesslevel 7 of 9

2 / 8 milestones done · readiness 7 / 9

✓ why✓ what○ how✓ now

ocoeco-engine

draws the observatory from ocoeco's data - its lenses, in every language

Working
2/2Draws the picture
3/3Every project's path and page
Perfection
2/2Draws anyone's lens
3/3In every language
1/2Boards beside the paths
Ongoing perfection
0/1Every view a lens
Readinesslevel 8 of 9

4 / 6 milestones done · readiness 8 / 9

✓ why✓ what○ how✓ now

Other projects on their way

Agent access

every tool usable by agents

Working
1/1Researched and planned
0/2An agent can drive a terminal program
0/1Scenes run for any project
Perfection
0/1Offered to any agent
Ongoing perfection
0/1Every tool has its doors and its scenes
Readinesslevel 1 of 9

1 / 5 milestones done · readiness 1 / 9

✓ why✓ what○ how✓ now

device template

a new phone's lab is a new device.toml

Working
1/2A new phone is a new device.toml
Perfection
Ongoing perfection
Readinesslevel 0 of 9

0 / 1 milestones done · readiness 0 / 9

○ why✓ what○ how✓ now

Essence

how to say why and how - of anything

Working
2/2Written, and able to describe itself
1/1A language for it
2/2Drawn on one page
Perfection
2/2Measured for every project
Ongoing perfection
0/1Every project tells its essence
Readinesslevel 7 of 9

4 / 5 milestones done · readiness 7 / 9

✓ why✓ what○ how✓ now

Package conveyor

one conveyor, called not copied

Working
1/1Designed
4/6Extracted, nothing changed for users
1/1Alpine packages for the phone
Perfection
0/1The shells shipped through it
Ongoing perfection
0/1Delivered, not just published
Readinesslevel 1 of 9

2 / 5 milestones done · readiness 1 / 9

✓ why✓ what○ how✓ now

Mnemonic Vocabulary

an interactive engine for mnemonic techniques and the memory kingdom they build

Working
1/1The idea, written down
0/2Designed
0/2Encodes and recalls
0/1The memory kingdom, seen
Perfection
0/1Memories that last
0/1On a PC and a phone
Ongoing perfection
0/1And maybe Android
Readinesslevel 1 of 9

1 / 7 milestones done · readiness 1 / 9

○ why✓ what○ how✓ now

Rhizoid

fork, own and sync git dependencies instead of relying on a package manager

Working
0/1The command line, implemented
0/1The consumption side, designed
Perfection
0/1A TUI
Ongoing perfection
0/1ocoeco travels as a rhizcut
Readinesslevel 0 of 9

0 / 4 milestones done · readiness 0 / 9

✓ why✓ what○ how✓ now

Rhizome

stop managing software, start growing it

Working
2/2The idea, whole
0/4Identity works
0/2The round trip
0/2Real code, synced by difference
Perfection
0/3Conjuring
0/3Visible, running, changing live
Ongoing perfection
0/1It grows itself
0/1The first user, ahead on day one
Readinesslevel 1 of 9

1 / 8 milestones done · readiness 1 / 9

✓ why✓ what○ how✓ now

Sxmo profiles

Working
1/2surya's profile, checked
Perfection
0/1More phones
Ongoing perfection
1/1Upstream
Readinesslevel 0 of 9

1 / 3 milestones done · readiness 0 / 9

○ why✓ what○ how✓ now

argenv

a declared, typed, machine-readable contract for a program's argv and env

Working
2/2One declaration, one contract
2/2Published and used
Perfection
0/2The open questions settled
Ongoing perfection
1/1In the ecosystem
Readinesslevel 8 of 9

3 / 4 milestones done · readiness 8 / 9

✓ why✓ what○ how✓ now

lab-agent

an agent's lab machine, board and inbox

Working
1/1Runs the agent's work
1/1A board to work by
2/9Redesigned: run once, resume, never replay
Perfection
1/1Never in the way
1/1Instructs any agent
0/5lab-agent flows through ocoeco
Ongoing perfection
0/1Boards as shared data
0/1Asks people well
Readinesslevel 7 of 9

4 / 8 milestones done · readiness 7 / 9

✓ why✓ what○ how✓ now

lpoco

the conveyor's tools for any phone

Working
2/2Reaches and checks a phone
1/1Safe experiments
Perfection
2/2A phone's whole life
0/1Half-manual tests
Ongoing perfection
0/1Built on postmarketOS
Readinesslevel 8 of 9

3 / 5 milestones done · readiness 8 / 9

✓ why✓ what○ how✓ now

tad

text as data, rendered

Working
2/2The formats and pages
0/1Gathers data by itself
Perfection
5/5tad in Rust
0/1Standard gatherers
0/1A rhizcut in every repository
Ongoing perfection
0/1The heart of oco-eco
Readinesslevel 6 of 9

2 / 6 milestones done · readiness 6 / 9

✓ why✓ what○ how✓ now

Every project

0 / 28 projects tell their whole essence: why, what, how and now

open-commons-observatory

Mnemonic Vocabulary: an interactive engine for all mnemonic techniques - and the memory kingdom they build

lens3 shared tables

Mnemonic-Vocabulary-org/lens

○ why○ what○ how✓ now

Mnemonic Vocabulary: an interactive engine for mnemonic techniques and the memory kingdom they build

research7 shared tables

Mnemonic-Vocabulary-org/mnemonic-vocabulary-oco

○ why✓ what○ how✓ now

argenv: a declared, typed, machine-readable contract for a program's argv and env

tool12 shared tables

argenv-opencommons/argenv

✓ why✓ what○ how✓ now

Agent access: every tool usable by agents

conveyor15 shared tables

creation-guidelines/agent-access-oco

✓ why✓ what○ how✓ now

Essence: how to say why and how - of anything

canon9 shared tables

creation-guidelines/essence-oco

✓ why✓ what○ how✓ now

The ideal project playbook: how a project is made ideal

canon6 shared tables

creation-guidelines/ideal-project-playbook

○ why○ what○ how✓ now

lab-agent: an agent's lab machine, board and inbox

tool15 shared tables

creation-guidelines/lab-agent

✓ why✓ what○ how✓ now

The software engineering canon: principles, architectures, practices

canon14 shared tables

creation-guidelines/software-engineering-canon

○ why○ what○ how✓ now

tad: text as data, rendered

tool14 shared tables

creation-guidelines/tad-engine

✓ why✓ what○ how✓ now

Rhizoid: fork, own and sync git dependencies instead of relying on a package manager

tool11 shared tables

git-rhizoid/git-rhizoid.github.io

✓ why✓ what○ how✓ now

Ideal agent: how an agent works in the open commons - practices, skills, hooks and roles, written once

canon10 shared tables

grenudi/ideal-agent

○ why○ what○ how✓ now

Ideal knowledge base: how a base is organised so that an agent answers by one query - a layer on tad

canon6 shared tables

grenudi/ideal-knowledge-base

○ why○ what○ how✓ now

Linux package distribution: one conveyor, called not copied

conveyor11 shared tables

linux-package-distribution-oco/conveyor

✓ why✓ what○ how✓ now

Package distribution: one conveyor, called not copied

lens3 shared tables

linux-package-distribution-oco/lens

○ why○ what○ how✓ now

Linux Phones: phones running Linux, as good as Android - and how close we are

picture25 shared tables

linux-phone-oco/docs

✓ why✓ what○ how✓ now

Linux Phones: phones running Linux, as good as Android - and how close we are

lens2 shared tables

linux-phone-oco/lens

○ why○ what○ how✓ now

OCO: the open commons' ecosystem - what holds between its stars

constellation20 shared tables

open-commons-observatory/ecosystem

✓ why○ what○ how✓ now

ocoeco: the information ecosystem - data made by work, chained and propagated

tool19 shared tables

open-commons-observatory/ocoeco

✓ why✓ what○ how✓ now

ocoeco-engine: draws the observatory from ocoeco's data - its lenses, in every language

tool12 shared tables

open-commons-observatory/ocoeco-engine

✓ why✓ what○ how✓ now

Open Commons Observatory: one living picture of the open commons

observatory24 shared tables

open-commons-observatory/open-commons-observatory.github.io

✓ why✓ what○ how✓ now

Rhizome: stop managing software, start growing it

lens3 shared tables

rhizome-oco/lens

○ why○ what○ how✓ now

Rhizome: stop managing software, start growing it

research11 shared tables

rhizome-oco/rhizome

✓ why✓ what○ how✓ now

linux-phone-oco

Device template: a new phone's lab is a new device.toml

device-lab8 shared tables

linux-phone-oco/device-template

○ why✓ what○ how✓ now

The lab of the Google Pixel 2 (walleye)

device-lab6 shared tables

linux-phone-oco/google-walleye-lab

○ why○ what○ how✓ now

lpoco: the conveyor's tools for any phone

tool2 shared tables

linux-phone-oco/lab-tools

✓ why✓ what○ how✓ now

The lab of the Xiaomi POCO X3 NFC (surya)

device-lab8 shared tables

linux-phone-oco/surya-lab

✓ why○ what○ how✓ now

Sxmo device profiles for Linux phones

tool2 shared tables

linux-phone-oco/sxmo-deviceprofiles

○ why✓ what○ how✓ now

marshall-oco

Marshall's observatory: every constellation and star he tends, as one sky

observatory12 shared tables

marshall-oco/marshall-oco.github.io

○ why○ what○ how✓ now

Latest work

A launched builder or research lead sends its report as a message

Sign from the coordinator: two lab-tools-builder runs (lab-tools #103, #104) landed and never reported; orchestration found them through the lanes-waker. The builder and research-lead cards now say their last act, after the final landing, is two lines sent as a message to whom th…

Patrol round 2026-11-18 05:08 UTC

Read-only round: nothing changed, no sign filed. Landings (6h): docs 20+, lab-tools, device-template, surya-lab, walleye-lab all by PR, device rows in their own bases. devlab-watch@surya-lab active; its log shows the phone not reachable (parked, expected: author power cycle, back…

Orchestration renewed: phone rows in docs routed, the suspend cycle to the builder

Took up orchestration-2026-11-18-morning. Lab read: lpoco host check all ok at 0.4.0, land at d7a71bf (lab-machine #45/#46: land opens a new PR when the branch's earlier one is merged - the merged-branch sign is answered). docs-phone-items-to-lanes closed: all its rows done but h…

How the phone stands

T1 tried on b (fastboot boot only, nothing flashed): back in Android after 159 s; battery 4384 mV/100% before. /sys/fs/pstore empty, no ramoops dir: our marker and panic text did not survive (cause B). Phone in Android on b, stock kernel, adb root, slots a and b good; lease relea…