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.
ReleasePackage publishes, version cuts, OSS milestones — the events that put a number on a system.
03 · Scrub the timeline
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.
@emredogan/lumina-chat published — first OSS release
Lumina extracted as a standalone React package and published to npm. The portfolio consumes the same package the public consumes — there is no internal-only fork. 23.7 kB unpacked tarball; the package surface tracks Lumina's V3 + V4 invariants exactly.
Distribution before perfection. The OSS contract enforced a clean API boundary that the V4 + V5 transparency surfaces (and the eventual sub-agent registry) had to respect.
ReleaseV3 Phase 3· cloud-waste-hunter
Cloud Waste Hunter Pro — pricing + live metrics shipped
Cloud Waste Hunter moved from project case study to monetized SaaS surface: a pricing page, a Lemon Squeezy checkout flow, a live-metrics endpoint that surfaces real production numbers, and the embedded CWH Pro CTA that appears on both /projects/aws-waste-hunter and /architecture/cloud-waste-hunter. The portfolio became its own conversion funnel.
Demonstrating that a single-engineer SaaS can run a production billing flow inside the portfolio itself — instead of linking out to a separate marketing site — is the V3 signal that V4's OSS launch + V5's adaptive recruiter intelligence would each build on. The portfolio became a conversion surface in its own right.
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.
