RISE and AI models: since RISE #294 the RISE server calls no model. An AI reading request runs on the reader’s own connection: hosted Jev through the reader’s OpenRouter account, or a pinned Kev-4B on the reader’s machine (
/kev/on the site). local Kev did not meet RISE’s bar in internal checks on RISE’s evaluations (RISEdocs/product/tasks/SCR-004.json), and there is no production Kev deployment, by design. Once the reader connects, RISE’s visual direction sends sections of the reading text to that connection.
Company and portfolio site for syberlabs.io.
Site v3 "Observatory" (October 2026) adds a shared 3D layer on top of the kit: src/site/field.js is a raw WebGL2 scene fixed behind every page (a domain-warped nebula shader and a 3D Pickover attractor point cloud that leans toward the pointer and morphs with scroll), src/site/motion.js holds the reveal, 3D tilt, magnetic-button, scroll-progress and scroll-spy behaviours, and src/site/nav.js drives the Atlas, the full-screen site map behind the header's Menu button (also / on the keyboard). The static pages load all of it from /syberlabs.js, built unhashed next to /syberlabs.css; the homepage bundle calls the same modules. The hero’s Living Lab (src/living-lab/) plays up to 180 Unicode graphemes as a short, deterministic typographic scene, with three CSS landscape presets, pause/replay and pace controls. It sends and stores no input, requires no model or WebGL, and becomes a full-text still for reduced motion or low-power devices. It links to a full RISE reading without transferring the sentence. Run node --test scripts/living-lab.test.mjs for the pure renderer tests. Project pages get breadcrumbs, a 3D sigil spun over the flat one, and previous/next cards; the footer carries the whole map so every page is reachable without JavaScript. The field is progressive enhancement: software WebGL and prefers-reduced-motion each get a still, and no copy ever depends on it. node scripts/shoot.mjs <dir> screenshots every page at desktop and phone widths with the field forced on (headless Chromium, SwiftShader). Every page carries Open Graph and Twitter card tags pointing at a committed 1200×630 card in og/; node scripts/og-cards.mjs regenerates the cards (same Chromium, with each project's sigil in its accent) after a headline, intro or status changes.
Built with React and Vite on SyberLabs Design System v2 "Atlas": ink and vellum, the Orb in the homepage hero (src/site/orb.js: a sphere of fractal flame and spectral attractor whose dots spell what you type), and a seeded de Jong sigil for each project. The kit lives in kit/v2/ (syber-atlas.css tokens and components, syber-atmosphere.js plate engine, syber-sigil.js sigils; see kit/v2/README.md) and is published at syberlabs.io/kit/v2/, which is its canonical public home; product apps vendor a copy. src/syberlabs.css is the site layer on top of the kit. The homepage imports both, and the build emits them together at /syberlabs.css for the static pages. node scripts/site-chrome.mjs rewrites the shared header and footer into the static pages; CI runs it with --check, so a page whose chrome has drifted fails the build. Project data and navigation live in projects/site-data.js, shared by the homepage and the project pages. Run pnpm install and pnpm build:site to generate the full Cloudflare Pages output in dist/. The public RISE demo is copied into dist/rise-demo/ by the deployment workflow, and omni-demo/ holds the OmniOS recording (the acceptance test's "morning" journey against a local build with fixture data; see the caption on the OmniOS page).
The System maps components (src/system-maps/) draw Relay, FLYSPACE (formerly OmniOS), RISE, Barn, OSAHR and SyberRuntime from their own repositories. The RISE, FLYSPACE, Relay and OSAHR maps are mounted on their project pages as an Inspect section: src/system-map-embed.js is built unhashed as /system-map.js, a small loader that imports src/system-map-mount.jsx (React, the maps and their linked stylesheet) when the section nears the viewport and renders one map into [data-system-map]. The homepage renders none of them. Recorded traces in src/*-trace.json are regenerated by the scripts in scripts/; the RISE map is rule-based from src/core/decision/; docs/SYSTEM_MAPS.md records the evidence, commits and grades for every map.
Five projects are published: RISE, FLYSPACE (formerly OmniOS, at /projects/flyspace/; /projects/omnios/ redirects), SyberWork, Relay and OSAHR. The homepage features three of them: RISE, FLYSPACE and SyberWork. Each project page is rendered from projects/site-data.js through projects/project-template.js: a live bar when the thing runs somewhere (RISE at rise.syberlabs.io, the OmniOS preview at omni.syberlabs.io), an optional demo film, then Why, Use, Design, Evidence and Facts. The RISE page keeps its hand-authored hero and paced passage, and scripts/prerender.mjs fills its <!-- rise:sections --> marker with the same sections at build time. Every evidence row carries the state it has reached (implemented, tested, measured, deployed, not yet) and the page names the commit it reflects. Commons was removed on 2026-10-05; its old addresses redirect to the homepage (_redirects). OmniOS is deployed from its own repository (see its DEPLOYMENT.md); the earlier manual deploy workflow in this repository was removed with it.
The reader-owned AI status lives in kev/ and is published at /kev/. The prior Jev evaluation and integration case study remains at /jev/ as historical evidence; its results must not be attributed to Kev.
The research index at research/ (published at /research/) carries one card per research artifact, on this site and in the SyberLabs/papers, cross-platform and OSAHR_Cell repositories, with its claim, evidence state, limits, date and source; the Reflects line at its foot names the commits it was checked against, so update it when they move.
The Sybershoke research note lives at research/sybershoke/. Revision 2 reports the Week 0 harness against its reference simulator (that repository is still unpublished), the public SyberLabs/sybershoke workspace, and its first real system, the RISE Worker source run against recorded Jev answers; every number on it comes from that project's committed reports (REPORT.md, docs/REDTEAM.md, docs/ADAPTER-RISE.md), so update the note when they change.
The GrokCell Execution report lives at research/jev-execution/. It summarizes the durable offline prototype and its evidence limits; preserve the distinction between observed results and planned live integration.