OPEN ENGINEERING REALITY · FIELD ARCHIVE · SUMMER 2026

MANY STUDENTS.
MANY RUNTIMES. ONE REALITY DISCIPLINE.

The 2026 intern servers were not one course website. They became a distributed testbed for public publishing, safe AI API use, commerce experiments, product design, machine vision, Bluetooth, photo pipelines, 3D models, evidence, handoff and personal capability formation.

这些学生服务器的价值，不在于所有人做同一个 Demo，而在于让不同背景的人沿不同路线形成真实能力，同时保持共同的边界：Reality、Work、Evidence、Authority、History 与 Continue。

Infrastructure topology Representative cases Evidence JSON

PUBLIC C0-001 · Historical infrastructure archive. It does not assert current employment, attendance, continued student participation or present support obligations.

INFRASTRUCTURE TOPOLOGY

One student could move across more than one server Reality.

HK002 · Homelinked public RuntimePer-student public domains and owned web roots hosted portfolio, product pages, project evidence, practice pages, history snapshots and handoff surfaces.

Azure / Gmall · USA AI SandboxPer-student Linux accounts, isolated Runtime services, upload/API routes, photo-event receivers and later 3D runtimes provided a safer place to experiment with code and AI.

Shared infrastructureAdmin guides, upload receivers, event logs, workshop packages, team directories and common Runtime contracts let students share infrastructure without becoming one undifferentiated account.

Public / compute separationThe historical operating rule became simple: Azure handled upload + GPT/API experimentation; Homelinked carried final public display. The two could evolve independently.

MANAGEMENT HISTORY

The management model evolved from webpages into capability continuity.

09–16 Jul · Versioned public pagesPer-student homepage histories were preserved as timestamped snapshots instead of overwriting every earlier state.

21 Jul · “Small Success” contractsEach student received a different bounded direction, but used common states: CHOOSING, MAKING, TRIED, CONNECTED, READY_FOR_NEXT, NEEDS_HELP; and common success levels from Visible to Continuity.

30 Jul · Safe AI RuntimePer-user AI services introduced a staged First AI Success: login → status → first OpenAI answer → evidence → safe handoff. API keys stayed outside source code; sandbox came before trusted publishing.

12–20 Aug · Shared events + 3DPhoto-event receivers and upload events became shared infrastructure. Kelvin, Kyle and Nicholas then received separate 3D Runtime identities with common model contracts.

20–21 Aug · ONE REALITY handoffThe workshop reframed the students as one system: design-to-make, measure-to-accept and identity-to-retrieve, with failures and acceptance questions preserved for the next builder.

Late Jul onward · Team link directoryA shared directory made multiple independent public capability hubs discoverable without merging their ownership or histories.

REPRESENTATIVE CASES

Diversity was the feature.

Angela · Product / service / commerceSmall-success direction: one clear, test-buyable product. Public work included design services, a Cup Noodle service/product experiment, Stripe test paths and accessible smart-furniture research. Kyle · Human-centred design → makePuzzleBox, Study Space, product pages and smart-glasses design work demonstrate a path from bounded requirement → CAD / prototype → physical review. Kyle also operated an independent 3D Runtime. Kelvin · Signal / measurement / understandingSmall-success direction: one Sensor / IoT demo showing one real signal. Later pages explored AI image feedback, socket/cable estimation and an independent 3D Runtime. Nicholas · Identity → capture → retrieveBluetooth-bound glasses, W610 photo pipelines, API/gallery work, RFID-linked retrieval, mobile bridge research and the shared Team Link Directory formed a deep identity-and-memory branch. Jay / Ho · AI helper + Runtime boundaryAn ingredient scanner and Python Runtime reference showed that a student could build useful capability inside a personal workspace without being taught to administer the entire server as root. Kenny · Replication / onboarding / field researchA later runtime reused the infrastructure pattern for a new intern: Human Space After AI, TapPort field-trial reference and bounded public research pathways rather than copying earlier projects verbatim.

The archive also contains a separate Kevin runtime. Kelvin and Kevin are not silently merged here because the historical records use both names/identities inconsistently. This first public pass preserves that ambiguity instead of inventing a reconciliation.

ONE REALITY · THREE COMPLEMENTARY PATHS

By the August workshop, three branches could be described as one infrastructure story.

Kyle · DESIGN → MAKESolidWorks intent → printed component → assembly → physical review. The important result was not “AI generated a design,” but whether a bounded design decision survived physical making.

Kevin / measurement station · MEASURE → UNDERSTAND → ACCEPTObservation → candidate measurement → visible assumptions → comparison → human acceptance. AI output was explicitly separated from truth.

Nicholas · IDENTITY → CAPTURE → RETRIEVEBluetooth ID → photo → RFID ID → shared folder → retrieval, with Save / Delete / Share decisions retained as human authority.

SHARED MANAGEMENT CONTRACT

Standardize the contract—not the student's outcome.

Own a small capability

Each person starts from a bounded result that can actually be shown or tested.

Use a personal Runtime

Separate account, URL, files and service boundary make ownership and handoff visible.

Keep secrets out of public code

Keys live outside source; sandbox is distinct from trusted public publication.

Record failure

Backups, history snapshots and workshop templates treat failure as evidence for the next builder.

Accept Reality

Visible result, usable result, connected result and continuity result are different levels—not one “done” label.

Continue

A later student, engineer or AI should understand what existed, what changed and what remains uncertain.

PUBLIC REFERENCE SURFACES

Several historical surfaces remain reachable today.

Team Link DirectoryHistorical public directory connecting multiple intern capability hubs. Kyle · 3D RuntimeSeparate student-owned research runtime following the shared HSIMC 3D contract. Kelvin · 3D RuntimeSame infrastructure contract, separate owner account and Runtime identity. Nicholas · 3D RuntimeSame model vocabulary while keeping independent student ownership.

WHAT THIS TAUGHT HSIMC

Infrastructure diversity is not “many websites.” It is many ways to form capability under one evidence discipline.

Different talents need different RealityCommerce, industrial design, IoT, machine vision, accessibility, Bluetooth, Python and field research should not be forced into one curriculum-shaped output.

Personal Runtime is a management primitiveA person can own a bounded workspace and public evidence without receiving unrestricted authority over shared infrastructure.

Compute and display can separateThe Azure/Homelinked split anticipated later HSIMC separation of execution, public projection and durable Work continuity.

Student work can become infrastructureUpload pipelines, photo events, 3D runtimes, public directories and handoff templates outlived any single exercise and became reusable capability for later work.

Historical evidence boundary

This archive describes what the surviving servers, public pages, management snapshots and workshop material support. It does not grade individual students, assert that every prototype reached production acceptance, or assume former interns remain available. Public URLs may evolve independently. Historical labels such as “success” describe bounded milestones or intended workflow levels, not current employment, revenue, product certification or continuing obligations.

MANY STUDENTS.MANY RUNTIMES. ONE REALITY DISCIPLINE.