Synchronous call across cells

errorcross-cell-call

In a cell architecture each cell has to be able to fail on its own. A synchronous call that leaves the cell ties the two cells together and defeats the point of draining one.

Severity: error
Selects: every synchronous edge
Components in scope: 2,366

What it checks

It looks at every synchronous edge, and fires when:

— all of these hold:
— the edge crosses a cell boundary, or at least one end is in no cell at all
— the design requirement `isolation.tenancy` is "cell"

Message

Synchronous edge '{{edge.from}}' -> '{{edge.to}}' crosses a cell boundary while the design requires cell isolation.

{{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 an edge, so it belongs to a pair of nodes rather than one component.

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

Tripped by · 3

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.

amazon-orderreference robinhood-tradingreference slack-messagingreference

Source

1# yaml-language-server: $schema=../schema/rule.schema.json
2# In a cell architecture each cell must be able to fail alone. A synchronous call that
3# leaves the cell couples the fate of both cells and defeats the drain button.
4# Tripped by: designs/slack-messaging.broken.yaml
5schemaVersion: "1"
6type: "rule"
7id: "cross-cell-call"
8severity: "error"
9select:
10  edge:
11    mode: "sync"
12when:
13  all:
14    - crossesGroup:
15        kind: "cell"
16    - requirement: "isolation.tenancy"
17      equals: "cell"
18message: "Synchronous edge '{{edge.from}}' -> '{{edge.to}}' crosses a cell boundary while the design requires cell isolation."

The same page as markdown, for an agent: /catalogue/rules/cross-cell-call.md