Decisions

In one sentence: The agreed choices behind these docs and behind RIQS business rules, so nobody has to ask the same question twice.

Add a new row at the top when a decision is made. Never delete a row. If a decision changes, add a new one and mark the old one as Replaced by D-x.

ID	Date	Decision	Why	Status
D-7	2026-10-27	The site is hosted on Azure Static Web Apps and deployed automatically on every merge to main.	GitHub Pages could not be switched on for the organisation repository.	Active
D-6	2026-10-27	Pages without agreed content are created with Status: Will be added later instead of being left out.	Readers see the full map of RIQS, and gaps are visible.	Active
D-5	2026-10-27	The knowledge base lives in the organisation repository. Docs are in docs/, design prototypes in design/.	One shared place for the whole team.	Active
D-4	2026-10-26	Screenshots are taken from the test system with test accounts. Module screens show the Power User view, administration screens the Administrator view. Email addresses and phone numbers are blurred.	Power User is closest to what most users see; the site can be opened by clients.	Active
D-3	2026-10-26	The RIQS wiki Roles & Rights sheets are the source of truth for permissions. They win over the feature list. Where the app differs, the gap is tracked internally and fixed in the app later.	The sheets are the agreed target; the app will be aligned.	Active
D-2	2026-10-26	Pages use the names shown on screen (for example Day Planner, Monitor, ToDos) and the business word unit (not "client").	Readers must find what they read.	Active
D-1	2026-10-26	Audience is internal team and clients. No repository, code, API or ticket names in page text. The mobile app is out of scope for now. The React web app is the current app.	Business docs, not technical docs. Architecture comes later.	Active

Last reviewed: 2026-10-27