OPTOMON Glossary

What this is. A vocabulary that gives OPTOMON a shared shorthand for the discipline of trading. The terms below are organized into three sections: (A) OPTOMON-native (terms invented for this platform); (B) Transmutated from skydiving (terms adapted from the parachuting lexicon, where the analogy is precise enough to be useful); and (C) Cross-walk index (skydiving term → OPTOMON term, for readers coming from the source material).

What this isn't. A glossary of generic options-trading terminology. Standard terms (delta, gamma, IV, OTM, ITM, etc.) are defined in docs/glossary/OPTIONS_GLOSSARY.md (forthcoming) — this document is the OPTOMON-specific lexicon layered on top of standard knowledge.

---

A — OPTOMON-native terms

A.1 Optimeter

The per-opportunity deal/timing meter at the core of OPTOMON. NOT a portfolio risk gauge. For a single position (or a single planned entry), the Optimeter expresses the deal's current standing relative to the system's projected trajectory: how much room is left, where the system says to act, and how far the position has drifted from optimal. Visually rendered as a horizontal timeline-band with system-entry / system-exit markers, user-entry / user-exit markers, and a now-cursor moving across.

Reading guide: Reading the Optimeter — Dial vs. Mountain walks through both layouts, the shared zone vocabulary, and how to choose a default in Settings → Cockpit.

A.2 Zone

A categorical label the Optimeter assigns to a position's current standing. Five zones in order along the deal-life timeline, derived from the days to system exit:

CONSTRAINT-LOCKED and LTCG-CLEARED are overlays on a zone, not zones of their own. CONSTRAINT-LOCKED marks a DECIDE, APEX or DECAY position that has not yet passed its 12mo+1d hold (§ A.4, § A.5). LTCG-CLEARED marks a position past that day, in any zone. On the Dial the overlay's name replaces the zone word; on the position list and detail pages a LOCKED chip sits beside it. The full table is in Reading the Optimeter — Dial vs. Mountain.

Zones drive the LCD's color-state language across all surfaces (banners, alerts, glyphs, charts).

A.3 Loud Calm Display (LCD)

The mobile-first UI design language. Loud in critical moments (Apex/Decay flashes, alert banners, two-step confirmations); Calm by default (monochromatic neutrals, minimal chrome, no chart noise). Codified in @options-platform/brand-design-system (BDS).

A.4 Constraint Lock

A flag on a position indicating that an external constraint is preventing the system-recommended action. The canonical example is the LTCG window: a long-term capital-gains hold of 12 months + 1 day before a profitable exit becomes a long-term gain rather than short-term. While the lock is active, the Optimeter renders the exit marker as constrained-in-place; the system doesn't recommend exiting profitably until the lock clears.

A.5 LTCG Window

The 12-months-and-1-day hold required (in the U.S.) before a profitable position is taxed at long-term capital-gains rates rather than short-term. OPTOMON tracks this per position; the Optimeter renders the LTCG-clear day as a milestone on the deal timeline.

A.6 Two-Step Trade Auth

Order-placement gating distinct from login MFA. After login (with TOTP), the act of submitting an order re-prompts the user with a separate confirmation step. Aligned with TastyTrade's customer-side 2FA policy and specified in the Apr-1 client meeting.

A.7 DRY_RUN Default

The broker package's default operating mode. Order placements always route through TastyTrade's /orders/dry-run endpoint instead of /orders until all three conditions hold: DRY_RUN=false AND environment='production' AND LIVE_TRADING_CONFIRMED=YES_<accountNumber>. The triple-flag gate keeps live wire calls behind an unmistakable opt-in.

A.8 Trade Path

The hard-segregated order-execution code path. Lives in packages/brokers/tastytrade + services/trading-service. Forbidden from importing the Aux Layer; enforced by scripts/lint/no-execution-leak.ts.

A.9 Aux Layer (Auxiliary Monitoring)

The hard-segregated monitoring code path. Lives in packages/market-data

• services/market-data-service. Provides quotes, fundamentals, options chains, bar history for thinking, never for executing. Forbidden from importing the Trade Path.

