# My projects

The portfolio behind projects.navonsimon.com: every project, its story and how to reach it, with a guide on the front page that answers questions from the briefs.

**Status:** Live · Projects · 2026

- **Local checkout:** `/Users/simon/Developer/my-projects` (branch `main`, last commit cfffaec, 2026-11-08 — pil-dataflow: document the Grafana edition)
- **Uncommitted changes:** 209 file(s) at brief generation time
- **Open portfolio:** https://projects.navonsimon.com/
- **Ask the agent:** https://projects.navonsimon.com/#ask
- **Where it runs:** namespace my-projects · NodePort 30092 · ubuntu01 edge + Cloudflare tunnel

## Stack

Single-file HTML, CSS/JS, Kubernetes ConfigMap

## Start here

- `site/index.html` — the whole gallery; projects are the P array near the bottom
- `site/screen-pointer.html` — Screen Pointer case study and guide
- `site/seta.html` — SETA documentation page
- `site/context/` — generated agent briefs, one Markdown file per project
- `context/stack.json` — the tool inventory behind /stack: harnesses, MCP servers, CLIs, data, servers
- `tools/build_stack.py` — renders site/stack.html, stack.json and stack.md from context/stack.json
- `context/catalogue.json` — project catalogue, mirrored from the build ledger
- `context/enrichment.json` — hand-written repo paths, commands, deploy facts
- `tools/build_context.py` — builds briefs, llms.txt and the JSON index
- `deploy/deploy.sh` — ConfigMaps + rollout to the cluster
- `site/outcomes.html` — selected public case studies from Remodeling; never private journal fields
- `tools/deploy_workspace_site.py` — scoped publication preserving other agents’ live site changes

## Commands

- **Build briefs:** `python3 tools/build_context.py`
- **Find a brief:** `python3 tools/brief.py screen-pointer`
- **Build the stack page:** `python3 tools/build_stack.py`
- **Deploy:** `./deploy/deploy.sh`
- **Deploy the site agent backend:** `./agent/deploy.sh`
- **Deploy workspace public surface only:** `python3 tools/deploy_workspace_site.py`

## Deploy and where it runs

- Static ConfigMaps applied to namespace my-projects, NodePort 30092 on ubuntu03.
- Edge nginx on ubuntu01 (/srv/edge/nginx/conf.d/projects.conf) behind a Cloudflare tunnel serves projects.navonsimon.com.
- deploy.sh also mounts the generated site/context directory as its own ConfigMap.

## Current state

Live. Briefs are generated from context/enrichment.json; every project page is a catalogue entry even when no local checkout exists. /stack lists the harnesses, MCP servers, CLIs, databases and servers from context/stack.json. The site agent (a guide that answers from the briefs) is on the front page as the "Ask the agent" panel in the header, and full page at /agent. Since 2026-10-31 it works as first-line service: it leads with the answer, closes every answer with a next step (project page, live URL, README or LinkedIn), routes work enquiries, quotes, timelines and feedback to Simon on LinkedIn instead of guessing, replies in the visitor's language, and only links pages it was given. Backend agent/ in namespace my-projects, NodePort 30104, OpenRouter, 5 minutes and 50,000 tokens per visitor after a drag puzzle (chips queue the question and send it once unlocked). Since October 31, the homepage links to the private Now workspace in Remodeling and /outcomes shows separately authored public case studies. /remodeling#workspace documents the workflow. Tasks, owners and results join existing project slugs; private work never enters the public outcomes projection.

## Watch out

- Projects live in the P array inside site/index.html, not in a database; keep the catalogue in sync when editing the gallery.
- ConfigMap keys cannot contain slashes, so site/context is mounted as a separate ConfigMap (name context) under /context.
- No origin remote is configured for this repo; commit locally or add the GitHub remote before pushing.
- The front-page panel in site/index.html and site/agent.html are two clients of agent/server.mjs; a protocol change there must keep both working.
- The site agent re-reads /knowledge (the context ConfigMap) every 10 minutes; before 2026-10-31 it loaded briefs only at startup, so new projects stayed unknown until a restart.
- Security headers live in deploy/security-headers.conf and are included at server level and again in every location that sets its own add_header; nginx drops inherited add_header in those locations (that is how the JSON proxies once lost their CSP).
- Chat WebSocket upgrades require the exact site Origin, and model output rendering only allows http(s) links or a single-slash site path, so [x](//evil.com) stays text in both clients.

## Secrets — locations only, never print values

- agent/.env (gitignored): OPENROUTER_API_KEY, TURNSTILE_SECRET, TURNSTILE_SITE_KEY for the site agent, applied as Secret portfolio-agent-env by agent/deploy.sh.

## Tags

Portfolio, Ledger, Site agent

---

Brief generated 2026-11-08 from `~/Developer/my-projects/context/`. Canonical URL: https://projects.navonsimon.com/context/my-projects.md
