rTracer

Find your line.

rTracer is the site at rtracer.com. It is not a marketing page. It is a short interactive film, set inside the early atlas of a motorsport world that bridges digital simulation and real-world racing. Visitors arrive on a dark holographic globe, find Japan glowing amber, and follow a single road to a single corner — Fuji Speedway's final turn — where they take the wheel and look for their line. The site is the platform's first artifact. It is also the platform, distilled.

I. Identity

Name. rTracer. The R is Real. Real Tracer. The platform traces the real world — its roads, its circuits, its drivers, its rituals — into a continuous digital atlas, and then traces a path back from the digital into the real (real seat time, real track days, real series entries). The site is the proof of that two-way trace.

Tagline. Find your line. It is the universal instruction of motorsport — the apex curve every driver chases. It is also a quiet philosophical claim: the line through any corner, like the line through any pursuit, is discoverable by anyone willing to look for it.

Voice. Editorial, curatorial. Present-tense. Observational. The site speaks as a documentarist on the ground at the paddock — telling the visitor what is there, in calm sentences with literary detail. Where the concept memo is declarative and ceremonial, the site is quiet and credible.

Today at Fuji, the air is clean. The cars are already on the grid.

II. Audience

The site is for two publics. The future player — the sim racer, the road-car enthusiast, the fan who has watched Super Formula on a small screen at three in the morning and felt the urge to be there in person. And the press — motorsport journalists, gaming writers, culture editors, industry observers — who need a shareable artifact with a quotable line and a screenshot-able beauty.

It is not a B2B pitch. Strategic partners and investors will find their answers inside the experience, but the experience is not built to convince them. It is built so the visitor leaves changed — having driven a corner they have only ever watched, having felt the world that promises every road on Earth.

Credibility is earned, not claimed. The site shows only what is real today: Japan, the Super Formula partnership, one circuit, one road journey, a small set of founding films. The rest of the Earth is dark on the globe, and that darkness is part of the story.

III. Brand visual system

Palette.

• Tire-smoke off-white. The base layer. Primary surface text, high-priority moments.
• Asphalt near-black. The world surface. The night. The negative space that gives the atlas its depth.
• Sodium amber. The signature. Streetlights on a Japanese expressway at four in the morning. The lights of the paddock. The glow of a stamp materializing on a wrist device. Used sparingly and meaningfully — never decoratively.

Typography. Locked. Primary pairing is Manrope (sans) + Fraunces (serif). Manrope carries gentle curvature in its terminals — letterforms that already feel like racing lines. Fraunces is expressive at hero sizes, with character through the literary-serif body voice. JetBrains Mono is the telemetry voice for instrument readouts (lap times, line tolerance, leaderboard positions). Noto Sans JP is the Japanese companion across all surfaces. All four faces are off-the-shelf Google Fonts, licensed for production.

Logo. Locked. The pure wordmark: rTracer set in Manrope Light with a custom-modified R whose leg traces an apex curve — instead of the standard straight diagonal, the leg sweeps outward then down, a single quadratic curve that reads as the exit line from a corner. The custom R sits at Manrope's cap height; the rest of the wordmark uses the face directly. The mark works at favicon scale (the curved leg remains legible) through hero scale.

Atlas mode. Maps in rTracer are not rendered in the cartographic surface treatment of OpenStreetMap or Stamen — they are rendered in a dark holographic style closer to the globe in an Apple Vision Pro briefing than a printed map. Racing lines are the dominant graphic element drawn across this surface. Glass-AR panels are the UI layer that explains what you are looking at. Topography is implied through depth and lighting, not through contour lines. The atlas is felt more than read.

Glass-AR principles. Every UI surface is a panel suspended in space. Frosted glass with subtle refraction. Soft amber rim-light on active edges. Light depth blur on inactive panels. UI sound is short, percussive — a single chime when a panel opens, a soft tap when a stamp lands. Glass panels are sized to feel architectural at hero scale and palmable at mobile scale. They are never decorative.

IV. The site as cinema

The site is structured as a short interactive film. The visitor is not browsing. The visitor is moving — through scales, through scenes, through one continuous arc that begins on a globe and ends on the start line at Fuji. There are no pages. There is one experience, with chapters that connect through cinematic transitions instead of navigation clicks.

The visitor's input is selective. The camera flies on rails between locations; the visitor takes the wheel only at the trial moment, where the experience becomes truly interactive. Everything else is direction — a film that respects the visitor's eye and lets them feel the world rather than navigate it.

The visitor's exit, if they choose to leave, is the leaderboard moment — score landed, stamp earned, real-world unlock teased. From there, the visitor can keep exploring the atlas freely, claim their stamp by joining the atlas (email capture), or leave with the line they found.

V. The cruise (the full story)

The cruise is open and non-linear in principle — the visitor can fly anywhere on the active atlas — but the first compelling path is the founding journey. The site recommends it on entry.

Scene 1: The globe

The visitor arrives in darkness. A holographic globe rotates slowly at the center of the frame. Japan pulses sodium amber. The rest of the Earth is dark.

A single curve draws itself across the lower third of the frame — the racing line through an unseen corner — becoming legible as the tagline:

Find your line.

A glass-AR panel emerges below: Enter the atlas.

Scene 2: The mountain road

The camera dives. Sky, then forest, then tarmac. The visitor is in the passenger seat of a Toyota GR86 on a mountain pass — the kind of road that has been the proving ground of Japanese driving culture for half a century. The trees are close. The road is narrow. The light is dawn.

A glass-AR panel offers a brief reading:

The first road is older than racing. Drivers came here at night to learn their cars by feel — apex to apex, no clock, no audience. The line was something you discovered, not something you were told.

The car follows the road. The line — drawn in sodium amber a half-second ahead of the wheels — shows the optimal path.

Scene 3: The expressway

The camera transitions. Forest gives way to highway. The Tomei expressway opens up, four lanes wide, traffic light, the sun risen now. Mount Fuji enters frame in the distance. The line still draws ahead — straighter here, but no less considered.

The second road is the pilgrimage. The expressway from Tokyo to Fuji is taken by drivers, fans, mechanics, and team principals on every race weekend. It is a real road. You can drive it tomorrow.

Scene 4: The paddock

The car enters Fuji Speedway through the main gate. The camera follows it past the pit lane, into the paddock. The cars are already on the grid in the distance.

A glass-AR scan-in moment: a sodium-amber beam reads the visitor's wrist. The wrist device materializes — a slim band of brushed metal and glass, sitting on the visitor's left wrist. The first stamp folds onto its surface: Fuji Speedway — Arrival.

The passport is wearable. It collects stamps as you travel — in the digital atlas, and in the real world at partner events. The stamps unlock things that matter.

Scene 5: The grid

The visitor walks (cinematically, on rails) to a parked Dallara SF23 in Super Formula livery. Helmet on. Steering wheel in hands. The HUD comes alive in glass-AR overlay: gear, RPM, lap time, line tolerance.

