Vegman · documentation

Vegman Documentation

Research, requirements and design notes for the school-timetabling product. Israel first, generalize later.

Documents

Research and market brief What problem we are solving in exact computer-science terms, which solver to build on, how the Israeli and global markets work, the research frontier and AI, and Vegman's inputs from Mevo Hagalil. English and Hebrew, glossary tooltips, search. תקציר מחקר ושוק: הבעיה, הפותר, השוק בישראל ובעולם, חזית המחקר ו-AI, והקלט של ווגמן ממבוא הגליל.
apps/docs/site/brief.html · sources in apps/docs/content/
Mevo Hagalil requirements, v0.1 The pilot school's timetable rules with IDs (R, S, Q, N), translations, interpretations, evidence from the achieved timetable, and open questions. Standalone copy of section 6 of the brief. דרישות מערכת השעות של מבוא הגליל, עם מזהים, פרשנות, עדויות ושאלות פתוחות.
generated from apps/docs/content/requirements/mevo-hagalil.en.md
Mevo Hagalil requirements table The same items as a sortable, filterable table: ID, category, title, statement, Hebrew original, kind, scope, status, priority, evidence, related IDs, source. Column toggles and CSV export. טבלת הדרישות: ניתנת למיון ולסינון, עם ייצוא CSV.
generated from apps/docs/content/requirements/mevo-hagalil.json

Design

Domain model proposal How the product models a school and everything it must timetable: organisation, people, curriculum, events, constraints and timetable versions. Entity diagram, entity catalogue, and the mapping from Vegman's requirements to model elements. הצעת מודל התחום: ישויות, קשרים, ומיפוי הדרישות למודל.
generated from apps/docs/content/design/domain-model.md
API and data contract, v0.1 The single agreement between the engine track and the experience track: JSON shapes for every domain object, the constraint types with their parameters, and the HTTP endpoints. Both tracks build against it. חוזה ה-API והנתונים: צורות ה-JSON, סוגי האילוצים ונקודות הקצה שהצד השרתי וחוויית המשתמש בונים מולן.
generated from apps/docs/content/design/contract.md
Solver strategy: living with NP-completeness How the engine makes the problem tractable without pretending it is easy: fix what is decided, decompose, let CP-SAT propagate and learn, run anytime, warm-start and repair. With measured numbers from Mevo Hagalil's real timetable. אסטרטגיית הפותר: איך הופכים בעיה NP-שלמה לפתירה בפועל, עם מדידות על המערכת האמיתית של מבוא הגליל.
generated from apps/docs/content/design/solver-strategy.md · engine track
Personas and flows Who uses the product and how: the timetable coordinator as primary persona, nine journeys from import to mid-year change, information architecture, the RTL and bilingual approach, what explainability looks like on screen, and a screen inventory with build status. פרסונות ותהליכים: מי משתמש במוצר ואיך, מסעות המשתמש, ארכיטקטורת המידע ומלאי המסכים.
generated from apps/docs/content/design/ux-personas-flows.md · experience track

Applications

Timetable application prototype The working UI prototype against a stubbed backend: dashboard, timetable grid in class, grade and teacher views, violations panel, staff and availability, constraints checklist, solve dialog, drag-to-swap and local repair. Hebrew RTL by default. אב-טיפוס של יישום מערכת השעות מול שרת מדומה.
apps/web · served at /app/ · locally: cd apps/web && npm run dev (port 5173)
Back-office The question exchange with Mevo Hagalil: every question with its filed and live answers, the questionnaire link for Vegman, and exports. Password protected. משרד אחורי: חילופי השאלות והתשובות עם מבוא הגליל.
apps/backoffice · FastAPI in Docker · served at /backoffice/, /q/, /api/

How this site is maintained

Markdown files under apps/docs/content/ are the source of truth for generated sections. Run npm run build in apps/docs to regenerate, and npm run dev to serve the site at localhost:4173. Reference data that must not be published lives outside the site, under data/.