Design has custom nodes

warningcustom-nodes-present

The design places nodes the catalogue does not name, so the rules are blind to that part of the architecture. The count belongs on the design, not only on the individual boxes.

Severity: warning
Selects: every design
Components in scope: 2,366

What it checks

It looks at every design, and fires when:

— the design contains a node of kind custom

Message

This design has custom nodes; rules are blind to them. Aim for zero.

{{node.id}} style paths are filled in from the node, the edge or the design the finding is about.

Applies to · 2,366 components

This rule is about the whole design, not one node.

This rule names no kind: it reads the design as a whole.

Tripped by · 1

Reference designs whose broken twin names this rule in its header. The gate reads the same header, and fails when a rule no design trips.

custom-escape-hatchreference

Source

1# yaml-language-server: $schema=../schema/rule.schema.json
2# The same hole, counted once for the whole design, so the number is visible on the design and
3# not only on the boxes. Tripped by designs/reference/custom-escape-hatch/design.broken.yaml.
4schemaVersion: "1"
5type: "rule"
6id: "custom-nodes-present"
7severity: "warning"
8select:
9  design: true
10when:
11  hasNode:
12    kind: "custom"
13message: "This design has custom nodes; rules are blind to them. Aim for zero."

The same page as markdown, for an agent: /catalogue/rules/custom-nodes-present.md