DIJJI.ai Academy

Documentation

Everything you need to operate DIJJI.ai — from your first delivery to day-to-day reference.

Interactive walkthroughs Prefer to learn by doing? Walk the product surface — a guided scroll, a live run, and a pan-zoom map.

Getting Started

New to DIJJI.ai? Start here. These pages take you from creating an account to shipping your first delivery.

  • Welcome to DIJJI.ai

    What DIJJI.ai is, who this documentation is for, and where to start.

  • Sign up and verify your email

    Create your DIJJI.ai account with the email verification code — what each field asks for, and how to fix a code that won't go through.

  • Find your way around

    A quick tour of the interface once you're signed in — the Inbox home, the icon rail, the breadcrumb bar, the Cmd-K command palette, light and dark mode, and the help tooltips.

  • Create your organization and team

    Your organization already exists — here's how to name it, set its logo, and create the teams that organize your projects and people.

  • Connect GitHub

    Install the DIJJI.ai GitHub app, choose which repositories to share, and confirm the connection is healthy — the one connection your projects can't run without.

  • Connect Jira

    Authorize DIJJI.ai against your Atlassian site, label the issues you want synced, and confirm the connection is healthy — an optional second source for tasks alongside GitHub Issues.

  • Create your first project

    Fill in the New Project form — name, team, repository, and trunk branch — and clear the $100 balance gate so DIJJI.ai can start delivering work.

  • Design your first pipeline

    Open your project's Pipeline page, start from a template or build by hand, then set each stage's name, branch, and gate — and save.

  • Run your first task

    Open Deliver > Tasks, pick a task that came in from GitHub Issues, and select Run — then watch the first run begin.

  • Approve a plan

    Your first run paused at Awaiting Plan Approval. Open the run detail page, read the plan it produced, and decide whether to approve it or send it back.

  • After your first delivery

    You've taken a task from issue to approved plan to a run working through your pipeline. Here's where the rest of the documentation picks up.

Concepts

The vocabulary of DIJJI.ai — what each thing is and how the pieces fit together. Read these once and the rest of the documentation reads more easily.

  • Projects, tasks, and runs

    The three things you'll see most often in DIJJI.ai and what they mean.

  • Blueprint: your project's design docs

    What a Blueprint is — the four design documents DIJJI.ai generates for a project, how you review them, and what writing them to the repository does.

  • Requests: turn an idea into tasks

    What a Request is — describe what you want, let DIJJI.ai break it into ordered work items you review, and save them as tasks.

  • The task queue

    How a project runs one task at a time and lines the rest up — what In Queue and Queued mean, how tasks join the queue, and how to reorder, hold, and release it.

  • Organizations and teams

    How DIJJI.ai groups your work — what an organization holds, what a team scopes, and where each setting lives.

  • The pipeline: stages and gates

    How a delivery travels from first branch to production — what a pipeline is, what a stage does, and what a gate decides.

  • Plans and plan approval

    Before DIJJI.ai writes code, it shows you a plan — what that plan is, why you approve it, and what happens when you approve or reject.

  • Run states

    Every state a run can be in — running, the five ways it pauses for you, and the three ways it ends — and what each one means.

  • Stage states

    What each stage is doing while a run travels the pipeline — pending, in progress, waiting for gate, waiting for deploy, passed, and failed.

  • Credits and billing

    What a credit is, how your organization's balance works, what charges look like, and the minimum balances you need to start work.

  • Integrations: what each connection does

    What connecting GitHub, Jira, and Slack to DIJJI.ai changes for you, and which connections you actually need.

  • Roles: admin and member

    What an admin can do that a member can't in DIJJI.ai — and where that difference shows up on screen.

  • The audit log

    Where DIJJI.ai records what changed, who changed it, and when — and how to read an audit entry.

  • Assurance: regression and security regression suites

    What Assurance is — on-demand regression and security regression suites you run against a live deploy, each an immutable report whose delta is measured against the suite's previous run.

  • The Needs You inbox: your home screen

    What the Needs You inbox is and how to read it — the attention-first home screen that gathers every gate, approval, question, failure, and live run across all your projects in one place.

  • Project sections: Overview, Plan, Deliver, Assure, Reports, Settings

    How a project is organized — the six top-level sections, the sub-features inside Plan, Deliver, and Assure, and the path style every how-to uses to point you somewhere.

How-to

Step-by-step walk-throughs of individual tasks. Find the operation you need and follow it end to end.

Projects

  • Create a project

    Open the New Project form, fill in the four required fields, clear the $100 balance gate, and land on the new project's Overview page.

  • Edit a project's name or description

    Open a project's Settings, change its name or description in the General card, and save the change.

  • Pause, archive, or delete a project

    Move a project through its lifecycle states from the Project Lifecycle card in Settings — pause it to stop new tasks, archive it to retire it, and delete it once archived.

  • Reset Dijji to recalibrate a project

    Rebuild DIJJI.ai's understanding of a project from scratch when its grasp of the code looks wrong — from the project's Settings danger zone.

  • Set up Slack notifications for a project

    Connect a Slack channel to a project so it receives updates when tasks start, finish, or need your attention — connect a webhook, send a test message, and manage the connection from the project's Settings pill.

  • Generate and write a Blueprint

    Generate your project's four design documents, review and correct them, and write them to the repository as a pull request.

