b6450d866d
The point is not a disclaimer, it is the argument: the tool is not the measure of a project. Code nobody understands is bad code whoever typed it, and code whose every decision can be explained is good code by the same standard. Placed next to a link to history/ on purpose. That directory is where the claim can be checked -- the bugs are written up in full, including the wrong hypotheses and the measurements that killed them. An explanation you can follow is the evidence; a byline is not. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2
73 lines
2.3 KiB
HTML
73 lines
2.3 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<title>Docs — SchOS</title>
|
|
<meta name="description" content="The SchOS documentation: architecture, guides, plans and the history of the bugs worth remembering.">
|
|
<link rel="icon" href="Assets/shift.svg" type="image/svg+xml">
|
|
<link rel="stylesheet" href="style.css">
|
|
</head>
|
|
<body class="reading">
|
|
|
|
<header class="top">
|
|
<div class="wrap">
|
|
<a class="brand" href="index.html">
|
|
<img src="Assets/shift.svg" alt="">
|
|
SchOS
|
|
</a>
|
|
<a class="pride" href="#pride-note" title="SchOS stands with the LGBTQIAP+ community — every month of the year">
|
|
<img src="Assets/pride.svg" alt="Progress Pride flag">
|
|
</a>
|
|
<nav>
|
|
<a href="index.html">Home</a>
|
|
<a href="docs.html" class="on">Docs</a>
|
|
</nav>
|
|
</div>
|
|
</header>
|
|
|
|
<div class="docshell">
|
|
<aside class="sidebar" aria-label="Documentation index">
|
|
<div class="sticky">
|
|
<nav id="docnav"></nav>
|
|
</div>
|
|
</aside>
|
|
|
|
<main>
|
|
<article id="doc" class="prose" aria-live="polite">
|
|
<p class="loading">Loading…</p>
|
|
</article>
|
|
</main>
|
|
|
|
<aside class="rail" aria-label="On this page">
|
|
<div class="sticky">
|
|
<nav id="toc" hidden></nav>
|
|
</div>
|
|
</aside>
|
|
</div>
|
|
|
|
<footer>
|
|
<div class="wrap">
|
|
<span>SchOS — kernel <b>SchIFT</b>, filesystem <b>SchFS</b>.</span>
|
|
<span class="mono">Apache-2.0, with the xv6-derived core under MIT.</span>
|
|
<span class="pride-note" id="pride-note">
|
|
<img src="Assets/pride.svg" alt="">
|
|
Built by, and for, people of every orientation and gender identity.
|
|
The flag stays up all year.
|
|
</span>
|
|
<span class="note" id="ai-note">
|
|
<b>On AI.</b>
|
|
Parts of SchOS were written with AI assistance, and that is not the measure
|
|
of anything. A project is good when the people building it understand what
|
|
was built, and bad when nobody does — whoever, or whatever, typed it. Vibe
|
|
your way through and you get something no one can fix. Stay in the loop and
|
|
you get a system you can explain line by line. The bug writeups in
|
|
<a href="?doc=history/kernel.md">history/</a> are where that gets
|
|
checked, including the wrong turns.
|
|
</span>
|
|
</div>
|
|
</footer>
|
|
|
|
<script src="docs.js"></script>
|
|
</body>
|
|
</html>
|