Permissions for coding-assistant search — Technical — Bachelor’s https://thesis.uya.no/proposals/an-assistant-that-knows-its-boundaries/?degree=bachelor#technical-track FINAL RESULT A permission-aware search demo and exhaustive policy tests. WHAT TO DO Build document search that filters results using a fixed role-permission matrix. DATA 30 fictional documents, 3 roles, 60 queries (planned) Ten documents per project. Define membership and copied-content rules; label authorized relevant IDs for all 180 role/query pairs, including empty-access cases. HOW TO TEST IT Use the fictional repository documents and role-labelled queries; test allowed retrieval and prohibited content/identifier leakage. 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 30 fictional documents, 3 roles, 60 queries. Make the answer key and pass criteria before testing. 4. Build a working version of a permission-aware search demo and exhaustive policy tests. 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, BM25 library, Streamlit, pytest Equivalent tools are fine. ACCESS OR PEOPLE IT participants and one independent policy reviewer.