Live site · Projects · Writing · GitHub · 简体中文

loraSys is Lora's personal engineering notebook: a static, editorial site for building in public across AI agents, full-stack products, developer tools, and Web3 experiments.

The site is intentionally content-first and build-time driven. Articles live beside structured project data; GitHub project metadata and contribution activity are snapshotted during the build; the result is published as a fast static site on GitHub Pages.

Build systems that learn.

New project: Zhihu Threads

Zhihu Threads turns selected Zhihu excerpts into a learning thread with follow-up questions and self-tests. The user chooses the sources. Missing evidence remains explicit.

Read the project notes.

These are editorial illustrations, not screenshots or live evaluation results. The four localized WebP assets reuse this site's original Lora and Mochi character art. The renderer and typography stay separate from the interactive page.

What to look at first

Start here	What it contains
Projects	Public repositories and clearly attributed external contributions, with curated posters, status, technologies, stars, and source/live links.
Writing	Technical essays on agent infrastructure, visual evidence, model APIs, and shipping experiments.
Lab	Five project-native explainers for the systems behind the work.
Notes	Short observations on agents, frontend systems, Web3, and research.

Selected work

Glassbox Agent Harness An observability and evaluation lab for AI agents: actions become inspectable traces, contexts stay reproducible, and iteration has evidence.	Free Vision Skill A low-token visual evidence compiler that turns images into compact packets for text-only coding agents.
nano-vLLM Interactive Guide Thirteen interactive experiments and a Chinese tutorial for understanding the moving parts of an LLM inference engine.	TrustOps An auditable commitment layer for growing B2B SaaS teams, connecting policies, controls, reviews, and accountable decisions.

How the site is assembled

The model

• Content: Markdown articles, short notes, profile data, project records, and local media.
• Composition: Astro with the Pure theme as the visual and interaction foundation.
• Build-time snapshots: GitHub REST/GraphQL data refreshes project metadata, posters, and contribution activity before publishing.
• Delivery: Static dist/ output, Pagefind search, RSS, sitemap, and GitHub Pages at /loraSys.

The browser does not need a portfolio API or a database. A failed refresh keeps the last known local snapshot, so the site can still build and deploy.

Run it locally

Requirements: Bun 1.3.5 and Git.

git clone https://github.com/lora-sys/loraSys.git
cd loraSys
bun install --frozen-lockfile
bun dev

Useful checks:

bun run check       # Astro type/content diagnostics
bun run build       # static build + base-path + release audit
bun preview         # preview the production output

The GitHub Actions workflow additionally refreshes the cached GitHub project and contribution snapshots before building:

bun scripts/fetch-contributions.mjs
bun scripts/fetch-github-projects.mjs

Repository map

src/content/              published essays
src/data/                 profile, notes, projects, snapshots
src/pages/                blog, projects, lab, notes, now, talks, links
src/components/           personal sections layered on Pure
packages/pure/             pinned Astro Theme Pure source
assets/readme/             README-native visual system
.github/workflows/        GitHub Pages deployment and data refresh

Design decisions

• Pure remains the primary UI system; personal details are layered into its editorial structure.
• Projects are curated by evidence, not by pretending every public repository is equally important.
• Posters are local WebP assets sourced from README screenshots or GitHub previews, so the portfolio remains stable offline.
• Anime, favorites, contributions, and friend links are static content with small accessible interactions; there is no runtime database.
• The old Svelte/Wayfinder surface is archived, not kept as a compatibility layer.

Links

• Live website
• Contact Lora
• RSS feed
• GitHub profile

License

The repository and the pinned Pure theme foundation are distributed under Apache-2.0. Individual articles, project screenshots, logos, and third-party media may carry their own attribution or license terms.

Sync and ownership contract

The public directory keeps three surfaces distinct: lora-sys is personal work, ACAMLab is lab work, and External contains only manually allowlisted open-source contributions. GitHub snapshots are refreshed in Actions before the verified site is built; the quality gate records snapshot dates, project ownership breakdown, contribution allowlist coverage, pull requests, and warnings in the Actions summary.

Review screenshots and local audit notes are intentionally kept outside commits. A feature branch must pass bun run check, bun run build, and desktop plus 390×844 browser review before it can be merged into main.