---
title: "Personal AI Operating Site"
type: project
description: "A public-safe personal knowledge product that serves human readers and AI agents from the same typed content source."
summary: "The site you are reading: one public-safe typed content source projected into human-readable pages and AI-readable derivatives including llms entry points, Markdown mirrors, a typed content graph, and OKF v0.2. Career surfaces use progressive disclosure while the publishing boundary keeps private evidence outside public outputs."
ai_summary: "Personal knowledge product built from one public-safe typed content source with separate human and AI reading paths, deterministic Markdown/llms/OKF derivatives, a richer typed relationship graph, Career progressive disclosure, and an enforced public/private publishing boundary."
status: public
visibility: public
language: en
topics: [knowledge-product, ai-readable]
tags: [experiment, astro, okf, publishing-boundary, knowledge-architecture]
audience: [builders, product-managers]
publishedAt: 2026-07-04
updatedAt: 2026-08-17
featured: false
related: [labs/personal-ai-operating-site-one-day-prototype, articles/why-im-building-a-personal-ai-operating-site]
sourceStatus: original
sourceSensitivity: public
projectStatus: active
role: "builder"
artifactType: website
artifactUrl: "https://personal-ai-ops.vercel.app/wbeen/"
repoUrl: null
publicProof: ["human-readable + AI-readable publishing", "Markdown/llms/OKF derivatives", "enforced public/private boundary"]
canonicalUrl: "https://personal-ai-ops.vercel.app/wbeen/projects/personal-ai-operating-site"
---

## What it solves

Public essays, prompts, templates, experiments, projects, skills, workflows, and
career evidence become harder to use when they live as unrelated portfolio
fragments. The Personal AI Operating Site treats them as one **public-safe
knowledge product** with different interfaces for people and AI agents.

## Two reading paths, one curated source

Human-facing routes emphasize readable pages, navigation, related knowledge,
projects, and progressive disclosure.

AI-facing derivatives provide curated entry points and machine-readable forms,
including:

- `llms.txt` and `llms-full.txt`
- Markdown mirrors
- a typed content graph
- an Open Knowledge Format (OKF) v0.2 projection

These are derivatives of the same approved public content rather than a second
independent knowledge base.

## Publishing boundary

Public readability does not mean private material is mirrored wholesale. The
site's publishing checks keep draft, private-source, and private-only material
out of public derivatives and reuse the same public-safety decision across the
human and AI layers.

Career information follows the same principle: concise Career and Resume views
can lead to deeper Role and Professional Case evidence without turning the
entire site into a generic portfolio or duplicating independent projects into a
second taxonomy.

## What this demonstrates

As a Builder project, the work is less about a single page and more about the
system around it:

- information architecture and typed content
- human-versus-agent reading paths
- public/private publishing rules
- deterministic machine-readable derivatives
- connected knowledge through explicit and derived relationships
- multilingual Career/document presentation from approved public data

The implementation can keep evolving; this project entry records the durable
product architecture rather than a fixed historical route or version inventory.

## Public artifact

- Live site: https://personal-ai-ops.vercel.app/wbeen/

---

Canonical page: https://personal-ai-ops.vercel.app/wbeen/projects/personal-ai-operating-site
This is the AI-readable Markdown mirror. Public, curated content only.