The car is the SF23. The series is Super Formula. You are about to attempt the final corner.

The trial begins.

Scene 6: The trial

The visitor drives the SF23 through Fuji's final corner — the long right-handed turn that flows onto the main straight — and onto the main straight itself. The line draws ahead in amber. The HUD shows two readouts: lap time and line tolerance (how close the visitor stayed to the optimal racing line, scored continuously).

The visitor has three attempts. The third lap is recorded. The first two are practice. The visitor's previous ghost is shown faintly as they drive.

Scene 7: The stamp

The lap completes. The car coasts. A new stamp unfolds onto the wrist device: Fuji Final Corner — Time: 1:30.482 — Line tolerance: 92%.

A glass-AR leaderboard rises in front of the visitor:

Top 10% this week earns a Fuji track day in the F4 program.

Your position: #847 of 12,402.

A CTA appears: Claim your stamp. Join the atlas.

A second option: Keep exploring.

After the trial

If the visitor keeps exploring, the camera pulls back to the atlas. The globe returns. The visitor is now free to fly to any active road, any active beacon — the UGC feed begins to populate, the concept beats reveal themselves as the visitor zooms through scales.

VI. The atlas (the persistent world)

The atlas is the world layer that contains everything else. It is rendered in dark holographic style and supports four scales of zoom, each with its own scene:

• Globe. The whole Earth, rotating slowly. Japan glows amber. No other zones are visible at launch. This is the honest framing: we have one partnership, one founding zone, and we say so by what we show.
• Region. Japan in detail. The active circuits are pinned with amber beacons (Fuji is brightest; other Super Formula venues are lit but quieter — Suzuka, Motegi, SUGO, Autopolis, Okayama — visible but not yet driveable in the cruise).
• Circuit. An individual circuit (Fuji at launch), seen from above with its racing line drawn. Clicking the racing line begins the trial cinematic.
• Corner. The immediate physical environment of a single corner. The trial's playable scene.

Scale transitions are seamless — the camera flies smoothly between zoom levels rather than cutting. The sound bed and ambient color shift with the scale.

The atlas is always summonable from the edges of the experience. Even during cinematic scenes, the visitor can return to the atlas via a corner gesture or a discreet edge button and reorient.

The UGC feed

The headline feature of the atlas is the live-feeling feed of real driver journeys. Roads on the map are pinned with small video markers — each marker is a real (or stylized) film of a driver's journey to or from a Super Formula event. Hovering or tapping a pin opens a glass-AR panel that plays the film with telemetry overlaid.

At launch, the feed contains the five founding films (two pilgrimage, two pre-race ritual, one after-the-flag reflection) plus six to nine shorter stylized demo pieces in the same visual language. The feed is designed to feel populated — as if the platform has been alive for some time and these are the films real drivers have already uploaded.

The feed will become real (real driver uploads) in a later phase. The site does not claim otherwise; copy describes the founding films as exactly what they are.

VII. The trial (centerpiece beat)

The trial is the only fully interactive moment in the cruise. Everything else is cinematic; the trial is the visitor's. It is short, considered, and survivable on first try.

Course. Fuji Speedway's final corner — a long, sweeping right-hander — into the start of the main straight. Roughly ten seconds at racing speed; under thirty for a full attempt with run-up.

Vehicle. Dallara SF23 in Super Formula livery. Rendered with high-fidelity 3D and lit to match the time of day in the scene (early morning, soft light).

Scoring. Two metrics, displayed in the glass-AR HUD:

• Lap time. Measured to the thousandth. Recorded automatically.
• Line tolerance. A continuous score (0–100) measuring distance from the optimal racing line throughout the corner and the straight. Tighter is higher.

The final score is a composite that respects both metrics. The fastest lap with poor line tolerance does not win; the cleanest line with mediocre pace does not either. This mirrors how race coaches actually evaluate young drivers, and aligns the trial with the platform's tagline.

Three attempts. The visitor can try the corner three times. The third is recorded. The first two are practice. The visitor's previous ghost is shown faintly as they drive.

Controls.

• Desktop. Keyboard (WASD or arrow keys) with optional gamepad detection. Steering is analog where possible; throttle and brake are mapped to W/S or up/down.
• Mobile. On-screen steering wheel (left thumb), throttle and brake paddles (right thumb). Optional tilt steering as a setting.

Feedback.

• A sodium-amber ghost line draws ahead of the car, showing the optimal path.
• The line tolerance score updates continuously, with subtle haptic and audio feedback when the visitor strays.
• Engine sound is positional — SF23 audio, lightly stylized.

Leaderboard. After the third lap, the visitor's score is placed against the current week's field. Top 10% qualifies for a real-world Fuji F4 track day (the prize structure is the digital-to-real exchange made literal). Top scores are displayed by initials and country flag. The leaderboard resets weekly.

Real-world unlock. The teased prize is honored at scale once the platform is live; for the launch period, top scorers are entered into a verified queue and contacted by the team. The site does not over-promise — copy is precise about what the prize is, when it is awarded, and who fulfills it.

VIII. The wrist passport

The passport is a wrist-worn device, rendered always in the visitor's first-person view when the experience is in cinematic mode. It is a slim band of brushed metal with a holographic upper surface that displays the visitor's stamps as they accumulate.

Form. Approximately the size of a watch. Sodium-amber light edges. The surface displays stamps in 3D — each stamp unfolds as a small architectural object (a low relief seal, a folded-light glyph) before settling flat onto the band.

Behavior.

• A new stamp lands with a quiet chime and a brief light bloom.
• Tapping the wrist (or hovering it in desktop mode) opens a glass-AR drawer showing the full stamp collection.
• Each stamp is a record: where, when, what was achieved, what it unlocked.

Symbolic role. The wrist device is the physical-feeling proof that the digital atlas and the real world are continuous. It is worn by the visitor in the cruise; it is the artifact a real player would wear at a real event. The eventual brand object — the thing the platform sells, gives, or grants — is a physical wrist device that scans in at real circuits and updates the digital atlas. The site previews this future without making it the headline.

IX. Real-world anchors

The site is anchored in real places, real cars, and real partners. Specificity is the discipline that earns the brand's larger claims.

Fuji Speedway. The founding circuit. Built in the foothills of Mount Fuji. Host of Super Formula, Super GT, the WEC's 6 Hours of Fuji, and historically Formula 1. The final corner and main straight are the site's centerpiece beat — chosen for visual drama (Mount Fuji backdrop), driving accessibility (a long sweeping corner is forgiving for first-time virtual drivers), and recognizability.

Super Formula (JRP). The series. The confirmed partnership. Marks, livery, and venue assets are usable. The site names Super Formula prominently and frames the founding zone as the home of the world's most demanding open-wheel racing outside Formula 1.

The two roads. The composite cruise begins on a mountain pass (Hakone Turnpike or a touge road — final choice TBD) and transitions to the Tomei Expressway approach to Fuji. Both are real, both are drivable today, and both are documented in the site's accompanying UGC films.

