This is the engineering memory layer for the portfolio ecosystem. Not the changelog (that lives at /changelog and reads the raw commit firehose). Not the project archive (those live at /architecture). This is the editorial registry of architectural moments the system chooses to remember — versioned, typed, append-only.
01 · The registry
17 architectural events recorded across 2026-05-14 → 2026-05-19. 16 currently active; the rest carry the superseded flag and remain in the archive for the audit trail.
Architecture
1
Infrastructure
3
AI system
7
Topology
2
Release
2
Milestone
2
Evolution
0
02 · Filter by category
Seven categories index the registry. Each one is an architectural axis — not a content type. Pick one to narrow the archive, or stay on the unfiltered view to read the full memory.
The slider below is the cursor over the engineering memory. Drag the thumb, click a tick, step with the arrow keys, or press play to let the cursor advance from the present back to genesis. The track is a single WAI-ARIA slider — keyboard, mouse, and touch all work; reduced-motion preserves the slider but removes the easing.
A dedicated `/playground` namespace with capabilities-detection infrastructure, lazy-loaded experiment shells, per-experiment funnel telemetry (visit / mount / capability-miss hashes), and the diagnostic `hello-playground` experiment shipped as proof-of-contract. Triple-gate access: env feature flag, browser capability detection, explicit visitor opt-in.
Quarantining experimental surfaces from the production portfolio's bundle + Lighthouse posture meant the experimentation cadence could rise without dragging the cinematic identity down. Phase 6+ surfaces that need WebGPU, heavy 3D, or experimental APIs land here first.
InfrastructureV4 Phase 1 · Sub-PR 1.2· portfolio
Public telemetry dashboard — /telemetry
A public `/telemetry` page renders every observable axis the platform tracks: Lumina p95 latency, auto-tweet success rate, npm download counts, MRR, lab adoption funnels. Backed by `lib/telemetry/metrics.ts` — a single allow-listed metric registry that gates every KV write and read against the V4 § 2.13 schema. Graceful no-op when KV is unavailable.
The telemetry surface became the platform's first explicit operator console — a contract that turned `claims about how the site works` into `live numbers the visitor can audit`. Every subsequent V4 + V5 sub-PR has had to declare which metric slot it occupies before merging.
Five small foundation commits hardened the platform for what V4 would later need: the GitHub events feed moved behind an edge KV cache; the Lumina chat endpoint migrated to edge; conversations persisted across reloads; the global reduced-motion guard collapsed every animation to 0.01ms under the OS preference; a sitemap + robots + JSON-LD + skip-to-content + 44px touch targets shipped together.
The cinematic identity required a performance posture rigid enough to absorb the V4 + V5 AI surface area without ever sacrificing Lighthouse Mobile 98+. Phase 1 was where that contract became architectural rather than aspirational.
05 · Live adoption
The temporal layer records three kinds of adoption event: the page rendered, a category filter was applied, an event deep-link was followed. All three are aggregate-only — counters by event kind, no per-visitor identifier, no session-id field. The numbers below are cumulative since the layer was first enabled.
view
—
category_view
—
event_view
—
Playback verbsCounters for the five primitive operations the slider exposes — seek (click or keyboard jump), scrub (drag), play (auto-advance), pause, step (single frame). Every counter increments fire-and-forget; the slider never blocks on the network.
seek
—
scrub
—
play
—
pause
—
step
—
Timeline engagementThe slider's lifecycle hash. Each visitor session increments mounted at most once when the slider renders, and engaged at most once on the first scrub, seek, step, or play interaction. The rate captures awareness vs use.
mounted
—
engaged
—
engagement_rate
—
06 · Source files
Every entry in the registry is grounded in code. Click any row to read the file on GitHub.
Phase 7 closes here. Four sub-PRs landed the temporal architecture: 7.1 the schema + registry + archive surface, 7.2 the deterministic playback primitive, 7.3 the WAI-ARIA slider above, and 7.4 the per- project mount on /architecture pages (hidden below 768px viewport, opt-in by registry coverage). The observation window now opens before Phase 8 (cinematic topology); no further temporal surface ships during that window.