A.10 Tenant

A logical "book" — one user's set of broker credentials + the projection data sourced from them. A user can own multiple tenants (Personal, LLC, Trust) and can be granted Advisor membership on tenants they don't own. See 06_MULTITENANCY_*.md.

A.11 Vault

The end-to-end encrypted credential store. Each user holds a vault key derived from a passphrase (Argon2id) or a device WebCrypto key; broker session tokens / API keys are AES-GCM encrypted client-side and persisted as ciphertext only. The server cannot decrypt under any circumstance.

A.12 Flight Plan

A curated configuration of (a) entry/exit rules + thresholds for a class of trades, (b) advisor-message routing and approval bands, (c) alert delivery channels. Replaces the term "playbook" used in earlier docs. See 06_FLIGHT_PLANS.md for the full spec. The skydiving etymology — a flight plan is a pre-jump briefing covering deployment altitude, breakoff signals, abort criteria, and group coordination — is structurally exactly what OPTOMON Flight Plans codify for a trading session.

A.13 Advisor (persona)

A user granted scoped, read-only-plus-draft access on a foreign tenant. Cannot place orders. Sees what the tenant owner permitted; can prepare draft tickets with comments for owner review. Renamed from earlier "broker_user" to avoid the regulated term "broker."

A.14 Persona Toggle

A control that lets a user with multiple assigned roles switch their active view (e.g., super_admin / developer / end_user / advisor). The same login identity, different content surfaces. David, as super_admin + developer + end_user, sees all three modes; Glen, as advisor + end_user, only sees the two he's been assigned.

A.15 Loud Quote

A quote rendered in the loud color of its Zone (Apex orange, Decay red, etc.) when the underlying position is in that zone. Otherwise quotes are rendered Calm.

A.16 Provenance Stamp

Every quote, position, fundamental, and derived metric the cockpit shows carries a small provenance tag indicating the source (e.g., alpaca-basic, tastytrade-stream, sec-edgar, mock-fallback) and a freshness timestamp. The tag is unobtrusive but always present. The user should never have to wonder which vendor served their data.

A.17 Mock Fallback

A graceful-degradation marker indicating that a live data fetch failed and the displayed value is from a deterministic mock. The cockpit shows a banner when any active feed is in fallback. (Session 05 § non-obvious decision 2 + Session 06 06G card.)

A.18 Vendor-Aware, Not Vendor-Dependent

OPTOMON's architectural posture toward broker / market-data providers. The platform supports TastyTrade and Alpaca as first-class peers; users can connect either or both per tenant; data engines have 2+ source streams with graceful fallback; provenance is always surfaced. No single vendor is load-bearing.

A.19 Optimeter Dial

The altimeter-style gauge presentation of the Optimeter. Brand color binding for markers (shared with the linear Optimeter):

Same data, same five-state vocabulary (HOLD / WATCH / DECIDE / APEX / DECAY), same CONSTRAINT-LOCKED and LTCG-CLEARED overrides — different read. The active scale sweeps ~270° clockwise from 7:30 (day 0, entry) to 4:30 (gauge max); the 90° wedge at the bottom is empty by design and houses the STATE + countdown sub-windows. A gold radial line

• "12mo+1d" pill mark the LTCG-clear day at its proportional angle along the arc — answering "how close to tax-clear?" at a glance.

Coexists with the linear Optimeter Mountain (the profitability-curve view at A.1); both render off the same OptimeterFrame and both consume zone state from lib/optimeter/zone.ts. The user toggles between them per-card with the in-position pill, and sets a default via /settings/cockpit.

See also: Reading the Optimeter — Dial vs. Mountain — full reading guide for both layouts, including state-badge semantics and γ-peak divergence behavior.

A.20 Word-Formulaic Synopsis (WFS)

The deterministically-generated textual concordance of an Optimeter position. Same data → same string, byte-for-byte. Every marker on the Dial and the Mountain has a corresponding clause-fragment in the WFS; the WFS is the alt-text twin of the visual rather than its prose paraphrase.

Surface forms (one underlying state → five canonical renderings):

