Loading…
Loading…
SGC OS is the environment this site runs as: a small operating system for exploring the work, the story behind it, the experiments, and the record that supports all three. This page is its manual — what the environment contains, how its record is kept, and the rules the interface keeps.
Six applications, one shell.
The system bar above lists the applications; the status line below reports on the record. This ledger and that bar read the same manifest, so neither can name an application the other does not.
How a statement earns its place.
Every statement about a piece of work carries a source, and every source is graded. The grade is read off a small square beside the statement. It can say four things.
Measured or directly observed, with the source on record.
Supported, but resting on the author’s own account, or on a source that could only partly check it.
Not established. What would settle it is recorded instead of the blank being filled.
Known, and not cleared for publication — an employer’s, a client’s, or under review.
A source also says what it can attest — that something exists, how it is structured, how it behaves, or what was measured — so a reader can tell “we read the code” from “we watched it run” without taking anyone’s word for which it was.
When something is not known, the page says so in the reader’s words rather than filling the blank: never measured, awaiting a written account, awaiting first-person reflection, withheld. A document lists what it still lacks at its end, under Still open.
Access to a repository is not permission to publish it. Work that belongs to an employer or a client can be named where the name is already public, and nothing more appears: no page, no figures, no screenshots, no sources. The status line counts such work as withheld.
Provenance and lifecycle are different facts about a thing.
How strongly is this statement supported?
What stage is this object in?
In development · Released · Beta · Dormant · Archived
The two never merge. Lifecycle is always a word and never a square: it says what a project is doing, not how much of what is said about it was checked. A released product can still carry a provisional claim; a dormant one can be verified end to end.
Only the ones the interface keeps.
A fact cannot be written without a source on record. What rests only on the author’s word renders as provisional; what nobody knows renders as a gap.
Not known, withheld and reserved each have a fixed appearance — a plain sentence, a hatched square, four corner marks. Nothing renders as a blank or a promise.
The bar, the status line and the ledgers on this page display only what the registry computes. No count, tagline or availability is typed in.
Home says what exists, Work what was built, Story who built it, Lab what is being explored, Contact how to reach the author, System how this works. None repeats another.
An experiment can stop at any point and still be listed, as long as what it was and where it stands are stated plainly. Finished, substantiated work becomes a document in Work.
What the visual language means.
The system speaks in a monospaced face — labels, states, counts, paths — and narrative is set in a text face. The two never share an element, so a reader can tell the system talking from the author talking without a border between them. Type is set in two weights; nothing is bold.
Structure is drawn with one-pixel rules. A box only frames something that is an object: a figure, a window, an experiment.
Four corner ticks mark a region the system has declared and not yet filled: a reserved figure, an empty bench.
Yellow is the system’s accent. Green marks what is fine, amber a caution, red danger, cyan what is live or interactive, purple what is withheld. Lab alone borrows cyan as its accent.
Something moves because a state changed or a context opened — a document settling as it opens, a line registering an identity — never because the page scrolled. Under reduced motion it cuts.