From 2cdfe71707939fd6b19ef5e3fb24e931f8dbeb5a Mon Sep 17 00:00:00 2001 From: Daniel Date: Mon, 7 Sep 2026 01:00:50 +0200 Subject: [PATCH] docs: record revamp execution authorization and defaults --- docs/quiz-revamp-plan.md | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/docs/quiz-revamp-plan.md b/docs/quiz-revamp-plan.md index 92ca86a..f4a36de 100644 --- a/docs/quiz-revamp-plan.md +++ b/docs/quiz-revamp-plan.md @@ -1,6 +1,6 @@ # Orthobullets-inspired quiz revamp -Status: scoped, not implemented. User requested Git tracking and Forgejo synchronization. +Status: implementation authorized and in progress. Git tracking and Forgejo synchronization are ongoing requirements, not a stopping point. Complete the staged implementation, tests and review without another scope-approval gate. ## Confirmed requirements @@ -54,9 +54,9 @@ Provide side-by-side reading on desktop and an accessible mobile drawer. Treat e Reuse `get_model_for_task`, existing LiteLLM configuration, Celery and job-progress UI. Existing classification produces tags, not category hierarchy; add reviewable category suggestions rather than automatically moving questions. Support article drafting/refinement and cards from authorized questions/articles. -Proposed default (pending confirmation): shared educational AI content is educator-authored and remains draft until approved. Do not fabricate reference claims or auto-publish generated material. Learner-private AI drafting is a separate permissions/cost decision. +Implementation default: shared educational AI content is educator-authored and remains draft until approved. Do not fabricate reference claims or auto-publish generated material. Learner-private AI drafting is not required for this release. -Add comments with author ownership, moderation state, pagination and server-side educator controls. Proposed default: learners see their own pending comments; public visibility requires educator approval. Sanitize rendered content and bound request sizes/rates. +Add comments with author ownership, moderation state, pagination and server-side educator controls. Implementation default: learners see their own pending comments; public visibility requires educator approval. Sanitize rendered content and bound request sizes/rates. ### 5. Verification and release @@ -64,10 +64,9 @@ Use existing Vitest/Testing Library and backend tests. Cover category cycles/des Run frontend build and targeted/full relevant suites; obtain independent review, inspect actual diffs and browser-check visible outcomes. Use versioned reversible migrations, a database recovery point and matching backend/Celery/frontend builds. Verify live behavior after an approved rollout; retain rollback information. -## Remaining product decisions +## Delivery defaults -1. AI authorship: educators/admins only, or learner-private generation too (shared publication still moderated)? -2. Lab content: educator-supplied data with an initially empty panel, or cited pediatric age-specific seed data for educator review before publication? -3. Confirm the proposed staged implementation and moderation defaults before application edits. - -No app implementation, migrations, AI-generation jobs or deployments were performed during this scoping/Git synchronization work. +- AI authoring is available to educators/admins; generated shared material requires review before publication. +- Lab-reference support includes educator-managed entries and source/age/unit fields. Do not publish unsourced or AI-invented ranges. An honest empty state is permitted until verified clinical data is supplied. +- The user has authorized implementation. Continue each completed milestone into verification, review, Git synchronization and the next milestone; stop only for a genuine blocker. +- No migrations or deployments were performed during the initial scoping/Git synchronization. Subsequent implementation and validation evidence must be recorded in focused commits.