ManYue: Separate part identifiers from assembly-step numbers in exploded views

Numbers one,two,three can identify parts or order operations. Smaller identifiers do not automatically mean earlier assembly. Read an original toy schematic or authorized comic instructions, establishing number roles before text and state checks. ManYue does not recognize parts, generate assembly animation or certify physical installation, and unprovided actions remain unknown.

Preserve the whole view and identifier legend

Select a page with parts, leaders and wording and record work, edition, chapter, location and title. Retain the whole view including legend. Invent base A, peg B and cap C with separate steps one place base, two place peg, three add cap. This is reading practice, not fabrication guidance. Letters identify parts and numbers order steps only in this example. A real work using numerals for both systems needs separate records based on title and layout.

List part identity, quantity and scope

Record identifier, name, location, quantity and source for each part. An unspecified quantity is not automatically one: a representative item or repeated views may appear. A in main view and inset remains one depicted identity, not automatically two bases. Use shape evidence while preserving unclear matches. This manual list neither changes the original nor assumes clickable part entities in the app.

Trace leader endpoints rather than nearby labels

Trace labels to endpoints: B must identify peg, not nearby empty space; C cap, not a dashed line beneath it. A crossing is not automatically a junction, and a leader is not a shaft or physical rod. Return from zoom to the whole view to avoid mistaking a cropped edge for its endpoint. Preserve labels sharing a region rather than forcing unique mapping. Upper-left placement is not evidence of step one; target relationships matter.

Do not read exploded separation as a motion path

Separation often clarifies relationships, not actual travel distance. Vertically aligned A/B/C suggest correspondence without proving every part moves straight through the others. Record explicit hole or orientation instructions, not invented invisible holes. Exaggerated gaps provide no physical dimensions. Separate spatial correspondence, motion instruction and dimensional conditions, retaining missing information rather than promoting a clear schematic into assembly acceptance.

Check actions, prerequisites and results in a separate step list

For the invented instructions, record action, parts, prerequisite and completion state for base, peg and cap steps. C need not always be step three under another instruction. Preserve orientation checks and stopping conditions, not verbs alone. Placed does not mean locked, and a hidden interface does not prove completion. Check supplied instructions without physically trying an unknown structure or expecting automatic execution in ManYue.

Compare renamed parts with unchanged actions

In an external original copy, relabel A/B/C as seven,two,nine while retaining base-then-peg-then-cap instructions. Update leaders and list consistently. Seven being larger than two does not reverse the actions. This is your own control, not an altered publication as proof. A genuinely changed instruction requires versioned action evidence, not calling every difference renumbering. Preserve both copies without combining one’s leaders with the other’s list.

Check view identity and missing conditions when inconsistent

For an extra disc, check alternate view, washer or inset before merging shapes. Retrieve legend, appendices and same-edition instructions for missing parts rather than inventing assembly steps. Mark blurred labels or cropped edges unread and consult the full source, not generated completion. Retain simplification and missing-material candidates without forcing an answer from general intuition. Reports need part ID, step ID and location; third one wrong is ambiguous.

Recheck both identifier systems and states after returning

Leave the reader and return to the whole view. Locate A base/B peg/C cap separately from steps one/two/three, then verify seven/two/nine retains the same order and repeated views do not add quantities. Preserve parts, leader evidence, step conditions and unknowns separately from the source. Completion locates objects and actions independently rather than inventing plausible assembly from numerical order or certifying sufficient real-making instructions.

Related guides and sources

ManYue cutaway scenes: distinguish explanatory layers from transparent objects; ManYue instructional-comic reading: audit step states and missing conditions.

Checked on November 9, 2026: Apple public version information lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the official App Store description and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and personal analysis or code observations are not presented as verified automatic capabilities.

The A/B/C and seven/two/nine identifiers and three instructions are original. Their roles follow the legend, not numerical magnitude. App scope follows the official sources above. No real product assembly diagram is quoted and no fabrication or assembly acceptance is supplied by this static reading exercise.