Archive

How each part of skoro came to be: the mathematics worked out for it, the implementation it was given, and the plan it was built by, kept as they were approved.

An entry is opened for each piece of development and moves through its stages: for a feature, the mathematics, then the implementation, the plan, the build, and last the pages that say what the feature made true. What each stage approved is kept here as it was approved. When the library later changes, a new entry revises the old one rather than rewriting it.

In progress

The coreIn progress The core of skoro, built to the charter: the API for building models, with quantity types (the Euclidean manifolds, products, and the discrete types), the primitive operations and their derivatives of first and second order, composition, the compilation graph and its compiler, the probabilistic graph, terms and bindings, the writer with its snapshots, branches and building scopes, addresses, explicit random keys, and the layer over burn. It ends where models can be built and differentiated but no distribution exists yet, except private ones in tests. Much of it is ported from the archive branch, reshaped to the charter. When it is done, REVISIT.md lists every feature of the archive not yet brought back, each to return as an entry of its own.

Done

What skoro isDone The library's charter: what skoro is for, who it serves, and the positions on which everything else in it rests. It was written when the repository started over, from an interrogation of the design that came before (kept on the archive branch), so that each later entry has a stated purpose to build towards and to be measured against. It settled skoro's purpose and its users, and twelve positions on the shape of its core; the home page and What is skoro? were written from it.