SYS / 007 Living architecture
One domain. Seven experiences. Independent deployments, shared facts, optional services, and fallbacks designed as first-class architecture.
MAP / SYSTEM TOPOLOGY
Primary request path
Every journey begins on one stable public origin.
The edge owns routing, preferences, and API boundaries.
A clear precedence rule prevents accidental experience drift.
Three presentations share one professional identity.
Facts have a canonical source even when layouts diverge.
Enhancements fail softly and stay behind narrow contracts.
The enhanced experience is never the only experience.
INDEX / FIVE LAYERS
The spatial map is an interface. This index is the complete, accessible record behind it.
Seven expressions of one portfolio, each with a deliberate audience, interaction model, and fallback posture.
Scroll is the canonical long-form portfolio. Card compresses the same identity into a tactile single-view artifact. Terminal turns it into an operable command surface. Each presentation stays useful without its enhanced motion or graphics.
Nexus maps the portfolio as miniature worlds. Halfpipe and Counter are complete arcade loops with local-first progress and optional global boards. None is served to an unprepared first-time visitor.
One public domain resolves stable paths, explicit version choices, session preferences, and API requests.
The public URL remains consistent even though the experience behind it may come from a different independently deployed branch. Same-origin navigation also makes cross-document transitions possible.
A small Worker resolves path-owned content first, then explicit version choices, then a validated session preference, and finally the canonical Scroll experience. It also owns the site APIs so they behave consistently across every visual version.
Blueprint and other durable content paths are invariant. For the portfolio root, an explicit visitor choice wins over a valid session preference; without either, Scroll is always served.
Canonical identity and career facts move across divergent presentations through a checked content contract.
Identity, career history, project metadata, the universe dial, and transition styles originate from a shared content branch. A repository check catches drift across consuming worktrees before release.
Optional intelligence and scoreboards enhance the site without becoming dependencies for the core portfolio.
The terminal assistant is content-grounded, secret-gated, streamed, and rate-limited. Halfpipe and Counter use isolated leaderboard contracts with plausibility checks. Missing configuration produces a useful local fallback rather than a broken experience.
KV stores rate-limit counters, optional assistant grounding context, and compact top-ten scoreboards. Clients retain local progress, and service failures never block browsing or play.
Independent branches and deployments are held together by shared validation, progressive enhancement, and release evidence.
The visual versions live on separate long-running branches and Cloudflare Pages projects. The main branch owns only the public router and operating documentation, keeping presentation deployments isolated from edge behavior.
Static builds, typed checks, Worker tests, shared-file validation, reduced-motion modes, no-JavaScript content, and graphics fallbacks keep the system honest across browsers and capabilities.
DESIGN / OPERATING PRINCIPLES
Presentation can change radically; professional facts should not.
The canonical journey is clear. Experiments wait to be invited.
Motion, WebGL, storage, and APIs can disappear without taking the experience with them.
Tests focus on the routing and service contracts where independent systems meet.
END / CHOOSE A VIEW
Step into the system, or return to the portfolio it was built to support.