This repository is the planning and design source for VirtuJudge. VirtuJudge helps teams practise a pitch, review measurable delivery signals, answer grounded follow-up questions, and receive evidence-linked team and individual feedback.
The current delivery target is a ten-day competition MVP. Production hardening and larger product ideas are recorded separately so they don't silently enter the MVP.
- Product scope
- Requirements and success measures
- Risks and evidence gaps
- Domain language
- User-story map
- System architecture
- Backend architecture
- AI/ML architecture
- Technology stack
- Security, privacy, and retention
- Frontend/backend API
- Backend/AI contract
- Job and notification catalogue
- Data contracts
- Ten-day delivery plan
- Testing and quality plan
- Review workflow
- Documentation review
- Future work
- Repository bootstrap
- Architecture decisions
- Original proposal
Proposal/VirtuJudge-Proposal.pdfPresentations/Presentation.pdf
The proposal is the source of the product idea. The documents linked above resolve ambiguities in it and define the plan that should be reviewed before implementation starts.
- Change the contract or decision document before changing behaviour.
- Keep diagrams and examples consistent with the written contract.
- Record hard-to-reverse decisions as ADRs.
- Run the documentation and contract checks before requesting review.
- Do not merge reviewed contract snapshots by hand when they can be generated from a service-owned schema.