# Contributing to Jarassic Park — The Symbian Heritage Archive

## Before changing code

1. Read `README.md`, `AGENTS.md`, and `docs/README.md`.
2. Link the work to a GitHub issue and state the intended outcome.
3. Create a focused branch from the default branch.
4. Keep secrets, personal data, generated state, and private scratch files out of git.

## Change discipline

- Prefer small coherent commits with meaningful messages.
- Update architecture, decisions, operations, brand, or visual docs when their contract changes.
- Validate in proportion to risk; always run the mandatory build or smoke path.
- Explain user impact and evidence in the pull request.

## Review

A change is ready when its behavior, documentation, and operational consequences agree.