The cars. Toyota GR Corolla or GR86 (TBD — the GR86 is more emotionally specific to driving culture, the GR Corolla is the current performance flagship) for the road portion of the cruise. Dallara SF23 — the current Super Formula chassis — for the trial.

X. The UGC seed films

Five founding films, in the same editorial visual language, distributed across the emotional arc of attending a race weekend.

1. Pilgrimage I — Tokyo to Fuji at dawn. A real driver leaves Tokyo at four in the morning in a road car. Coffee, gas station, the empty Tomei, sunrise on Mount Fuji. Arrives at Fuji paddock as the team begins to wake. ~4 minutes.

2. Pilgrimage II — Kansai through the mountains. A driver from the Kansai region takes a longer, more scenic route through the mountains. Touge sections, hotel overnight, second-day approach to the circuit. ~5 minutes.

3. Pre-race ritual I — The driver. An SF driver's pre-race morning. Walking the grid in the early light. Helmet, gloves, the quiet before the cars fire. ~3 minutes.

4. Pre-race ritual II — The engineer. A race engineer's setup morning. Telemetry preparation, the strategy meeting, the moment before the start. ~3 minutes.

5. After the flag — A driver reflects. Post-race, in the quiet of the team garage. The driver talks about the line they found or didn't find on a particular lap. ~4 minutes.

