> For the complete documentation index, see [llms.txt](https://docs.prophetmarket.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prophetmarket.ai/brand-guidelines/overview.md).

# Overview

This section is the working reference for anyone producing Prophet content, whether staff, freelancer, clipper or agency. It covers the logo, the visual system, the voice and the claims that must be stated carefully.

Four pages, in the order most people need them.

| Page                                                    | What it covers                                                          |
| ------------------------------------------------------- | ----------------------------------------------------------------------- |
| [Logo](/brand-guidelines/overview.md)                   | The files, which variant to use where, and what not to do to them       |
| [Colour and Type](/brand-guidelines/colour-and-type.md) | Palette, surfaces and typography                                        |
| [Voice](/brand-guidelines/voice.md)                     | How Prophet writes, with the terminology rules                          |
| [Claim Rules](/brand-guidelines/claim-rules.md)         | The claims that are easy to get wrong and the approved wording for each |

{% hint style="danger" %}
**Read Claim Rules before writing anything public**

Four claims about Prophet are routinely stated incorrectly, and each is expensive to correct once published. An independent fact check of draft social content found false claims in three of six posts. The approved wording for each is on the [Claim Rules](/brand-guidelines/claim-rules.md) page and can be copied verbatim.
{% endhint %}

## The short version

Prophet writes like an analyst who respects the reader's intelligence and refuses to flatter them. Three adjectives govern every decision: **precise**, **candid**, **unimpressed**.

The brand line is **Challenge the Machine**. It is a positioning platform rather than a slogan, so it should not be pasted onto content that makes no argument.

Visually, the system is built on flat colour fields rather than gradients or texture, with condensed all-caps display type and a monospaced label style for data. The ring mark appears on every asset.

## Positioning

Prophet is the world's first single-player prediction market. A user writes any verifiable yes or no question with a resolution date, the market prices it within about thirty seconds, and the user takes a position if they believe they have an edge.

The distinctive claim is that a market can exist for a question nobody else has asked. Conventional prediction markets need two willing sides before a question can trade at all, which limits them to questions of broad interest. Prophet removes that constraint.

{% hint style="info" %}
**Candour is the differentiator, not a compliance obligation**

Prophet's audience is sceptical by disposition; they trade against models for a living. Stating the unglamorous part out loud, including the spread and the settlement delays, is what makes the rest of the argument credible. Content that oversells reads as a tell.
{% endhint %}

## Scope and ownership

| Field           | Value                                             |
| --------------- | ------------------------------------------------- |
| Version         | 1.0                                               |
| Date            | 07 August 2026                                    |
| Applies to      | All external Prophet content across every channel |
| Source of truth | The product specification, for anything factual   |

Where this section and the product specification disagree, the specification wins and this section needs correcting.


---

# 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://docs.prophetmarket.ai/brand-guidelines/overview.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.