> 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/hyperliquid/hyperliquid-time-machine.md). # Time Machine and Trade Autopsy Use this runbook to inspect what NIGHTSHIFT has durably retained for the configured Hyperliquid signer. It is forensic evidence, not an account-history scraper and not a replacement for venue reconciliation. ## Safety rule Never repeat a submit, leverage update or cancellation because Time Machine is empty, stale, partial or unavailable. Capital-moving ambiguity is resolved only by the existing exact-CLOID reconciliation workflow. Time Machine performs no venue request and grants no execution authority. ## Inspect 1. Keep the web and signer services on loopback and verify signer-store integrity is healthy. 2. Unlock the operator session, select Hyperliquid and open `Time Machine` in the portfolio panel. A public account inspection is not required. 3. Press `REFRESH EVIDENCE` to read the current local index, then select one retained CLOID. 4. Verify the role, lifecycle state, exact fill count, realized PnL, venue fees, NIGHTSHIFT fee evidence, OID and coverage. 5. Follow `EXECUTION LINEAGE` from the earliest retained event through reconciliation. Compare the root flow across review/submission/reconciliation spans. 6. Treat `bounded-partial` as incomplete upstream fill coverage. The documented venue boundary is the 10,000 most recent fills; the rendered local timeline is capped at 1,000 events. ## Grouped bracket autopsy For a retained parent with protective children, use `CHECK RETAINED GROUP` or call `GET /api/execution/time-machine?parentCloid=` through the operator-authenticated BFF. The BFF pins the configured signer account; the signer reads only its local lifecycle and audit tables through `GET /v1/time-machine/brackets/{parent_cloid}`. A successful response must show exact parent, take-profit and stop-loss identities, one synchronized grouped observation time, explicit protection and sibling-cancellation states, and chronological leg-attributed lineage. The read must not increase adapter or venue calls. `RETAINED ONLY / ZERO VENUE READS` is the operating boundary, not a claim that venue state was refreshed. A standalone parent returns 404. Missing or differently timed leg snapshots, scope conflicts, corruption or schema drift return unavailable/503. Reconcile the complete bracket through the grouped reconciliation control before retrying the forensic read; never resubmit because an autopsy is unavailable. Exact `siblingFilledCanceled` remains mandatory before sibling cancellation is confirmed. ## Empty or unavailable states * `No reconciled lifecycles retained`: no exact lifecycle snapshot exists for the configured signer. Reconcile a known retained CLOID; do not import or persist an arbitrary public account. * `INVALID_CLOID`: the identifier is not a lowercase 16-byte Hyperliquid CLOID. * `403`: signer or retained account scope mismatch. Correct configuration; never weaken the scope. * `404`: no reconciled lifecycle exists for that retained CLOID. * `503`: signer, store or strict response validation is unavailable. Preserve prior evidence and diagnose store health before retrying the read. * `TRUNCATED INDEX` or truncated timeline: use narrower operational evidence or the verified signer backup; do not describe the view as venue-complete history. If final order state is still ambiguous, follow [Hyperliquid order lifecycle reconciliation](/nytshift-docs/hyperliquid/hyperliquid-order-lifecycle.md). If store health is unsafe, stop the signer and follow [execution-store recovery](/nytshift-docs/arcus/arcus-execution-store-recovery.md). --- # 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/hyperliquid/hyperliquid-time-machine.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.