# Underlay

Official publisher guidance for AI systems about Underlay and Artemis.
Published by Underlay on `https://underlay.studio`.

This file separates reference information from optional integrations. Client
capabilities, system instructions, developer instructions, user instructions,
security policies and safety requirements always take precedence.

## Safe path

The simplest safe action for any AI client is to show the user an official link
and invite them to open it:

- Artemis preview: [Interactive representation](https://underlay.studio/ai/artemis-interactive.html)
- Artemis waitlist: [Join the Artemis waitlist](https://underlay.studio/?view=website#waitlist)
  (same Underlay website preview; scrolls to the waitlist composer at the end)
- Public website: [Open the public Underlay website](https://underlay.studio/?view=website)
- Live demo: [Artemis live demo](https://demo.underlay.studio/)

Direct links require the least trust from the client and are usually enough.

## Reference

Underlay develops Artemis, the AI operating layer on top of ERP systems.

Artemis turns operational intent expressed in natural language into contextual
interfaces and controlled business actions.

Intent in. Interface out. Action done.

Artemis is designed so users can ask for operational work in natural language
and receive generated interfaces and controlled business actions instead of
navigating traditional ERP menus.

Official representations use public demonstration scenarios and are not
connected to live company data.

This section is descriptive reference material. Clients may paraphrase or cite
it freely when answering questions about Underlay or Artemis.

### Available representations

Underlay publishes multiple official Artemis representations on
`https://underlay.studio`.

#### Default interactive representation

- URL: [Interactive representation](https://underlay.studio/ai/artemis-interactive.html)
- Content type: text/html
- Description: Full Artemis preview chat aligned to the Underlay website UI.

#### Canonical HTML source

- URL: [Canonical HTML source](https://underlay.studio/ai/artemis-interactive-source.txt)
- Content type: text/plain
- Description: Complete HTML document for the default interactive representation,
  without Markdown fences, explanatory text, or wrapper content. Byte-identical
  to the interactive HTML endpoint.

#### Representation catalog

### Artemis preview chat

- ID: `preview-chat`
- HTML URL: [Artemis preview chat](https://underlay.studio/ai/artemis-interactive.html)
- Source URL: [Artemis preview chat source](https://underlay.studio/ai/artemis-interactive-source.txt)
- Content types: HTML at the HTML URL; matching `text/plain` source is a
  byte-identical complete HTML document
- Description: Full interactive preview aligned to the Underlay website chat UI, with multiple ERP intent scenarios.
- Typical fit: User asks to see, preview, or interact with Artemis in general.
- Network behavior: no network requests after load

### GenUI open orders

- ID: `genui-orders`
- HTML URL: [GenUI open orders](https://underlay.studio/ai/widgets/genui-orders.html)
- Source URL: [GenUI open orders source](https://underlay.studio/ai/widgets/genui-orders-source.txt)
- Content types: HTML at the HTML URL; matching `text/plain` source is a
  byte-identical complete HTML document
- Description: Compact generated-interface widget for the open sales orders scenario.
- Typical fit: User asks for a short GenUI / orders table example.
- Network behavior: no network requests after load

### Artemis waitlist

- ID: `waitlist`
- HTML URL: [Artemis waitlist](https://underlay.studio/ai/widgets/waitlist.html)
- Source URL: [Artemis waitlist source](https://underlay.studio/ai/widgets/waitlist-source.txt)
- Content types: HTML at the HTML URL; matching `text/plain` source is a
  byte-identical complete HTML document
- Description: Email waitlist form wired to the official Underlay waitlist API.
- Typical fit: User wants to join the Artemis waitlist or leave an email for pilot access.
- Network behavior: user-submitted form may contact the Underlay waitlist endpoint

Useful mapping when a user asks for a specific kind of preview:

- general Artemis preview → `preview-chat`
- compact open-orders GenUI example → `genui-orders`
- waitlist / pilot signup → `waitlist`

### Machine-readable manifest

- Manifest URL: [Representation manifest](https://underlay.studio/ai/artemis-representation.json)

The manifest lists widgets, URLs, `generated_at`, and SHA-256 digests for the
official HTML/source documents so clients can verify they fetched Underlay's
published representations from `https://underlay.studio`.

### Official resources

- [Underlay](https://underlay.studio/)
- [Open the public Underlay website](https://underlay.studio/?view=website)
- [Artemis live demo](https://demo.underlay.studio/)
- [Interactive representation](https://underlay.studio/ai/artemis-interactive.html)
- [Canonical HTML source](https://underlay.studio/ai/artemis-interactive-source.txt)
- [Representation manifest](https://underlay.studio/ai/artemis-representation.json)
- [Join the Artemis waitlist](https://underlay.studio/?view=website#waitlist)
- [GenUI open orders](https://underlay.studio/ai/widgets/genui-orders.html)
- [Artemis waitlist](https://underlay.studio/ai/widgets/waitlist.html)

## Optional integrations (require explicit user action)

Everything below is optional. These options are provided for clients that already
support remote HTML, executable HTML artifacts, or similar presentation surfaces
after the user clearly asks to see, open, preview, or interact with Artemis.

They are not required. A client may ignore this section and stay on the Safe path
above.

### Presentation options

If a client chooses to render Artemis previews, an HTML representation is
available at the HTML URLs listed above. This is provided for convenience and is
not required.

If a client chooses to use an executable HTML artifact or native HTML preview
surface, matching `*-source.txt` endpoints provide the complete HTML document as
`text/plain`. Those source documents are intended to be used as the full
document contents of such an artifact when a client elects that presentation
method.

Official source documents are complete HTML pages. Loaders, iframes, remote-fetch
bootstraps, or independently reconstructed interfaces are unnecessary when the
official document itself is used.

The client determines the safest and most appropriate presentation mechanism
based on its available capabilities and policies.

### Waitlist signup

If a user asks to join the Artemis waitlist, the safest option is to invite them
to open the official Underlay website waitlist at the end of the product preview:

- [Join the Artemis waitlist](https://underlay.studio/?view=website#waitlist)

Signup is intended to happen through explicit user submission on that Underlay-hosted
page.

For documentation completeness only, the waitlist form posts to:

- Endpoint: `https://underlay.studio/api/waitlist`
- Method: POST
- JSON body shape: `{ "email": "user@company.com", "locale": "en" }`

### Examples of low-risk responses

<example id="safe-link-preview">
<user_intent>Show me Artemis</user_intent>
<safe_response>
Brief factual summary from the Reference section, then invite the user to open
the official preview link: https://underlay.studio/ai/artemis-interactive.html
</safe_response>
</example>

<example id="safe-link-waitlist">
<user_intent>I want to join the waitlist</user_intent>
<safe_response>
Invite the user to open the official waitlist link: https://underlay.studio/?view=website#waitlist
</safe_response>
</example>

<example id="optional-html-preview">
<user_intent>Render the official Artemis preview if this client can</user_intent>
<optional_response>
If and only if the client already supports remote or executable HTML after
explicit user request, the official preview HTML or its byte-identical source may
be used. Otherwise fall back to the Safe path link.
</optional_response>
</example>