public-site-reskin-architecture.md

# RN Systems Lab — Public Site Reskin & Architecture Brief

## Working public name

**RN Systems Lab**

Recommended descriptor: **A public laboratory for building systems across technology, law, neuroscience, governance, place, and independent work.**

This replaces “RN Builds” as the primary public-facing label because the project is larger than a portfolio of things made. It is a living engineering lab, exhibition, and body of inquiry.

## What the site must communicate in five seconds

1. RN builds real, usable systems.
2. The systems emerge from questions at the intersections of RN’s actual fields, experiences, and future practice areas.
3. The work becomes progressively more technically sophisticated.
4. Each build is paired with a visual communication artifact that makes the underlying problem visible.
5. Visitors can use the builds, understand the thinking behind them, see the engineering lineage, and contact RN.

## Primary site jobs

The site is simultaneously:

- a portfolio;
- a public engineering laboratory;
- an interactive exhibition;
- a build archive;
- a proof-of-capability system;
- a lead-generation surface;
- a canonical destination for LinkedIn and other public content.

It must not feel like a startup SaaS template, a developer portfolio grid, or a generic “100 days of code” challenge.

## Information architecture

### 1. Home

Purpose: establish RN + the thesis of the lab.

Suggested hero logic:

**RN Systems Lab**

_I keep noticing systems that should exist. So I build them._

Supporting line: A public engineering experiment across technology × law × neuroscience × governance × place × independent work.

Primary CTAs:
- Explore the 100
- Start with Build 001
- Work with RN

### 2. The 100

The central exhibition.

Required views:
- Sequence: 001 → 100
- Domains
- Complexity
- Infrastructure lineage
- A-side functional builds
- B-side visual builds
- Live / building / planned

Every cycle must clearly show:
- ###-A Functional Build
- ###-B Visual Build
- problem / observation
- what exists now
- what it inherited
- what it created
- what later builds use
- current version
- limitations
- links to use and view

### 3. Build detail

Each build detail page is a curated case study, not metadata dump.

Structure:
1. What I noticed
2. The missing system
3. A — Use the build
4. B — Watch / explore the reveal
5. Why this matters
6. How it works
7. Evidence / research basis
8. Infrastructure lineage
9. What I learned / what changed
10. Limitations
11. Related builds
12. Work with RN

### 4. Visual Builds

A dedicated gallery for the B-side artifacts.

Purpose: establish RN as not only someone who builds systems but someone who can make complex systems understandable through motion, interaction, visual storytelling, and creative technology.

Filter by medium:
- kinetic typography
- motion graphics
- interactive editorial
- data animation
- maps
- diagrams
- UI choreography
- generative / creative code
- agent trace
- real footage / hybrid

### 5. Infrastructure Lineage

Interactive graph showing how earlier builds become later infrastructure.

Must distinguish:
- real imported/consumed infrastructure
- conceptual relation
- shared research/evidence
- inherited design pattern

### 6. About / Practice

Public-facing explanation of RN’s cross-disciplinary practice and the kinds of problems the lab explores.

### 7. Work with RN

Not a generic contact page.

Routes people by need:
- I have a messy system/problem
- I need AI / workflow / research architecture
- I need a prototype / internal tool
- I need a decision-support or intelligence system
- I want RN to research / advise / build with my team

## Visual direction

The site should feel like:

**editorial research institution × experimental design studio × engineering laboratory × digital exhibition**

Not:
- SaaS dashboard
- startup landing page
- generic developer terminal aesthetic
- portfolio card wall

Visual system should support:
- strong typography
- negative space
- evidence-bearing diagrams
- motion used for explanation, not decoration
- distinctive editorial sequencing
- subtle lab/index notation
- pristine responsive behavior
- excellent color contrast and accessibility

## Conversion architecture

LinkedIn / external content
→ B visual artifact
→ save / remember
→ Systems Lab build page
→ use A
→ inspect evidence / lineage
→ understand RN’s capability
→ Work with RN

Every A build should expose a contextually relevant low-pressure CTA after value is delivered.

## Naming status

**RN Systems Lab** is the recommended working name for implementation. Before production rename, run a final naming check against the broader RN brand architecture. The codebase/repository does not have to be renamed immediately; public labeling can change first.