The WFS is not prose generation — no LLM call, no temperature. The grammar + decision DAG fully specify every emitted clause; see FC-002 Word-Formulaic Synopsis for the canonical spec, FC-002a Math & Finance Underpinnings for the formal definition of every slot value, and FC-002c WFS Long-Form Briefing for the narrative-format spec.

Example for a TSLA long call at day 153 of 473, HOLD zone, LTCG locked:

TSLA · LONG_CALL · -20.3% · day 153/473 (32% in) · HOLD
◇ CONSTRAINT-LOCKED — 213d to LTCG

Greeks @ IV 0.56: Δ 0.18 · Γ 0.005 · θ -$12.70/d · ν 8.4 · ρ 1.2

System: BUY D0 → SELL D450. User: ◆ FILLED D4, EXIT ↻ FOLLOW.
γ-peak D310 (140d before sysExit).

ACTION → HOLD — needle inside the green window, +297d to sysExit (>14d HOLD threshold).
LTCG → WAIT — 213d to clear (D366). Exiting now ⇒ short-term capital-gains tax.

A.21 OOC (Options-Opportunity-Cycle)

The OPTOMON unit of work. The full lifecycle of a trade idea from screener hit to post-mortem, encompassing the 7 stages Spawn → Evaluate → Stage → Open → Manage → Close → Post-mortem. Distinct from a Position (which only spans Open→Close) and from a Watchlist (passive interest, no hypothesis).

Reading guide: What is an OOC?

A.22 Options Opportunity Cycle

The unabbreviated form of OOC. Used in prose where the acronym would be opaque; the canonical short form is "OOC."

A.23 Spawn / Evaluate / Stage (OOC lifecycle stages 1–3)

The pre-trade stages of an OOC. Spawn creates the OOC from a screener hit, alert, or manual entry — ticker + hypothesis only. Evaluate opens the Eval Workspace and reviews scorecard + hypothetical Optimeter. Stage picks a strategy template and persists a candidate ticket, still pre-order. Stages 4–7 (Open / Manage / Close / Post-mortem) cover the live trade and its debrief.

A.24 IV Rank

A 0–100 scale measuring where today's implied volatility sits within the ticker's own past-52-week IV range. Rank 0 = at the year's IV low; rank 100 = at the year's IV high. Distinct from IV percentile (which counts days below current IV). Premium-selling strategies prefer ≥ 50; long-options strategies prefer ≤ 40.

A.25 Strategy Template

A pre-shaped trade structure offered at the Stage step of an OOC: legs, strike geometry, and exit rules pre-sketched. OPTOMON ships five system templates (Covered Call, CSP, Vertical Credit Put, Iron Condor, Diagonal Call); custom templates can be added later. The template ensures structural coherence — the user picks strikes and size.

Reading guide: Strategy Templates Explained

A.26 Tier-Gated

A feature available only above a given subscription tier. On Massive Options Basic (free), the screener interface is visible but result rows are locked beyond the top 3; upgrading unlocks the full result set, 15-min-delayed live option chains, and saved scan presets. Tier-gating is content-side only — the Trade Path and Vault are not tier-gated.

A.27 Hypothetical Optimeter

The Optimeter variant rendered on the Eval Workspace for an OOC that has not yet been opened. Same visual language (dial / mountain toggle, same brand color binding) but the trajectory is projected, not lived. Zone overrides like CONSTRAINT-LOCKED only fire once the trade is opened, because the LTCG window clock starts at user-entry day.

---

B — Transmuted from skydiving

Each entry: OPTOMON term — definition. Then ← origin: <skydiving term> with a note on the metaphor's load-bearing structure.

B.1 Auto-Stop

Automated kill-switch that closes a position when a hard threshold (price, time, P&L) is breached. Mechanically activates without user intervention — the trader's "last line." ← origin: AAD (Automatic Activation Device). In skydiving the AAD fires the reserve at a preset altitude+descent rate if the jumper is incapacitated. In OPTOMON, the Auto-Stop fires the close when the trader is asleep, distracted, or dead-frozen. Same role: protect against the unable-to-act case.

B.2 Decision Threshold

