Onboarding Path

A two-week guided track for getting comfortable with HiveCFM. Each week ends with a concrete, reviewable outcome: by the end of Week 1 you can run the stack and explain what is happening inside it; by the end of Week 2 you have shipped a small change to production behind a PR.

The two weeks at a glance

• Week 1 — Explore & run. Get the stack running, trace a request from button-click to database insert, read both flow diagrams, and find your way around the monorepo. Output: you can confidently answer “what does each service do?” without opening a file.
• Week 2 — Ship your first change. Pick up a small feature slice: add a Prisma field, migrate it, write a test, extend an API, and (if time) add a Go worker or a runbook entry. Output: a merged PR.

How to use these pages

Each week is a checklist. Today the checkboxes are plain Markdown — they do not persist. An interactive OnboardingProgress component that remembers what you have ticked lands in task P3.1; the copy will stay identical, so starting now is safe.

Every milestone has three parts:

1. What to do — a verb, a file, and an outcome.
2. What file to open — the real path, not an abstraction.
3. Why it matters — so you know what you should understand after finishing it, not just that it “worked”.

Ground rules

• Ask sooner rather than later. The fastest onboarding we have seen had two or three messages on day one asking “is this line doing what I think it’s doing?”
• Read the [Getting Started](/getting-started) pages first. Everything here assumes you have skimmed What is HiveCFM?, Tech Stack, and Run it locally.
• Keep a log. A file called onboarding-notes.md in your home directory, updated daily, is worth more than any wiki page.

Open Week 1 when you are ready.