Project identity (.pp) · Project Planner

Documentation describes the planned Windows application. Interface examples use demo project content and are labelled as previews.

Purpose

The identity file answers three questions: what is this project, where is the planning documentation, and which schema version does it use. It does not contain secrets, source code or generated artifacts.

Example

# Project Planner identity file
version = 1
project = Atlas Field Service
project_type = saas
planner_folder = ./project-planner
schema_version = 1
created_at = 2026-08-14
updated_at = 2026-09-20

Fields

Field	Meaning
`version`	Identity-file format version.
`project`	Human-readable name.
`project_type`	web, desktop, mobile, api, ai, saas, library or other.
`planner_folder`	Relative path to the planning directory. Default `./project-planner`.
`schema_version`	Version of the planning-directory schema.

Planning directory

Planning documentation lives beside application source so that AI coding tools can read it first:

ProjectRoot/
├── .pp
├── application/
└── project-planner/
    ├── README.md
    ├── project-identity/   ├── requirements/
    ├── architecture/       ├── data-flow/
    ├── ui-ux/              ├── agents/
    ├── skills/             ├── mcp/
    ├── memory/             ├── development/
    ├── testing/            ├── security/
    ├── compliance/         ├── deployment/
    ├── decisions/          ├── changelog/
    ├── artifacts/          ├── presentations/
    └── blueprint/

The Windows application is designed to keep these folders in sync with the live project model. This website does not write files.

What other tools should do

If an AI development tool finds a .pp file, it should read the planning directory — identity, requirements, architecture, agent instructions, constraints and security notes — before generating or modifying code. That is the point of the identity file.

Something missing? Send feedback.