Concepts

Development Standards (AI-DLC)

AI-DLC (AI Development Lifecycle) is the delivery standard your organization sets for work in Clauge. Every card on a board in an organization group moves through five stages: Plan, Ticket, Implement, Review, Merge. Administrators define what each stage requires, and Clauge checks it when someone starts work on a card, raises a pull request or merges.

AI-DLC applies to organization groups that have a published standard assigned. It does not apply to private groups.

The five stages

Stage What is checked When
Plan A plan note is attached to the card. At Start work
Ticket Every ## heading of the Ticket template has real text under it. At Start work
Implement The change contains no match for a data-protection pattern. At Raise PR and at merge
Review An AI review of the latest commit finds no blocking issue, and a person has approved if the standard requires it. At Merge
Merge Nothing is checked. The merge is recorded. When the pull request merges

What a stage contains

Each stage in a standard has five parts:

Part What it is
Instructions What the agent does at this stage, which files it reads for context, and which it updates afterwards.
Template The format for that stage's output: the plan note, the ticket, the pull request description, or the review reply.
Rules Statements the agent should follow. On Implement and Review each rule has a severity. On the other stages rules are guidance for the agent and are not checked.
Gate The check that decides whether the card may move on.
Metrics Figures for the last 30 days: cards in the stage, median time in the stage, gate pass rate, overrides.

Off, Advisory and Blocking

Gates and rules use the same three levels.

Level Gate Rule on Implement or Review
Off Not checked. Not sent to the agent or the reviewer.
Advisory Checked and recorded. It never stops the action. A review finding that cites the rule is counted. It never blocks.
Blocking Clauge refuses the action until the gate passes, and marks the card blocked. A review finding that cites the rule blocks the merge.

Data-protection patterns always block, whatever the gate is set to. A pattern is either a secret pattern or a file name. Clauge checks them before every commit and push it makes, and on the pull request diff at the Review gate.

What you see on a card

On a board in an organization group with a standard:

  • A chip on the card shows the stage. If a gate has failed, the chip reads Blocked for a blocking gate or Needs work for an advisory gate. Hover over it to read the reason, for example which ticket headings are missing.
  • Start work is refused while a blocking Plan or Ticket gate fails.
  • Raise PR is refused when the change matches a data-protection pattern.
  • Merge is disabled while a blocking Review gate fails. The button shows the reason.

If the standard requires a person's approval at Review, someone other than the author approves the pull request in Clauge's pull request viewer. Clauge posts that approval to GitHub or GitLab. An AI review cannot approve.

A card blocked at a gate on an organization project.

Overrides

If a stage has Allow human override turned on, an administrator can pass a blocked card by giving a reason. Every override is recorded and listed under Governance → AI DLC → Compliance, in Gate overrides. Overrides count against the group's adherence figure.

Define a standard

Administrators manage standards under Governance → AI DLC in the Organization Console. The page has three tabs: Standards, Activity and Compliance.

  1. Select New standard.
  2. Enter a Name and a Description.
  3. Choose the Scope: Organization (groups follow it by default) or Group (assigned to chosen groups). There can be one organization standard.
  4. Choose what to Start from: Clauge default, one of your published standards, or Blank.
  5. Select Create standard. The standard opens as a draft.
  6. Select a stage to edit its instructions, template, rules and gate.
  7. Under Data protection, select Add pattern to add a secret pattern or a file name.
  8. Select Publish changes.

Nothing is checked until a standard is published. Later edits are also saved as unpublished changes until you publish again. Each publish creates a new version, listed under Version history. The built-in Clauge default is read-only: select Duplicate to edit to make your own copy.

Assign a standard to groups

On a published standard, select Change in Groups using this standard. For each group choose one of:

Choice Effect
Follow organization (latest) The group uses the newest published version of the organization standard.
Pin to a version The group stays on that version of the organization standard.
A group standard The group uses that standard.
No standard AI-DLC is off for the group. Offered only while AI-DLC is optional.

The Standards tab shows whether AI-DLC is Required or Optional for the organization. Select Make required or Make optional to change it.

Cards already in progress keep the version they started under. To move them to the group's current version, open the group's AI DLC tab and select Re-pin open tickets.

Follow the results

  • Activity shows how many cards are in each stage per group or repository, how many are blocked at a gate, and work done without a ticket.
  • Compliance shows adherence by group, the most violated rules, gate overrides with their reasons, and review findings by group.

Sessions and coworkers

AI-DLC decides whether a card may move forward. The work itself is done in sessions, by you or by a coworker. Agents working on a card in a group that uses a standard receive that standard's stage instructions and rules.

What’s next