Each film is shot in the same editorial language: handheld where appropriate, observational, ambient sound, minimal narration (the film's subject speaks; the site does not). They are presented inside glass-AR panels in the atlas, with telemetry and metadata overlaid in the brand's UI vocabulary.

Six to nine shorter stylized demo pieces (15–45 seconds each) populate the feed alongside the five hero films — short loops of a steering wheel, a tire wall, a refueling rig, a stretch of expressway. Together they make the feed feel alive without overpromising.

XI. Engineering approach

Stack.

• Framework: Next.js 14 (App Router), TypeScript.
• 3D: React Three Fiber + drei + three.js. Custom shaders for the holographic globe, the racing-line drawing, and the glass-morphic panels.
• Map: a custom Three.js globe (lighter than Cesium for the launch scope), with circuit and corner scenes loaded as discrete GLB assets.
• UI: TailwindCSS for base, custom CSS for glass morphism (backdrop-filter blur and saturation), bespoke shader passes where the effect must be physically convincing.
• State: Zustand for visitor session state; persistent leaderboard in Vercel KV / Postgres.
• Animation: GSAP for cinematic camera paths and interface transitions; Framer Motion for incidental UI.
• Sound: Howler.js. Positional audio in 3D scenes via three.js audio listeners.
• Internationalization: next-intl for JP + EN with hard parity (no English fallback for missing JP strings — both copies are written deliberately).
• Video: HLS streamed from a CDN for the UGC films, lazy-loaded.

Performance & device parity.

• Adaptive LOD: device detection on entry selects a quality tier (mobile / mid / hi-fi). Asset packs differ by tier.
• Mobile: simplified globe shader, fewer particles, lower-poly cars, compressed textures (KTX2 / BasisU).
• Connection-aware: low-bandwidth detection serves a poster-first version of UGC films that play full quality on tap.
• Bundle splitting: hero scene + brand reveal is the only thing in the initial bundle. Cruise, trial, atlas, and UGC layers are dynamic imports.

Sound design philosophy.

• Three layers: ambient bed (continuous, contextual), interaction (short percussive UI sounds), and event (engine notes, stamp chimes, leaderboard rise).
• Default state on first visit: silent for 2 seconds, then a quiet ambient bed begins. A mute control is always visible.
• Engine notes are the heaviest audio asset and are gated behind the trial scene's load.

Localization. Japanese and English are parity languages. Copy is written natively in each, not translated. Layout is tested in both. A language toggle is always available; default language is detected from browser locale.

Hosting & deployment. Vercel (Edge runtime where possible). Media on Cloudflare R2 or Mux. Domain: rtracer.com.

XII. Asset sourcing plan

Licensed (through partnership).

• Toyota GR Corolla / GR86 (model + livery rights — Toyota direct or via GR Garage)
• Dallara SF23 (model + Super Formula livery rights — via JRP partnership)
• Fuji Speedway venue assets — track centerline, paddock layout, photography (via JRP and FSW)

Shot or commissioned.

• The 5 UGC seed films — production over 6–10 weeks; one production team or split between two
• Hero road photography for the two-road composite (Hakone/touge + Tomei) — drone + ground
• Paddock ambient sound — recorded on a Super Formula race weekend

Rendered or designed.

• The holographic globe (custom shader)
• All glass-AR UI panels
• The wrist passport device (3D model + animation)
• The racing-line drawing system (procedural)
• The atlas zoom transitions
• The logo (3 directions explored)
• The type system (off-the-shelf license + companion JP face)

Stock / library where appropriate.

• Ambient music score (commissioned or licensed) — minimal, atmospheric, never anthemic
• Engine note baseline (recorded or licensed from a Super Formula source; tuned for the site)
• Generic incidental sound effects (UI chimes, glass taps)

XIII. Phased delivery

The site is not built all at once. Each phase ships a real artifact that stands on its own.

Phase 1 — Hero scene + brand reveal. The globe, Japan glow, tagline draw, glass-AR CTA. Working in browser at rtracer.com. Mobile parity. JP + EN. The artifact that establishes the brand direction publicly and can be linked, screenshotted, and shared.

Phase 2 — Hub cruise + paddock + trial. The full road-car cruise (composite road), the paddock scan-in, the wrist device materializing, the SF car, and the playable Fuji trial. Leaderboard live. Real-world unlock teaser copy locked. The "feel the product" phase.

Phase 3 — Atlas + UGC layer. The switchable-scale atlas fully operational. UGC seed films integrated. Non-linear exploration enabled. Concept beats (passport, zones, talent pipeline, paid trials, phased delivery) integrated as discoverable glass-AR cards.

Phase 4 — Polish, sound, localization, accessibility. Full sound design pass. Full JP copy review. Accessibility audit (keyboard-only path, reduced-motion mode, captions for all video, audio descriptions where needed). Performance audit and tuning.

Each phase is approximately 3–6 weeks. The whole site reaches steady state in approximately 3–5 months from start. No fixed deadline; the pace is set by quality.

XIV. Open questions

To resolve before or during the build:

• The mountain road. Hakone Turnpike vs. a touge — final pick after seeing the seed film direction.
• Road car model. GR Corolla vs GR86 — final pick after partnership conversation.
• Sign-up flow. "Claim your stamp — join the atlas" — what is the minimum data we collect, and where does it live?
• UGC seed film commissions. Single production house or two? Domestic Japanese team primary, ideally.
• Real-world prize fulfillment. Who runs the actual track day? FSW directly, or a third-party program (Toyota GR Garage, Suzuka Racing School, etc.)?

XV. The hub world and the zones — a complete world of motorsport

If sections I–XIV are the site as cinema and the passport as record, this section is the world as place. rTracer is, by design, an open-world social-exploration and competitive-event space in the lineage of GTA and Forza Horizon — a complete digital world of motorsport. The animating phrase is direct: compete in the digital world to earn your chance to drive in the real one. The platform is the XR enhancement layer for racing in both directions — every road on Earth is a road in rTracer, and every road in rTracer can be overlaid onto real geography through AR.

The structural ambition is two-way. Real circuits are pulled into rTracer as faithful digital twins. rTracer-native circuits — designed first in the imaginative space of the world — can be materialized as real venues through circuit operators and developers. Game and world iterate on each other until the distinction softens. The atlas is not a metaphor; it is the architecture.

A. The architectural move — zones as physics pods

rTracer is not one monolithic engine. The map is composed of zones, and each zone runs its own physics model, control scheme, and fidelity target. This single decision solves the technical problem (no need to ship a global physics model that handles MX, tarmac rally, snow, F1, and casual touge cruise on day one) and unlocks the business model in the same stroke.

Each zone is its own mini-game inside a cohesive world. Physics does not need to be globally continuous. Identity, progression, and the social graph do. The passport, the credentials, the witness record, the social connections — all travel with the user across zones. The handling model, the controller, the camera, and the fidelity vary by zone according to what that zone is for.

Concretely, this means a zone built for tire-deformation accuracy can run a specialist tire model that wouldn't be appropriate (or affordable) for an arcade touge cruise zone. A drift zone tuned to a specific dynamic envelope can demand a wheel-and-pedals controller while a casual exploration zone accepts a phone-tilt input. The platform does not flatten the experiences down to a lowest common physics; it celebrates the differences and routes the user into the right input mode for the zone they entered.

B. The hub world — the connective tissue and the sales artifact

The hub world is the geographic and social spine that connects the zones. It is the place the user lands when they open rTracer — a coherent rendered world they can navigate, where each zone appears as a place on the atlas, signposted, walkable, contextual.

For the launch window, the hub world's brief is narrow and disciplined: a basic version that renders to a single, isolated, impressive demonstration. The launch artifact is not "every zone live"; it is "the hub world plus one demonstration zone, both rendered to a quality that a partner will sign an LOI after seeing." The hub holds the passport, the scan-in flow, the social surfaces, the early storefront for stamp-eligible events, and the routing into the demonstration zone. Everything else is partner-funded build that arrives after the launch.

This is the structural reason the hub world is the right Day-1 product. We are not selling end-users a complete game on Day 1; we are selling partners the conviction to collaborate on building their zone. The hub-with-demonstration-zone is the conviction-generating artifact. Each subsequent zone signing makes the world more credible to the next prospect.

C. Zone categories — the partnership matrix

A zone is a partnership surface. Each category corresponds to a partner type with a clear stake in what the zone is for. The catalog is open-ended; the categories below are the load-bearing ones for Year 1.

Each row above is a conversation we can have on its own merits. We are not asking partners to fund the platform; we are asking them to fund the zone that demonstrates their engineering, product, community, or sanction, on a substrate that gives them more reach than they could build alone.

D. The Toyota / Yokohama / BMW examples — concretely

Three illustrative zone briefs to ground the abstraction:

• Toyota Gazoo Racing — GR drift zone. Toyota is releasing a car and wants its drift envelope rendered in the imaginative space before it ships. The zone is a Japanese touge or a closed circuit with a drift physics model tuned to the car's actual chassis dynamics. Customers who never touch the car can experience it inside rTracer. Customers who own the car get a digital twin of their build. Marketing pays for the zone; the customer relationship lasts beyond a launch cycle.
• Yokohama / Bridgestone — tire-deformation zone. A tire OEM funds a zone tuned for tire-deformation fidelity — slip angle, compound temperature, sidewall behavior under load. The zone hosts a paid trial competition the tire brand sponsors. Users see their lap-time-vs-tire-temperature curve and develop intuition for the brand's R&D. This is marketing budget that currently has nowhere to go in motorsport because no platform exists at this resolution.
• BMW — xDrive snow zone. BMW is launching a new xDrive variant and wants its snow behavior visible in the world. The zone is a Hokkaido-themed snow circuit with snow-physics, AWD power distribution, and the new car as the showcase vehicle. The Driving Experience program at the BMW Performance Centers ties in — sim-side qualifier credentials route users to the real Performance Center experience.

None of these zones requires the others to share physics. Each can be built to the partner's specification, funded by the partner's marketing or product budget, and integrated into the world via the shared identity layer. The hub world is the airport; the zones are the destinations.

E. The Pagani / Racing Unleashed / Forza-Horizon-Dubai examples — concretely

Three more, in different directions:

• Pagani — hypercar-house zone. Pagani has ~800 customers globally and a customer-only Huayra R simulator at the factory. They cannot scale that experience cost-effectively. An rTracer Pagani zone is an invite-only digital extension of the factory simulator — owners and pre-owners experience the marque inside rTracer at fidelity Pagani approves, and physical factory visits route into rTracer-credentialed users. The marque keeps the cultural exclusivity; the platform keeps the relationship persistent.
• Racing Unleashed — sim-arcade network zone. Racing Unleashed runs premium real-world racing-sim arcades. The zone is the physical-to-digital crossover: your laps at a Racing Unleashed venue land directly in your passport; your friends in rTracer see when you're at a venue; the venue gets a customer-acquisition channel and the platform gets venue-density in markets where it would otherwise need to build its own physical presence.
• Forza Horizon Dubai weekly meetup group — regional community zone. A specific community already exists, meets weekly, and lacks digital infrastructure of their own. A community zone gives them their own home in the atlas — a recreated Dubai backdrop with the meetup's weekly event calendar, member roster, group chat, and shared media. The fidelity is community-appropriate (presence, social, light competition) rather than tire-deformation-grade. This is the long-tail surface that turns rTracer from a B2B-funded platform into a culturally credible global community.

The pattern across all three: rTracer is the substrate. The partner contributes what they are uniquely good at — a marque, a venue network, a community. rTracer contributes the identity, the social graph, and the substrate that makes the partner's contribution global, persistent, and credentialed.

F. Why this compounds

Three things stack:

1. Partner-funded fidelity. Each zone's physics, art, and audio R&D is paid for by the brand that benefits from it. The atlas gets deeper without rTracer absorbing the cost. The cost curve of the platform diverges from the value curve in our favor.
2. AR continuity. rTracer is not confined to a screen. The same world is accessible through AR overlay onto real geography — so real road trips, meetups, circuits, and dealerships become extensions of the world rather than competitors to it. Scan-in at a real venue produces a stamp in the same passport that holds the digital lap-time records.
3. Digital-to-real exchange rate. Every other racing title is a closed loop. The passport makes rTracer's value proposition leak into the physical world — seat time, track access, event entry, manufacturer experience programs, hypercar-house visits, sim-arcade laps. This is what brands, sanctioning bodies, and serious players actually want, and it is the bridge across which affiliate revenue flows back to the platform.

G. The launch demonstration — Fuji as Zone One

The Super Formula Fuji activation on July 18, 2026 is Zone One. It is the artifact we walk JRP, Dentsu, APCC Fukuoka, Racing Unleashed, Simagic, and every subsequent partner through. It is also the first proof that the hub-plus-zone model holds — that we can build to the fidelity a partner expects, integrate with venue activation hardware, route credential and passport data through the identity layer at scale, and convert a race-weekend audience into passport holders at a pace the partner takes seriously.

The JRP follow-up conversation immediately after the Super Formula race weekend is the moment Zone One has to be legible. The five-LOI list in §XVI.E and the decision gates calibrated against it are anchored on that conversation. The pitch is not "rTracer is a platform we hope to build." The pitch is "Zone One is Fuji. Here is the world it lives in. Here is the zone you would have if we built yours next."

Each subsequent zone signing — Toyota, Honda, Yokohama, Pagani, Racing Unleashed — adds to the world. The world becomes more credible with each signing, which makes the next signing easier. This is the partner-funded fidelity flywheel.

H. What this implies for the early site

The site at rtracer.com is the first artifact of the hub world. The cinematic prelude already shipped (globe → touge → expressway → paddock → grid → trial → stamp) is the artistic over-delivery of the hub world's v0.1 demonstration. The next surfaces that bring it closer to the working hub are:

• The atlas surface. A switchable-scale map showing the Fuji zone live and other zones as silhouettes-awaiting-signing. Each silhouette is a sales surface — when a partner signs, the silhouette resolves into the zone.
• The passport-with-stamps synthesis. The passport already appears in the cinematic concept. The early site makes it real — a verified-email signup that creates an actual passport, with the Fuji activation as the first stamp users can earn. Competition + passport is the primary attention mechanic; without the stamp at the end, the cruise is decoration.
• The zone catalog page. A partner-facing page showing the zone categories (Real-circuit twin, Manufacturer product, Tire-OEM technical, Hypercar-house, Sim-arcade network, 3rd-party esports host, Regional community, Sanctioning-body) with example pitches and contact paths. The partner directory is the credible-floor; the zone catalog is the door.
• AR teaser. A short embedded video or interactive surface showing the AR overlay — pointing a phone at a road and seeing the rTracer racing line draw onto the asphalt — establishes that the digital-to-real bridge is real, not aspirational.

The B2B sales motion in the 60-day window is anchored on these surfaces. JRP, Toyota, Yokohama, BMW, Pagani, Racing Unleashed all need to see the hub world's intent before they sign their zone. The early site is the artifact that gets them to yes.

I. Revenue from the hub-and-zones architecture

The streams documented in the operational roadmap (XVI.J) all flow through the hub-and-zones architecture. To name the ones zones specifically unlock:

• Zone co-build fees — the primary B2B revenue motion. Each partner pays to develop their zone with us. The fee covers our build cost, our integration work, and the platform's margin. This is the work that funds engine R&D for everyone else.
• In-zone advertising — inventory inside zones and at hub-world surfaces, sold to manufacturers, tire brands, energy drinks, and motorsport-adjacent advertisers. AR overlay extends the same inventory into the physical world at partner locations.
• Paid trials inside zones — the carnival mechanic at zone-appropriate fidelity. Tire-OEM zones run technical trials; manufacturer zones run brand-tuned trials; community zones run social trials.
• Tournaments and events — entry fees and sponsorship across structured competitive tournaments, hybrid digital-physical formats, season championships, and real-world events the passport unlocks. Each tournament lives inside a specific zone or crosses several.
• Ticket fulfillment — when stamps or trial wins unlock real-world race entries, track days, and manufacturer drives, those tickets flow through rTracer as the issuing layer. Each zone has its own ticketing tail.
• Scan-in monetization — at venue activations (Fuji, Racing Unleashed locations, BMW Performance Centers, Pagani factory days), scan-in into the passport produces both the user's stamp and a partner attribution event that contributes to the partner's reporting and our own.

The zones do not replace the operational lifecycle economy (insurance, service, parts, provenance — covered in XVI.J). They sit alongside it as the cultural and commercial superstructure inside which the lifecycle economy operates. The user lives in the world; the operational economy is what they pay for to keep their car alive in it.

J. One line for the world

rTracer is a complete digital world of motorsport — a hub world that renders cleanly, zones that each run their own physics and serve their own partner, a passport that travels across them all, an AR continuity that lets the world spill into the road outside your door, and a Day-1 demonstration at Fuji on July 18 that proves the model by being the first zone of a world that compounds with every signature.

XVI. Concept roadmap

The site at rtracer.com is the first artifact of a longer build. This section is the canonical roadmap for what comes after it. It is not a project plan in the project-management sense. It is a map of what counts as on-track and what counts as drift, calibrated against four operational realities running simultaneously: the 60-day public-launch window, the five-arc journey to canonical infrastructure, the seven-layer OS architecture, and the three identity passports that accumulate value across years.

A. The unifying thesis — identity density as moat

For the demographic rTracer is built for — drivers, builders, fans, engineers, every R that the prefix can stand for — their motorsport identity is not a hobby. It is a significant component of who they are. The platform that holds the canonical record of that identity has structural lock-in no feature competitor can replicate.

The lock-in mechanism is data density. Specifically:

• Every car you have driven — owned, borrowed, test-driven, sim-driven, dreamed of — logged with photographs, locations, dates, performance context.
• Every event you have attended — race weekends, cars and coffee, track days, concours, museum visits — captured as moments with co-attendees and conditions.
• Every modification you have made — receipts, install photos, dyno results, before/after comparisons, the build narrative as it unfolds across years.
• Every credential you have earned — driving school certificates, track-day check-rides, sim ratings, racing licenses, sanctioning-body memberships, manufacturer-experience completions.
• Every connection you have made — drivers you have met, teammates you have raced with, fellow attendees at events.
• Everything you have watched — F1 weekends, Le Mans hours, Super Formula rounds, iconic esports moments witnessed live.
• Everything you look forward to — bucket-list cars, bucket-list tracks, target events, build aspirations, savings goals tied to specific cars or experiences.

This is not a settings page. It is the canonical record of someone's life as a motorsport person, accumulated over years. Once it exists in enough density, the exit cost is not "switch to a different app." The exit cost is leaving behind your identity.

B. The five structural problems we solve

Other platforms own slices. None own the synthesis. rTracer exists to close five gaps no incumbent can credibly close:

1. Credentialing fragmentation. A driver who races on iRacing, ACC, GT7, and in real karting has no portable credential that represents their full ability. Each platform owns its slice; nobody owns the synthesis. rTracer is the translation layer.
2. Vehicle identity fragmentation. A specific car has a real history — track days, modifications, concours appearances, ownership transfers — that lives nowhere except scattered Instagram posts, lost receipts, and the memory of its current owner. The car's individual identity is not canonical anywhere. rTracer makes it canonical.
3. Witness data loss. The cars enthusiasts have seen, the races they've watched live, the events they've attended, the moments they've witnessed — none of these accumulate into a permanent identity record anywhere. The data is lost as it is created. rTracer is the apparatus that catches it.
4. Affiliate-flywheel disaggregation. Insurance, parts, track days, driving schools, vehicle purchases all happen through siloed channels that don't share data or revenue. rTracer routes intent into transaction and earns at the routing.
5. Cultural-infrastructure absence. Motorsport has commercial infrastructure (series, manufacturers, broadcasters) and retail infrastructure (dealers, parts, shops) but no consumer-facing cultural infrastructure analogous to Letterboxd for movies, Strava for running, Goodreads for books. The behavior pattern exists; the platform doesn't.

Each gap is its own product surface. The unification is what creates the structural value — the data compounds, the moats deepen with time.

C. The ray-tracing foundation

The platform is named after the rendering algorithm because the algorithm is the architecture. Rays cast from an observer's position bounce off surfaces, gather information, and produce the rendered scene. Applied to rTracer:

• The user is the observer. Their attention determines which moments matter.
• The moment is the ray. Each event, sighting, race, modification, achievement is a ray cast from the user into the world.
• The vehicle is the surface. Cars are the primary objects motorsport identity attaches to.
• The transaction is the photon's flight. The completion of a desire — a parts purchase, a track-day booking, a vehicle acquisition, an insurance policy — is the moment the ray's path completes and the rendered image becomes part of reality.
• The platform is the renderer. rTracer aggregates the rays, computes the image, persists the record.

This is not decorative. It produces concrete architectural commitments: persistence is thermodynamically enforced (rendered moments stay rendered; erasure costs energy the platform refuses to spend gratuitously), the observer's perspective determines what matters (algorithmic feed manipulation is rejected as interference with the integrity of the observer's perspective), rays are bidirectional (the user observes the world and the world presents itself to the user — the platform mediates both directions), and dimensional fidelity is variable (a photograph, a sim session, and a real test drive each contribute to the same identity record at different fidelities).

