---
title: "Project Intelligence"
canonical_url: https://auteurintelligence.com/platform/project-intelligence/
description: "The project remembers what the chat window forgets while keeping approved canon separate from suggestions. Project Intelligence is the persistent layer that…"
---

# Project Intelligence

The project remembers what the chat window forgets while keeping approved canon
separate from suggestions. Project Intelligence is the persistent layer that
holds a project's approved truth, scoped memory, doctrine, research, decisions,
and evidence, and keeps its identity, so serious work accumulates instead of
resetting every session.

---

## Approved truth, kept apart from suggestions

Not everything an agent produces is true, and the system is built around that
fact. Persistent approved truth, scoped recall, and project identity are
separated by authority, so a suggestion never quietly becomes canon. Approved
production truth is human-reviewed and versioned, you can see what was decided,
when, and by whom, and approved canon stays separate from automated
suggestions.

---

## Context that is grounded, not drifting

Agents receive the tools and project context relevant to the task instead of an
unrestricted, drifting transcript. That context is assembled from a
hash-validated operations authority, which keeps tools, routes, project facts,
and constraints grounded and auditable rather than accumulating in a conversation
until it goes stale. The bounded context is a feature, not a limit: it keeps
tools, routes, and project facts grounded and auditable over long, complex
projects.

---

## One identity for the work, from writing to production

Visual and production assets retain identity, versions, references, approvals,
and downstream bindings across the production system, so a project does not have
to be rebuilt each time it crosses a tool boundary. A reviewed production graph
holds scenes, entities, occurrences, review states, source evidence, references,
and handoffs as versioned truth.

Carrying an entire story's approved identity, characters, world rules, scene
identities, research, and approvals, from writing into film and game is what the
shared production graph is built to preserve.

---

## Why it matters

Persistent project intelligence is the reason the platform's other promises hold.
Governed campaigns need a memory of what was approved. Receipts and readback need
a durable record to check against. Bring-your-own-harness works because the
project, not the interface, is where the truth lives. The persistent project
intelligence stays where it is, in the project.