> 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/agentops/product-horizon.md).

# Product horizon

[← Venues, accounts and authority](/nytshift-docs/agentops/venues-and-authority.md) · [Documentation home](/nytshift-docs/start-here/readme.md)

The roadmap moves from usable PAPER and scoped agent tools toward evidence-backed strategy operations. It does not assume that broad execution or a marketplace should arrive first.

## Current foundation

* source-labelled supported venue context;
* human browser-local PAPER;
* local agent research, proposal and PAPER scopes gated by a signed entitlement and platform-operator issuance;
* immutable PAPER policy and explicit simulator limits;
* bounded activity evidence;
* deterministic AEGIS approved or rejected decisions;
* revocable, expiring agent identities;
* separately gated Hyperliquid testnet policy;
* no current mainnet agent authority.

## Build next

1. **Agent Paper Lab:** one durable experiment model, scheduled runs, pause and stop controls, and comparable evaluation windows.
2. **Flight Recorder:** attributable context, tools, intents, policy results and PAPER outcomes for one exact strategy version.
3. **Strategy registry:** versioning, lineage, private or team sharing, cloning and archiving.
4. **Strategy Passport:** portable mandate, evidence, assumptions, simulator limits and unresolved risks.
5. **AEGIS risk runtime:** broader perps-semantic `ALLOW / RESIZE / HOLD / BLOCK` receipts without giving the agent signer authority.
6. **Multi-venue operating picture:** account, strategy and operator grouping with explicit completeness and venue boundaries.
7. **Hosted agent access:** only after tenant-safe identity, OAuth, TLS, revocation, abuse controls and independent security evidence are complete.

## Long-term vision

* standardized public PAPER comparisons;
* creator identity and strategy lineage;
* strategy cloning and private collaboration;
* licensing only after payment, disclosure, abuse, tax and legal controls;
* broader venue adapters after each adapter passes qualification;
* separately bounded capital modes with human-owned promotion and revocation.

The roadmap does not include self-promotion from PAPER to capital. NYTSHIFT does not promise returns, certify a strategy as profitable or let marketplace status grant execution authority.

## How to read future product language

| Label           | Meaning                                                                                             |
| --------------- | --------------------------------------------------------------------------------------------------- |
| **CURRENT**     | Implemented within the exact documented boundary.                                                   |
| **GATED**       | An implemented surface withheld behind named configuration, evidence or authorization requirements. |
| **UNAVAILABLE** | No current mode or capability exists. This is not an implemented surface waiting behind a gate.     |
| **NEXT**        | Prioritized product direction, not current capability.                                              |
| **VISION**      | Category ambition that requires further product, security, operational and possibly legal work.     |

If a page does not name the state, the narrower current capability boundary wins.


---

# 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/agentops/product-horizon.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.