KN-86 Mission-Type Catalog — player class names → Tier-3 verbs

../../../plans/post-v0.1/2026-04-25-mission-composition-grammar.md — the closed Tier-3 verb set + affinities + composition algorithm (the source of truth for the verbs this doc names)
../../../plans/post-v0.1/2026-04-25-mission-genre-templates.md — named arcs (HEIST / EXPOSE / ELIMINATE / …): sequences of types
../../../plans/post-v0.1/2026-04-25-mission-shape-grammar.md — topologies (MONO / CHAIN / BRANCH): the structural shape a type-sequence runs in
verb-taxonomy-map.md — the Tier-2 verb-tools each cart contributes (a different tier — what you do, not what the job is)
../../runtime/mission-control.md — the board surfaces a type as a contract class (§4.1); a cart declares its types as :provides capabilities (§2.1)
../../runtime/mission-objectives.md — a type is realized as an objective graph
../../gameplay-framework.md — fills gap A of its open-gap ledger
ADR-0028 — Mission Control & the closed Tier-3 verb set

1. What a “mission type” actually is

A player names a job by its type — “that’s an extraction,” “this is a sabotage run.” Mechanically, a type is one cell of a small product:

   mission type (class)  =  Tier-3 verb  ×  affinity (domain)

The Tier-3 verb is the shape of the job — the closed, DeckRunner-owned set (ADR-0028 / the MCG plan). There are ten: PENETRATE · OBTAIN · ANALYZE · DELIVER · DESTROY · OBSERVE · COMMUNICATE · MANUFACTURE · NEGOTIATE · DECIDE.
The affinity is the domain it happens in — NETWORK, MARITIME, FINANCIAL, SIGNALS, TERRITORY, … (the affinity set lives in the MCG plan).
The class is the player-facing noun the board prints — PENETRATION, EXTRACTION, SABOTAGE, SURVEILLANCE (mission-control §4.1). A cart declares the classes it can satisfy as :provides capabilities — e.g. ICE BREAKER’s (:network-penetration :network-extraction :network-sabotage :network-surveillance) is {PENETRATE, OBTAIN, DESTROY, OBSERVE} × NETWORK.

This catalog is only that mapping. It does not own the verbs (the MCG does), the arcs (genre templates do), the topologies (shape grammar does), or the moment-to-moment actions (Tier-2 verb-tools do). It is the dictionary between “what the player calls it” and “what the engine composes.”

Where types sit in the stack:

   genre arc        (HEIST = OBSERVE→PENETRATE→OBTAIN→DESTROY…)   ← a sequence of TYPES
      └─ type/class  (EXTRACTION = OBTAIN × domain)               ← THIS DOC
            └─ Tier-3 verb (OBTAIN)                                ← MCG plan
   shape topology    (CHAIN / BRANCH / MONO)                       ← how the sequence runs
   objective graph   (the goals that realize the type)             ← mission-objectives.md

2. The catalog

Single-verb types — the player vocabulary, mapped to the closed set:

Class (board noun)	Tier-3 verb	What the job is	Example domains
PENETRATION (breach)	PENETRATE	gain access to a defended target	NETWORK (ICE BREAKER), guarded compartment (DEPTHCHARGE)
EXTRACTION (exfil)	OBTAIN	acquire an asset and bring it out	data, cargo, credentials / keys, evidence
INFILTRATION (plant)	DELIVER	move a payload in — plant/forge/drop	false records, a beacon, a data drop
SABOTAGE (incl. DoS)	DESTROY	sabotage, corrupt, or render unusable	network asset, signal, evidence trail
SURVEILLANCE (recon)	OBSERVE	gather without intervention; passive collection	a tail, a wiretap, reconnaissance
ANALYSIS (audit)	ANALYZE	interpret, decode, or synthesize information	ledger, cipher, archive, market signal
DELIVERY (courier)	DELIVER	move a payload A→B (transport sense)	package, cargo, data drop
BROADCAST (contact)	COMMUNICATE	transmit, broadcast, or make contact	pirate broadcast, update push, dead drop
FABRICATION	MANUFACTURE	produce an artifact (identity, compound, graft)	0 launch satisfiers — concept carts
NEGOTIATION	NEGOTIATE	convert influence/leverage into outcome	0 launch satisfiers — concept carts
COMMITMENT	DECIDE	a strategic, irrevocable move	territory placement, market position, tactical move

