KAIM / Privacy

This page describes the data behavior of the current portfolio build. It is intentionally minimal and should be updated if additional analytics, external forms or services are introduced.

01

Public portfolio

The public site sets no non-essential cookies or advertising trackers. Cloudflare provides cookieless performance analytics. Your theme preference is stored locally using localStorage.

02

Contact

The contact form does not submit data to this website. It prepares a mailto: message and opens your local email client. Any message you send is then handled by your email provider and the recipient's email service.

03

Studio

The private /studio area is designed to sit behind Cloudflare Access in production. Cloudflare may use strictly necessary authentication cookies for that protected area. Local development bypasses Access and writes content directly to the project filesystem.

04

Questions

For privacy questions or requests concerning this site, use the contact address.

Implementation / 01

The public surface stays intentionally static-first. Runtime appears only where it earns its cost: Kaimtosh, restrained motion, spatial Three.js experiences and GPT Nano inference running locally through WebAssembly.

AstroStatic-first · Collections · SEO

Most of the portfolio ships as HTML/CSS. Notes are Markdown-backed Astro content collections.

SolidJSFine-grained islands

Used only where stateful interaction earns its runtime: Kaimtosh, the interactive GPT Nano microscope and other isolated UI islands.

Three.jsSpatial interfaces

The main 3D computer moves through welcome → hero → Kaimtosh, while a separate GPT Nano scene spatially maps forward-pass stages and their real tensors.

HTML-in-CanvasProgressive enhancement

Where Chromium exposes the experimental API, the retro DOM is painted through the CRT canvas; normal DOM remains the fallback.

LenisLow-amplitude motion layer

Smooth scrolling is paired with restrained per-element inertia rather than aggressive scroll hijacking.

Bun + CloudflareBuild · Pages · Access

Bun drives local tooling. Cloudflare Pages serves the site, while Zero Trust is reserved for the protected Studio surface.

KAIM StudioGit-backed CMS

Local development writes Markdown directly. Production commits through Pages Functions to GitHub, with no separate CMS database.

WebAssemblyLocal inference · Real tensors

A native WASM module runs the GPT Nano forward pass locally in the browser. The interface reads intermediate tensors directly from WASM memory and exposes 42 observable stages. No external model API is involved.

Architecture / 02

How this build moves traffic, state and content.

The public surface stays static-first, UI state lives locally, and the private publishing surface moves through Access and a Git-backed workflow instead of a separate CMS database.

01 PUBLIC REQUEST Browser

Renders HTML/CSS, light interaction and client islands.

  • client render
  • light JS
  • no tracker
02 STATIC HTML Cloudflare Pages

The public portfolio ships static-first from the edge cache.

  • edge cached
  • asset pipeline
  • serverless
03 CONTACT Mail client

The contact surface opens mailto: instead of writing into a public server endpoint.

  • mailto
  • local app
  • no endpoint
04 LOCAL STATE Theme / localStorage

Only local theme, style and font preferences.

  • local only
  • no cookie
  • UI prefs
05 PROTECTED ROUTE Cloudflare Access

Protects the private /studio surface outside the public route.

  • identity gate
  • private route
  • zero trust
06 PUBLISH BRIDGE Pages Functions

Handles save and publish without a separate application backend.

  • save / publish
  • validated writes
  • no monolith
07 PRIVATE SURFACE Studio workspace

The private layer for content and settings authoring, activated only where it adds value.

  • authoring
  • controlled state
  • protected UI
08 VERSIONED CONTENT GitHub repository

Markdown and configuration stay versioned with the project.

  • git-backed
  • no DB
  • audit trail