Pipeline

  • Add a stage to a pipeline

    Add a new stage to a project's pipeline, set its name, branch, and gate, and save the change.

  • Reorder stages

    Change the order stages run in by dragging them along the pipeline row, then save.

  • Change a stage's branch

    Point a pipeline stage at a different branch, understand the no-repository warning, and save the change.

  • Choose a gate type for a stage

    Set the gate on a pipeline stage so a run pauses for your approval or flows straight through.

  • Delete a stage

    Remove a stage from a project's pipeline and save the change.

  • Deploy confirmation and the deploy wait

    Make a stage wait for its deployment before the run moves on — turn deploy confirmation on or off, read the Waiting for Deploy state, and use Force Advance if the confirmation never arrives.

Tasks and runs

  • Create a request and save it as tasks

    Describe what you want, let DIJJI.ai break it into ordered work items, review them, and save them to your task list as pending tasks.

  • Where tasks come from

    How issues in your connected GitHub repository become tasks in DIJJI.ai — the dijji label, what keeps a task in sync, and the Tasks page.

  • Switch task views: Board and List

    See a project's tasks two ways — a Board that lays out the whole flow of work, or a List filtered to one status — and search within them.

  • Execute a task

    Start a run on a task from the Tasks page or task detail page — including the balance and active-run checks that run first.

  • Keep your project in sync with your code

    When your code changes outside DIJJI.ai, sync before you run — what the "map is out of date" prompt means, how Sync first works, and why the sync is free.

  • Approve or reject a generated plan

    Open a run that's waiting at Awaiting Plan Approval, read the plan, and either approve it to continue or reject it with a reason.

  • Resume a run that's waiting on a gate

    Get a run moving again when it has stopped at a stage's gate — review and merge the stage's pull request, then watch the run advance.

  • Resume a run that's waiting for payment

    Get a run moving again after it paused because your organization's balance ran out — top up the balance and let the run continue, or resume it yourself.

  • Answer a question a run is waiting on

    Get a run moving again when it has stopped to ask you a question — read what it's asking, type your answer, and let it pick up where it paused.

  • Add context with issue comments

    Read the comments on a task's source issue in the Issue tab, and fold new comments into a run that's still working with Apply comments.

  • Cancel a running task

    Stop work that's underway — cancel the current run to end one attempt, or cancel the whole task to stop all work on it — and know what each does.

  • Pause and resume a run

    Put a running task on hold without losing your place — pause it while it's developing, then resume from where it stopped, on the task or run detail page.

  • Delete or archive a task

    Take a task off your list — delete a pending task you never ran, or archive a cancelled one to hide it while keeping its history.

  • Retry a failed run

    When a run ends in Failed, read why it stopped and start a fresh attempt with Re-run — a clean run from the beginning, not a resume.

  • Trigger E2E tests manually

    When a stage is set to trigger E2E tests manually, start them yourself from the run detail page — confirm the deploy, run against the stage's configured targets, and watch the result.

Assurance

  • Run an assurance suite and read its results

    Trigger a Regression or Security Regression suite against a live deploy, then read its delta, suspect changes, coverage gaps, and case results.

  • The Delivery & Governance Report

    Read and export the project's Governance report — delivery outcomes, what the gates caught, input rigor, and cost — as evidence for stakeholders and auditors.

Integrations

Members

  • Invite a team member

    Send an invitation to join your organization, choose the new person's role, and resend or revoke an invite that's still pending.

  • Change a member's role

    Promote a member to admin, or move an admin back to member, from the Members page.

  • Remove a member

    Remove a person from your organization, what removal takes away, and the one person you can't remove.

  • Create, rename, or delete a team

    Add a team to your organization, edit its name or description, and delete a team you no longer need — including why some teams can't be deleted.

Billing

  • Set a daily spending limit

    Cap how much your organization can spend in a single day, what happens when the limit is reached, and when it resets.

  • Read your usage charts

    Open the Usage & billing screen, switch between organization, team, and personal scope, change the date range, and read the spend charts and top-spender rankings.

Account

Navigation

Reference

Exhaustive lookups — states, limits, permissions, formats. Land here from search when you need an exact answer.

  • Run states reference

    Every run state at a glance — what each means, how a run enters it, and what action it leaves you.

  • Stage gate types reference

    The gate options for a pipeline stage side by side — what each waits for, how a run clears it, and when to pick it.

  • Roles and permissions

    The full admin-versus-member permission matrix — every action, and which role can do it.

  • Balances, spending limits, and time

    Every billing number in one place — the minimum balances, the low-balance warning thresholds, the daily spending limit, and how times are displayed.

  • Invite expiry and retention

    How long an invitation stays valid, the rules for resending one, and what happens to an invite once it expires.

  • How spend works

    When the balance is drawn down, where run spend shows up, and what the transactions list does and doesn't record.

  • Notifications reference

    Every email and Slack message DIJJI.ai sends — what triggers each, what it contains, and how to configure delivery.

  • Delivery Evidence reports

    Field-by-field reference for the per-deploy Delivery Evidence report — the fused functional and security audit document for one deploy, its header, sections, and PDF export.

  • Engine Configuration: quality and reasoning depth

    The two project-wide controls on the Engine Configuration card — a quality-and-speed tier and a reasoning-depth tier — what each option does, how they interact, and where higher settings cost more.

Help

Something not behaving as expected? These pages diagnose the common situations and point you to support.