Skip to content

site: the 1bit.MONSTER template, a cleaned-up blog, three new posts - #36

Merged
bong-water-water-bong merged 2 commits into
mainfrom
site-blog
Sep 24, 2026
Merged

bong-water-water-bong merged 2 commits into
mainfrom
site-blog

Conversation

@bong-water-water-bong

@bong-water-water-bong bong-water-water-bong commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

The site takes on the 1bit.MONSTER site's template, and the blog is cleaned up with new posts on the move to 1bit engine.

Template (from the old site's own CSS, header and footer): the light modern-minimal tokens and their dark mode, the animated relay mark, the top bar with the light / auto / dark switch, the centered hero with the latest post, the site cards, the blog log, the article column, the three-part footer. Docs get a sidebar layout in the same tokens. Pages: home, overview.html (the README, "Meet the engine"), docs.html (docs index), each doc, blog.html, each post, feed.xml, 404.html.

Blog, new posts (every number from docs/, the wiki and the merged PRs):

Blog, cleanup: blog/archive.tsv lists the 15 old posts worth keeping, linked to the archived old site under "From the 1bit.MONSTER years". Left out: 115 machine-generated "new architecture" model posts, 7 posts flagged as corrected, and posts about the old monorepo's other products (vendored Lemonade releases, JARVIS, the coding agent, the agent fleet, FLM).

Also: copyright.py covers *.js and *.svg and exempts images; pages.yml rebuilds on blog/ changes.

🤖 Generated with Claude Code

Posts are blog/YYYY-MM-DD-<slug>.md. tools/site.py renders each as blog-<slug>.html with
its date under the title and newer/older links, lists them newest first on blog.html, and
writes feed.xml (Atom, full content). The top bar gets a Blog link and every page
advertises the feed. First post: 1bit.MONSTER is now 1bit engine.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The site now uses the 1bit.MONSTER site's template: its tokens, relay mark, top bar with
the light/auto/dark switch, centered hero, site cards, blog log, article column and
footer, with a docs layout in the same tokens. tools/site.py builds a home page (hero,
latest post, a card per page), overview.html from the README, docs.html (the docs
index), the docs with a grouped sidebar, the blog and its Atom feed, and the 404.

The blog: three posts on the move from 1bit.MONSTER to 1bit engine (the new direction,
the first week's milestones, HRX prefill with Vulkan decode on one KV cache), with every
number taken from the docs, the wiki and the merged PRs. blog/archive.tsv lists the 15
old posts worth keeping, linked to the archived old site; the 115 machine-generated
model posts, the posts flagged as corrected, and the ones about the old monorepo's
products are left out. Posts may carry tags and link to each other.

theme.js and the favicon come from the old site; copyright.py learns *.js and *.svg
and exempts images, and pages.yml rebuilds on blog/ changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bong-water-water-bong bong-water-water-bong changed the title site: blog, Atom feed, first post site: the 1bit.MONSTER template, a cleaned-up blog, three new posts Sep 24, 2026
@bong-water-water-bong
bong-water-water-bong merged commit c528878 into main Sep 24, 2026
3 checks passed
@bong-water-water-bong
bong-water-water-bong deleted the site-blog branch September 24, 2026 10:39
bong-water-water-bong added a commit that referenced this pull request Sep 29, 2026
…#232)

* Pin llama.cpp c9283cf: HRX ZAYA decode fusions (62 -> ~90 tok/s)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* registry + docs/hrx: llama.cpp (hrx) at c9283cf, ZAYA decode fusions

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: bong-water-water-bong <bong-water-water-bong@1bit.gg>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
bong-water-water-bong added a commit that referenced this pull request Oct 1, 2026
…260)

Wrapped lines in docs/hrx.md starting with '#36', '#39', '#40' became
<h1> headings (python-markdown needs no space after '#'), so hrx.html
had 4 h1s and the daily SEO check flagged it. Prefix them with 'PR'.
tools/site.py now fails the build when a page has other than one h1.

Co-authored-by: bong-water-water-bong <bong-water-water-bong@1bit.gg>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
bong-water-water-bong added a commit that referenced this pull request Oct 25, 2026
Private HIP add-on pin 744bd713d968 -> 17a882640fa88: NVFP4 + Q2_0 on every family (#33), 2..16-token verify kernels (#32) and the GEAK WMMA rewrite (#37), DFlash2 selector (#34), ZAYA lm_head + one-token kernels (#35), Bonsai ternary verify + PQ2_0 prefill (#36), IQ2_S expert prefill + decode (#38/#39). hw-gate kat goldens (7 models x 9 cases) and KLD bases re-recorded at llama.cpp e7e5cd08 + this pin; check-back 13/13 PASS on the gate box.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
bong-water-water-bong pushed a commit that referenced this pull request Nov 5, 2026
… sha #1126 pins

The row was written against the fork tip before `bump-lemonade` ran. #1126 pins f44ff953bcd8 (which is
e58c9f111 + #36, the LayaClientTest ctest fix), so name that sha and say where it comes from, rather than
a tip that moves under the reader.
bong-water-water-bong added a commit that referenced this pull request Nov 5, 2026
… port, not a candidate (#1123)

* docs(releases): the Lemonade pin is the GA port, and the catalog counts are 23 + 4 (not 22 + 3)

Two rows in this file had drifted from what the fork actually ships:

* **The pin.** `Lemonade (fork) | 27abcc24da99` names the *v2026.43 candidate*, two releases behind
  what the engine builds. It is now the fork's `main` tip, `e58c9f111`, with the standing caveat that
  `bump-lemonade` re-pins the submodule to whatever `main` is at cut time, so the row is re-read from
  `git ls-tree` then rather than trusted.
* **The catalog.** "22 HRX entries ... and 3 NPU entries" is the pre-flint, pre-35B count. The fork's
  `server_models.json` carries **27 onebit rows: 23 non-NPU + 4 NPU** (verified against the file).

The paragraph also gains what this pin changed, because a release note that omits it would not describe
the shipped behaviour:

* the port target is now **`v2026.45.3` (GA, fork #29)**, so the suite evidence for this pin is a run
  against the *ported* `lemond` — `Ran 31 tests in 110.6s`, `OK (skipped=2)`, measured at load 28.5
  with two foreign HRX clients resident;
* **an NPU model switch evicts the previous NPU model before the new one starts** (fork #34, the
  fleet's NPU-exclusivity decision: the array runs one hardware context at a time);
* a **refused** context is queued on a budget instead of being declared a dead array
  (engine #1100, `1bit serve --load-queue-ms`).

Counts verified from the fork: 27 onebit rows, 23 with no `onebit_backend: npu` and 4 with it
(`Qwen3-0.6B/1.7B/4B-NPU-1bit`, `Qwen3.6-35B-A3B-NPU-1bit`). `tools/copyright.py --check` rc 0.

* docs(releases): the Lemonade pin row follows the bump — f44ff953, the sha #1126 pins

The row was written against the fork tip before `bump-lemonade` ran. #1126 pins f44ff953bcd8 (which is
e58c9f111 + #36, the LayaClientTest ctest fix), so name that sha and say where it comes from, rather than
a tip that moves under the reader.

* docs(lemonade): the HRX checklist row is the ported lemond, not the c22 package

The row is what a future pin is verified against, and it named `lemonade-onebit-rc-2026-11-03-c22` — a
package built before the v2026.45.3 port. Since the port is what ships now, the evidence has to be a run of
the ported server: 31/31, 2 skipped, exit 0, `Ran 31 tests in 110.605s`, against `lemond
2026.47.0~1759.f44ff953`, measured at load 28.5 with two foreign HRX clients resident. The row also said
"29 / 29 run" against a 31-test suite, which reads as two tests never counted; it is 31.

---------

Co-authored-by: agent <agent@local>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant