Original bounded handset evidence report · scope revision53

Saved original-report · Original source proposals/2026-10-09-continuation/research-bfs/section01/01-handset.md · original SHA256 45526ca5e603a5ac93029851f4a0c22a91fadec6d4585faa2454bb6acb6a76da · immutable published snapshot proposals/research-artifact-archive/1cf267def27a/45526ca5e603a5ac93029851f4a0c22a91fadec6d4585faa2454bb6acb6a76da.md · SHA256 45526ca5e603a5ac93029851f4a0c22a91fadec6d4585faa2454bb6acb6a76da

Bounded research/review evidence. This artifact does not certify physical manufacturing closure or later changed routes.

Smartphone

Part · evidence research draft · manufacturing closure open. The handset integrates completed, mutually compatible modules into a portable phone. This is the first of exactly five BFS evidence reports. Selection began at graph revision 52; the saved scoped records were reread at revision 53. Scenario: coordinated-discovery-v1; selected method: discovery-handset-v1. Discovery inventories remain hypotheses. None of the cited commercial products is available workshop stock.

Required capability and unresolved specification

One accepted phone is the output. Prototype, test-piece and loss quantities are not yet specified. The project requires flagship-equivalent compute, memory, storage, imaging, display/touch, audio, sensing, radio and usability, charging from a standard external charger, and operation on real-world networks after import. A reference model, measurable equivalence, dimensions, power budget, supported bands, thermal limits, operating environment, battery service life, ingress/drop criteria and acceptance thresholds are not yet specified. Each module needs a compatible mechanical envelope, electrical interface, voltage, signaling and black-box firmware/driver contract. No cited repair instruction freezes these demands.

Immediate physical inventory

The following preserves all 34 selected immediate requirements, including unresolved allocation. Part counts and whether a module already includes another listed object must be settled by a quantity/containment ledger. Downstream factories remain inside module routes.

Additional known operational requirements need explicit ownership: stable clean workshop-surfaces; containers and protected module storage; cleaning materials and surface-cleaning; compatible lead/contact fixtures for tests; handling and waste capture for dispensed material, wipes and rejected cells; calibration/reference transfer within acceptance equipment. Existing canonical identities are candidates for reuse, not qualified assets. Cleaning and fixture capacity must support actual adhesive chemistry and module delicacy. These are staged additions/allocations, not inserted edges.

Bounded making method

Freeze the physical architecture and interface matrix before manufacture. Allocate accepted modules, connector pin maps, mechanical datums and power/thermal budgets; check that the combined radio, antenna, enclosure and firmware configuration supports the intended network. Determine whether cover glass and touch layers arrive laminated to the display. Count each incorporated object once, while retaining every making dependency through its real consumer.

Prepare the clean, protected assembly surface. Verify tools, independent references, torque range and joining fixtures against the chosen design. Fit the board and completed modules into the enclosure without bending flexible cables or loading lenses. Connect harnesses, mount thermal interfaces, fasten modules using design-specific settings, and dispense/cure only the selected adhesive system. Seal and fit covers with the selected compression or bond arrangement. A detachable screw/clip architecture is an alternative to extensive bonding, requiring its own fit, sealing and reliability evidence.

Fairphone's official repair page documents a real phone with separable rear cover, battery, screwed display and board-to-board cable connections. It also warns that module compatibility is model-specific. This supports preserving completed-module hierarchy and connector/handling obligations; it does not prove a production recipe, flagship equivalence or from-nature manufacture. Fairphone repair instructions [H1]

Inspect fit, exposed damage, continuity/isolation and the power path before energizing. Use an earlier workshop supply with current limitation/protection appropriate to the actual circuit, never an external household supply borrowed from the final charger allowance. Independently verify charging protection and the acceptance fixtures. Conduct functional, optical, acoustic, sensing, radio and thermal tests against the frozen target, retaining failed results and rework stock. Destructive tests need trial units; one finished phone is not enough stock for every test.

Software and external interfaces

OS, firmware, applications, radio protocols, drivers and charging negotiation are black boxes. Their required functions, compatible processor/memory/storage, boot path, cable, programmer and permissions remain explicit. Final installation may occur after import. Any earlier manufacturing/test program needs a separate physical host, loading connection, supply and availability declaration before its operation. boot-and-development-tools must not spawn software-development dependencies.

USB-IF describes permitted Type-C power signaling; a connector alone does not establish a charging contract. Freeze a supported charger/cable/power mode and obtain the applicable test specification. USB-IF compliance updates [H2] PTCRB's published workflow includes authorized testing and possible operator-specific requirements. This is evidence that radio hardware alone is insufficient for network acceptance, not a claim that every network mandates this program. PTCRB certification [H3]

Reuse, alternatives and evidence limits

All named requirements reuse canonical IDs. Generic tooling must be matched by cleanliness, range, calibration, force and timing; its existence in the registry establishes none of these. No new identity is requested. A modular architecture may reduce assembly/rework difficulty but cannot bypass chip, battery or display manufacture. Qualification independent of the device under test remains required. Repair references, standards bodies and commercial fabrication accounts provide bounded evidence, not a complete executable recipe.

Next review: freeze target and module architecture; allocate duplicate/intermediate stock; assign cleaning/support/storage requirements; reconcile loading tools and hidden-joint inspection; define tests and quantities. No reviewed natural endpoints, successful build or closed path is claimed.