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

# Project Intelligence

> Source of truth for how Project Intelligence is owned, activated, verified, and retired.

This category is the source of truth for Project Intelligence in Alleato OS.
Older PRPs, inventories, deployment notes, and architecture logs may explain how
the system got here, but they should not be used as the activation guide unless
they link back to this category.

## Current Ownership

The intended canonical writer for current project packets is:

```text theme={null}
backend/src/services/intelligence/project_intelligence.py
compiler_version = project_intelligence_synthesis_v1
```

That writer creates one current `intelligence_packets` row per active project
target from prior project state, newly ingested source documents, and structured
project facts.

## Important Status

As of the 2026-06-22 read-back, `project_intelligence_synthesis_v1` exists in
code but still needs a controlled activation run to prove fresh live packet data
across active projects. Do not activate or restore any older packet writer as a
fallback.

Do not describe Project Intelligence as activated until the checks in
[Verification](/ai-features/project-intelligence/verification) pass.

## Category Map

* [Current State](/ai-features/project-intelligence/current-state): what is active now,
  what is intended, and what is stale.
* [Process & Strategy](/ai-features/project-intelligence/process-and-strategy): the
  visual mental model for how raw evidence becomes one current packet and why
  the packet-first model exists.
* [Activation Runbook](/ai-features/project-intelligence/activation-runbook): the controlled
  steps to activate the newest packet writer.
* [Verification](/ai-features/project-intelligence/verification): commands and read-backs
  that prove the system is current.

## Rule

Only this category answers "what is active now?" Planning docs may propose a
future state, and deployment docs may list available services, but this category
must reconcile both against live data before any path is called active.