Deterministic reasoning
Start with a specification: given this state and input, the program must take one of these paths and preserve these invariants. Atlas asks for path coverage and counterexamples, not an eval score that hides which case failed.
Orientation
Five minutes here saves you a week of confusion. This is the whole system — what each section does, how they connect, and how to work it day to day.
New here and want the quick version? Run the step-by-step tutorial first — this page is the deeper reference to come back to.
Software work is splitting: pre-AI skills for specifying, verifying, and operating systems on one side; prompting and assembling libraries on the other. Atlas trains the first group, with AI still present as planner, grader, reviewer, and a tool whose output needs inspection.
Start with a specification: given this state and input, the program must take one of these paths and preserve these invariants. Atlas asks for path coverage and counterexamples, not an eval score that hides which case failed.
Observe the process, memory, syscalls, timing, and failure state before proposing a patch. In Anthropic's 2026 randomized study, the AI-assisted group averaged 50% versus 67% on the mastery quiz, with the largest gap on debugging questions.
Framework calls eventually become instructions, memory traffic, syscalls, and device I/O. Atlas keeps the language, compiler, kernel, and hardware path visible so model.generate() is never the whole explanation.
Existing systems carry contracts that may live in callers, tests, timing, storage, and operational habits rather than a type signature. The job is to identify those dependencies before asking what a local change improves.
A fixed buffer, a deadline, and a finite power budget make tradeoffs concrete. Atlas treats capacity, latency, allocation, and worst-case behavior as part of the specification.
Security begins with the language and runtime behavior already in the program. Atlas makes boundary states, ownership, integer wrap, races, and timing part of review before prompt injection enters the conversation.
The best patch is usually the smallest one that makes the invariant explicit and covers the failure paths. A smaller diff is not better when it only moves the same bug behind a new name.
Atlas is a mastery-paced study system aimed at the job you actually want. New here? The journey runs Learn → Drill → Prove: Coding Fast Track teaches you the material without pressure, Problem Solving drills each skill with instant feedback, and Pathway is where you prove it with portfolio-grade work on schedule. Underneath, the curriculum is split into Phases (like semesters), each phase into Weeks — one topic per week. You move forward when you've learned it, not when a calendar says so, and everything the AI generates aims at your dream job.
The four pinned items in the nav are one story. Start in Coding Fast Track: placement finds your level, then you learn one career-relevant topic at a time with no deadlines. Every Fast Track topic hands you Problem Solving drills for that exact skill — bite-size questions with instant feedback that teach you to reason about evidence before you guess a fix. Once your Foundations labs are done and you want portfolio-grade work, move to Pathway. Best combos: Fast Track + Problem Solving as your default daily loop (learn, then drill); Pathway + Problem Solving when you have homework (drill the skill before the graded work); or all three when you're preparing to apply. Fast Track and Pathway stay in sync — struggles in Fast Track wire directly into your Pathway week.
Your first task in the app. The Lab Path is one sequence of labs beside your pathway: work each in depth, submit a lab report (reasoning, real outputs, code), and Claude grades it — 80+ passes and unlocks the next. Labs 1–3 are the mandatory Foundations: the Linux command line, the toolchain & git, and your first real contact with the field. Until they're passed, homework, mini projects, and projects stay locked — every path needs the baseline before real work. Each pass also raises the ambition of what gets generated for you: portfolio-grade projects you publish to GitHub.
Open This Week to see the current topic. The left rail runs the loop in order: Reading → Tutorial (ungraded items paired with this topic) → Materials (your books & course videos) → Guided Practice → Homework → Mini Project → Project → Report. Graded work aims for real understanding; anything you get wrong becomes a Knowledge Gap tracked until you close it. When everything required is done, an advance card appears — right on the week page. In Study preferences you can mark steps like discussions, homework, or the report Optional; they're never counted against you.
Every assignment gets a score out of 100, and your Phase GPA tracks how well you're absorbing material — a falling GPA is a signal to slow down, not push harder. Advancing is unlimited once the required work is done (optional steps and extra credit never block you), and the pace tracker projects your finish date from your real weekly throughput, so the projection is honest.
Four free tutorials in a fixed order: C first, then C++, then Circuits (the theory and bench builds), then Hardware last (breadboarding, soldering, power supplies, scopes, PCB design). Every tutorial's stages unlock in order — finish one to open the next — and stages that build on another path lock across tutorials too: C++ waits on the core C chapters it assumes, and each Hardware stage waits on its matching Circuits and C stages. Lessons are always free to read ahead; the lock bar tells you exactly what to finish first. Completed check-offs cannot be undone. Every stage ends in a Stage Lab: write every answer, submit once, then the answers lock permanently and worked-answer reveals become available. The week page shows the tutorial items that pair with your current topic.
Material you bring in doesn't sit outside the curriculum — it becomes part of it, and the AI only runs when you ask it to. Documents go through Technical Reading, which is verify-first: books start as recommendations (a wishlist that never touches your plan), and only entering your plan when you upload the actual PDF — its text is extracted as-is (no AI in the conversion), chapters and practice exercises are built from the real content, and the AI judges how useful it is and pins it to the phase it best accompanies. Full video courses go through Courses: a course holds sub-modules (its chapters), each with videos and any homework the course itself provides. Once every video is transcribed, an “Add to program” button appears — one click sizes the course to your pace and dream job, places it, and turns its sub-modules into normal graded weeks with homework, mini projects, and projects generated from the course's own content. Review or undo the placement any time; each video still offers its own ungraded recall quiz, exercise, and mini walkthrough.
Knowledge Gaps compound: a gap that persists 3+ weeks gets flagged red on the dashboard — clear those first, they block everything built on top. Work-Ahead unlocks when the current week is fully closed. The Playground and Practice areas are sandboxes; nothing there affects grades.