0002: Project Maps Are Proportional Profiles

Status: Accepted for STAGE 0.3

Context

The same documentation depth imposed on a two-script prototype and a multi-editor production project creates either omission or bureaucracy.

Decision

Project maps declare one profile:

• compact: the smallest complete orientation and safety map;
• standard: domain, lifecycle, authoring, operation, ownership, and evidence detail for a maintained game;
• extended: cross-tool, generated-content, external-audit, or high-risk production detail.

Profile selection follows coordination and change risk, not prestige or line count. A compact map may expand one risky surface without becoming extended.

Consequences

• Empty boilerplate is discouraged.
• The core questions remain stable while artifact depth varies.
• Conformance cannot be inferred from document length.