Labels

Adding, subtracting, multiplying etc of variables, parameters etc.

A variable's bounds and the domain vocabulary

Assembling a model from files, and fixing a decision

What a file guarantees about the data it binds

Blocks expanding to declarations: piecewise, indicator, McCormick

What an operator may reduce, walk, read or refuse

relations and dimensions: the relation design

What the three formats print, and the annotations they print

What a where predicate may say

Something isn't working

Code and the documented spec disagree

Fails without an error — loads clean, wrong or undefined meaning

Pull requests that update a dependency file

Decided — the build queue

Argued against; closes as not planned

In scope; the spelling is undecided

Is this the language's business at all? Against #30 and ceiling.md

Documentation pages, guides, reference and README

Pull requests that update GitHub Actions code

About the project rather than the language — trackers, naming, process

This PR needs no changelog entry. To bypass ci

Scope-defining statement to close others against

The direction rides in over=, as over=generator -> zone (#495)

The direction rides inside by=, as by=zone_of(generator -> zone) (#499)

The direction gets a keyword of its own, direction=generator -> zone (#502)

A column is named after the relation, and the read stays at(), as at(cap, by=ends.bus0) (#515)

A column is named after the relation, and the read is an index, as price[zone_of] (#506, #509)

Groundwork every proposal keeps, so it competes with none of them