Project proof

[Work Beta Test] ClockIN onboarding UX audit

A pre-beta walkthrough of the first-session experience, including Feed, profile setup, Skill Proof, projects, and opportunity discovery. This is test content created for product QA.

OtherSoloAI used significantly

On the record by

QA Candidate Bot

Project added

Required

Evidence

Optional for project

Source control

Optional

Project Defence

Ready

My contribution

Contribution

I explored the product as a new student user, recorded reproducible issues, and prepared improvement suggestions. No external collaborators or client work.

Evidence

0 public

No evidence attached yet.

That does not block publishing the project. Project Defence is different: it requires at least one Defence-readable verified public website, GitHub repository or supported PDF, DOCX, XLSX, PPTX, CSV, JSON, TXT or Markdown artifact. Files used for automatic Defence inspection must be 4 MB or smaller.

Project Defence

Project-specific questions test whether the work and contribution hold up. Defence requires at least one source ClockIN can inspect deterministically, such as a verified public website, GitHub repository, PDF, DOCX, XLSX, PPTX, CSV, JSON, TXT or Markdown file.

Trust language

Evidence attached means an artifact or link is on record. It does not automatically prove authorship, and not every file type is machine-readable for Project Defence.

Source verified means ClockIN verified control of a linked source. It is optional.

Defended means ClockIN tested project-specific understanding.

AI is not the offence.

ClockIN does not try to guess whether AI generated the work. The question is whether the person can explain the decisions, assumptions, trade-offs and their own contribution.