A pre-committed price or time level at which the trader has agreed (with themselves, in the Flight Plan) to act — close, roll, hedge, or hold. Below this level, latitude is constrained. ← origin: DECISION ALTITUDE. In skydiving, the altitude at which a malfunction must trigger emergency procedures — typically 2,500 ft AGL for students, 1,800 ft for experts. The discipline is identical: pre-commit the level, act when crossed.

B.3 Hard Floor

A no-trade-after time threshold per session or per position. Below this floor, no entries; only exits, hedges, or no-action. ← origin: HARD DECK (CRW). The altitude after which no more incoming canopies may dock to a CRW formation. In OPTOMON, the floor below which no new bets are made.

B.4 Forced-Exit Zone

A condition on the position where the system will close it without asking — typically when Decay is severe AND the trader is non-responsive (no acknowledgment to alerts within configured window). ← origin: BREAK ALTITUDE / BREAKOFF. In a skydiving formation, the predetermined altitude at which all jumpers must turn 180° from the center and track to clear airspace. Same idea: the deal is over; everyone separates.

B.5 Pre-Trade Briefing (Flight Plan readout)

The structured review a trader (or trader+advisor) does before opening a position: Flight Plan, max risk, decision thresholds, exit signals, advisor notes. Codified as the "open Flight Plan" UI flow. ← origin: PRE-JUMP BRIEFING. Universal in skydiving; the dirt-dive + plan walkthrough is non-optional.

B.6 Dirt Dive

Paper-trade rehearsal of a setup, run through the proposed legs / fills / levels without putting money at risk. Used to confirm the mechanics before the live trade. ← origin: DIRT DIVE. Direct semantic carryover.

B.7 Stable Posture

The default in-trade discipline: rules-following, no improvisation, constant proximity to the Flight Plan. ← origin: ARCH (stable freefall position). In skydiving, the "hips forward, back arched" baseline that lets every other maneuver emerge from control. In OPTOMON, the posture from which every active management decision is made.

B.8 Pre-Exit Wave-Off

A signal — visual on the cockpit, alert via channels — that the trader is about to close. Used to coordinate with advisors who may have outstanding draft tickets so they don't fire conflicting suggestions. ← origin: WAVE OFF. Pre-deployment arm signal to nearby jumpers.

B.9 Post-Trade Debrief

Post-position-close review: what was briefed, what happened, where the deviation was, what to improve. Generates a record attached to the position's audit trail. ← origin: DEBRIEF. Direct carryover.

B.10 Pre-Trade Self-Check

A short, ritualized pre-submit checklist: Flight Plan loaded? Decision thresholds set? Auto-Stop active? Position size within Risk Floor? ← origin: CHECK OF THREES. Pre-jump self-check (3-ring release / harness attachment / 3 operation handles).

B.11 Decision Cascade

The chain of triggers — alert fires → decision threshold crossed → auto-stop arms → pre-exit wave-off → close. Each link is configurable in the Flight Plan. ← origin: CASCADE. The point where multiple suspension lines join.

B.12 Loud-Quote Burble

The brief liquidity gap that follows a fast move — the "no-fill zone" behind the printed price. Quotes inside the burble are stale/illusory. ← origin: BURBLE. The turbulent-air zone behind a freefalling body or flying canopy.

B.13 Hook Risk

A late, aggressive maneuver — closing a position at the last minute with high-leverage urgency, often in chase of an outsized exit. High-payoff if timed right; high-loss if mistimed. ← origin: HOOK TURN. "Sudden turn close to the ground (90°+) used to build up speed for a spectacular landing. When misjudged, smashed bones." The trading analog has the same risk profile.

B.14 Forced-Out Position

A position closed not on signal but because of an external mandate (margin call, regulatory window, expiration). ← origin: OUT LANDING. Off-target / off-DZ landing — the jumper is on the ground regardless of whether they wanted to be.

B.15 Trading Window

The active session boundary (market hours + extended-hours configuration) during which the platform is in monitoring + execution mode. ← origin: DROP ZONE / DZ. The notified airspace within which jumps occur.

