Developer Documentation
This index identifies the current owner for each kind of maintainer-facing information. Canonical documents define project-wide policy, while focused contracts describe one subsystem without superseding their canonical parent.
Canonical project-wide sources
| Area | Current owner |
|---|---|
| Architecture, module ownership, and dependency direction | Architecture |
| Repository paths and build ownership | Repository Layout, with repository_structure_baseline.json as the machine-readable structural contract |
| Code-health and refactoring policy | Code Health |
| Maintainer operations and recovery | Maintainer Runbook |
| Build and dependency workflows | Build and Dependency Guide |
| Dependency maintenance policy and quarterly review | Dependency Management |
| Packaging and platform integration | Packaging |
| CI and release workflow architecture | GitHub Actions workflow architecture, with Main branch protection as the focused ruleset contract |
| Versioning and release/change-history policy | Versioning Policy |
| Localization | Localization, with the Localization glossary as its terminology companion |
| Documentation organization | Documentation Policy |
The repository tree is a navigation aid, not a second architecture or repository-layout specification.
Active subsystem and technical contracts
- MVR: the Canonical MVR contract owns format and behavior rules. MVR identity recovery, grouped transform mutation, attachment paths, and the MVR technical-note entry points cover narrower implementation responsibilities.
- GDTF: GDTF Mutation Policy and GDTF resource identity own write and derivative identity rules. GDTF Share catalog ingestion and the GDTF technical-note entry points cover focused catalog, compatibility, and editor behavior.
- Application and GUI: Startup Architecture, GUI Shortcut Architecture, Storage Policy, and Text-to-scene Rules.
- Command line:
perastage-cliships experimentally with Perastage 1.7.0 packages as a separate headless executable. The Developer CLI owns its grammar and technical contract. The Rust MCP adapter remains separately configured and is not packaged with Perastage. - Semantic commands: the Command API contract owns typed requests, results, headless execution context, transactional mutation, and versioned machine output independently of the current Console grammar.
- Rendering and placement: Viewer coordinate and placement, UI unit systems, and the viewer technical-note entry points.
- Testing and other focused policies: Test fixture policy, PDF portability, fixture category, and the remaining topic-specific documents in this directory. These apply only to their named subsystem and defer project-wide ownership to the table above.
The issue triage policy remains the focused repository-maintenance contract for issue handling.