SchOS

Author SHA1 Message Date

Author	SHA1	Message	Date
Nexoniarz	c0ed23cc56	freeze: one register for everything half-built, and the corners cleared The failure this is against is not scope creep. It is abandonment by promotion: a thing gets built to the point where it works, the next thing becomes more interesting, and the first is left in a corner -- in the tree, not finished, not deleted, and not in any list. Enough of those and the tree stops matching its own documentation. docs/plan/1.0.md now holds the register, and it is the only place anything half-built is listed. Four sections, because the kinds are genuinely different: built and connected to nothing (the text layer, a font from disk, socket activation, wait_vblank); started and stopped part-way (foundations 2-5, hybrid H2, Schcom v0, a released PCI device that nothing brings back); named in a "what it does not do" and still true; and frozen -- scoped, unstarted, not to be started. The rule is that nothing enters except by being finished or deleted, and that adding a row requires closing one. 1.0.md already said "two things in flight, never three". It was right and it was not being followed. Then the corners themselves, because a register written over a tree full of them is just a longer list: - cmd/init is deleted. Nothing had execed /bin/init since initcode.S changed to /bin/schinit; it was built and installed on every image as an unreachable fallback, and an unreachable fallback rots rather than saves. - projects/schwm/ and projects/schde/ are deleted. Both said "to be deleted" in their own first paragraph, which proves only that a directory marked for deletion is not deleted by being marked. README-only, no code lost, and the arguments each made are moved into wayland.md where they are still true. - projects/schcom/schcom and schcom-demo were tracked binaries. Untracked, and .gitignore'd. Three code comments and one document described a boot that has not happened since `7d44eb7`. cons_serial_only starts set, but kmain clears it on its first lines now, so the splash does not survive the boot and the kernel log is on screen from the start. That reversal was earned by a Chromebox with no serial port freezing at boot showing nothing at all, and the comments still argued the losing side of it. The site: - a download page. One ISO, what it has actually been run on -- one machine, under test -- Ventoy and dd, what the first boot looks like step by step, and the build if you would rather. The support table names one Chromebox rather than listing hardware, because one Chromebox is the entire bare-metal record and a list would be fiction. - Assets/usb.svg, drawn to the same rule as the other marks: two tones, geometry only, the accent spent in one place, and that place is the activity light because it is the part that tells you something is happening. - Download is in both navs and is the hero's primary action; a closing band ends the front page on it. - the uberblock-slots and drivers-outside-the-kernel figures are gone. Three numbers left, including the fastfetch one, which stays because it is funny. Two things caught by rendering the pages instead of assuming: .hero p was beating .filemeta on specificity and the file line was coming out at body size, and the dd command was one line long enough that the card clipped it at `conv=` -- a destructive command that can scroll half of itself out of view is a good way to take somebody's disk. It is two lines now. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2	2026-09-13 20:28:05 +02:00
Nexoniarz	57aff40228	docs: four directories, and a rule for when a thing leaves the roadmap docs/ was ten files where a plan, a description, a guide and a bug report all sat next to each other. It is now architecture/ (what SchOS is), plan/ (what it will be), guides/ (how to work on it) and history/ (why it is like this), with an index that states the one rule holding it together: when something is finished it moves from plan/ to architecture/ and is rewritten as a description of the thing rather than a record of building it. A ticked checkbox says the work happened. It does not say what the work produced, and six months later the checkbox is all that is left. The network stack proved the point: finished, verified end to end, and for a month the only description of it anywhere was a checkbox four levels of indentation deep. So roadmap.md went from 534 lines to 181 -- nothing deleted, the done work graduated. Seven subsystems that were finished and undescribed now have descriptions: boot, kernel, syscalls, filesystem, networking, graphics, usb, init. Every one ends with "What it does not do", which is the section that pays; a document listing only strengths is marketing, and the reader who needs it most is the one about to trip over a limitation nobody wrote down. schfs.md still opened with "phases 1 through 3 1/2 are done, phase 4 is next" long after all five had landed. It is a description now, with the phase record and the hard-won bugs moved to history/. Three corrections found on the way, all load-bearing: * projects/schcom/README.md claimed SCM_RIGHTS was done. There is no sendmsg/recvmsg in the kernel at all, and an entire GUI plan rested on it. * The root README said "No TCP/IP" months after the stack landed. * history/kernel.md sec.7 was marked "in progress" on a problem that process groups solved. Also adds plan/1.0.md, which draws a finish line so the open list stops being infinite, and marks schwm/ and schde/ superseded: in Wayland the compositor is the window manager, so that split dissolves rather than being abandoned. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2	2026-09-12 17:13:35 +02:00

Nexoniarz

c0ed23cc56

freeze: one register for everything half-built, and the corners cleared

