Skip to content

Blog

Short, dated notes sit here when a new handbook chapter would be heavy-handed: release context, design trade-offs, and engineering notes. The site is English-only; each post is one Markdown file under docs/blog/posts/.

Start procedures in Quick Start; vocabulary and principles in Design Philosophy. Longer narrative—e.g. Research Review and Design Insights—lives in posts, not in the manuals.

The Changelog lists factual documentation moves and milestones. The blog can explain why something changed without copying every changelog line.

RSS is emitted when the build runs with CI=true (as in publishing). A plain mkdocs serve often skips the RSS plugin; that is normal locally.

See also: Changelog · Contributing

Recent posts

2026 05 06 design insights

Note

Exploratory note on architecture and open questions around scientific data processing. Not a stable product commitment.

Design Insights

Quick links: Home · Quick Start

Model-centric pre-training and literature-scale mining impose different failure sensitivities. The pipeline therefore treats semantic stability, structural consistency, and minability as explicit design targets, implemented mainly through Processor (quality) and Designer (views and contracts). Executable detail on pipelines, tags, and acceptance tests now lives in those product docs rather than in this essay.

2026 05 06 research review

Note

Exploratory note on architecture and open questions around scientific data processing. Not a stable product commitment.

Research Review

Scientific papers encode terminology, numerals, notation, figures, and qualifiers in ways that general-purpose text tools rarely preserve. Once PDF or OCR pipelines emit machine-readable text, small formatting defects propagate into training corpora, extractors, and review tools—so preparation standards must be domain-aware, not merely “spell-checked.”

Mapping the pipeline to the docs

This documentation splits operational detail (how to run and validate) from conceptual pages (contracts, layout, governance). This note is a map, not a tutorial: it tells you where to read once you know which stage you care about.