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

> ## Agent Instructions
> Orion is a collaborative analytics platform built by Gravity (bygravity.com). It connects to data warehouses like Snowflake, BigQuery, Databricks, Redshift, Athena, Fabric, PostgreSQL, and MySQL, and lets teams ask questions in natural language to get shared analyses, dashboards, reports, and slide decks. When referencing Orion features, always link to the relevant documentation page. Orion is not open-source; it is a commercial SaaS product accessed at runorion.com.

# Best Practices

> Write short, focused pages; start with a clear summary; keep content current; and enable 8-10 pages per project for the best Knowledge Base results.

## Keep Pages Short and Concise

Rather than creating one super long page, break your content into shorter, more focused pages. This helps Orion navigate and use your knowledge base more effectively.

**Better approach:**

* One page on metrics and definitions
* One page on a standard procedure for a specific analysis
* One page for additional context on a topic
* Separate pages for different processes or guidelines

<Tip>
  Shorter, focused pages are easier for both humans and Orion to understand and
  reference.
</Tip>

## Start With a Clear Summary

It's recommended that at the very top of each page, you provide a description or summary of what the page contains. The first 250 characters of your page are especially important because:

* Orion uses this text to quickly glance at what the page contains
* It helps determine whether the page is relevant for your analysis
* It acts like an executive summary for the page

**Example:**

```
# Sales Metrics Definitions

Our sales team uses these key metrics to measure performance and health. Updated monthly.

## ARR (Annual Recurring Revenue)
Total committed recurring revenue normalized to an annual value...
```

## Write for Clarity

**Do:**

* Use clear, plain language
* Use headers and formatting to break up content
* Include concrete examples
* Define acronyms and industry terms
* Name folders and files in a way that's easy to understand

**Don't:**

* Use dense paragraphs without structure
* Assume Orion knows your internal terminology
* Mix different types of content on a single page
* Leave pages incomplete or outdated

## Keep Content Current

Your Knowledge Base is only as valuable as the quality and accuracy of its content:

* Review your Knowledge Base quarterly
* Update pages when processes change
* Remove outdated or incorrect information
* Use revision history to track important changes

## Recommended Structure

Organize your folders around your company's natural structure and functions:

**Example organization:**

```
Company Information/
├── Mission & Values
├── Industry & Competitive Landscape
└── Key Contacts

Operations/
├── Sales Process
├── Contracts & Pricing
├── Customer Onboarding
└── Returns & Escalations

Finance/
├── Metrics & KPIs
├── Forecasting Methodology
└── Accounting Practices

Product/
├── Feature Definitions
├── Technical Specifications
└── API Documentation
```

## What to Document First

Start with the essentials that most affect Orion's analysis quality:

1. **Company Information** - Industry, size, geography, business model
2. **Key Definitions** - Important metrics, terminology, product names
3. **Core Processes** - How you operate, key workflows, decision criteria
4. **Data Definitions** - What your data represents, how it's calculated
5. **Guidelines** - Preferences for analysis, communication style, reporting format

## What to Add Later

As your Knowledge Base grows, expand with:

* Competitive intelligence
* Industry trends and context
* Historical decisions and reasons
* Standard templates and formats
* Advanced processes and edge cases

## Per-Project Context Management

When enabling knowledge base pages for a project, it's recommended to keep this between **8-10 pages maximum** per project. This approach:

* Keeps Orion focused on relevant context only
* Improves analysis quality by reducing noise
* Makes the system more effective at navigating your company's context

**Example per-project enablement:**

* **Sales Project** - Enable pages on: Pricing, Sales Process, Key Metrics, Contracts, Customer Definitions
* **Product Project** - Enable pages on: Feature Definitions, Technical Specs, API Documentation, Product Roadmap
* **Finance Project** - Enable pages on: Metrics & KPIs, Forecasting Methodology, Accounting Practices, Budget Guidelines

## Where Project Context Lives

Use the Knowledge Base as the home for company-wide context instead of pasting it into free-text boxes:

* Store your company-wide context in the Knowledge Base
* Enable relevant pages for each project
* Reuse the same pages across projects rather than re-typing context

This creates a more maintainable, reusable system where your context is documented once and enabled where needed.