The failure this is against is not scope creep. It is abandonment by promotion:
a thing gets built to the point where it works, the next thing becomes more
interesting, and the first is left in a corner -- in the tree, not finished, not
deleted, and not in any list. Enough of those and the tree stops matching its
own documentation.

docs/plan/1.0.md now holds the register, and it is the only place anything
half-built is listed. Four sections, because the kinds are genuinely different:
built and connected to nothing (the text layer, a font from disk, socket
activation, wait_vblank); started and stopped part-way (foundations 2-5, hybrid
H2, Schcom v0, a released PCI device that nothing brings back); named in a "what
it does not do" and still true; and frozen -- scoped, unstarted, not to be
started. The rule is that nothing enters except by being finished or deleted,
and that adding a row requires closing one.

1.0.md already said "two things in flight, never three". It was right and it was
not being followed.

Then the corners themselves, because a register written over a tree full of them
is just a longer list:

  - cmd/init is deleted. Nothing had execed /bin/init since initcode.S changed
    to /bin/schinit; it was built and installed on every image as an unreachable
    fallback, and an unreachable fallback rots rather than saves.
  - projects/schwm/ and projects/schde/ are deleted. Both said "to be deleted"
    in their own first paragraph, which proves only that a directory marked for
    deletion is not deleted by being marked. README-only, no code lost, and the
    arguments each made are moved into wayland.md where they are still true.
  - projects/schcom/schcom and schcom-demo were tracked binaries. Untracked, and
    .gitignore'd.

Three code comments and one document described a boot that has not happened
since 7d44eb7. cons_serial_only starts set, but kmain clears it on its first
lines now, so the splash does not survive the boot and the kernel log is on
screen from the start. That reversal was earned by a Chromebox with no serial
port freezing at boot showing nothing at all, and the comments still argued the
losing side of it.

The site:

  - a download page. One ISO, what it has actually been run on -- one machine,
    under test -- Ventoy and dd, what the first boot looks like step by step,
    and the build if you would rather. The support table names one Chromebox
    rather than listing hardware, because one Chromebox is the entire bare-metal
    record and a list would be fiction.
  - Assets/usb.svg, drawn to the same rule as the other marks: two tones,
    geometry only, the accent spent in one place, and that place is the activity
    light because it is the part that tells you something is happening.
  - Download is in both navs and is the hero's primary action; a closing band
    ends the front page on it.
  - the uberblock-slots and drivers-outside-the-kernel figures are gone. Three
    numbers left, including the fastfetch one, which stays because it is funny.

Two things caught by rendering the pages instead of assuming: .hero p was
beating .filemeta on specificity and the file line was coming out at body size,
and the dd command was one line long enough that the card clipped it at `conv=`
-- a destructive command that can scroll half of itself out of view is a good
way to take somebody's disk. It is two lines now.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2

2026-09-13 20:28:05 +02:00

Nexoniarz

57aff40228

docs: four directories, and a rule for when a thing leaves the roadmap

docs/ was ten files where a plan, a description, a guide and a bug report all
sat next to each other. It is now architecture/ (what SchOS is), plan/ (what it
will be), guides/ (how to work on it) and history/ (why it is like this), with
an index that states the one rule holding it together: when something is
finished it moves from plan/ to architecture/ and is rewritten as a description
of the thing rather than a record of building it.

A ticked checkbox says the work happened. It does not say what the work
*produced*, and six months later the checkbox is all that is left. The network
stack proved the point: finished, verified end to end, and for a month the only
description of it anywhere was a checkbox four levels of indentation deep.

So roadmap.md went from 534 lines to 181 -- nothing deleted, the done work
graduated. Seven subsystems that were finished and undescribed now have
descriptions: boot, kernel, syscalls, filesystem, networking, graphics, usb,
init. Every one ends with "What it does not do", which is the section that pays;
a document listing only strengths is marketing, and the reader who needs it most
is the one about to trip over a limitation nobody wrote down.

schfs.md still opened with "phases 1 through 3 1/2 are done, phase 4 is next"
long after all five had landed. It is a description now, with the phase record
and the hard-won bugs moved to history/.

Three corrections found on the way, all load-bearing:

  * projects/schcom/README.md claimed SCM_RIGHTS was done. There is no
    sendmsg/recvmsg in the kernel at all, and an entire GUI plan rested on it.
  * The root README said "No TCP/IP" months after the stack landed.
  * history/kernel.md sec.7 was marked "in progress" on a problem that process
    groups solved.

Also adds plan/1.0.md, which draws a finish line so the open list stops being
infinite, and marks schwm/ and schde/ superseded: in Wayland the compositor is
the window manager, so that split dissolves rather than being abandoned.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2

2026-09-12 17:13:35 +02:00

Renamed from docs/architecture/schapi.md (Browse further)