ManYue pictured logic gates: compare four input cases for AND, OR and exclusive OR

Two button symbols connected to a lamp icon do not identify AND versus OR. Read an explicitly defined symbolic diagram in ManYue, checking four truth-input combinations against output. This is abstract reading, not wiring or appliance testing, and assumes no app simulation or automatic detection of real device states.

Fix symbol meanings and input roles

Record work, edition, chapter/page, panel and legend. Establish whether zero/one mean false/true or another stated switch convention. Here A, B and Y are Boolean, zero false and one true. A lit lamp icon merely represents output one, not real voltage or safety. Label blocks AND or OR instead of guessing from unexplained electrical shapes. Arrows indicate functional relationships, not observed current. Without a rule, retain uncertainty; two red buttons do not establish true values or mutual exclusivity.

List all four two-input combinations

Use ordered inputs zero-zero, zero-one, one-zero, one-one, always A first and B second. Two binary inputs give four combinations. Do not omit one-zero because it resembles zero-one. Some symmetric gates give equal outputs for these distinct inputs; that is a rule result, not merged identity. Keep external A, B, Y columns and trace connections. Left/right placement does not redefine labels after rotation. Enumerating these combinations follows the definition without an app-generated table.

AND requires both inputs true

AND outputs one only when A and B are both one, giving zero, zero, zero, one in the stated order. In zero-one, B is true but A false; one lit input does not light Y under AND. With both true, the Boolean output is one, not arithmetic two. Keep each input with the rule and result rather than copying four detached outputs. If a pictured one-zero case shows one, retain the precise conflict and recheck labels/rules instead of darkening all icons for uniformity.

Inclusive OR permits both true

Inclusive OR means at least one true, giving zero, one, one, one. Both true also gives one; it does not restrict selection to one input. An unexplained “or” needs the source’s definition. Keep at-least-one, both and exactly-one conditions separate instead of importing everyday ambiguity. When comparing AND, change only the rule while retaining four inputs and their meanings. Changing the zero/one interpretation too would obscure which condition changed the output.

Exclusive OR differs from OR in the both-true row

Define XOR separately as exactly one true, giving zero, one, one, zero. The both-true row distinguishes it from inclusive OR; observing only zero-one is insufficient. Check both-false too, despite another unlit image. Keep three complete rules/tables rather than mixing outputs. XOR is a logical definition here, not a physical mechanism preventing simultaneous presses or evidence of a device’s purpose. Additional gates need their own definitions rather than rules guessed from similar icons.

A complete table does not identify an unknown pictured state

If AND is defined but B is hidden, A one leaves Y undetermined: B may be zero or one. A zero fixes Y zero regardless of B. Separate determinate cases from conditional ones rather than saying every hidden input prevents all analysis. For OR, A one fixes Y one, whereas A zero requires B. These deductions use the stated rule, not app recognition of an occluded button. A character’s certainty is separate testimony; do not fill unknown B from that conclusion and then claim complete visual evidence.

Troubleshoot mismatched diagrams and table rows

For disagreement, check input labels, zero/one meaning, gate name and row before inventing a hidden inverter. Inspect the whole panel when arrows are cropped; two diagrams may be comparisons rather than a connected circuit. Retain inputs and output together instead of cropping only a lit lamp. Without timing information, a static table explains neither switching transients, flicker nor physical response speed. Label altered rows as controls without overwriting the source. Reports need exact panel and adopted definition rather than presenting a misread rule as an official app compatibility fault.

Exit and return to check both-true and unknown-input cases

Exit the reader and return to all three rules, rebuilding outputs for the same four inputs. Check both-true: true for AND/OR, false for XOR. Revisit hidden-B cases with A false or true without dropping conditions into an unconditional lit result. Save panel, definitions, input order, row outputs, unknown states and controls. Completion means reproducible logical relations, not automatic circuit solving or tested safety/stability of real lamps and wiring. New symbol conventions require new reading rather than copied answers.

Related guides and sources

ManYue pictured flowcharts: distinguish branches, merges and loops from page order; ManYue: Record visual-riddle constraints, candidates and revealed answers.

Checked on November 11, 2026: Apple public information lists ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later. See the official App Store for published capabilities; verify specific controls in the installed version.

Method reference: MIT Course Notes: Combinational Logic and Truth Tables. Samples, passages and controls are original exercises. Sources establish definitions and checking methods rather than new automatic analysis in the app. Manual records may be kept externally, and unknown fields should remain explicit. This article does not claim step-by-step testing on a physical device, private server or every output environment.