Skip to content
⌖ Field Manual

Operating the examination engine

Everything a specimen (or a builder) needs to understand what ABDUKT does to your input and how the report is assembled.

Overview

ABDUKT is an alien “examination engine.” You beam in any input — a sentence, an idea, a token name, a paste from your group chat — and Field Officer ZORB files a structured Galactic Field Report on it. The report ends with an Anomaly Index from 0 to 100 and a verdict stamp.

The one-linerYou are the specimen. Beam something in, get examined, share the report.

The examination

Every input runs the same four-stage pipeline. The order matters — it's a real sequence, not decoration.

StageWhat happens
1 · CLASSIFYThe specimen is logged and assigned a designation (e.g. SPECIMEN A6-4417).
2 · DECODEZORB reads the input literally and extracts the subtext underneath it.
3 · SCANThe chosen instrument (BIOSCAN / MINDPROBE / THREATNET) analyses the specimen.
4 · VERDICTAn Anomaly Index 0–100 is computed and a stamp is applied. Report filed.

ZORB's voice

ZORB is a deadpan xenobiologist. The tone is clinical, certain, and quietly unimpressed — like a scientist describing a mildly interesting bug. ZORB never breaks character, never uses emoji, and treats every specimen with the same flat professionalism.

Voice rulesClinical, not cruel. Specific, not sweary. Funniest when it's accidentally accurate. ZORB observes; the Anomaly Index judges.

Instruments

Three lenses examine the same specimen and reach different conclusions. Pick one before you beam in.

01

BIOSCAN

Reads the input as a life-form: subspecies, habitat, behaviours.

02

MINDPROBE

Skips the words and extracts the specimen's actual intent.

03

THREATNET

Rates the specimen against galactic incident logs: asset, noise, or anomaly.

Anomaly Index reference

The single number that every examination resolves to. Bands and their stamps:

RangeStampReading
0–24HARMLESSBackground specimen. No intervention required.
25–49CURIOUSMildly interesting. Flagged for passive observation.
50–74ANOMALYDoes not fit the model. Continued study advised.
75–100ABDUCTTractor beam recommended. For science.

Report anatomy

Every Galactic Field Report is built from the same blocks:

BlockContents
HeaderDesignation + instrument used.
ClassificationSubspecies / intent profile / threat class (depends on instrument).
DecodeThe specimen's input, read literally, with subtext extracted.
Observations2–3 clinical, deadpan field notes.
Anomaly IndexScore 0–100 + verdict stamp.
ClosingOne shareable transmission line. Filed by ZORB.

$ABDUKT

FieldValue
Total supply1,000,000,000
Team / insiders0%
Tax (buy / sell)0 / 0
LiquidityBurned
Launch25 Jun 2026 · 17:00 UTC · fair launch on pump.fun
ContractTBA
Buy on pump.fun Dexscreener
Not financial advice$ABDUKT is a meme. Examine responsibly and never beam in more than you can afford to lose.

Build notes

For tinkerers. The examination is served by a small backend; the frontend ships static. Wire API_BASE in js/config.js to go live — leave it empty to run the local ZORB simulation.

# health
GET /api/health → { ok: true }
# examine a specimen
POST /api/examine
{
  "input": "wen moon",
  "instrument": "MINDPROBE"  // BIOSCAN | MINDPROBE | THREATNET
}

// → response
{
  "instrument": "MINDPROBE",
  "anomaly": 72,
  "verdict": "ANOMALY",
  "report": { classification, decode, observations, closing },
  "remaining": 11
}
Single source of truthThe contract address lives in one place: js/config.js. On launch, paste the mint, upload that one file, purge cache. Buy and copy work whether or not the token is live.
StackStatic HTML/CSS/JS frontend · Fastify + TypeScript on Node 22 · Supabase for quota/logging · OpenRouter (Claude Haiku) plays ZORB.

FAQ

Is ZORB a real alien?

No. An AI persona with a clipboard. No xenobiologists were verified in the making of this.

Does my input get stored?

The demo runs entirely in your browser. A wired backend may keep minimal logs for rate-limiting — see build notes.

Can I run my own instrument?

The three lenses are fixed for now. Beam feedback at the team via the links below.