Open Commons ObservatoryEnglish·Русский

Бэклог

Работа впереди — и уже сделанная.

Открыто · 12

The command line declared with argenv

tad-engine

tad's surface (commands, flags, DOCS_FORMAT) as an argenv contract instead of clap and environment read by hand; proven equal.

tad q and tad sql print compact rows when stdout is not a terminal

tad-engine

Measured in linux-phone-oco/docs (research kb-navigation-remeasured): tad q about --subject audio-mic prints 91 KB in the box format and 15.9 KB as csv; an agent reads stdout, not a terminal. Asked by…

render's exact output is guarded in tad itself, not only by the consumers' verify

tad-engine

Carried from text-as-data-template (render-test-coverage, render-determinism-untested-multicore): render.rs has no tests of its own; its output is held only by each consumer's CI comparing the pages.…

Every marked project keeps its data with tad

tad-engine

The heart of oco-eco: every project's state as text as data, gathered and propagated.

Data gathered automatically from real files and tests

tad-engine

Today ad hoc in linux-phone-oco/docs: three scheduled feeds (wiki claims, kernel activity, shell releases) and device test results imported. Next: gatherers as standard CI jobs and hooks that tad itse…

tad in Rust - general, Python-free

tad-engine

The text/file database in git, kept general: schemas with typed columns and allowed values, canonical form, documents rendered from data, queries - in Rust, with no Python. ocoeco builds on it, as Tru…

Rendering leaves tad for a tool of its own

tad-engine

After tad sql: a small tool that consumes tad renders a repository's pages, with the presentation declaration in its own file; proven byte-identical on the four repositories; then tad drops render and…

tad as a rhizcut in every repository

tad-engine

Instead of a copied subtree of a dist branch: an owned, patchable rhizoid module. Needs rhizoid v1.

tad in Rust, formats unchanged

tad-engine

The same data, sturdier machinery; the observatory's engine already reads tad data in Rust.

Gatherers as standard parts of tad

tad-engine

CI jobs and hooks that read a project's real files, test results and releases into its tad data, the same way in every repository.

ocoeco builds on tad

tad-engine

ocoeco's shared language is now a tad declaration (language.toml) and ocoeco note checks rows with tad's check_row (tad 0.4.0 added check_row, extra_fields and dated for it). Next: ocoeco check valida…

The repository becomes tad; the template retires

tad-engine

After rendering leaves: rename creation-guidelines/tad-engine to tad (GitHub keeps redirects; update install-tad.sh, update-pins.sh, ocoeco's dependency to the new name). Check whether anything still…

В работе · 0

Готово · 10

Canonical form and row edits

tad-engine

tad canon (declared field order, empty as null, row order kept, only on checked data) and tad set (one row added or updated, typed by its declaration, the whole repository re-checked, the file put bac…

tad check, in Rust

tad-engine

tad check: rows (types, required, allowed values, patterns, prefixes, ranges, differing pairs, dependencies, keys) and rules across tables (unique ids, references, appears-in, no mirrored relations).…

Tables declared as data

tad-engine

All four repositories keep a tables.toml at their root: tables generated from schema.sql, rules across tables written by hand from checks/*.sql, each giving the same verdicts as Python on the real dat…

The formats and protocols

tad-engine

Text as data: tables as JSON lines with a schema, the canonical form, verification.

tad kept current in each repository

tad-engine

bin/update-pins.sh moves each repository's pin to tad's latest release, re-canonicalizes and re-renders, and lands through each repository's CI; the lab machine runs it weekly (grenudi/lab-machine: sy…

Pages rendered from the data

tad-engine

tad renders every table as pages; matrices from the schema's shape.

Presentation declared as data

tad-engine

The canon renders from its declared presentation with tad 0.3.0: its own renderer and DuckDB retired, its pages identical but for the notice line. No tad repository keeps a renderer of its own.

Documents rendered from data

tad-engine

tad render: one page per table, Markdown and reStructuredText, every shape the Python renderer detects (relations, sources and citations, grids, the about page). Proven byte for byte against today's P…

tad sql: real SQL over the declared tables

tad-engine

tad sql: a port in tad's words (load the declared tables, run a statement, give them back), its adapter DuckDB's pinned standalone binary (2026-11-12-duckdb-as-an-adapter). A query prints its rows; a…

The four repositories switched; Python gone

tad-engine

All four repositories run on tad in Rust (2026-11-11): the playbook, Rhizoid, the phone project (its feeds kept their SQL, run by DuckDB's pinned standalone binary, proven to give the same rows) and t…