> ## Documentation Index
> Fetch the complete documentation index at: https://docs.appeeky.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge base and memory

> What you tell the Co-founder about your business, the documents it reads, and what it learns on its own.

The Co-founder knows two kinds of things:

* **What you told it**: your business profile and your documents. This always wins.
* **What it learned**: facts and outcomes it picked up from your data and conversations, kept in the **Vault**.

When the two disagree, your version wins. The Co-founder can suggest a change to what you wrote, but never makes one on its own.

***

## Business profile

**Settings → Business** holds two short profiles. Both reach every briefing.

| Profile | Fields |
| - | - |
| **Company**, shared across every app | Company name, website, what you do, stage, team size, business model, primary markets, ICP, positioning, mission, differentiators, values, brand voice, **hard rules** |
| **This product**, one per app | What the product is, target user, jobs it does, monetization, pricing, differentiators, known weaknesses, current focus, **do not touch** |

Two fields matter most:

* **Hard rules — never do these**: "Never recommend removing the free tier." The Co-founder won't propose an action that breaks one.
* **Do not touch**: "app name", "MX pricing". Stops it from suggesting changes to those.

> [!NOTE]
>
> You don't start from a blank form. Shortly after you connect an app, the Co-founder drafts both profiles from your store listing, competitors, reviews and website. Hard rules and do-not-touch items only take effect once you confirm the draft. It never overwrites anything you wrote.

***

## Documents

**App Co-founder → Knowledge base** is a library of Markdown documents: research, playbooks, notes for each part of your business. Start with `business_context.md`, the prose version of your profile: what you're building, who it's for, what you already tried.

| Control | What it does |
| - | - |
| **Pin** | Pinned documents are read on every briefing. Keep them short. |
| **Scope** | Company-wide, or one app only |
| **Visibility** | *Agents*: the Co-founder can read it. *Private*: never shown to it. *Public*: readable and shareable later. |

Unpinned documents are found and read when they're relevant to the question or briefing. Each document keeps its revision history.

### Keep Notion pages in sync

Under **Settings → Automation → Company Brain sync**, add a Notion page or a URL. The Co-founder keeps it ingested so your knowledge base stays current. Requires Notion connected in **Integrations**.

### Suggestions

When the Co-founder notices something that doesn't match what you wrote — your profile says "pre-launch" but you have 10,000 downloads — it suggests an edit. It keeps using your current version until you **Apply** or **Reject**, from the knowledge base or straight from the briefing email.

***

## Memory vault

**App Co-founder → Vault** shows what the Co-founder learned: facts (stable things it observed, such as your brand voice) and episodes (each action it proposed and what came of it). It shows how they connect, and which ones support or contradict each other.

| You can | How |
| - | - |
| **Add a fact** | Seed it by hand to make the first briefings smarter, for one app or all apps |
| **Approve or remove a fact** | Facts it isn't sure about wait as *Pending review* |
| **Ingest knowledge** | Paste a URL or text, upload a `.txt`, `.md`, `.csv` or `.json` file, or pick a Notion page. It extracts candidate facts for you to review. |
| **Export and import** | Download your memory as JSON or Markdown, or import a JSON export, as pending or active. An import can be undone. |

You can also teach it in chat: "the spike last week was a YouTube sponsor" is remembered and used in later briefings.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.