> 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/release-and-readiness/production-activation-audit.md).

# Production activation audit

Run this after a public promotion and after any Privy, chart-library or Robinhood provider change:

```powershell
pnpm activation:audit --origin https://nytshift.xyz
```

For a deployment gate that must fail until every public lane is ready:

```powershell
pnpm activation:audit --origin https://nytshift.xyz --require-public-ready
```

Interpret the result by lane. `publicFoundation` proves the exact release, capacity, disabled-execution lock, live market discovery and core durable stores. `customerAccess` requires complete browser/server Privy configuration plus fresh exact-app NS-430 production rehearsal evidence. `nativeCharts` requires both the licensed v32 tree/manifest and fresh exact-release/tree NS-431 production rehearsal evidence. `robinhoodData` requires fresh stable independent HTTP/archive/WSS evidence. An `unsafe` lane is a stop condition; `action-required` names missing external configuration, missing rehearsal or expired/mismatched evidence.

`publicLaunchReady=true` is not trading authorization. The public audit deliberately cannot inspect or establish operator authentication, signed eligibility, signer keys, testnet order finality, rehearsal evidence, legal approval or a user-authorized canary. `capitalTradingReady` therefore remains false in every anonymous report.

Do not add cookies, tokens, signer endpoints or provider URLs to this command. Use the existing private operator and signer runbooks for capital evidence. Keep both execution modes disabled and both mainnet flags false while configuring public services.


---

# 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/release-and-readiness/production-activation-audit.md?ask=<question>&goal=<endgoal>
```

`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.