B.16 Fall Rate

A position's velocity of value change — the magnitude of P&L delta per unit time. Distinct from theta (time-decay-only); fall rate combines underlying movement + time + IV. ← origin: FALL RATE. The speed at which a skydiver falls. Matching fall rate is essential to formation flying — same in trade-pair management.

B.17 Tracking

Riding a directional move toward the exit, taking maximum advantage of the trend. ← origin: TRACKING. Horizontal movement in freefall, used to clear group airspace before deployment. The metaphor in OPTOMON: ride the trend, then deploy your exit.

B.18 Senior Advisor (rating)

The Advisor persona equivalent to a USPA Instructor — experienced, with a track record of useful suggestions for the granting tenant. Rating maintained per advisor per tenant; visible on the advisor's profile chip. ← origin: JUMPMASTER / INSTRUCTOR.

B.19 Coach (advisor entry-level)

Lower-tier advisor rating — newer, less context, suggestions weighted more conservatively in the Flight Plan approval bands. ← origin: COACH (USPA).

B.20 Flight Pattern (exit pattern)

The structured close path: typically (a) initial trim / partial close, (b) re-evaluate, (c) full close at decision threshold. Reduces "panic close" slippage. ← origin: LANDING PATTERN. Three-leg approach (downwind / base / final).

B.21 Position Drift

The accumulated displacement of a position from the Flight Plan's projected trajectory — how far the actual is from the briefed. ← origin: DRIFT (uppers vs surface winds). Wind drift requires the spotter to compensate for it; in OPTOMON, drift triggers re-evaluation.

B.22 Pre-Position Spot

The pre-entry analysis that selects timing + level for the planned trade. ← origin: SPOT / SPOTTING. The pre-exit selection of the jump point.

B.23 Currency

