Backlog
The work ahead and done.
Open · 17
A path for the canon and for the playbook
open-commons-observatory.github.io waits on the authorNeither has milestones, so neither has an Essence page. What each must reach is for its own records to say - to be drawn from their backlogs with their author, not invented.
lab-agent becomes lab-agent-oco
open-commons-observatory.github.ioThe repository, the package and the command; guide prints the whole working set - practices, tools, how to get them.
land and shot under the roof
open-commons-observatory.github.ioFrom a personal repository to creation-guidelines, marked, with their own records.
How we work as a lens
open-commons-observatory.github.ioCurated; views think, do and tools; a path whose measure is the share of practices carried by a tool; replaces the hard-coded page. To be reshaped by "a project, whole": practices and tools appear in…
The practices under the roof
open-commons-observatory.github.ioMoved from the observatory's design data to creation-guidelines, with a tool column: the tool or check that carries each, or none yet. To be reshaped by "a project, whole": practices and tools appear…
The tools as data
open-commons-observatory.github.ioA tools table: what each is, the practices it carries, how to get it - land, shot, ocoeco init and check, lab-agent-oco, the Rust environment template, devlab.
Languages: data translations
open-commons-observatory.github.ioThe face lays each project's own translations over its source text, and only its own; the Linux Phones lens has its Russian (by machine). Next: each project translating its own names, milestones and b…
Every project's idea, told for anyone
open-commons-observatory.github.ioWritten, each in its own repository, and each also in Russian: Rhizome, Rhizoid, the observatory, ocoeco, Essence, Linux Phones, the phone's lab, the engine, devlab, lab-agent, tad. argenv's awaits it…
land checks a commit's title before pushing
open-commons-observatory.github.ioA playbook landing failed in CI on a 106-character title against a 100-character rule: land can read the repository's commitlint rules and refuse before the push, not after a CI round-trip.
How we work and the observatory's family as lenses
open-commons-observatory.github.ioEvery view the observatory shows, built as a lens like anyone's.
Boards as data in each project
open-commons-observatory.github.ioEach project's live tasks as a shared table, harvested and shown next to its path.
The path: every project's visit card
open-commons-observatory.github.ioThree horizons on the readiness ladder, milestones with measured criteria, drawn as one line; the board beside it; switchable between projects, and a grand view of all. Settled 2026-11-11: the canon's…
tad in Rust, formats unchanged
open-commons-observatory.github.ioThen tad as a rhizcut; rhizoid v1 first.
A tidy commons: clean up the repositories and organizations
open-commons-observatory.github.ioAsked for by the author: the mess of his repositories and organizations (some thirty-five organizations, many from earlier years) sorted out - what is alive, what joins the ecosystem, what is archived…
Every project's workings
open-commons-observatory.github.ioWritten: Essence, Linux Phones and the phone, ocoeco, the engine, the observatory, devlab, lab-agent, Rhizoid, Rhizome, tad; argenv's awaits its author's merge. No project has all four marks: each has…
The workings in Russian
open-commons-observatory.github.ioIn Russian: the workings of Essence, Linux Phones and the phone, the observatory, ocoeco. To follow: the engine, devlab, lab-agent, Rhizoid, Rhizome, tad. Settled 2026-11-11: next: the engine's, devla…
The wrap-up pass
open-commons-observatory.github.ioSettle each of the 25 in-progress items: done, open with its next step, or parked with a reason.
In progress · 0
Done · 22
The attention view
open-commons-observatory.github.ioLive on the front page: what waits on a person, steps nothing delivers in projects being worked on, work gone quiet (unknown is not quiet).
Essence: the signature view
open-commons-observatory.github.ioLive: a project lands on its Essence page - why, what, how, now, down one line, with four marks. Essence is also its own project, the method, describing itself (creation-guidelines/essence-oco).
Two kinds of gap, told apart
open-commons-observatory.github.ioThe Essence page says which gap it is: reached but its delivery untold, or not reached and nothing serves it.
Languages: every interface message
open-commons-observatory.github.ioSixty messages and counted phrases (commits, readiness level) in the right plural form; left: "N of M" phrases and a few labels. Settled 2026-11-11: English and Russian for every message.
Languages: the structure
open-commons-observatory.github.ioLive: /en/ and /ru/ with identical paths, the root redirecting old addresses, the switcher (English · Русский) at the header end, lang and hreflang on every page, Fluent in the face.
The Linux Phones lens in its own repository
open-commons-observatory.github.ioIn linux-phone-oco; docs keeps producing the research data.
A lens-driven renderer
open-commons-observatory.github.ioThe engine renders any lens from its lens.toml with the view vocabulary, instead of hard-coded grand projects.
Lenses specified
open-commons-observatory.github.ioocoeco SPEC.md section 8: lens.toml, the family, the view vocabulary, curated and discovered.
Curated and discovered lenses
open-commons-observatory.github.ioCurated lenses take the navigation and the overview's grand projects; every other lens found is shown under Discovered lenses, drawn the same way.
Loose ends on the attention view
open-commons-observatory.github.ioLive 2026-11-11 under the attention view.
The -oco suffix: where it belongs
open-commons-observatory.github.ioSettled with the author: -oco is a telling touch for future projects and organizations, not a renaming of what exists.
Every agent instructs itself: lab-agent guide
open-commons-observatory.github.ioThe working practices as tad data here; lab-agent guide prints the living practices fetched from the observatory (a built-in copy offline); lab-agent's AGENTS.md sends every agent to it at the start o…
The observatory's own concepts and decisions on its site
open-commons-observatory.github.ioRendered from this repository's tables.
The observatory's own family as its sub-views
open-commons-observatory.github.ioUnder the Observatory tab: the overview, the observatory's path, ocoeco (its backbone), the engine.
Discovery and the harvest
open-commons-observatory.github.iooco discover and oco harvest; scheduled in CI.
The mark and its schema
open-commons-observatory.github.iooco.toml schema 1, the topics, seven projects marked.
Milestones as a standard table
open-commons-observatory.github.iomilestones: id, title, horizon (working | perfection | ongoing), readiness level, criteria (what measures it), status; first for Linux Phones and surya.
Still perfecting everything
open-commons-observatory.github.ioStanding item: every improvement to tools, data, practices or an agent's memory is carried back and recorded here. Settled 2026-11-11: a practice, not a task: practices 20 to 24 carry it.
Every project's how-close view
open-commons-observatory.github.ioA page per project with its path, backlog, log and ideas; the observatory's other projects as cards linking to them.
The site, first versions
open-commons-observatory.github.ioThe observatory as the meta tab, Linux Phones with its own views; ranked tables; honest how-close.
Recording as a tool: ocoeco note
open-commons-observatory.github.ioAdd or update a project's backlog item, decision, concept, working or log entry from the command line, validated against the format - so no agent hand-writes JSON in a job again. For tad repositories,…
Words that change with the number
open-commons-observatory.github.ioFixed in the engine: the count of projects is a counted message with each language's forms. The catalog could always do it; the cards had not asked.