Put the highest-priority reviewer asks, copy-ready messages, submission links, and sent-event recording commands on one public page so real outreach can happen without inventing outcomes.
5prioritized asks
5not sent
0accepted evidence
0resume upgrades
Next Reviewer Asks
#1 · ai_engineer_review_items
AI engineer, mentor, or ML systems reviewer
Choose one AI/ML engineer, professor, mentor, or advanced student who can inspect agent architecture.
python scripts/record_reviewer_outreach_event.py --slot-id review_slot_07 --status sent --reviewer-contact "" --channel-used "LinkedIn DM or mentor email" --note "Sent ai_engineer_review_items reviewer request"
A non-owner public GitHub issue passes the external reviewer evidence gate, includes explicit permission to count the evidence, and contains no private data.
#2 · confirmed_external_users
reviewer who opened the demo or ran the repo
Choose one person who can simply open the demo and confirm what they tried.
python scripts/record_reviewer_outreach_event.py --slot-id review_slot_04 --status sent --reviewer-contact "" --channel-used "class Discord, friend DM, or club Slack" --note "Sent confirmed_external_users reviewer request"
A non-owner public GitHub issue passes the external reviewer evidence gate, includes explicit permission to count the evidence, and contains no private data.
#3 · reproducible_feedback_items
engineer comfortable with Docker or local setup
Choose one developer who can run a command or inspect the local replay instructions.
Channel: GitHub issue comment, Discord, or DM to a developer comfortable with Docker
python scripts/record_reviewer_outreach_event.py --slot-id review_slot_03 --status sent --reviewer-contact "" --channel-used "GitHub issue comment, Discord, or DM to a developer comfortable with Docker" --note "Sent reproducible_feedback_items reviewer request"
A non-owner public GitHub issue passes the external reviewer evidence gate, includes explicit permission to count the evidence, and contains no private data.
#4 · business_case_feedback_items
data analyst or analytics student
Choose one person who has seen messy spreadsheets, support tickets, sales data, or operations data.
Channel: email or in-person ask to someone who has handled messy operational data
python scripts/record_reviewer_outreach_event.py --slot-id review_slot_05 --status sent --reviewer-contact "" --channel-used "email or in-person ask to someone who has handled messy operational data" --note "Sent business_case_feedback_items reviewer request"
A non-owner public GitHub issue passes the external reviewer evidence gate, includes explicit permission to count the evidence, and contains no private data.
#5 · external_feedback_items
UC Davis data science peer
Choose one peer who can leave specific product or README feedback.
Channel: LinkedIn DM, class Discord, or project channel
python scripts/record_reviewer_outreach_event.py --slot-id review_slot_01 --status sent --reviewer-contact "" --channel-used "LinkedIn DM, class Discord, or project channel" --note "Sent external_feedback_items reviewer request"
A non-owner public GitHub issue passes the external reviewer evidence gate, includes explicit permission to count the evidence, and contains no private data.
Counting Boundaries
Recording a sent message proves distribution execution only.
Private replies do not count as public evidence.
A resume outcome is upgraded only after a non-owner public GitHub issue passes the evidence gate.
Do not include raw business rows, secrets, customer names, private emails, addresses, or tokens.