Capacitor Series/Parallel Combiner mechanism

Model scope

Formula verification passes for the two stated pure topologies, but the specification needs review because input units and the exact topology representation are unspecified. The empty honest_label is a concern: the instrument should clearly state that it supports only pure series or pure parallel networks unless mixed series/parallel reduction is implemented.

• The formulas are standard and correct for a purely parallel network (Cp=ΣCi) or a purely series network (1/Cs=Σ1/Ci). They do not define how arbitrary mixed series/parallel topologies are represented or reduced.
• The series formula requires every capacitor value Ci to be nonzero; for physical capacitors, values should also be strictly positive.

Units and conventions

• All capacitor values in a calculation must use one common unit, or the implementation must perform explicit unit conversion before summation or reciprocal calculation.
• The test outputs below are expressed in microfarads unless otherwise stated.
• Capacitance values are ideal lumped capacitances; parasitic effects, voltage dependence, tolerance, and frequency-dependent behavior are not included.

Inspectable vector

One of 4 source-bound review vectors:

{
  "inputs": {
    "topology": "parallel",
    "capacitors": [
      {
        "value": 10,
        "unit": "uF"
      },
      {
        "value": 22,
        "unit": "uF"
      }
    ]
  },
  "expected_outputs": {
    "Ceq": 32,
    "unit": "uF"
  },
  "working": "Cp = ΣCi = 10 uF + 22 uF = 32 uF."
}

Failure boundary

BREAK_CLAIMED · SELF_FLAGGED

A zero-valued capacitor in a series network creates a 1/0 undefined term, and omitted units create a convention-dependent result. Inputs should be validated and units made explicit.

Other records

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• VERIFIED_LEDGER.json
• evidence-tranche5/tranche5-results.json
• BOUNDARY_HAZARD_CATALOG.json