ok> documents

How it was built, and what it says.

Every release builds its documents from the same tree as its images: the design record, the dictionary of every word, the book, the formal volumes. Each is a PDF on the release, with its checksum.

[TAG] SHA256SUMS → All releases →

Start here

Two books, kept with every release.

The Book of Fabric

the design record, as it happened

Every ruling, the reasoning behind it, what was built and what was abandoned, written as the work went -- reproduced as written, corrections and all. The living record first, then the closed ones in order. Fabric is about steady state: this is how it was reached.

SHA-256 [SHA:fabric.pdf]
fabric.pdf

The Dictionary of v4

every word, alphabetical

Every word StarForth v4 boots with: its stack notation, what it does, and where it is defined. The names come from the booted system itself, and the build refuses a dictionary that has fallen behind it.

DUP      ( x -- x x )       Copy the top value.
MINT-ZUSE ( -- )            Mint the real Zuse onto a second stick.
SHA-256 [SHA:dictionary.pdf]
dictionary.pdf

And the rest

The book, the formal set, the API.

The book
StarshipOS, end to end
[SHA:book.pdf]
Volume I
the formal set
[SHA:vol1.pdf]
Volume II
the formal set
[SHA:vol2.pdf]
Volume III
the formal set
[SHA:vol3.pdf]
API reference
StarForth's C, generated
[SHA:api.pdf]

The paper

The ideas behind it, on SSRN.

The whitepaper the design starts from.

Read the paper →