Synchronous call chain too deep

warningsync-chain-too-deep

Every consecutive synchronous hop from this entry point spends part of the stated p95 latency budget, and the chain's failures multiply. More than three hops is a budget nobody is tracking.

Severity: warning
Selects: every node of kind api-gateway
Components in scope: 41

What it checks

It looks at every node of kind api-gateway, and fires when:

— all of these hold:
— the design requirement `latency.p95Ms` has a value
— the longest chain of synchronous calls starting at the node is more than 3 hops long

Message

Entry point '{{node.id}}' starts a synchronous call chain deeper than 3 hops while the design states a p95 latency target.

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

Applies to · 41 components

API gateway api-gateway

Tripped by · 5

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.

coinbase-exchangereference monzo-platformreference order-processingreference robinhood-tradingreference zerodha-kitereference

Source

1# yaml-language-server: $schema=../schema/rule.schema.json
2# syncChainDepth is the longest path of consecutive sync edges starting at this node.
3# With a stated p95 latency target, every extra synchronous hop eats into that budget.
4# Tripped by designs/order-processing.broken.yaml.
5schemaVersion: "1"
6type: "rule"
7id: "sync-chain-too-deep"
8severity: "warning"
9select:
10  node:
11    kind: "api-gateway"
12when:
13  all:
14    - requirement: "latency.p95Ms"
15      exists: true
16    - syncChainDepth:
17        gt: 3
18message: "Entry point '{{node.id}}' starts a synchronous call chain deeper than 3 hops while the design states a p95 latency target."

The same page as markdown, for an agent: /catalogue/rules/sync-chain-too-deep.md