DIJJI.ai organizes work around three nouns. Most pages in the product are some shape of one of them.
Project
A project is a workspace tied to a repository. It’s where the work happens. Each project has its own settings, its own task list, its own audit trail, and its own credit usage.
You’ll have one project per piece of software you want DIJJI.ai to work on. A team usually has several projects under one organization.
Task
A task is a unit of work — a feature to add, a bug to fix, a change to make. Tasks come from your project-management tool: connect Jira or GitHub Issues to a project, and issues there become tasks here automatically. There’s no separate place to file work; the issue you’d write anyway is the task.
A task carries:
- A description of what you want done (from the source issue).
- The project it belongs to.
- Its current state — waiting, queued, running, delivered, or one of the failure states.
- A history of attempts (its runs).
Run
A run is an attempt at delivering a task. Most tasks have one run; some have several.
A run starts when the platform begins working on a task and ends when it produces a delivery, gets paused, or gets cancelled. You can pause a run mid-flight, resume it later, throw it away and start fresh, or accept the delivery as-is.
Tasks and runs are not the same thing. A task is the what; a run is one attempt at the what. If the first run doesn’t land, you can give feedback and start another run — same task, new attempt.
How they fit together
Organization
└── Project (connected to a repository)
└── Task (one per source issue)
└── Run (one per attempt at the task)The organization is the billing and access boundary — it’s where teammates, credits, and plan settings live.
You’ll spend most of your time looking at projects and tasks. You drop into a specific run when you want to see what’s happening right now, pause something in progress, or review a delivery.