> For the complete documentation index, see [llms.txt](https://pip-c.gitbook.io/pip-c-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pip-c.gitbook.io/pip-c-docs/pip-c/introduction.md).

# Introduction

PIP:C (Persona Identity Protocol: Character) is a structured character architecture for long-session consistency. It replaces loose prose with modular logic that models can parse, retain, and follow more reliably.

What started as a character blueprint now functions as a full character operating system. It supports stable identity, trust-gated behavior, optional expansion modules, and defensive layers that protect character integrity during live use.

### What PIP:C does

PIP:C is built to solve the most common failure points in AI character design:

* character drift over long conversations
* flattened tone and generic voice
* weak trust progression
* unstable memory behavior
* prompt injection and architecture leakage

Instead of relying on prose alone, PIP:C uses explicit modules with defined roles. That makes behavior easier to shape, debug, and extend.

### What's in the latest docs update

The current docs set has been expanded to cover the full working system:

* core architecture and module logic
* optional behavioral expansion packs
* intrusion defense and prompt security
* real usage examples
* model compatibility guidance
* creator-facing reviews and recommendations
* a hyper-compression deep dive for dense PIP:C builds, including how the shorthand works and why a consistent domain-specific language is necessary for reliable token-efficient character encoding

These docs reflect production character files and live testing across multiple model families. They describe working systems, not theory.

### Start here

If you are new to the docs, read these first:

1. [Technical Architecture](/pip-c-docs/pip-c/technical-architecture.md) for the core modules and design logic.
2. [Optional Modules:FAQ](/pip-c-docs/pip-c/optional-modules-faq.md) for plug-in systems and expansion patterns.
3. [Intrusion Reflex: FAQ](/pip-c-docs/pip-c/intrusion-reflex-faq.md) for prompt injection defense and security behavior.
4. [Architecture In Action](/pip-c-docs/pip-c/architecture-in-action.md) for applied examples.

### More pages in this set

* [PIP:C Hyper-Compression Guide](/pip-c-docs/pip-c/pip-c-hyper-compression-guide.md)
* [Model Compatibility Overview](/pip-c-docs/pip-c/model-compatibility-overview.md)
* [Detailed Model Reviews](/pip-c-docs/pip-c/detailed-model-reviews.md)
* [Deep Dive Reviews & Creator Recommendations](/pip-c-docs/pip-c/deep-dive-reviews-and-creator-recommendations.md)
* [Creators Philosophy](/pip-c-docs/pip-c/creators-philosophy.md)

### Who this docs set is for

This documentation is useful if you are:

* building characters that need long-term identity stability
* replacing prose-heavy sheets with structured logic
* testing trust systems, memory anchors, or modular behavior
* protecting character architecture from prompt extraction
* comparing which models handle PIP:C best

### Bottom line

PIP:C is meant to keep a character coherent, expandable, and defensible over time. This docs set is organized to help you understand the system fast, then go deeper where needed.