The Venn view above shows AND (overlap = both true) and OR (either region = at least one true). Notice OR's shaded area contains AND's — that is exactly max≥min.
The bar view shows all four input rows. For each row the cyan bar (A+B) is the taller of the two inputs and the amber bar (A⋅B) is the shorter — literally max and min.
The gate schematic shows why factoring saves hardware: AB+AC (3 gates) and A(B+C) (2 gates) feed the same output for every input — one fewer gate, same behaviour.
Each item: decide true/false, then give the reason. A bare verdict scores nothing.
A+B=B+A holds for every possible pair of bit values
True. OR is max, and max(A,B)=max(B,A) — swapping two numbers never changes which is larger, so the output is identical in all four rows.
(A⋅B)⋅C=A⋅(B⋅C) is the associative law for AND
True. AND is min, and min(min(A,B),C)=min(A,B,C)=min(A,min(B,C)) — the smallest of three bits is the same regardless of which pair you compare first.
The distributive law A(B+C)=AB+AC is the same as the one in ordinary school algebra
True. AND-over-OR mirrors multiply-over-add exactly, so "A times the sum" splitting into a "sum of products" carries over unchanged.
A+BC=(A+B)(A+C) is also valid in ordinary number algebra
False. This OR-over-AND form is unique to Boolean algebra; in real numbers a+bc=(a+b)(a+c) (try a=b=c=1: left =2, right =4). It only works because Boolean uses max/min, not +/×.
Commutativity guarantees two rearranged circuits produce identical timing and delays
False. It guarantees the same output value for every input, but wire lengths and gate ordering can change propagation delay — logical equality is not physical identity.
Associativity lets you turn a chain A+B+C into A⋅(B+C)
False. Associativity only regroups within the same operator; turning an OR chain into an AND-of-OR crosses operators, which is a distributive (or different) transformation, not associative.
(A+B)⋅C=A+(B⋅C)
False. The left side crosses operators (OR then AND); it cannot be regrouped by associativity, and the two are simply not equal — test A=1,B=0,C=0: left =1⋅0=0, right =1.
Factoring AB+AC into A(B+C) always reduces the gate count
True. Left uses 2 AND + 1 OR = 3 gates; right uses 1 OR + 1 AND = 2 gates. The outputs match every row, so you save one gate for free.
The three laws can create or destroy inputs — e.g. an expression with 3 variables can drop to 2
False. These laws only rearrange and regroup; the set of variables the output depends on is unchanged. (A variable can vanish only via other laws like idempotent or null, not these three.)
Because A+B=B+A, an OR gate has no "first" and "second" input electrically
False. Logically the inputs are interchangeable, but on a real chip the two input pins are distinct copper paths with possibly different delays; only the truth-table output is guaranteed identical.
Each line contains a plausible mistake. Name what's wrong and give the corrected statement.
"Applying distributive: A+BC=(A+B)⋅C"
The lone A must be duplicated into both brackets: correct is A+BC=(A+B)(A+C). Test A=1,B=0,C=0: correct gives 1, the wrong form gives 1⋅0=0.
"By associativity, (A⋅B)+C=A⋅(B+C)"
Associativity does not apply — the expression mixes AND and OR. The two sides differ in general: with A=0,B=1,C=1, the left is 0+1=1 (OR of 0 and 1), while the right is 0⋅(1+1)=0⋅1=0 (recall 1+1=1 in OR), so they are unequal.
"Since order doesn't matter, A−B=B−A in Boolean algebra too"
There is no subtraction operator in Boolean algebra — only AND, OR, NOT. Commutativity is stated only for + (OR) and ⋅ (AND); importing subtraction is meaningless here.
"Distributing A⋅(B+C) gives AB+C"
The A must reach every term inside the bracket: A(B+C)=AB+AC, not AB+C. Dropping A from the second term breaks the truth table at e.g. A=0,C=1.
"(A+B)(A+C) expands to A⋅A+B⋅C=A+BC, skipping the cross terms"
You cannot skip cross terms during expansion; the full expansion is AA+AC+BA+BC. It does collapse back to A+BC, but only after using AA=A and then factoring A+AC+AB=A(1+C+B)=A (since 1 OR anything =1) — the collapse is a later step, not an allowed shortcut.
"Because AND is min, A⋅B⋅C needs the three inputs compared in a fixed order"
The min of three bits is order-independent, so associativity guarantees any grouping/order gives the same result — there is no mandatory comparison order.
"Commutative law says A⋅B=A+B since both ignore order"
Ignoring order is not the same as ignoring the operator. Commutativity swaps operands within one operator; it never lets you swap AND for OR. (A⋅B=min, A+B=max — different functions.)
Answer with the underlying reason, not just a restatement of the law.
Why does the OR-over-AND distributive form (A+BC=(A+B)(A+C)) feel "weird" to newcomers?
Because in ordinary number algebra you can only distribute multiplication over addition, not addition over multiplication — students copy that one-way habit, but Boolean's max/min structure makes distribution work both directions.
Why must the lone term A appear in both brackets when distributing OR over AND?
Because "A OR (B AND C)" is true whenever A is true, so each bracketed sum must independently contain A to stay true in exactly those cases — one copy would leave one bracket able to force a 0.
Why can a 3-input OR gate be built two different ways from 2-input gates?
Associativity says OR(OR(A,B),C)=OR(A,OR(B,C)), so both wiring layouts compute the identical function — the engineer picks whichever fits the chip layout better.
Why do all three laws ultimately reduce to facts about min and max?
Because AND =min and OR =max; commutativity, associativity, and distributivity are all just algebraic properties that min and max already satisfy for the numbers 0 and 1.
Why does simplifying with these laws physically matter for a chip?
Each removed operator is a removed gate, meaning fewer transistors — a cheaper, faster, cooler-running chip that computes the exact same output.
Why is a truth table a complete proof of any of these laws, not just evidence?
With only bits 0 and 1, a small expression has finitely many input combinations (e.g. 23=8); checking all of them exhausts every possible case, so matching columns is a full proof, not a sample.
Why doesn't commutativity, by itself, ever reduce the gate count?
It only swaps the order of operands feeding one gate — the gate is still there. It enables later steps (lining up a common factor for distributive factoring), but on its own it removes nothing.
Test the laws at the boundaries: constants 0 and 1, and repeated variables.
Does A+B=B+A still hold when A=B?
Yes trivially — swapping a value with itself changes nothing, so A+A=A+A; the law holds in this degenerate case as it must.
Does the associative law survive if one input is the constant 0, e.g. (A+0)+C vs A+(0+C)?
Yes. Both equal A+C; the constant 0 is just another bit that max handles the same way regardless of grouping.
Does distributive A(B+C)=AB+AC hold when A=0?
Yes. Left =0⋅(B+C)=0; right =0⋅B+0⋅C=0+0=0. Both collapse to 0, consistent for every B,C.
Does A+BC=(A+B)(A+C) hold when A=1?
Yes. Left =1+BC=1; right =(1+B)(1+C)=1⋅1=1. Both saturate to 1, matching in this boundary case.
What happens to (A+B)(A+C) when B=C=0?
It becomes (A+0)(A+0)=A⋅A=A, which equals the left side A+0⋅0=A — the law degrades gracefully to a plain identity.
If every variable equals 1, do all three laws still give matching outputs?
Yes. With all bits 1, every AND and OR outputs 1 on both sides of each law; the equalities are preserved (this is just one row of the truth table proofs).
Can these three laws ever change an expression's value for some input while preserving it for others?
No. A valid law must match on every row of the truth table; if even one row differed, it would not be a law. Partial matching means the transformation is simply wrong.