> For the complete documentation index, see [llms.txt](https://jordan-7.gitbook.io/jordan-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jordan-7.gitbook.io/jordan-docs/internal/directive-changes.md).

# Directive changes (supersede the run spec)

Standing amendments from Jordan, applied to every phase from here on. Where these conflict with megachat-ui-overhaul-prompt, THESE WIN.

## 2026-09-02 — Logo directive withdrawn

Jordan has NOT settled on what to do with the logo. Drop it as a constraint:

* The current converged logo (violet→magenta MEGA over white CHAT, chrome keyline) is NO LONGER a fixed anchor to design around.
* Do NOT gate palette selection on "does it fight the logo" (R4's logo tests are moot).
* Do NOT put the current logo in nav mocks as a settled element, and do NOT add it to the Phase 3 PRESERVE list.
* The real logo assets were never modified by this run (wordmark.tsx, the public icons, and design-assets/branding/\* are all untouched). The only logo-related outputs are the palette-against-logo TEST artifacts under docs/ui-overhaul/directions/*/ (logo-test*.html/.png, a copied jpg); those are to be removed once the Phase 1 research workflow finishes writing there.

## 2026-09-02 — Refocus

The run's emphasis is overall AESTHETIC, UI, and VIBE per section 0 of the prompt (beautiful, intuitive, fast, exciting; the three-lens balance; the color-system fix; soften-the-square; copy that grabs). Keep the token/type/ spacing/radius/color and copy research. The logo is simply not part of the scope until Jordan decides.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://jordan-7.gitbook.io/jordan-docs/internal/directive-changes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.