Files
OKF_CV_Website/decisions/v1-scope.md
T
Noel Sabia 01cab5a565 docs(okf): rebuild roadmap for Terraform, own proxy and WebMCP
insert 0.2.0 Terraform server and 0.4.0 reverse proxy/DNS, renumber releases, fold story cards into 0.9.0 and tracker into 1.0.0; release 1.1.0 becomes WebMCP from the Nuxt page (server-side MCP endpoint dropped); update open questions, v1 scope and log
2026-10-14 21:54:40 +02:00

1.6 KiB

type, title, description, tags, status, generated
type title description tags status generated
Decision v1 scope What the first public version keeps and what moves to later phases.
decision
scope
roadmap
stable
by at
claude-code/claude-opus-5-5 2026-10-11T12:15:30Z

Keep in v1

  • First screen: name, role, contact, PDF CV. Never gated behind interaction.
  • Life map with plain-word states and a "Push this chapter" button.
  • Story cards with real recovery seconds, lesson cards for failed chapters.
  • Live states: Completed, Ready, NotReady, CrashLoopBackOff, restart counts.
  • Gateway: SSE plus /fall with per-chapter cooldown and global rate limit.
  • "Someone just knocked down X" messages. Free, the SSE stream carries them.
  • Dev view: the raw event stream in a <pre>. Also free.
  • CI: Snyk, build, deploy, release-please.

Cut from v1

Cut Why Where it went
Separate Nuxt pod Static build served by the gateway is simpler Decision
Snapshot persistence, offline banner Downtime accepted for v1 Decision
Server-side MCP endpoint on the gateway Replaced by WebMCP from the Nuxt page: agents use the same public API, the gateway gains no new authority Phase 2 (1.1.0)
k6 as a CI gate Needs a staging target first Phase 2
Full kubectl-style terminal (YAML, probes) The raw stream covers it Phase 2
Interactive k6, HPA demo, latency graph Most work and most abuse risk Phase 3
Rolling update as "pivot" Nothing triggers it yet Not planned
client-go informer Polling every 2 seconds is enough at about 10 pods When polling falls short