Whether the trader has been engaged with the markets recently enough to be "current" — fresh on intraday flow, rules, broker quirks. Used in Flight Plan approval bands (e.g., a non-current trader's drafts are auto-flagged). ← origin: CURRENT. "To be current is to have jumped recently enough to retain proficiency."

B.24 Risk Floor

The platform's hard caps on per-position exposure, leverage, daily loss, etc. — non-negotiable, configured per tenant. Trades exceeding the floor are rejected at draft time. ← origin: BSR (Basic Safety Requirements). USPA's minimum safety standards; non-optional even for experts.

B.25 Hard Close

Immediate, market-order, all-or-nothing close — used in emergency to exit a position regardless of slippage. ← origin: CUTAWAY. Releases the main canopy from the harness so the reserve can deploy. Same idea: shed the bad position so you can survive.

B.26 Panic Button

The UI control that triggers Hard Close on a position. Mounted prominently on the position detail; behind a 2-tap confirm. ← origin: CUTAWAY HANDLE.

B.27 Double-Stop / Doubled-Out

A position where both legs of a hedge stopped out (downside protection + upside cap both fired). Net result: full P&L lost on the hedge structure. ← origin: DOWN PLANE. "Both main and reserve deployed and pointed toward the ground." Two protections firing simultaneously is, paradoxically, the worst case for a parachute system. Same here.

B.28 Oscillation

Repeated opening + closing of similar positions in a short window — indicates lack of discipline or whipsaw conditions. ← origin: OSCILLATION (canopy swinging). Pendulum motion under canopy.

B.29 Bag Lock

A failure mode where the trade deployment system has fired (order placed) but the order is hung (working / partial-fill / rejected) and won't finalize. Triggers an alert and an auto-recovery path. ← origin: BAG LOCK. Lines deployed but canopy still trapped in deployment bag.

B.30 Trim

A small, partial-size adjustment to the position — closing one leg, rolling a strike, scaling out. ← origin: TRIM (canopy angle of attack). Fine-tunes the glide.

B.31 Snivel

An abnormally slow position fill / late open — the order is being filled across the book gradually, sometimes at worsening prices. ← origin: SNIVEL. "Abnormally slow canopy opening."

B.32 Wind Drift Indicator (WDI)

The platform's ambient-conditions readout: VIX, market breadth, sector rotation, news intensity. Used to anticipate slippage on entries / exits. ← origin: WIND DRIFT INDICATOR. The literal weighted-paper streamer dropped before a jump to measure drift.

B.33 Funnel

A formation skydiving term carried over: when one trade goes sideways and drags adjacent trades into bad positions (correlated stops cascade, margin-call selling, etc.). ← origin: FUNNEL. "When one or more skydivers find themselves in an unstable position and end up in another's burble. The resulting loss of stability for the others usually causes the formation to break up."

B.34 Manifest

The list of currently-open positions for the active tenant, in order of zone urgency. Default cockpit view's left rail. ← origin: MANIFEST. "The list of skydivers on the jump plane."

B.35 Boogie

A high-volatility / event-driven trading day (FOMC, earnings cluster, OPEX Friday) where the rules are more conservative and the cockpit shifts to event-mode chrome. ← origin: BOOGIE. "A gathering of skydivers, usually focused on fun rather than competition." A bit playful — boogies need extra discipline.

---

C — Cross-walk index (skydiving → OPTOMON)

Use this when you're coming from the source material and want to find where the term landed in OPTOMON.

C.1 Skydiving terms intentionally NOT mapped

The following source terms are part of the regulatory or equipment vocabulary of parachuting and have no clean OPTOMON analog. They remain in the source material for reference but are not part of the OPTOMON lexicon: USPA, FAI, BPA, FAA, FAR, NAA, NCPC, IPC, BIC, CCI, JCC, ICC, IRM, S&TA, I/E, PRO RATING, SIM, BSR-as-a-document, NAS 804, AS 8015A, TSO-C23, TSO, AAF, NAF, AN-contract, STC, Form 337; aircraft model names (Beechcraft, Cessna, DC-3, Otter, King Air, Porter); equipment and fabric specifics (Dacron, Spectra, Slinks, F-111, Zero-P, Microline, Astra, Cypres, Sentinel, FXC, B-12s, Hooker Harness, Three-Ring Release, Mini-Three-Ring, Diaper, Slider, Stabilizer, Risers, Toggles, Steering Lines, Steering Toggles, Suspension Lines, Closing Loop, Closing Pin, Pull-Up Cord, Bridle, Cell, End Cell, End Cell Closure, Rib, Cross-Braced, Cross Connectors, Cross Ports, Aspect Ratio, Chord, Span, Planform); discipline names that don't translate (Accuracy, Style, Classics, Skysurf, Skyboard, Surfboard, Speed, Sit Fly, Head Down, Belly Flying, Free Fly, Freefly, Freestyle, Box Man as a posture-name only — though the spirit informs Stable Posture, Half Series, Round (formation), Star); jump-types (AFF, IAD, S/L, Tandem, Hop & Pop); license letters and rating-track names; miscellaneous (Wuffo, Skygod, Frap, Frommel, Zoo, Zoo-Load, Sky Shark, Farmer McNasty, Hot Fuel, Manifest-as-physical-place, Pit, Peas).

These are preserved verbatim in the SOURCE file. Their absence from the OPTOMON lexicon is intentional — vocabulary discipline matters, and forcing analogs where none exists creates clutter.

---

D — Future additions (OPTOMON-native, not yet defined)

These terms appear in design docs but await a definition pass:

• Read Model — the projection-pattern data structure for tenants.
• Composite Position — the multi-leg-grouped strategy view.
• Approval Band — Flight Plan section that defines auto-accept / notify / hold-for-review thresholds for advisor-drafted tickets.
• Break-Glass Grant — time-bound super-admin support access.
• Persona View — content surface tied to a user_type.
• Ledger — the per-tenant, per-vendor account snapshot record.

Each will land here once its 06_*.md source-of-truth doc settles.

---

Provenance: Adapted from skydiving vocabulary preserved at __.ignore_DEV-RES_BIN/_src-reference-materials_bin/Skydiving-terms-glossary.SOURCE.md. The transmutation favors structural fidelity over decorative use. Where the analog is precise (decision altitude → decision threshold), it's used; where it's approximate (e.g., "exit weight"), it isn't.