Decide tutor payout tracking scope for MVP 0.2

Open
#132 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
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
documentation

Research direction

Read docs/plan-CorvEd.md open question #1 and the tutor payout model in docs/MVP.md first. Decide whether payout tracking belongs in MVP 0.2; document the minimum model and admin workflow if in scope, or the off-platform process and admin-note guidance if not, then create implementation follow-up issues as needed.

Written by the indexing model from the issue text.

Description

Admin P2 Payment question

Context

docs/plan-CorvEd.md asks whether tutor payout tracking needs a payout_records table/admin notes field or should remain fully off-platform for MVP.

Acceptance criteria

  • Decide whether tutor payout tracking is in scope for MVP 0.2.
  • If in scope, define the minimum data model and admin workflow.
  • If out of scope, document the off-platform process and where admin notes should capture payout-relevant context.
  • Update docs and create implementation follow-up issues if needed.

References

  • docs/plan-CorvEd.md open question #1
  • docs/MVP.md tutor payout model
Dominant language
TypeScript
Stars
5
Forks
0
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.