D. The three identity passports — the spine

Across every arc and every layer, three passports accumulate value:

1. The Driver Passport. The canonical record of an individual's motorsport identity: verified name (KYC'd via driver license), skill credentials (sim ratings, real licenses, school certifications, track-day check-rides, manufacturer-experience completions), witness record (cars spotted, races watched live, events attended, moments witnessed), vehicle relationships (owned, frequently driven, on wishlist, test-driven), experience record (track days, road trips, modifications performed), social graph, achievement record. Progresses through states: Anonymous → Verified → Credentialed → Premium → Pro → Dormant → Closed. Portable by construction — users own their identity; the platform is custodian.
2. The Vehicle Passport (Carfax+++). The canonical individual identity record for specific vehicles. Schema: core identity (VIN, chassis, year/make/model/trim, original factory spec, original delivery), plate history (encrypted; visibility owner-controlled), ownership timeline, modification record (receipts, install photos, tuner attribution), service history, performance history (track days, dyno, autocross, time-attack, drift, racing incidents), witness record (community sightings per privacy tier), concours and event history, damage and incident record, documentation (window stickers, factory letters, period photos), and verified provenance certificate where issued. Privacy tiers: Private (default) → Limited → Public Profile → Promotional. Every parameter of the plate-tracking architecture is privacy-by-design (see §K).
3. The Experience Passport. The canonical record of what the user has witnessed, attended, watched, and lived through in motorsport. Event attendance, cars-and-coffee, concours, track visits, race watching (live and replay), esports-moment witnessing, carspotting, modification observation, driving experiences, educational experiences, social experiences. Verification levels range from self-reported to cryptographically attested (NFC tap-in at venue, signed credential from organizer).

