# Project manifests: the project's information card

[Concepts explained](README.md)

A **manifest** is a file describing how a project is organized. Think of an information card on a box: it tells a tool what is inside and where to begin.

Pliro's `.bipli` bundle contains `manifest.json`, source files, and optional assets. The manifest uses [JSON](json.md). Its field names are fixed format names, even for a Dutch project.

## Read the main labels

| Field | What it describes |
| --- | --- |
| `name` | The project's title |
| `entry` | The source file where execution starts |
| `syntaxLocale` | The source-language code, such as `en` or `nl` |
| `schemaVersion` | Which version of the project format is used |
| `appID` | The stable identity used for the app's private data |

A **schema** is a set of rules for a data document's structure. It tells a reader which fields and value kinds are expected. A version lets tools recognize which set of rules applies.

## Identity is not the title

Two projects can have the same title and still be different apps. Renaming a project does not necessarily create a new data identity. In the current project workflow, Save As, Duplicate, and Import as copy give a separate identity so copies do not unexpectedly share private data.

Normally let the IDE manage the manifest. Do not invent fields or replace the identity to try to access another app's data. The [project specification](../../../docs/spec/projects.md) defines the supported format.

Try explaining why a starting filename and a friendly project title need different fields.