Operator manual · Revision 01 · Under review
How to use the Operator Dossier
The Operator Dossier turns the GD808 archive into a participatory record. Every interaction you make is logged against your personal dossier and accumulates over time. This manual explains in plain English what you are looking at and how to make use of it.
Section 01
What the dossier is
The Operator Dossier is a personal record inside the GD808 recovered engineering program. The program is presented as discontinued — you, as a participant, are either reviewing the archive or resuming operational work that was interrupted.
Inside the dossier you will find a weekly task (the cycle), a puzzle layer (anomaly drops), a permanent record of your contributions (stamps), and a list of upcoming evaluation sessions. None of it is required. All of it is recorded.
Section 02
Where you find it and how to access it
The dossier appears on the homepage at venturi.tv, directly under the hero video, but only when you are logged in.
First-time access
/operator-access.html. If you do not have an account, sign up.
OBSERVER. The first-recorded date is set to today.
Section 03
The header strip — your personal record
The top of the dossier shows four facts about you. None of them are editable directly; they update automatically as you interact with the system.
| Field | Meaning |
|---|---|
| CALLSIGN | Your username on the platform. |
| DESIGNATION | Your current operational role. Starts as OBSERVER. See section 08. |
| LAST ACCESS | How long since you last opened the dossier. Updates on every load. |
| FIRST RECORDED | The date your dossier was opened. Permanent. |
Section 04
The weekly evaluation cycle
The largest module on the dossier is the Configuration of the cycle.
One configuration runs each week, on a Monday → Sunday rotation. The current
configuration is shown in large monospace text (for example FC-X2-04).
What you see
- Configuration code — which prototype configuration is being evaluated this week.
- Window — the open and close timestamps of this cycle.
- Briefing — what the cycle is about and where to focus.
- Sector focus — the part of the test environment under particular review.
- Day strip (Mon → Sun) — highlights the current day of the cycle.
What you can do
Intent on file and
will not fire again. This is a low-effort signal; no submission is required.
#driver-briefing and discussion in
#run-logs.
CYCLE-<ref>.
Section 05
Anomaly drops and recovered identifiers
Anomaly drops are the puzzle layer of the system. The archive surfaces partial, redacted fragments of recovered material — for example a livery serial with missing characters, or a telemetry log with redacted speeds.
Each fragment contains a hidden identifier. Submitting the correct identifier into the
input box reconciles the fragment against your dossier and awards you a stamp coded
ANOMALY-<ref>.
How to attempt a recovery
█), and a citation.
Submit recovered identifier… input. Codes
are case-insensitive. Whitespace is ignored.
Reconciled: …— success. A stamp is recorded and the dossier reloads.No archive entry matches that identifier.— try again.Identifier already reconciled against this dossier.— you have already redeemed this code.Identifier window closed.— the drop expired before you found it.
Where to look for codes
Codes are deliberately surfaced in places that reward exploration. Possible sources
include archive footage on Venturi.tv, the Bezier Ridge environment in BeamNG (QR
panels and signage), Discord pinned posts, and product README files distributed via
Gumroad. Discussion in the #anomalies channel on Discord is the natural
place to compare findings.
Section 06
Clearance stamps
Stamps are the permanent record of your activity. Every cycle contribution, anomaly recovery, and session attendance produces a stamp on your dossier.
| Stamp prefix | How it is awarded |
|---|---|
| CYCLE-<ref> | Filing a submission against the active evaluation cycle. |
| ANOMALY-<ref> | Submitting a correct recovered identifier. |
| SESSION-<slug> | Marking attendance on a scheduled evaluation session. |
Stamps cannot be revoked, traded, or transferred. The grid auto-grows as you accumulate them. There is no overall point total — the number and types of stamps you hold determine your designation.
Section 07
Scheduled evaluation sessions
The bottom module lists upcoming sessions. Each session has a permanent page at
/session/<slug> that you can bookmark or share.
Per-row actions
- Click the configuration code (e.g.
FC-X2-04 · BEZIER RIDGE) to open the per-session page. - Click Mark attendance to file your intent to attend. This awards a
SESSION-<slug>stamp.
Per-session page lifecycle
The same URL evolves through three states:
| State | What it shows |
|---|---|
| Pre-session | Briefing, scheduled time, voice room link, attendance button. |
| Live | Same as pre-session, plus a marker that the session is in progress. |
| Post-session | Briefing plus a summary of what happened, and a pointer to the next session of this configuration. |
Section 08
Designations and how you progress
Your designation is shown in the dossier header in teal. It updates automatically each time a stamp is awarded. The current rules are conservative and are subject to revision.
| Designation | Requirement |
|---|---|
| Observer | Default. No stamps required. |
| Test Pilot | 3 or more stamps total, including at least one CYCLE- or SESSION- stamp. |
| Engineer | 6 or more stamps total, including at least one ANOMALY- stamp. |
| Chief Engineer | 12 or more stamps total, with 3+ ANOMALY- and 2+ SESSION-. |
Section 09
Discord and Gumroad — the wider universe
The dossier sits at the centre of three surfaces. Each surface has a defined role.
| Surface | Role |
|---|---|
| Venturi.tv | The archive itself. Recorded material, the Operator Dossier, session pages, the Lap Of The Week. |
| Discord | The discussion layer. Briefings, sector times, anomaly comparisons, voice sessions, in-character roleplay channels. |
| Gumroad | The distribution layer. Recovered configurations released as additional artifacts. Some anomaly drops reference codes printed in product README files. |
You do not need to use all three to participate, but participants who orbit between them earn stamps faster and progress further. The Discussion layer button on the cycle module is the simplest entry point.
Section 10
Privacy and data
Everything in your dossier is stored against your account on the same database that holds your profile. Stamps, redemptions, and attendance records are visible only to you and to platform administrators. No third-party tracking is involved.
Your callsign is your username. If you change your display name in your account settings, the dossier will reflect that change on next load.
Deleting your account removes all dossier records. There is no public dossier listing — other participants cannot see your stamps unless you choose to share them.
Section 11
Troubleshooting
The dossier is not visible on the homepage
You are probably logged out. Sign in and reload the homepage.
I marked intent but the button is back to normal
The button is keyed to the current cycle. If the cycle has rolled over to a new one, the new cycle starts with intent unfiled. This is intentional.
I submitted a code and got “No archive entry matches”
Check the code carefully. Codes are case-insensitive but otherwise literal. Spaces and punctuation are ignored only at the very start and end of your input. If the code is correct, the drop may have already expired.
My stamp count looks wrong
Hard-refresh the page (Ctrl+F5). The dossier always shows the server-side truth on load. If the count is still wrong, contact an administrator.
The session page says “Authentication required”
Per-session pages require a session because they record your attendance against your operator record. Sign in and the page will reload.
Appendix A
Visual language
The dossier surface uses a small set of marks that recur across the archive: on fragments, on stamps, in the header, and in administrative records. The mapping between a mark and its meaning is not labelled inside the dossier itself. Operators are expected to recognise the marks through repeated encounter.
This appendix records the marks for reference. The same marks appear elsewhere in the program — in printed material, in test environment signage, and in archive footage — without explanation. Recognising them outside the dossier is part of the evaluation.
Program seal
The octagonal GD808 sigil identifies material as belonging to the
program. It is the only mark that is permitted to appear on its own without
accompanying text.
Provenance glyphs
Every recovered fragment carries one of five provenance marks in its top-right corner. The glyph indicates the kind of source the fragment was extracted from. The mapping below is provided here once. It is not repeated on the dossier.
Status marks
Status marks accompany drops, cycles, and sessions in administrative views. They are also embedded in archive listings.
Stamp seals
Each stamp on a dossier carries one of three seal marks indicating the activity that produced it.
Appendix B
Reference plates
The plates below are referenced by other archive material. Some are recovered from photographic sources and are reproduced as found; some remain pending recovery and appear here as placeholders. The generation parameters used to produce each plate are recorded alongside, for archival continuity.
Generation parameters
Generation parameters
Generation parameters
Generation parameters
Generation parameters
Generation parameters
Plates marked Pending recovery are reproduced from generation parameters rather than original photography. When original material is recovered, the plate window is replaced with the photographic source. The generation parameters remain on file regardless.