> For the complete documentation index, see [llms.txt](https://nytshift.gitbook.io/nytshift-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nytshift.gitbook.io/nytshift-docs/engineering-guide/14-glossary.md). # Glossary [← Repository atlas](/nytshift-docs/engineering-guide/13-repository-atlas.md) · [Documentation home](/nytshift-docs/start-here/readme.md) Project language is intentionally precise. Similar words often describe different authority. | Term | Meaning in NYTSHIFT | | ------------------------ | -------------------------------------------------------------------------------------------------------- | | **Account scope** | Exact venue plus master/subaccount/public address identity permitted by a capability | | **AEGIS** | Pure deterministic policy/risk evaluator; never a signer or model | | **Agent connection** | Expiring, revocable MCP identity with exact tools, symbols, accounts, mode and quotas | | **Agent Pro** | Signed commercial entitlement and expiring credentials for proposal/testnet-policy capabilities | | **Ambiguous outcome** | Multiple plausible identities/results or insufficient proof; requires investigation/reconciliation | | **Approval** | Human-gated reviewed action; not the same as AEGIS allow or venue finality | | **Arcus** | Robinhood Chain-rooted perpetual venue integrated for public reads and separately gated signing | | **Authority** | Capability to cause or authorize state change; never inferred from data availability | | **Available** | Contract-required current evidence exists and passed validation/freshness | | **BYOA** | Bring Your Own Agent; customer supplies agent/model provider while NYTSHIFT supplies governed tools | | **Canonical identity** | Reviewed chain ID + contract or venue metadata identity; stronger than ticker/name | | **CLOID** | Client order ID retained before Hyperliquid submission and used for idempotency/reconciliation | | **Configured** | Required values exist; does not imply healthy, ready or authorized | | **Consumer projection** | Rule deciding whether normalized evidence may feed charts, alerts, PAPER, review or evidence-only UI | | **DPoP** | Demonstration of Proof-of-Possession; binds automation requests to a client-held P-256 key | | **Exact context** | Venue + instrument/DEX/market ID + account where relevant + observation time/sequence | | **Execution capability** | Explicit contract enum describing mutation authority; `none` means no venue action path | | **Finality** | Authoritative venue/chain evidence of terminal outcome, not an HTTP acknowledgement | | **Flow root** | Durable server-owned execution correlation identity carried across review/signer/reconciliation | | **Fresh** | Observation age is inside the domain-specific budget and transport/context remain valid | | **Held mark** | Prior accepted mark retained after an uncorroborated implausible move; evidence-only, not live authority | | **Mainnet** | Real-capital venue/network mode; disabled until independent legal/security/operational gates pass | | **Market Brief** | First-party deterministic market summary; not a model Copilot | | **MCP** | Model Context Protocol transport/tool surface for customer-owned agents | | **NIGHTSHIFT** | Historical code/schema/environment namespace retained for compatibility | | **NYTSHIFT** | Public product and brand | | **Operator** | Separate authenticated human control-plane identity; not the same as a customer login | | **Paper** | Deterministic simulation using bounded live-book evidence with zero venue authority | | **Partial** | Some required components/pages/fields are missing; complete aggregate authority is withheld | | **Proposal** | Typed advisory object registered for review; no signer authority | | **Ready** | All evidence for one named activation lane is current; does not imply another lane or execution | | **Reconciliation** | Querying authoritative state by retained identity to resolve order/fill/funding/cancel outcomes | | **Reference quarantine** | Removing malformed/divergent oracle/index numeric authority while retaining reason/provenance | | **Release receipt** | Commit/archive/tree/count/byte hashes proving a reproducible public artifact | | **Signer** | Loopback-only Python process owning venue key use, final validation, idempotency and reconciliation | | **Stale** | Previously valid evidence outside its age/transport budget; cannot feed freshness-dependent consumers | | **Testnet policy** | Expiring DPoP-bound Hyperliquid automation scope with one attempt per request ID | | **Unknown** | A signed action may or may not have reached the venue; blocks retry until reconciled | | **Venue evidence** | Provider-normalized observation with explicit source, identity, time and coverage | | **Wallet connection** | User-consented address/chain evidence; not signing, transfer or execution consent | If a new feature needs a new authority term, define it in a versioned contract and add it here rather than overloading `ready`, `connected`, `active` or `live`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://nytshift.gitbook.io/nytshift-docs/engineering-guide/14-glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.