Development¶

Project setup, contribution rules, signed commits, testing expectations, and pull-request guidance live in CONTRIBUTING.md.

For architecture and ownership boundaries, continue with Architecture Decision Records, Architecture and the Application Boundary Baseline.

Use the decision register to distinguish accepted contracts from private implementation and unresolved choices. Changes to an accepted architectural decision need an explicit successor record; progress notes are not a substitute for decision authority. The open-question register lists known discrepancies without inventing new release blockers.

Before proposing a release, follow the Release Process.

The finite installed-interface and fictional transformation/session acceptance for stable 1.6.0 completed with recorded limits. Use the acceptance matrix to plan new changes; prior results do not approve later code or any dataset.

For versioned builds and offline exports, see Publishing Documentation.