The passports are how the OS architecture meets the user. They are the spine the rest of the system hangs from.

E. The 60-day window — May 26 → July 24, 2026

The public launch is the Super Formula round at Fuji Speedway on Saturday, July 18, 2026 (Day 54). The 60-day window opens on May 26 (Day 1, today) and closes on July 24 (Day 60), nine days after the launch. Three architectures run simultaneously through the window, each with its own cadence:

• Web hub — rtracer.com, progressing through four versions.
• Build-in-public media — daily X, weekly LinkedIn + YouTube, bi-weekly newsletter and longer-form vlog. Documents the build, supplies partner conversations with social proof, generates the audience.
• OS architecture + partnerships — the technical and commercial work that produces the substance the media documents and the partners ratify.

Web hub progression:

Five founding letters of intent. The launch lands credible if at least four are signed by July 18, ideally five:

1. JRP (Japan Race Promotion) — Super Formula series operator. Target LOI signed by Day 14 (June 9). Launch venue host.
2. Dentsu (Japan high-school tournament series) — talent-pipeline conduit into Japanese youth motorsport. Target Day 30 (June 24).
3. APCC Fukuoka — school integration. Formal proposal Day 10; LOI Day 30–35.
4. Racing Unleashed — premium sim-center network (European footprint, premium hardware). Target Day 45 (July 10).
5. Fifth LOI — Polyphony Digital, Super Formula at series level, or WRC. Whichever is most ready by Day 50. Hardware partner alongside: Simagic primary, Fanatec backup, LOI target Day 18 (June 12).

Decision gates inside the window. Each is a checkpoint where the plan re-traces itself rather than a deliverable:

• Day 7 (June 1) — strategic questions resolved, Platform Engineer hire on track. If both no, pause and re-plan.
• Day 14 (June 8) — JRP LOI signed or in clear signing trajectory. If not, escalate or pivot launch venue.
• Day 21 (June 15) — OS architecture v1.0 document published. If significantly behind, accept smaller v0.1 scope.
• Day 30 (June 24) — Dentsu LOI signed; at least two LOIs total by this date.
• Day 45 (July 9) — v0.9 working end-to-end. If not, scope cuts begin.
• Day 50 (July 14) — hard feature freeze.
• Day 60 (July 24) — Day-60 evaluation document submitted.

F. The five arcs — the longer journey

The 60-day window puts rTracer in the world. The longer build is sequenced as five arcs. Each arc has a clear end state, depends on prior arcs, and unlocks the conditions for the next. Exact timing matters less than the order of state transitions.

