Built-in checks

Aquilla runs a set of built-in checks over your cells to catch likely problems early. They run continuously as you work, so issues surface as they appear rather than in a separate “lint” step.

What the checks look for

The built-in checks fall into two severities. Major checks flag likely real problems:

• Empty translation — the source has content but the target is blank.
• Identical to source — the target matches the source verbatim, so it’s probably untranslated.
• Placeholder integrity — tokens like {name}, <tag>, or %s in the source are missing from the target.
• Number integrity — numerals in the source don’t appear in the target.

Minor checks flag smaller slips:

• End punctuation — the source ends in ?, !, or . and the target should match.
• Extra whitespace, repeated word, unpaired brackets, and abbreviation pass-through.

A project can also add its own rules on top of these (and import them from a style guide), so the catalogue grows with your team’s conventions.

The violations inbox

When a check finds something, it creates a violation. All violations collect in a single Violations inbox that you can sort and filter — by check, by file, by severity, or by status. It’s your one place to see “what looks off across this project.”

The severity colour

On a cell, a coloured marker shows whether the cell has a violation and how serious it is — red for a major issue, amber for a minor one, and nothing when the cell is clear. The same signal appears in both the cell list and the single-cell editor, so you can spot problem cells at a glance.

Resolving a violation

For each violation you can:

• Fix the cell — edit it so the check passes; the violation clears on its own.
• Apply an autofix — when a rule has an autofix defined, accept its suggested correction in one step.
• Waive it — mark the violation as a false alarm so it stops flagging.
• Tune the rule — adjust a check’s severity, or add and edit rules, in the project’s Rules area.

Checks don’t affect health

Violations are tracked separately from decay and health. A violation does not lower the Health Ring — checks answer “does this cell look like it has a problem?”, while health answers “has this been validated?” Keeping them separate means a single empty cell doesn’t distort your overall review progress.

Still settling

The checks surface is still being refined. The built-in checks above, the violations inbox, the severity colours, and project-defined rules are in place; some of the surrounding workflow is still being smoothed out.