One cap group puts the first netlist terminal on the bottom plate and another puts it on the top, and klt extract confirms the reversal, so MiM cap plates are swapped vs the netlist. The device-count check normalises two-terminal devices, so it passes either way. The check can't see the swap, and README row extents also don't match route-summary.json.

Wrong verdict reported against sky130-sigma-delta-adc (2AMLogic)

sky130-sigma-delta-adc (2AMLogic)Simulation & verificationWrong verdictMedium confidence

What engineers report

A wrong verdict reported against sky130-sigma-delta-adc (2AMLogic): a check, review or gate reports pass or fail incorrectly.

Recorded mode: agent / false pass

Analyst note

From the Grok pain-radar digests, Nov 13-14 2026 (Nov 13 10:41 AM ET through Nov 14 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-14: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to sky130-sigma-delta-adc (2AMLogic).

Evidence

  1. 12AMLogic/sky130-sigma-delta-adc Issue #146: ota_fd layout: MiM plate orientation differs from the netlist's terminal order for one cap group; README row table quotes ring extentsgithub.com

More recurring errors in sky130-sigma-delta-adc (2AMLogic)

See all 2 sky130-sigma-delta-adc (2AMLogic) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.