Historical specifications and delivery records

These pages preserve the reasoning and delivery history behind RiX. They can include proposed syntax, superseded APIs, old implementation gaps, or completed checklists. They are excluded from the site’s search index in both documentation build modes so a search for today’s API leads to current guides. Existing URLs remain available for citations and links.

For supported behavior, start with implementation status, the language reference, the plugin catalog, or the generated runtime catalog.

Historical material	Current starting point
Early language specification and open design questions	Language reference
April 2026 review	Implementation status
Handwritten IR snapshot	Generated IR registry
Document roadmap and notation proposals	Document persistence, publication layout, and assets
Reactive control delivery plan	Reactive controls
RiXCel delivery checklist	Workbooks, tensor editing, and regional output
Structural arithmetic completion record	Structural values
Editor and language-server proposal	Editor and coding-agent tooling
Plugin roadmap and rendering proposals	Plugin catalog and renderer guide

Current implementation contracts remain searchable even when their source lives under design/. In particular, concurrency semantics, runtime performance measurements, output contracts, and the RiXCel format are useful current references. File location alone does not determine whether a page is historical.

Unpublished scratch notes, old generated parser HTML, and reports outside the explicit site render list remain repository history; they are not documentation search results.