rTracer — General Manual

Mission, method, and how to create value — for every member of the team.

Date: June 2, 2026 · Written by LNK · Project: rTracer

This is the one document that aligns you. Read it once, fully. Then operate from it. It is written so that you do not need to be assigned work — you can read this, understand the whole, and generate your own tasks that create real value. When you are unsure, return here.

1 · Mission

Render lived motion into persistence — and build rTracer as the platform that does it.

In plain terms: we turn racing-game players into real motorsport participants, we capture and rank what they do, we teach them, and we document the whole thing as it happens. rTracer is the instrument; the championship and the events are how it runs in the world; the documented record is what we leave behind.

2 · Vision

rTracer becomes the always-on platform and identity layer for motorsport and car culture — the place a racer's whole path lives: their laps, their rank, what they've learned, what they've won. Around it runs a recurring championship that begins online and climaxes on a world stage, and a category we are the first to claim: eSim as a professional esport. Further out: every car captured and renderable, a player's identity carried into the real world, and a documented saga that runs season after season. We are not building a thing that ends. We are starting a line that keeps tracing.

3 · Why now

The pieces are aligned for a window that will not stay open:

Forza Horizon 6 is set in Japan and launches May 19 — the first Horizon on Japanese soil, a once-in-a-generation opening into a market and a culture.
Kingdom of Gaming lands in Riyadh Dec 1–3 — PIF-backed, government-aligned, investors in the room — a built-in world stage for the finale.
eSim is absent from the major esports stage (it isn't at the Esports World Cup) — the category is open, and first movers define it.
Saudi Arabia is the fastest-moving gaming capital on earth (Vision 2030), and we are positioned inside it through the holding.
The channels are warm now — a path to Xbox, to Qiddiya, to Super Formula — not cold outreach.
The technology crossed the line — photo → Gaussian splat → game asset makes a renderable world buildable, and creators give us reach we don't have to pay full price for.

The convergence is the reason to move fast. Late is the same as absent.

4 · What we are really doing (read this twice)

Underneath the business is a single act: we trace. A trace is a line laid down through time and made to stay. Reality is sampled from a vantage, along a line; what gets recorded is what becomes real and persists; integrate enough samples and the noise smooths into a coherent line — a lap becomes the racing line, a thousand moments become a story. Meaning is the smoothed line, never the single moment. Our work is to lay those lines, smooth them, and make them stay. The motorsport is the content of the trace. The trace is the point. (The full reasoning lives in First Principles.)

What that means for you: everything you do should lay a line, smooth a line, or make a line stay. If it does none of those, it's noise — cut it.

5 · Context — what you've joined

The company. rTracer sits under a holding company co-owned by LNK and Raven — a Saudi-led structure, government-aligned, with a path to lead in Qiddiya. We own what we build.
The program (the championship). One season, four moves: online qualifiers + creator hype → pop-up arcades (Japan + Saudi recruitment) → the Japan visit and trackside events at real Super Formula rounds (Fuji, Suzuka) → the grand final at Kingdom of Gaming, Riyadh. The prize is continuation — more races, more artifacts.
The product. rTracer is a super app made of many single-purpose mini apps, sharing one identity and one data ontology (the "data passport"). A zone is the 3D form of a mini app, where you can see who else is there. The first sprint collects only three things: vehicle, driver, experience. We self-host on Forgejo. Racers are gender-neutral — helmet always on. Brand assets live at rtracer.com/review.
The partners (the cast). Open lines: Microsoft/Xbox (via Eric), Super Formula/JRP, Racing Unleashed (Francisco Fernandez), Durhamtown (Mike, US/Atlanta), and Midori → Éric Boullier. We treat each as a real role in a real venture, win-win, with dignity.
The frame. We are making a documented film of real history — one continuous edit, released in real time. The only thing not scripted is who wins. (See The String of Movies.)
The canon (where to go deeper). First Principles — the why. Start Line Manuscript — LNK's procedure. Full Outline — the blueprint. Ledger — the live decisions. Partner Pipeline Tracker — the deal board. Super App Spec — the product. String of Movies — the documentary frame. Microsoft Deck Brief — the live pitch. This manual is the front door to all of them.

6 · The how — our method

We work as a single operation repeated at every scale. Learn the rhythm; it's how everyone here moves:

Stand — hold the mission as the frame. Measure work against the act, not the noise.
Cast — point your attention at the highest-signal target (what's nearest a partner yes, or lays the most line).
Trace — build it, run it, capture it. Ship the mini app, run the event, lay the line.
Record — cameras on. Document as you go; the making-of is part of the product. Nothing that matters happens off-camera.
Integrate — cut the noise down to the line. Edit, synthesize, rank, compress. Minimum viable signal.
Persist — send it, publish it, forge it. Nothing is real until it goes out; the sent version is canonical and seeds the next.
Loop — the output seeds your next task. Then go again, larger.

Operating principles that hold across all of it:

rTracer is the one constant; everything else is modular. Plug your work into the one identity and one ontology — that's what keeps a hundred mini apps coherent.
Ship small; let it collapse into core. Build the smallest useful thing; the ones that prove out become permanent features.
Own everything. Self-host (Forgejo). No leakage.
Publish in real time. It builds gravity, proves we're doing this either way, and is itself the record.
Subtract before you add. The blade: remove what obscures. Signal over volume, always.
Win-win or it's not a deal. Every partner and person gets a real benefit, handled with respect.
Coordinate through the shared record, not through gatekeepers. Update the ledger/tracker; claim your line so no one collides with it.

7 · How to create your own work (the engine of this manual)

You are not here to wait for tasks. You are here to find lines and run them to value. Here is the literal method.

What counts as value. A unit of value is one of:

a line laid — a real thing built, run, or captured (a mini app, an event, footage, telemetry, a relationship opened);
a line smoothed — noise turned into signal (an edit, a synthesis, a ranking, a decision made clear, a doc);
a line persisted — something sent, published, or forged so it stays (a formal comms, a release, an artifact, a credential);
a partner moved — a conversation advanced toward a commercial yes;
the category advanced — rTracer's public position strengthened.

If a piece of work is none of these, it is noise. Stop it.

The task loop (run this on your own):

Orient. Read the Ledger and the Pipeline Tracker. Know the mission, the current focus, the open lines, and what's nearest a yes.
Find the line. Spot where you can lay, smooth, or persist a line that advances the act — an unbuilt mini app, a partner waiting on a doc, footage to cut, an artifact to forge, an open decision you can resolve.
Define the task as an outcome. Write it: "By [date], I will [do X] so that [value: a line laid / smoothed / persisted / a partner moved]." Make it small enough to finish and fold into the whole.
Check alignment (the four gates). Does it serve the act? Does it use the one identity/ontology? Is it win-win for anyone involved? Is it the minimum viable signal (not gold-plated)? Four yeses → go. Any no → cut or reshape.
Claim it. Note it in the shared record so others don't collide. Own it end-to-end.
Run and record it. Execute; document as you go; self-host.
Persist it. Ship / send / publish, and fold it back into the shared record (codebase, ledger, content). Let it collapse into a core feature if it proves out.
Loop. Your output seeds the next line. Pick it and go again.

Decision heuristics (so you rarely need permission):

Default to action, and to shipping. A sent, imperfect thing beats a perfect draft.
Unsure what to do? Do the thing nearest a partner yes, or the thing that lays/smooths the most signal.
Cut anything off-axis before adding anything new.
Escalate only the irreversible, cross-cutting calls (engine choice, corporate structure, large spend, anything that touches every mini app). Everything else, decide and move.

Definition of done: shipped + documented + folded into the shared record — and, by default, public.

8 · How we organize

We run as small, owned lines, coordinated through shared docs — not a hierarchy of approvals.

The production house (LNK & the holding) sets the frame and the locked decisions.
Workstreams are where lines get run: platform & UI; deck & comms; content & documentary; partnerships & pipeline; events & ops. Most of you will own a line inside one and reach across as needed.
Autonomy with coordination. You generate and run your own tasks (§7). The shared record (Ledger, Tracker, the codebase) is how we stay coherent without slowing down — keep yours current, claim your line, hand off cleanly.
Everyone documents. You are crew on the film too; the making-of includes you.

9 · The standard

What "good" looks like here, every time:

Subtractive. Cut to the minimum viable signal. If it can be simpler, it isn't done.
Real. Documented, on the record, true. We don't fake; the unscripted result is sacred.
Shipped. Sent or published, not hoarded. Persisted, or it didn't happen.
Aligned. It serves the act and plugs into the one identity.
Considerate. Win-win, and dignity to every person in the frame.

10 · Cadence

Daily: advance your line, capture as you go, publish something, and update the shared record. Move the nearest partner yes.
Weekly: integrate — what got laid, smoothed, persisted; what's next-nearest to value.
The season: the program arc (online → pop-ups → Japan → final, Dec). Each ending seeds the next.

11 · The compact

By operating here you commit to a few things, and we commit them to you:

You hold the mission as the frame and generate work that creates value.
You ship and you document; you make things real by sending them.
You own your line and keep the shared record honest.
You treat partners and people as real, with respect and a real win.

In return: real ownership of your lines, the whole picture (this manual and the canon behind it), and a part in something we intend to make either way.

We are documenting history in real time. You have the mission, the method, and the means to create value without being told how.

Begin.