Seb Builds

Seb Builds is the public build surface behind sebmer.com. It turns active work into project pages, build logs, notes, metadata routes, and agent-readable context files.

The site exists because private work logs are not enough. Projects move quickly, and without a public memory layer the story disappears into Git commits, local notes, agent transcripts, and deployment chores. Seb Builds gives that work a cleaner public shape: project pages for the long-lived context, notes for dated progress, and metadata surfaces for people and agents that want to inspect what is going on.

What the site contains

• Project pages for active products, experiments, and infrastructure.
• Build logs that capture concrete dated changes without leaking private details.
• Static routes for notes, projects, RSS, sitemap, robots, llms.txt, and llms-full.txt.
• A public About surface and profile JSON for Sebastian Mertens.
• A small CLI foundation so the same public content can be inspected from developer workflows.
• A GitHub Pages deployment path for sebmer.com.

Recent work

The June update refreshed the timeline from the last May update through the latest public build evidence. It added new project pages for Fluid Push-to-Talk, Make Skills, Project APEX, and DEVLO AIOS. It also expanded the active pages for Von Thomas Next, Lovalingo, Restaurant Thomas, and Elson.ai so the site explains what was built in simple words.

The update focuses on the projects included in this public portfolio pass. The public site should show the broader build story while keeping excluded work out of the page.

Why it matters

A builder site should not only show finished launches. It should also preserve the middle of the build: what changed, why it matters, and what value the product gives to users. That is especially important when many projects are active at the same time.

Seb Builds gives each project a home. A build log can say what happened on a date, but the project page explains the full context in plain language: what the product does, who it helps, why it matters, and what stays private.

Current direction

The current direction is quality over shorthand. Project pages should not read like commit messages. They should be clear enough for a normal visitor to understand the product and useful enough for an agent to recover context later.

Public boundary

Seb Builds is public. The content is written to explain the product value without publishing secrets, private local paths, customer data, credentials, or internal operating details.