• Arc 1 — From idea to operational organization. Where we begin. End state: funded team in place, architectural direction set, named CEO and OS architect, build-in-public cadence established, web presence live, partnership outreach active to the five LOI targets. Key unlock: a team with capacity to build, partner conversations with momentum, the platform ready to begin construction.
• Arc 2 — From organization to launched platform. End state: rTracer publicly launched at Super Formula Fuji on July 18, 2026. OS v0.1 in production. Five LOIs signed. Web hub at v0.9 launch-ready. First merchandise drop live at the venue. Driver passports being created by attendees. Press coverage in the field. Key unlock: traction proof for the $200K Play! investment and the foundation for outside-venture conversations.
• Arc 3 — From launched platform to monetizing platform. End state: insurance affiliate engine live with Hagerty (or initial partner) and a mass-market carrier; track-day booking marketplace integrated with insurance offer; service-records platform piloting with 50–200 verified shops via AutoLeap or Tekmetric; first Bring a Trailer / Cars & Bids verified-provenance partnership; spotting mode v1.0; watch mode v1.0; License KYC layer in production; measurable monthly recurring revenue across affiliate, subscription, and B2B partnership streams. Key unlock: real revenue, real partner depth, foundation for the venture conversation.
• Arc 4 — From monetizing platform to venture-scale business. End state: outside venture round closed from strategic investors (motorsport-tech, OEM venture arms, sports-tech); Vehicle Identity layer with plate tracking operating at scale with the four-tier consent system; witness graph structurally meaningful; international expansion begun (UK, Germany, or one APAC market); first manufacturer data partnership operational (Toyota, Honda, BMW, or Mercedes-AMG); Year-2 revenue in seven figures with clear path to eight. Key unlock: capital for sustained growth and structural credibility with manufacturers and institutions.
• Arc 5 — From venture-scale business to canonical infrastructure. End state: rTracer is the canonical individual vehicle-identity layer of motorsport globally. Auctions, concours, insurers, manufacturers, restoration shops, sanctioning bodies, and OEM heritage divisions integrate as the standard. Multiple manufacturer data partnerships generate $5M+ annually. International operation across US, EU, UK, Japan, and at least one additional major market. OS v2.0 with a third-party developer ecosystem. Annual revenue in eight to nine figures with clear path to platform-defining scale.

The launch on July 18 is the inflection point between Arcs 1–2 (preparation) and Arcs 3–5 (compound growth). The arcs are not deadlines; they are the order of state transitions.

G. The seven layers of the OS

rTracer is built as seven layers. Each layer is documented in the Data Architecture and Engineering Manual; each ships behind the layers that depend on it.

The post-launch architecture (Volume 2) extends into communication, coaching, parts catalog, restoration projects, livery designs, championship standings, analytics, and decentralized identifiers — the surface area through which the affiliate flywheel and the talent-pipeline scouting subscription become real revenue.

H. The four strategic refinements

Four refinements tighten the architecture into the lock-in machine §A describes. They are not additions; they are the load-bearing structure.

1. Capture-first onboarding. The original architecture treated rTracer as primarily a credentialing and platform layer. The refinement makes capture — photo, video, location, social — the primary input. The architecture inverts: rTracer is first a recorder of motorsport life, and second a credentialing layer on top of the record. The PWA opens directly on the camera. New users do not see a form; they see "Take a photo of your car," and that photo becomes the foundation of their passport. Computer vision enriches every capture — year/make/model classification, event/venue identification, modification detection — so friction approaches zero. Memory-band visualization turns the passport into a chronological scroll with the visual density of a photo library and the structural density of credentials. Social graph emerges from physical co-attendance rather than abstract follow mechanics. The PWA is mobile-first, accelerated from the original Phase-2 plan into the 60-day window.
2. Driver license as KYC anchor. Email is weak; phone is mediocre; license is strong. License KYC produces a verified-identity tier everything else builds on (credentialing, sanctioning, sponsor data, insurance underwriting). The license certifies driving capability natively; endorsements (motorcycle, commercial, racing) extend it; the platform inherits the capability claims. The demographic anchor is decisive: someone gets their first license at 16–18, and the platform that captures them at that moment has a 10–15 year head start over every platform that pursues them later as adult enthusiasts. Revenue surfaces follow: license-renewal navigation ($5–25 per assisted transaction), driving-school affiliate ($100–1,000 per enrollment), endorsement upgrade guidance, International Driving Permit services, driver-education content subscriptions, performance-driving instructor marketplace. Privacy: license images encrypted at field level with KMS isolation from operational data; biometric data discarded after verification; jurisdiction-aware retention.
3. Government and sanctioning-body co-platforming. The partnership matrix expands beyond commercial partners (series, hardware, manufacturers, media) to include government entities, sanctioning bodies, and educational institutions. Prefecture and state governments (APCC Fukuoka already in motion, with natural expansions to other Japanese prefectures, US states, German Länder). Sanctioning bodies (SCCA, NASA, FIA, JAF, DMSB, MSA UK, CAMS). Driver-licensing authorities (state DMVs, DVLA, Kraftfahrt-Bundesamt). Educational institutions (high-school motorsport programs, university motorsport-engineering programs, karting academies). The pitch is consistent: rTracer is digital infrastructure for driver education and credentialing — you maintain authority over credentials; we maintain authority over the platform. Win-win without ceding sovereignty.
4. Race-day merchandise as identity manifestation. Merchandise is not Phase 2; it is Day 1 — both as revenue and as the physical manifestation of identity the platform represents. Super Formula and JRP have not built serious merchandise programs; the arbitrage opportunity is hiding in plain sight. The first drop is rTracer × Super Formula Fuji July 18, 2026: 8–12 SKUs, premium positioning, 500–1,500 units total, heritage-inspired Japanese aesthetics, hardware-partner-funded production in exchange for placement. Recurring drops at each Super Formula round through 2026, then manufacturer collaborations (Toyota Gazoo, Honda HRC, BMW M), heritage collaborations, driver collaborations. Loyalty-tier integration converts merchandise into a credential reward and credential accumulation into merchandise eligibility. Each reinforces the other.

I. The audiences served

The platform serves five publics simultaneously, each with its own progression and reward surface. The 60-day window targets a credible first version of each.

• Competitors (the pipeline). Driver passport with portable credentials across iRating, ACC SA/CC, GT7 DR/SR, and real licenses. Launch surface: passport creation flow, first leaderboard.
• Engineers, strategists, team roles. The six-tier progression applied to non-driver roles, with hybrid quantitative + portfolio measurement. Launch surface: role-aware credential issuance on signup.
• Casual players and spectators. Audience layer — watching, learning, attending. Launch surface: event calendar with Fuji as the anchor, build-log content archive.
• Plateaued players and builder-citizens. Horizontal mastery — touring, drift, off-road, media production, coaching, event organizing. Launch surface: partner showcase with seeds for each path.
• Partners, sponsors, racing series, manufacturers, venues. The B2B surfaces. Launch surface: partner directory with five signed LOIs, press kit, sponsorship inquiry.

The three sim-racing personas — Consumer/Evangelist, Crossover Competitor, Prosumer Builder — map across all five publics. Each enters at a different stage of the Spark → First serious game → Sim-racing awareness → First wheel → Community → Identity moment → Real-world bridge journey. rTracer's leverage is the credentialing translation layer that lets a passport earned on iRacing or GT7 become a Fuji track-day qualifier without either platform's permission.

J. The revenue trajectory

