CLAUDE.md

Change process

For any changes, the following must always be done, in sequence:

1. Requirements specification for each software component: create with unique IDs for each requirement. Changes or new documents need approval from user before continuing to the next step. Version must match the software specification (requirements.md).

2. Design specification for each software component: create based on the requirements document. Changes or new documents need approval from user before continuing to the next step. Version must match the software specification (requirements.md).

3. Implementation of software according to specifications. The writing of the code.

4. Testing of each software component against its requirements document. Output:

   • Test reports (Pass / Fail / Cannot be tested)
   • Test coverage statistics to requirements

5. Write documentation (README.md guides as specified in requirements.md).

Exceptions for testing

The following requirement types are excluded from testing:

• Process requirements
• Design and architecture requirements
• Documentation requirements