own-proxy decision, terraform provisioner, system diagram, gateway SSE notes, server-budget comment and roadmap 0.4.0 now use Caddy with ACME-managed TLS instead of nginx plus certbot
Rebuilt plan - Terraform-provisioned server, self-run Caddy proxy, and the original release track on top. Each release is a few days of work and ends in something that runs.
roadmap
planning
revised
by
at
claude-code/claude-opus-5-5
2026-10-14T00:00:00Z
Overview
Phase
Releases
Outcome
1: Ship the CV
0.1.0 - 1.0.0
Public interactive CV on the apex domain
2: Depth
1.1.0 - 1.7.0
WebMCP, k6 release gate, dev terminal, in-browser language model
3: Pressure and from scratch
1.8.0 - 1.13.0
Interactive load test with HPA, chat model, own autograd engine
Release
Name
Days
0.1.0
Chapter service
1-2
0.2.0
Terraform server
2-3
0.3.0
Chapters on k3s
2
0.4.0
Reverse proxy and DNS
1-2
0.5.0
Pipeline
2
0.6.0
Live states
2-3
0.7.0
Knockdown
1-2
0.8.0
First screen
2
0.9.0
Life map and story cards
3-4
1.0.0
Own tracker, real content, launch
3-4
1.1.0
WebMCP
2
1.2.0
k6 release gate
2
1.3.0
Dev terminal
2
1.4.0
LM: data and tokenizer
2-3
1.5.0
LM: model and training
3
1.6.0
LM: browser inference
3
1.7.0
LM: visuals
2-3
1.8.0
Interactive k6
3
1.9.0
HPA demo
2-3
1.10.0
LM: bigger base model
2-3
1.11.0
LM: chat fine-tune
3
1.12.0
Own autograd engine
3
1.13.0
Train with own engine
2-3
Each release is cut by release-please from feat: commits. A release is done
when its "done when" check passes on the real cluster, not locally.
Everything runs on a 2 vCPU, 4 GB server shared with Gitea. Every release
stays inside the memory budget.
Phase 1: Ship the CV
0.1.0 Chapter service
Go module with cmd/chapter: /healthz, /ready, /fall, behavior from MODE. See chapter service.
Dockerfile, distroless or scratch base.
One go test that checks /ready per MODE.
release-please config, manifest and Gitea workflow, so this release is the first one it cuts.
Done when:docker run -e MODE=not-ready answers 503 on /ready, and POST /fall ends the container with exit code 1.
Learn: Go net/http, container basics, Conventional Commits.
0.2.0 Terraform server
Terraform module that rebuilds server0 from nothing: packages, 2 GB swap file, k3s installed with traefik and servicelb disabled, kubelet reservations, and the imagePullSecret for the Gitea registry. See terraform provisioning.
Terraform also creates namespace cv with the ResourceQuota (384Mi) and LimitRange, and the DNS A record for the apex domain.
State file stays local; plan output is reviewed before every apply.
Done when:terraform destroy then terraform apply on a blank server0 leaves k3s running, swap active, namespace cv with its quota on a fresh server. No hand steps.
Learn: Terraform (providers, provisioners, plan/apply, state), cloud-init/SSH provisioning, why infra as code beats hand setup.
0.3.0 Chapters on k3s
Four placeholder chapters applied with kubectl apply -k deploy/: one Job (complete), one each of healthy, not-ready, crash.
Services with publishNotReadyAddresses: true, resource limits, pod label cv.noelsabia.dev/chapter.
Done when:kubectl get pods -n cv shows Completed, Running 1/1, Running 0/1 and CrashLoopBackOff, and a /fall from a debug pod raises restartCount.
Learn: Deployments, Jobs, probes, Services, kustomize, resource limits and quotas.
0.4.0 Reverse proxy and DNS
Caddy (installed and templated by the Terraform module from 0.2.0) is the only public entry: HTTPS with certificates it gets and renews itself via ACME. Until the gateway exists it forwards to a placeholder.
Router port-forward, static IP or DDNS, per own proxy.
Done when: the apex domain loads over HTTPS from outside the home network, certificate auto-renews, and a terraform destroy on the network config is recovered by re-applying Terraform.
Learn: reverse proxies, TLS/ACME, DNS records, port-forwarding.
0.5.0 Pipeline
Gitea workflow: go test, snyk test, build and push images tagged with the git SHA, kubectl apply -k.
Runner kubeconfig limited to namespace cv. Runner capacity 1, so builds never run in parallel.
Done when: a push to main deploys a new image without touching the server by hand.
Learn: Gitea Actions, RBAC for CI, Snyk.
0.6.0 Live states
cmd/gateway: polls pods and events every 2 seconds, streams changes on GET /api/events with a 30-second ping.
ServiceAccount with read-only Role. Caddy route now points at the gateway for real.
A bare HTML page that prints the stream.
Done when: the public URL shows a chapter going not-ready and back after kubectl delete pod.
Learn: client-go, in-cluster auth, SSE, serving through a self-run proxy.
0.7.0 Knockdown
POST /api/fall/{chapter}: allowlist, 30-second per-chapter cooldown, global rate.Limiter.
Recovery time from the Ready condition's lastTransitionTime.
"fell" and "recovered" events with seconds in the stream.
NetworkPolicy: only the gateway can reach chapter /fall.
One test for the cooldown and limiter logic.
Done when: a POST knocks a chapter over, a second POST within 30 seconds gets 429, and the stream shows the recovery seconds.
Learn: rate limiting, NetworkPolicy, measuring with Kubernetes conditions.
0.8.0 First screen
Nuxt project, nuxt generate with NODE_OPTIONS=--max-old-space-size=512, multi-stage Dockerfile that embeds the output in the gateway image.
Layer 0: name, role, contact, PDF CV download. Navy #1A3D64 and white.
Done when: the page loads and the PDF downloads with JavaScript disabled.
Life map (default: vertical timeline) with plain-word states from the stream and a "Push this chapter" button.
Story card on every fall with the measured seconds. Lesson card for CrashLoopBackOff chapters. Falls back to the data file with a "live cluster offline" note when the stream fails.
Dev view: the raw stream in a <pre>.
Done when: a non-technical person can push a chapter, say what happened, and two browsers see each other's knockdowns live.
Gateway middleware writing daily totals to SQLite (modernc.org/sqlite) on a local-path volume. See decision. Count page views, PDF downloads and falls per chapter. No IPs, no cookies. Deployment strategy Recreate.
Final chapter list, one manifest per chapter, story text, final PDF CV.
Done when: someone from HR finds the PDF within 10 seconds, the live map shows every real chapter, and a test visit, a PDF download and a fall each raise their count in the SQLite file.
Learn: SQLite, Go database/sql, HTTP middleware, privacy by design, finishing work.
Phase 2: Depth
1.1.0 WebMCP
No server-side MCP endpoint. Instead, the Nuxt page itself exposes tools over WebMCP (the browser-native agent interface): a tool to read chapter states and a tool to push a chapter.
Under the hood the tools call the same public gateway API, so agents get exactly the limits visitors get. The gateway gains no new authority.
Done when: an agent in the browser can list chapters and push one, and the gateway counts and rate-limits it like any other visitor.