Submitting evidence for review
A submission is how a mentor reviews your work without guessing. It bundles what you did, proof they can inspect, and an honest account of any AI involvement.
Evidence types
A task's evidence expectations are written as plain guidance, not a fixed picker — but they'll typically point you at something like a repository, commit, tag, url, markdown, file reference, screenshot reference, test result, benchmark, demo, or other — whatever the task actually needs.
Whatever form it takes, evidence should be something a mentor can actually open — a commit, a repository, a test run, a specific file — not a claim. What you submit today is a single evidence note attached alongside your reflection, written to satisfy whatever the task's evidence expectations ask for. As the in-app help puts it: "I did it" is not evidence.
Before you can submit
Submit for review stays disabled until three things are complete:
- Reflection — at least 20 characters answering what you tried and what's still unclear.
- Evidence note — at least 8 characters pointing at something inspectable: a commit, a repository path, a conflict-resolution note, a test run.
- AI disclosure — required whenever
the task's policy asks for it. Choose one:
- •None — you did not use AI on this task.
- •Assisted — AI explained a concept, asked a Socratic question, or gave a hint; you wrote the notes, code, and evidence.
- •Generated — AI produced substantial wording or code that you adapted into the submission.
Leaving disclosure blank is not the same as choosing None — pick deliberately. If a task has AI-sourced notes attached but disclosure is still None, the app warns you (it will still let you submit if the task's policy allows that combination) rather than silently rewriting your answer.
What happens after Submit
Your submission becomes a durable, structured record in your fork, visible to your mentor once they sync. From there, a submission moves through: submitted → approved, or submitted → revision requested → resubmitted → approved (or revision requested again).
If your mentor requests a revision, you'll see their comment on the task, make the change, and resubmit — the history of every round trip stays attached to the task, not just the latest attempt.