The clearest way to evaluate Developer Atlas is not to browse every folder. Complete one controlled change first.
Start with the remaining item-count exercise. It contains a baseline, bounded instruction, two competing patches, exact changed-file records, runnable verification, and maintained evidence and decision examples.
For the shorter static Laravel example, use the 15-minute Control walkthrough.
The public Navigator preview is independently buildable and intentionally smaller than the private product. It traces conventional Laravel controller-array routes to controllers and returned Blade views, packages only four allowlisted public nodes, and includes a clean demo plus a boundary lab.
Build the VSIX and demo ZIP locally, or run the manual packaging workflow after reviewing the branch. A Marketplace signature and broad clean-profile validation remain pending.
Open the six-node Compendium preview directly in a browser. It is generated from allowlisted public Markdown and evidence sidecars only. Search and node reading work locally; primary-source links require internet access.
- Beginner web foundations
- Rookie browser application
- PHP/Laravel bridge
- Knowledge Node samples
- AI Collaboration Pack
These paths support onboarding and research; they are not competing product entry points.
You are not being graded. The workflow is being evaluated. After completing one path, use FEEDBACK.md and report the first unclear instruction, trust concern, or point where you could not decide what to do next.