Future roadmap: evaluate admissions counseling product line

Open
#151 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
design

Research direction

Read docs/ROADMAP.md Phase 4, docs/ARCHITECTURE.md future-proofing notes, and the docs/MVP.md out-of-scope list. Define whether admissions counseling remains in CorvEd or becomes a separate workflow, including data-model differences and compliance/privacy implications. Done means launch prerequisites are decided and current tutoring MVP flows remain unaffected.

Written by the indexing model from the issue text.

Description

Epic P2 question

Context

The roadmap describes admissions counseling as a separate Phase 4 product line with deliverable-based packages, document upload, essay/application feedback, and higher-touch support. It should not leak into the tutoring MVP, but it is worth tracking as a distinct future decision.

Acceptance criteria

  • Define whether admissions counseling belongs in CorvEd or should become a separate product/workflow.
  • Sketch the minimum data model differences: deliverables, documents, calls, feedback cycles, and package pricing.
  • Identify compliance/privacy implications for document upload and application materials.
  • Decide launch prerequisites before any implementation issues are opened.
  • Keep current MVP tutoring flows unaffected.

References

  • docs/ROADMAP.md Phase 4 admissions counseling product line
  • docs/ARCHITECTURE.md future-proofing notes
  • docs/MVP.md out-of-scope list
Dominant language
TypeScript
Stars
5
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Taleef7/CorvEd

All issues in Taleef7/CorvEd

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.