The 60-day window is not about revenue; it is about proof. The revenue model that follows has eight streams compounding into one flywheel.

The affiliate flywheel as the core mechanism. Digital experience renders desire → desire crystallizes into intent → rTracer routes intent to real-world transaction → transaction generates affiliate revenue → transaction logs into passport → logged moment seeds next desire → cycle compounds. Conservative scale mathematics: 10K active users × $50 lifetime affiliate value = $500K ARR; 100K × $150 × 2-year lifecycle = $7.5M ARR; 1M × $400 × 5-year lifecycle = $80M run rate. The lifecycle multiplication is what makes the model defensible — recurring transactions, not one-time fees.

Stream-by-stream summary at scale (3–5 year horizon):

Aggregated trajectory:

• Year 2–3 conservative: $30–100M ARR.
• Year 4–5 scaled: $100–400M ARR.
• Year 5+ canonical infrastructure stage: $250M–1B+ ARR potential.

These are the numbers the outside-venture conversation in Arc 4 is structured around. They are conservative — the lock-in mechanism's strategic value is significantly greater than its direct revenue contribution because identity-density platforms compound across years and decades, not quarters.

K. The privacy and trust framework

The most strategically valuable feature in the architecture (vehicle plate tracking) is also the most ethically demanding. Done well, rTracer becomes the canonical individual vehicle-identity layer of motorsport. Done poorly, it becomes a stalking tool, a theft roadmap, and a privacy disaster. The architecture assumes "done well" requires hardcoded safeguards rather than policy-imposed ones. Privacy is structural, not procedural.

Seven privacy-by-design principles enforced architecturally:

1. Default-private. Every data point starts private. Public visibility requires explicit owner action.
2. Owner-controlled. Owners control their own data. Platform is custodian, not owner.
3. Minimal collection. Only data necessary for stated purpose is collected.
4. Purpose-limited. Data collected for one purpose is not repurposed without consent.
5. Time-limited. Deletion timelines enforced (dormant account data archived after 24 months).
6. Audit-logged. All access to sensitive data logged with cryptographic verification.
7. Right-to-be-forgotten. User-initiated deletion executed within 24 hours with cryptographic proof.

The four-tier consent system applies to vehicle identity, witness data, and other shared identity surfaces:

• Tier 1 — Private (default). Plate stored encrypted, accessible only to the spotter. No public profile exists for the car. No aggregated patterns visible publicly.
• Tier 2 — Limited (verified members only). Owner has claimed the car. Anonymous public profile exists. Plate hash visible only to verified members. Geographic patterns at city-level precision with 72-hour temporal lag.
• Tier 3 — Public Profile. Owner has claimed and chosen public visibility. Geographic patterns at neighborhood-level precision with 24-hour lag. All sightings publicly attributed.
• Tier 4 — Promotional. Owner actively promoting. Real-time location optional. Owner-curated content. Linked to social media. Available for press, partnership, content distribution.

Hardcoded mitigations against specific risks:

• Stalking and harassment. Plate aggregation is never publicly searchable by plate text. Plate text is never persisted — only HMAC-SHA-256 hashes with rotating salt are stored. Cross-sighting matching uses hashes only. Even rTracer internal staff cannot recover plate text from the system. Single-user query-pattern detection flags and rate-limits suspicious patterns.
• Theft targeting. Geographic data publicly available is temporally obscured (24–72 hour lag minimum) and spatially obscured (city-level precision maximum for public data). Real-time location is never publicly visible.
• Adverse insurance use. Owner consent explicitly governs what data flows to insurance companies. Default state: nothing. The platform serves the owner's interest, not the carrier's.
• Bad-actor exploitation. Repo agencies, debt collection firms, surveillance contractors, and abusive partners are categorically excluded from institutional API access. Detection systems flag suspicious access patterns. Government surveillance access requires proper warrant.
• Jurisdiction variance. The platform operates with the strictest applicable jurisdiction's rules as default. California (SB-712), GDPR, UK GDPR/DPA 2018, Japan APPI all baked into the architecture rather than bolted on.

Cryptographic schemes: Ed25519 for personal identity keys; ECDSA-P256 for issuer signing keys; AES-256-GCM for at-rest encryption; SHA-3-256 for general hashing; Argon2id for password hashing; HMAC-SHA-256 for plate hashing; TLS 1.3 minimum for all transit.

L. The five cross-cutting disciplines

Five disciplines operate continuously across every arc. Each must be sustained from Arc 1 onward; none can be picked up later as a corrective.

1. The build-in-public media engine. Daily X content, weekly LinkedIn long-form, weekly YouTube short and vlog, bi-weekly long-form vlog, bi-weekly Build Log newsletter. Continuous from Arc 1 forward. Captures the build for future Season 1 production. Generates audience that compounds across years.
2. The partnership outreach cadence. Each arc adds new categories: Arc 1 the founding LOIs; Arc 2 the operational partners (Hagerty, Lockton, shop POS, auction houses); Arc 3 the manufacturer relationships; Arc 4 international expansion; Arc 5 institutional credentialing. CEO and OS Architect maintain coordinated outreach with clear authority boundaries.
3. The OS architecture maturation. From v0.1 at launch through v2.0 at scale. Each arc expands the layers, adds sub-layers, deepens integrations. The seven-layer model persists; what changes is the maturity of each layer.
4. The privacy and trust architecture. The vehicle plate tracking, the License KYC, the witness graph all require privacy-by-design. Default-private. Owner-controlled. Bad-actor-excluded. Jurisdiction-aware. The architecture must remain unimpeachable as scale increases.
5. The cultural and brand maturation. Voice, aesthetic, and cultural credibility built over years. The brand memo's four readings (re-tracer, road and track racer, ray tracer, R tracer) continue layering depth. Merchandise, events, content, and partner activations all express the same coherent identity.

M. What rTracer is not — restated against the roadmap

A roadmap is partly a list of refusals. We are not building:

• A racing game (games are tiles in the atlas; rTracer is the atlas).
• A racing series (we partner with series; we are not one).
• An esports league (esports is a vertical activation, not the platform's identity).
• An academy (we credential and connect; academies are downstream partners).
• A media company (content serves the platform, not the other way around).
• A consumer-hardware brand (we partner with hardware; we are not one).
• A speculative-asset platform (tokens are utility, never investment, never competitive advantage).

Anything on the build calendar that drifts toward one of these categories is a drift.

N. One line for the roadmap

rTracer renders the moments of motorsport identity into a canonical, persistent, accumulating record — five arcs from current foundation to canonical infrastructure, three identity passports as the spine, seven OS layers as the substrate, an affiliate flywheel that earns at every real-world transaction the rendered desire generates, a privacy framework that makes the worst-case uses structurally impossible, and a public launch at Super Formula Fuji on July 18, 2026 that turns the prelude into the platform.

This is the document. Everything in it is settled in direction. The remaining decisions are taste-level and operational. The site is buildable from this brief.