---
title: "Project Knowledge | Jetstack AI Docs"
description: "What Jetty knows about your client: facts from your documents and chats, each linked to its source, shown on the Documents page and used in planning."
url: "https://jetstack.ai/docs/projects/knowledge/"
---

# Project Knowledge

**Project Knowledge** is what Jetty knows about your client. It’s built from the documents you upload and what you tell Jetty in chat, and every fact shows where it came from. Jetty uses it every time it plans. You can see it on the project’s **Documents** page under **What Jetty knows**.

## Uploading Documents

Upload documents from any chat with **Upload a build spec**, or from the **Documents** page. PDF, Word, text, CSV, JSON and Markdown files all work, and you can attach several at once. After you upload:

1. The document appears on the **Documents** page, showing whether it’s waiting, being read, or done.
2. Jetty reads it and posts what it found into the chat. If you uploaded from the Documents page, that’s your most recent chat.
3. The facts it finds are added to **What Jetty knows**.

On the Documents page, **Ask Jetty** next to a document opens a chat with a question about it ready to send.

## Every Fact Has a Source

Each fact comes with a quote from where Jetty found it: a passage in a document, one of your messages, or something in the portal. For example: *“Acme’s SDR team qualifies leads within 24 hours.”* If Jetty can’t point to a source, it doesn’t treat the fact as known.

When new information comes in, Jetty saves a new version and keeps the old ones as they were. The Documents page shows the latest, for example *Brief v4 · 38 facts from your documents*.

## What Jetty Keeps Track Of

| Group              | What it covers                                   |
| ------------------ | ------------------------------------------------ |
| **Company**        | The client’s business, market and how they sell  |
| **People**         | The client’s team and other stakeholders         |
| **Processes**      | How work gets done today                         |
| **Requirements**   | What the project needs to deliver                |
| **Systems**        | The HubSpot portal and the other tools around it |
| **Open questions** | Decisions nobody has made yet                    |
| **Conflicts**      | Places where two sources disagree                |

## How Jetty Uses It

- **It uses your exact wording.** If a document lists exact fields, options, pipeline stages or workflows, Jetty builds from the document itself, using your exact names and values.
- **The newest document wins.** If two documents disagree, Jetty goes with the one marked final or the most recent one (a later date or version, “final”, “replaces”). If it can’t tell which is newest, it asks you.
- **It asks in the chat.** When an open question stops Jetty building something, it asks you on a [questions card](https://jetstack.ai/docs/projects/chats#questions). Questions that don’t block anything aren’t put to you.
- **It remembers what you tell it.** If you say “leave out the renewal email” or “no SMS”, Jetty remembers it and applies it to every later plan, even if a document says otherwise. You can also say “add that to the project knowledge” to make sure something is kept.

## Requirements

The Overview’s **Requirements** section tracks each requirement, from *Not linked to a build* through *Planned*, *Built* and *Setup remaining* to *Saved configuration checked*. See [Requirements](https://jetstack.ai/docs/projects/chats#requirements).

## Next Steps

- **[Chats & Cards](https://jetstack.ai/docs/projects/chats)**: how questions and plans reach you
- **[Quickstart](https://jetstack.ai/docs/projects/quickstart)**: uploading your first build spec
