Page actions
instrument mechanism / verified-clean
Inductor Series/Parallel Combiner mechanism
The inspectable method record for Inductor Series/Parallel Combiner, kept separate from implementation and qualification.
Model scope
The stated series and parallel formulas are standard for ideal uncoupled inductors. The honest label correctly identifies the no-mutual-coupling assumption. Verdict is NEEDS_REVIEW because input units and mixed-unit behavior are unspecified, and valid-input constraints are not documented.
No additional formula finding is recorded.
Units and conventions
- All inductance values must use a common unit before applying either formula; the specification does not define an input-unit convention or mixed-unit handling.
- The formulas assume ideal, uncoupled inductors with linear, frequency-independent inductance values.
- For parallel combinations, each inductance must be nonzero; practical inductors also require compatible connection polarity and negligible parasitic effects.
Inspectable vector
One of 4 source-bound review vectors:
{
"inputs": {
"topology": "series",
"inductors": [
{
"value": 10,
"unit": "uH"
},
{
"value": 22,
"unit": "uH"
},
{
"value": 47,
"unit": "uH"
}
]
},
"expected_outputs": {
"Leq": 79,
"unit": "uH"
},
"working": "Ls = ΣLi = 10 uH + 22 uH + 47 uH = 32 uH + 47 uH = 79 uH."
}Failure boundary
BREAK_CLAIMED · SELF_FLAGGED
A parallel input containing a zero-valued inductor causes division by zero and must be rejected. Additionally, the input specification does not define a unit convention, so bare values can produce results differing by a factor of 1000 between mH and H.
Other records
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
VERIFIED_LEDGER.jsonevidence-tranche5/tranche5-results.jsonBOUNDARY_HAZARD_CATALOG.json