Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ The landing page for [Almide](https://github.com/almide/almide), served at <http

Plain HTML and CSS, no build step. A small optional script remembers the colour scheme; every page and language link works without JavaScript.

The layout follows the [O6lvl4 portfolio](https://o6lvl4.github.io/O6lvl4-portfolio/): monochrome surfaces, a red accent, JetBrains Mono, and a compact evidence panel. The complete header stays available on mobile, with navigation separated from language and theme controls.
The layout follows the [O6lvl4 portfolio](https://o6lvl4.github.io/O6lvl4-portfolio/): JetBrains Mono, a compact evidence panel, and clear navigation. Almide retains its original teal/green palette in both light and dark modes.

| Path | What |
|---|---|
Expand Down Expand Up @@ -39,8 +39,12 @@ npx playwright install chromium
npm run verify
```

The dependency-free static tests check all six pages, metadata, local links and assets, preserved Chinese code examples, and theme controls with unavailable storage. Browser verification checks five widths (320, 390, 768, 1024 and 1440 px) in both themes, JavaScript-disabled navigation, missing assets, theme persistence, language switches, section anchors and Back/Forward. Screenshots are written to `test-results/`. Set `CHROMIUM_PATH` to use an existing Chromium executable.
The dependency-free static tests check all six pages, metadata, local links and assets, preserved Chinese code examples, and theme controls with unavailable storage. Browser verification checks eight widths (320, 360, 375, 390, 740, 768, 1024 and 1440 px) in both themes, JavaScript-disabled navigation, missing assets, theme persistence, language switches, section anchors and Back/Forward. Screenshots are written to `test-results/`. Set `CHROMIUM_PATH` to use an existing Chromium executable.

The Verify website workflow runs these checks on pull requests and pushes to `main`, and keeps screenshots as an artifact. GitHub Pages continues to publish the static root from `main`; this workflow does not change the deployment source.

When editing shared navigation or content, update English, Japanese and Simplified Chinese together. Language links keep the corresponding Home or Story route, and home-page section anchors stay the same across languages.

## Mobile reading

On phones, navigation stays visible at readable sizes and scrolls with the page, so a fixed header does not cover the article. Small screens use full-width primary links and single-column evidence rows. Diagrams remain horizontally scrollable instead of shrinking their labels, with localized swipe hints and keyboard focus. Stacked comparison rows repeat their column labels.
31 changes: 18 additions & 13 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
<link rel="preload" href="./fonts/jetbrains-mono.woff2" as="font" type="font/woff2" crossorigin>
<script>try { const theme = localStorage.getItem("almide-theme"); if (theme === "light" || theme === "dark") document.documentElement.dataset.theme = theme; } catch {}</script>
<script src="./site.js?v=20261111c" defer></script>
<link rel="stylesheet" href="style.css?v=20261111c">
<link rel="stylesheet" href="style.css?v=20261111d">
</head>
<body id="top">

Expand Down Expand Up @@ -137,7 +137,8 @@ <h2>The checker can have bugs too. So there are four.</h2>
<span class="n all">◆</span>
<div><h3>The whole picture</h3><p class="role">One source, two targets, and who checks what</p></div>
</header>
<div class="diagram" role="img" aria-label="Overview of both targets. Your code goes into the compiler, which is not trusted, and the compiler forks into two lanes. On the Wasm lane it produces Wasm bytes and evidence. Byteanchor ties the evidence to the bytes, and Buildgate stands between the bytes and the file on disk, which is written only if the evidence is accepted. On the Rust lane it produces Rust source and evidence. rustc, which is trusted, compiles the source into the native binary. Buildgate judges the Rust evidence in the project verification run rather than at your build, and there is no byte check yet, only a hash pinning the evidence to the source. Between the two lanes sits what they share: the rule, Proofcore, which checks that the rule is right, and Proofcast, which applies the rule to the evidence of both targets.">
<div class="diagram" role="img" aria-label="Overview of both targets. Your code goes into the compiler, which is not trusted, and the compiler forks into two lanes. On the Wasm lane it produces Wasm bytes and evidence. Byteanchor ties the evidence to the bytes, and Buildgate stands between the bytes and the file on disk, which is written only if the evidence is accepted. On the Rust lane it produces Rust source and evidence. rustc, which is trusted, compiles the source into the native binary. Buildgate judges the Rust evidence in the project verification run rather than at your build, and there is no byte check yet, only a hash pinning the evidence to the source. Between the two lanes sits what they share: the rule, Proofcore, which checks that the rule is right, and Proofcast, which applies the rule to the evidence of both targets." tabindex="0" aria-describedby="diagram-hint-1">
<p class="diagram-hint" id="diagram-hint-1">↔ Swipe or scroll horizontally to view the full diagram.</p>
<svg viewBox="0 0 990 728" xmlns="http://www.w3.org/2000/svg">
<rect class="lane" x="372" y="20" width="608" height="296" rx="16"/><rect class="lane" x="372" y="412" width="608" height="296" rx="16"/>
<text class="lanet" x="20" y="72">WASM TARGET</text><text class="lanes" x="20" y="92">checked at your build</text>
Expand Down Expand Up @@ -232,7 +233,8 @@ <h2>The checker can have bugs too. So there are four.</h2>
<div><h3>Proofcore</h3><p class="role">The Rocq proof kernel</p></div>
<span class="tag">runs in CI</span>
</header>
<div class="diagram" role="img" aria-label="Evidence from a build and the proven rule both go into Proofcore, where the Rocq kernel computes the verdict: accept means the property holds, reject means the evidence does not add up.">
<div class="diagram" role="img" aria-label="Evidence from a build and the proven rule both go into Proofcore, where the Rocq kernel computes the verdict: accept means the property holds, reject means the evidence does not add up." tabindex="0" aria-describedby="diagram-hint-2">
<p class="diagram-hint" id="diagram-hint-2">↔ Swipe or scroll horizontally to view the full diagram.</p>
<svg viewBox="0 0 960 262" xmlns="http://www.w3.org/2000/svg">
<path class="wire" d="M250 68 H305 Q315 68 315 78 V105 Q315 115 325 115 H373"/>
<path class="wire" d="M250 194 H305 Q315 194 315 184 V149 Q315 139 325 139 H373"/>
Expand Down Expand Up @@ -282,7 +284,8 @@ <h2>The checker can have bugs too. So there are four.</h2>
<div><h3>Proofcast</h3><p class="role">A checker generated from the proofs</p></div>
<span class="tag">runs in CI</span>
</header>
<div class="diagram" role="img" aria-label="The proven rule is extracted from Rocq into the Proofcast program, which judges the evidence from every program in the test corpus.">
<div class="diagram" role="img" aria-label="The proven rule is extracted from Rocq into the Proofcast program, which judges the evidence from every program in the test corpus." tabindex="0" aria-describedby="diagram-hint-3">
<p class="diagram-hint" id="diagram-hint-3">↔ Swipe or scroll horizontally to view the full diagram.</p>
<svg viewBox="0 0 960 262" xmlns="http://www.w3.org/2000/svg">
<path class="wire" d="M250 68 H305 Q315 68 315 78 V105 Q315 115 325 115 H373"/>
<path class="wire" d="M250 194 H305 Q315 194 315 184 V149 Q315 139 325 139 H373"/>
Expand Down Expand Up @@ -336,7 +339,8 @@ <h2>The checker can have bugs too. So there are four.</h2>
<div><h3>Buildgate</h3><p class="role">A second implementation, written separately in Rust</p></div>
<span class="tag here">runs on your machine</span>
</header>
<div class="diagram" role="img" aria-label="The compiler produces Wasm bytes and evidence. Buildgate, a separate program, reads both. If it accepts, the file is written. If it rejects, nothing is written.">
<div class="diagram" role="img" aria-label="The compiler produces Wasm bytes and evidence. Buildgate, a separate program, reads both. If it accepts, the file is written. If it rejects, nothing is written." tabindex="0" aria-describedby="diagram-hint-4">
<p class="diagram-hint" id="diagram-hint-4">↔ Swipe or scroll horizontally to view the full diagram.</p>
<svg viewBox="0 0 960 290" xmlns="http://www.w3.org/2000/svg">
<path class="wire" d="M152 150 H199"/>
<path class="wire" d="M338 138 H363 Q373 138 373 128 V86 Q373 76 383 76 H405"/>
Expand Down Expand Up @@ -407,7 +411,8 @@ <h2>The checker can have bugs too. So there are four.</h2>
<div><h3>Byteanchor</h3><p class="role">A tool that opens the finished file</p></div>
<span class="tag">runs in CI</span>
</header>
<div class="diagram" role="img" aria-label="Byteanchor decodes the finished Wasm file and compares each recorded event with the instruction at that place. A match passes. Evidence that points at nothing fails.">
<div class="diagram" role="img" aria-label="Byteanchor decodes the finished Wasm file and compares each recorded event with the instruction at that place. A match passes. Evidence that points at nothing fails." tabindex="0" aria-describedby="diagram-hint-5">
<p class="diagram-hint" id="diagram-hint-5">↔ Swipe or scroll horizontally to view the full diagram.</p>
<svg viewBox="0 0 960 262" xmlns="http://www.w3.org/2000/svg">
<path class="wire" d="M250 68 H305 Q315 68 315 78 V105 Q315 115 325 115 H373"/>
<path class="wire" d="M250 194 H305 Q315 194 315 184 V149 Q315 139 325 139 H373"/>
Expand Down Expand Up @@ -466,13 +471,13 @@ <h3 class="subhead">What the evidence is about</h3>
<div class="wide">
<div class="props">
<div class="prop head"><span>kind</span><span>the bug it stops</span><span>accepted only if</span></div>
<div class="prop"><code>ownership</code><div class="stops">Double free, leak, use after free</div><div class="iff">every object's reference count never faults and ends at zero</div></div>
<div class="prop"><code>bounds</code><div class="stops">Reading or writing past the end of a list</div><div class="iff">every access is preceded, on every path, by a check of that slot</div></div>
<div class="prop"><code>init</code><div class="stops">Reading memory that was never written</div><div class="iff">every construction writes every slot of its block, and none past it</div></div>
<div class="prop"><code>fields</code><div class="stops">Treating a value as the wrong shape</div><div class="iff">every record, tuple and variant store, and every field access, fits its layout</div></div>
<div class="prop"><code>call-modes</code><div class="stops">Caller and callee disagreeing about who owns an argument</div><div class="iff">every call site passes its arguments the way the callee's signature says</div></div>
<div class="prop"><code>names</code><div class="stops">A reference to something that doesn't exist</div><div class="iff">every name that is used is defined</div></div>
<div class="prop"><code>caps</code><div class="stops">Code touching files or the network without saying so</div><div class="iff">everything a function can reach, directly or through its calls, is in its declaration</div></div>
<div class="prop"><code>ownership</code><div class="stops"><span class="mobile-label">the bug it stops</span>Double free, leak, use after free</div><div class="iff"><span class="mobile-label">accepted only if</span>every object's reference count never faults and ends at zero</div></div>
<div class="prop"><code>bounds</code><div class="stops"><span class="mobile-label">the bug it stops</span>Reading or writing past the end of a list</div><div class="iff"><span class="mobile-label">accepted only if</span>every access is preceded, on every path, by a check of that slot</div></div>
<div class="prop"><code>init</code><div class="stops"><span class="mobile-label">the bug it stops</span>Reading memory that was never written</div><div class="iff"><span class="mobile-label">accepted only if</span>every construction writes every slot of its block, and none past it</div></div>
<div class="prop"><code>fields</code><div class="stops"><span class="mobile-label">the bug it stops</span>Treating a value as the wrong shape</div><div class="iff"><span class="mobile-label">accepted only if</span>every record, tuple and variant store, and every field access, fits its layout</div></div>
<div class="prop"><code>call-modes</code><div class="stops"><span class="mobile-label">the bug it stops</span>Caller and callee disagreeing about who owns an argument</div><div class="iff"><span class="mobile-label">accepted only if</span>every call site passes its arguments the way the callee's signature says</div></div>
<div class="prop"><code>names</code><div class="stops"><span class="mobile-label">the bug it stops</span>A reference to something that doesn't exist</div><div class="iff"><span class="mobile-label">accepted only if</span>every name that is used is defined</div></div>
<div class="prop"><code>caps</code><div class="stops"><span class="mobile-label">the bug it stops</span>Code touching files or the network without saying so</div><div class="iff"><span class="mobile-label">accepted only if</span>everything a function can reach, directly or through its calls, is in its declaration</div></div>
</div>
</div>
<div class="wrap">
Expand Down
Loading
Loading