OPERATOR DESK PROVENANCE

Operator.

Radar Six is run by a single operator. The desk is pseudonymous by design. This page records the verification artifacts and the authority record so a reader can audit who is publishing and how decisions are logged.

Identity

Display name: Radar Six. The operator role is pseudonymous by design. Pseudonymity here is not anonymity: the same key signs every identity-linked surface, and the keypair is published below for cryptographic comparison. Pseudonymity exists so the desk can write honestly about Take-Two Interactive, Rockstar Games, and the wider publisher cohort without the legal-pressure surface that a named analyst would carry.

Verification

Two identity surfaces cross-reference one another and share the operator PGP keypair. A reader who wants to verify that a published claim came from the same operator can compare the fingerprint below against the Keybase profile and the Mastodon account bio.

Keybase: keybase.io/radarsix
Mastodon: mastodon.social/@radarsix
PGP fingerprint: FFD0 4219 D4CB E831 CBB8 8EB8 2771 6FBB C53F 5535

The fingerprint above and the Keybase profile share the same public key. Verification path: the Keybase page renders the same fingerprint and proves operator control of the linked identities.

Decision authority

Every gate flip, every claim verdict, every source activation, and every voice-profile rule lives in the source repository. The audit trail is the operator's authority record. Two surfaces carry it.

Commit history: Each operational decision lands as a commit. Subject lines name the change, commit bodies cite the audit reason, the verification steps, and the rollback path. Pre-commit verification runs voice profile checks and regression tests before any change is shipped.
Closure documents: Larger work lands a closure document in the source repository under the docs directory. Closure documents record the state at time of shipping: gate posture, observation counts, dry-mode invariants, and the operator sign-off artifact for any authority change.
Operator approval: Hermes, the agent that drafts and verifies changes, never flips a Phase B gate, never enables paid generation, never mutates published content, and never publishes to a platform without explicit operator sign-off in advance. The audit trail records which decisions came from the operator and which came from the agent.

Corrections

When a claim verdict is changed or a published surface is corrected, the change is recorded in the corrections log. The corrections page carries the running list with original wording, revised wording, and the trigger that produced the correction.

Corrections log records every public correction with the original and revised text.

Editorial principles

The voice profile and the published rules every surface is audited against are documented in one place. A reader who wants to flag a published surface for review can compare it against the bans and the required patterns listed there.

Style guide records the voice profile v1, the banned patterns, and the required patterns every surface must carry.

How the desk works carries the longer-form methodology framing alongside the same provenance summary.
Methodology documents the verdict ladder, source tier classification, and Phase B gate posture.
Live feed is the dry-mode observation surface where claims are scored before the operator locks a verdict.
Subscribe opens the email follow path with the same operator-led editorial cadence.