If you followed Getting Started from the top, you’ve gone the whole way: you created an organization, connected GitHub, created a project, designed a pipeline, ran a task, and approved its plan. That run is now working through your pipeline, opening a pull request at each stage.
The walkthrough ends here. The rest of the documentation isn’t a sequence — it’s there for you to reach into when you need it. This page points you at the right part.
Follow the run you started
Your first run is still going. To stay with it:
- Run states — every state a run moves through, and what each one means you should do.
- Stage states — what a single stage is doing while the run works through your pipeline.
- The pipeline: stages and gates — a refresher on gates, the checkpoints where a run waits for you.
When a run reaches a gate, it pauses for you to merge a pull request or otherwise sign off. Merge it, and the run carries on to the next stage. When the last stage clears, the delivery is done.
Rate the delivery
Once a run completes, its task page shows a short survey — How did this delivery turn out? — with three answers: Didn’t work, Used after fixes, or Used as-is, plus an optional comment. It’s optional and one rating per run, but it’s the most direct way to tell DIJJI.ai whether the output actually landed. After you rate it, a brief thank-you takes the survey’s place.
Learn the vocabulary
Getting Started moved fast to get you to a first delivery. Concepts slows down and explains the pieces properly — read it once and the rest of the documentation reads more easily.
- Projects, tasks, and runs — the three units of work and how they nest.
- Organizations and teams — how access and billing are scoped.
- Plans and plan approval — why the approval checkpoint exists and what it protects.
- Credits and billing — what a credit is, how your balance is spent, and the minimum balances.
- Integrations — what connecting GitHub and Slack changes for you.
- Roles: admin and member — who can see and do what.
- The audit log — where to find a record of what changed and who changed it.
Do more
Now that one project works, you’ll want to grow your setup — add stages, invite teammates, set a spending limit, wire up Slack. The How-to guides cover those operations one at a time: find the task you need on the documentation index and follow it end to end.
Look something up
When you need an exact answer — a limit, a permission, a state transition — the Reference section has it. It’s the part you’ll land on from search rather than read front to back.
When something looks wrong
If a run stalls, an integration drops, or a page you expect isn’t there, the Help section diagnoses the common situations and points you to support. Start from the documentation index and look under Help.
You’re set up
Your workspace is built and your first delivery is on its way. From here, DIJJI.ai is something you operate rather than set up — keep this documentation open in a tab, and reach for the section that matches what you’re trying to do.