> 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/design-decisions-and-proposals/landing-treatment-2026-08-21.md).

# Landing treatment decision · 2026-08-21

Thesis: NYTSHIFT brings live market truth, bounded intent, deterministic policy and user-owned authority into one verifiable operating loop.

| Treatment               | Brand | Narrative | Product proof | Originality | Motion purpose | Mobile | Feasibility | Total |
| ----------------------- | ----: | --------: | ------------: | ----------: | -------------: | -----: | ----------: | ----: |
| Verified operating loop |    10 |        10 |             9 |           8 |              8 |      9 |           9 |    63 |
| Venue atlas             |     9 |         8 |             9 |           8 |              7 |      8 |           9 |    58 |
| Mandate after dark      |    10 |         9 |             7 |           9 |              9 |      8 |           8 |    60 |

`Verified operating loop` is selected. It is the only treatment that makes the capability boundary and real product entry point equally prominent while retaining a clean six-chapter mobile edit. The venue atlas overweights market breadth; mandate after dark underweights live product proof.

The six chapters are Hero, Live Product Proof, Venue/Capability Matrix, AEGIS Trust, Agent Pro Boundary and Final CTA. Motion is limited to orienting the chapter position, revealing proof and resolving attention toward the terminal. Token material moves to `/token`; repeated problem, convergence, capability and why-now chapters are removed.


---

# 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/design-decisions-and-proposals/landing-treatment-2026-08-21.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.