# Three speakers · five minutes · PO first

Rehearsal estimate, not measured speaking time. Aim for 135–155 words/minute. Each speaker uses three primary navigation operations: Next, Next, Handoff. The optional Smart Tools sample demonstration adds three clicks.

| Time | Speaker / action |
|---|---|
| 0:00–0:15 | Introduce the buyer question: Which component or engineering requirement should we review? |
| 0:15–1:25 | BYTE: part → production / inspection → potential first work package |
| 1:25–2:40 | Smart Tools: modules → sample queue demonstration → integration brief |
| 2:40–3:50 | Hé Jī: five people → original equipment / documents → proposed work packages |
| 3:50–4:00 | Ask for a drawing or interface brief, acceptance owner and next technical conversation |
| 4:00–5:00 | Buyer questions. Open the relevant evidence or enquiry only if useful. |

## BYTE — We Build

At BYTE TCM in Pingtung, Taiwan, we support precision machining, tooling and mechanical prototypes.

These photographs show a company-published machined component, hands-on production, and dimensional inspection. Each reference links to its source.

For this forum, we want to start with one clearly defined component or fixture. Possible work includes a motor mount for a ventilation prototype, a Linux-base enclosure, or a sensor bracket for a surface vehicle. We would confirm the fit with each buyer.

Bring a drawing or CAD model, material, quantity and critical dimensions. We can review manufacturing feasibility, clarify inspection requirements, and determine whether we can issue a scoped quotation. Please identify any origin or quality-system requirements so the applicable evidence can be checked.

Let’s use the next conversation to agree on the part, acceptance criteria and person who can approve a first order. A broader cooperation agreement can follow when it helps the work.

## Smart Tools — We Enable

BYTE has shown the physical manufacturing side. Smart Tools focuses on the software and connectivity that make a device useful.

We can scope four work packages: local AI, short-message field communications, industrial data connectors, and an edge deployment configuration.

Each area has a documented technical path. These equipment images are concepts, and we are not presenting the complete hardware system as already validated.

Here is a small software example you can operate now. Using clearly labelled sample data, an event waits in a local queue when the simulated route is interrupted. When the route returns, the event is recorded once—even if it is replayed. This demonstrates the application logic, not radio range or AI performance.

Bring us your device interfaces, data restrictions and acceptance target. We can turn that into a bounded integration proposal and a test plan. Hé Jī will now show the people and product evidence behind the engineering discussion.

Demo: Create sample event → Restore & replay queue → Replay last event. Expected: queued 0, received 1, duplicates 1. This is browser memory and simulated transport; do not call it a hardware or AI demonstration.

## Hé Jī — We Integrate & Test

BYTE shows the manufacturing side. Smart Tools shows the local software and data workflow. Hé Jī brings the integration discussion together.

Our team covers systems planning, embedded control, aircraft integration and mechanical prototyping. Sun adds UAV flight-control and guidance-development experience, alongside software development and a background in military technical instruction. We agree project roles and responsibilities for each engagement.

Here, you can inspect original equipment references and product documents, including a ground station, flight controller and positioning system. They help us define interfaces; they do not establish Sun’s individual project history or prove that your configuration has passed testing.

We propose four practical starting points: an equipment shortlist, an integration and ground-test package, a manufacturing review, or a mission-data workflow. Sun’s proposed scope can include flight-control interfaces and test planning.

Bring your application, equipment and constraints. Together, we define deliverables and acceptance criteria for a paid first step. A broader MOU can follow when it supports the work.

## Before going on stage

Open each presentation URL once, then keep the three offline HTML files together on the presentation laptop. Test the actual iPad, projector, adapter and browser. The preferred English name Yi-Sheng Sun and his public biography, technical positioning and existing portrait use are approved. Confirm the other four preferred English display names and who will answer technical, price and schedule questions. Online evidence and enquiry links require connectivity; the offline copy does not store enquiries.

## Speaker boundary — approved update, 21 October 2026

Sun’s personal military technical-instruction background does not authorize Hé Jī to provide military systems operator training. That service is not currently offered. Project evidence and formal qualification details remain to be verified. Do not attribute historical product documents or supplier cases to Sun without individual contribution evidence.