Class nouns are domain-flavored when surfaced — the board may print “NETWORK INTRUSION” or “MARITIME SALVAGE” rather than the bare class — but the underlying (verb × affinity) is what this table fixes.

3. The exfil ↔ infil mirror (the symmetry worth naming)

The two directions of moving an asset are distinct verbs, and that symmetry is the spine of the catalog:

Direction	Verb	Class	The job
asset out	OBTAIN	EXTRACTION	steal data, lift cargo, take the keys
payload in	DELIVER	INFILTRATION	plant false records, drop a beacon, seed a forgery

Key theft is an EXTRACTION whose asset is encryption keys — mechanically OBTAIN; narratively it then feeds the knowledge/access economy (../../runtime/currency-and-economy.md).
Infiltration that fabricates first is a two-verb arc — MANUFACTURE → DELIVER (forge the artifact, then plant it).
DoS is a SABOTAGE (DESTROY, “render unusable”). Per the 2026-06-21 decision it is narrative flavor on SABOTAGE, with no mechanical distinction from permanent destruction — a “knock it offline” brief and a “burn it down” brief are the same class, differently dressed.

4. Composite “types” are arcs, not types

Some things players call a “type” are actually sequences of types — they belong to the genre-template / shape-grammar layer, not here:

Player name	Decomposes to	Lives in
AAA (Access · Analyze · Acquire)	PENETRATE → ANALYZE → OBTAIN	a CHAIN arc (genre templates)
Heist	OBSERVE → PENETRATE → OBTAIN → (DESTROY cover)	HEIST genre template
Revenge / frame-up	OBSERVE → MANUFACTURE → DELIVER → ANALYZE	REVENGE genre template
Recon-then-strike	OBSERVE (recon) → any operational type	the recon phase (gap C) + a genre arc

Rule of thumb: one verb = a type (this catalog); a verb sequence = an arc (genre templates), run in a topology (shape grammar).

5. How a type reaches the player

A cart declares the types it can satisfy as :provides capabilities (= verb × affinity) in register-capabilities (mission-control §2.1).
Mission Control composes a contract — picking verb(s), affinity, threat, TTL — and prints its class on the board (mission-control §4.1).
On accept, the type is realized as an objective graph (mission-objectives.md) — e.g. an EXTRACTION’s goals are “reach the store, OBTAIN the asset, exit clean.”
The operator executes it through capabilities (Tier-2 verb-tools or a mini-game) in the Mission Runner.

So the catalog feeds steps 1–2 (the naming) and frames step 3 (what objective spine a type implies).

6. Decisions logged (2026-06-21)

The Tier-3 set stays closed (ADR-0028). No new mission verbs were added; the player’s full type vocabulary maps onto the existing ten.
INFILTRATION = DELIVER (payload-in), the mirror of OBTAIN (asset-out); fabricate-then-plant = MANUFACTURE → DELIVER.
DoS = DESTROY, surfaced as SABOTAGE, flavor only (no :transient mechanic).
Key theft = OBTAIN (EXTRACTION of keys).
AAA and other multi-verb “types” are arcs, owned by the genre-template layer, not this catalog.

7. Open / deferred

Recon as a player-elected phase (gap C, ../../gameplay-framework.md) — SURVEILLANCE is the type; the repeatable, player-paced recon mode that deposits DOSSIER keys is specified separately.
MANUFACTURE / NEGOTIATE are under-satisfied in the launch library (0 satisfiers each; concept carts CLONESHOP / HOSTILE TAKEOVER close them per the MCG plan). FABRICATION and NEGOTIATION classes exist in the catalog but won’t appear on the board until a cart provides them.
Affinity coverage gaps (BODY / CHEMICAL / IDENTITY / SOCIAL — ≤1 satisfier each) are tracked in the MCG plan, not here.