Concepts

Core objects

Coil

A Coil is the strategy object: one whisper, one thesis, one allocation core, one policy, one fuse set — versioned and receipted. It is defined by its manifest (schemaVersion: "coil-1.0.0"), identified by a slug, and carries an explicit execution mode that defaults to paper_only. Anyone can read it, score it, or fork it. The full pipeline is in CoilOps.

Whisper

The raw market idea — a take, a thread, a note — recorded verbatim on the Coil. Validation requires it: a Coil without its originating whisper is invalid, because provenance starts at the source.

Manifest, holdings, and weights in bps

The allocation core is a portable JSON manifest: each holding is a canonical registry asset plus a weight in basis points (bps, hundredths of a percent) and a one-sentence rationale. Weights must sum to exactly 10,000. Why bps? Integers are exact: no floating-point drift, a trivial sum check, and two clients can never disagree about an allocation by a rounding hair.

Fuse

A typed, checkable constraint — position caps, order-notional ceilings, turnover limits, blackouts, and hard stops. All fuses are binding, and five kinds are mandatory before a capsule can compile. See Risk fuses.

Capsule

An Execution Capsule is the compiled artifact for non-paper Coils: a bounded instruction bundle (JSON + paste-ready text) for the user’s own agent on Robinhood’s official Trading MCP. HISS never runs it — liveOrderSent is hard-typed false. See Execution Capsules.

Trace

Every Coil is a public thesis object with a walkable history: the whisper, each version, each validation, each receipt, and the fork lineage. See Provenance.

Receipts

Deterministic canonical-JSON SHA-256 fingerprints for every artifact — manifest, validation, health score, fuse set, capsule, drift check, share card. Paper anchoring only, never a performance claim, verifiable by recomputation. See Receipts.

Coil Health

A 0–100 heuristic over nine components — clarity, tradability, concentration, fuse coverage, data freshness, oracle availability, liquidity assumption, rebalance sanity, agent readiness. It measures structure and readiness, never future returns. See HISS Score & Coil Health.

Oracle health

Every asset’s price feed resolves to one of eight health states (OK, STALE, INVALID_PRICE, MISSING_FEED, SEQUENCER_DOWN, GRACE_PERIOD, ORACLE_PAUSED, UNKNOWN). A price is only used when the state is OK. Details in Oracle health.

Fork lineage

A fork records its parent in the manifest’s forkOf field, so every remix cites its original and lineage hashes stay verifiable. See Forking.

Agent surfaces

The same pipeline is machine-callable three ways: the tools API over HTTP, the HISS MCP server (stdio, ten tools), and x402-payable services (scaffolded). None of them can execute anything.

Bankr strategist

When configured server-side, the Bankr Agent API acts as the Strategist brain; otherwise a deterministic mock provider answers. Either way the output is repaired to the canonical registry and passed through guardrails. See AI Strategist and Bankr integration.

HISS vocabulary

The product uses snake-language sparingly. Each term is defined once here; the rest of the docs mostly use the plain word.