Guided route. One clear move at a time.
Take the guided route from first impression to proof, then the operator desk.
This page is not a docs fragment. It is the shortest guided tour from the front door, to proof, to the workbench, and then to one real repo-owned command.
Minute-one route
Read the front door like a product evaluator
Start on the homepage, then jump into proof or compare depending on whether you are validating trust or market fit.
See the proof desk first
The proof desk explains what the repo has already proved, what still needs a human call, and why the operator desk comes later.
Open the operator desk once the proof meaning is clear
The workbench is the repo-local simulated operator desk inside apps/web. It is where smoke, e2e, visual QA, and UI/UX audits land after the proof contract is clear.
Read the longer walkthrough notes and run one real command
The app front door and the repo docs should tell the same truth. Use the longer walkthrough notes, then run a real repo-owned command before you treat the story as proven.
Pick the path that matches how deep you want to go.
This page should feel like a tour guide, not a detached doc excerpt. Each stop has one job, one question, and one next move.
Read the front door like a product evaluator
Start on the homepage, then jump into proof or compare depending on whether you are validating trust or market fit.
See the proof desk first
The proof desk explains what the repo has already proved, what still needs a human call, and why the operator desk comes later.
Open the operator desk once the proof meaning is clear
The workbench is the repo-local simulated operator desk inside apps/web. It is where smoke, e2e, visual QA, and UI/UX audits land after the proof contract is clear.
Read the longer walkthrough notes and run one real command
The app front door and the repo docs should tell the same truth. Use the longer walkthrough notes, then run a real repo-owned command before you treat the story as proven.
Run one real command before you decide how deep to go
The walkthrough should end in something concrete. Think of this as the boarding pass that proves you actually reached the right gate.
npm run demo:ship
npm run smoke:e2e
npm run repo:doctor
npm run visual:qaChoose the next route after the tour.
The front door should not force one journey. It should route a newcomer to the right depth quickly.