Approving software changes — Technical — Bachelor’s https://thesis.uya.no/proposals/from-promise-to-proof/?degree=bachelor#technical-track FINAL RESULT A release-review prototype and checklist evaluation. WHAT TO DO Build a release dashboard showing tests, changed files and a manual approval checklist. DATA HumanEval/0–29 + clean/mutated variants (mixed) Derive checkable requirements from prompts. Create one demonstrably faulty edge-case mutation per task; retain clean controls and independently checked hidden witness tests. HumanEval: https://github.com/openai/human-eval HOW TO TEST IT Use the fixed code patches and independent test keys; verify displayed results and observe approval tasks. Plan 4 participant sessions. STEPS Build and test 1. Read the starting sources and choose one established implementation method. 2. Write the requirements, data fields, system diagram and test cases. 3. Prepare HumanEval/0–29 + clean/mutated variants. Make the answer key and pass criteria before testing. 4. Build a working version of a release-review prototype and checklist evaluation. 5. Run function, integration and failure-case tests. Record each result. 6. Run the practical evaluation and list the changes the system still needs. EXAMPLE TOOLS Python, pytest, coverage.py, SQLite, HumanEval, Streamlit Equivalent tools are fine. ACCESS OR PEOPLE Recruit developers; run code in an isolated test environment.