Appendix J. Cross-domain reference transactions and proof obligations
The universal substrate is proved by applying the same identity, evidence, graph, time, authority, lifecycle and projection laws to physically different machines. Domain packs add vocabulary, equations and policy; they do not replace the kernel.
Concept & directionLNK
The universal substrate is proved by applying the same identity, evidence, graph, time, authority, lifecycle and projection laws to physically different machines. Domain packs add vocabulary, equations and policy; they do not replace the kernel.
#J1. KUN ‘Prague Workhorse’: evidence-to-story-to-value transaction
| Phase | Canonical records | Technical proof | Product expression |
|---|---|---|---|
| care intake | CareActivity + before media + capture/custody receipts | surface/process/product/equipment/environment; condition observations remain distinct | private raw gallery; public wash story after rights/privacy projection |
| connected drive | CaptureSession + channel/clock/config locks + segments | raw CAN/GNSS/camera values; boot/sample identities; gap and quality assessment | owner telemetry; delayed/coarsened mission card |
| diagnosis | DiagnosticAssessment + fault alternatives + evidence | suspected/isolated/confirmed states; no unsupported certainty | maintenance recommendation with scope and uncertainty |
| work + parts | WorkOrder + executions + consumptions + calibration | actual part instances/lots, labor, torque/procedure, findings and deviations | rebuildable maintenance record and service-cost view |
| modification | ChangeRequest + assessment + configuration diff + release | ports, energy/control paths, software/calibration and affected capabilities recompiled | before/after build story and verified-current scope |
| dyno/test | TestPlan + setup snapshot + raw artifact + result | measurement boundary, environment, correction, uncertainty and comparability signature | qualified performance chart; no crank/wheel conflation |
| vehicle post | AgentContextManifest + draft + atomic claims + approval | observed/asserted/derived/creative lanes and exact evidence checkpoint | KUN speaks vividly while factual claims remain traceable |
| sponsorship | CampaignPolicy + RightsGrant + PublicationReceipt + journals | sponsor terms, permitted vehicle facts, disclosure, consideration and beneficiary | clearly labeled partner content and balanced earnings |
| listing + bid | Listing + AuctionRuleSet + BidAdmission receipts | seller authority, dossier/config digest, terms, trusted bid ordering and reserve commitment | live asking/leading-bid surface with precise value nouns |
| close + transfer | CloseReceipt + SettlementSaga + TransferPlan | winner, money, inspection, custody, external title assertion and persona disposition stay independent | explicit new stewardship/fork/retirement and revoked old access |
Value is an output of accumulated trust—not an editable score
KUN's public value narrative can combine provenance, condition, maintenance completeness, current configuration, test comparability, cultural reach, event history and eligible market evidence. The source records remain visible by category and confidence; social engagement cannot overwrite defects, title conflicts or auction outcomes.#J2. 1/8 electric RC buggy
| Facet | Exact representation | Domain-specific differentiator |
|---|---|---|
| identity | physical model asset + scale/represents relationship + chassis/electronics/pack instances | never merged with full-size represented vehicle |
| support | four tire contact patches, suspension and ground frame | setup-sensitive ride height, camber, toe, droop and tire compound |
| propulsion | battery → ESC → motor → pinion/spur/differential → driven wheels | pack chemistry/C-rating, gearing, motor timing, thermal and current limits |
| control | human radio steering/throttle; optional gyro by function; failsafe | transmitter/receiver binding, link, latency and race-class restrictions |
| operation | track, heat, driver, marshal, transponder, lap timing and exact setup snapshot | competition rule pack and class eligibility attach to operation |
| lifecycle | battery cycles, tire sets, crashes, rebuilds, bearings/gears/shocks and setup deltas | small replaceable parts still retain lot/instance provenance where valuable |
| physics | geometric/inertial/aero/tire/control similarity dimensions | 1:8 label does not imply Reynolds, Froude or full dynamic similarity |
#J3. Remotely operated blimp with camera and gripper
Support, propulsion, tether, utility and control remain separate
Configuration A — tethered display:
helium envelope supplies aerostatic support
tether supplies constraint and may carry power/data
electric propellers supply air-reaction translation/yaw
camera observes; gripper manipulates under separate utility authority
Transition guard to Configuration B — free flight:
net lift margin inside bound
weather/airspace/energy/link/envelope-health predicates TRUE
tether release authorized by its own hazardous-function lease
free-flight controller READY; authority epoch barrier committed
Lost link in free flight invokes local blimp fallback: stabilize/maintain altitude,
respect geofence and energy margin, then recover/land at declared site. A generic
"stop" command is physically incomplete.- Envelope identity/configuration tracks gas composition, cells/ballonets, pressure, volume, temperature, leakage, valves, patches and life limits.
- Net lift is a computed interval over air/gas density, envelope/structure/payload weight and uncertainty—not a boolean lighterThanAir field.
- Camera media binds capture configuration, pose/frame/clock, rights and privacy; gripper task evidence does not imply flight-control authority.
- Famous persona and event followers do not expand airspace, weather, payload, tether-release or operator authority.
#J4. Fan-propelled bicycle versus two propeller boats
| Machine | Support path | Propulsion/reaction path | Differentiating safety/test facts |
|---|---|---|---|
| fan bicycle | wheels/tires support on ground; front geometry steers | battery/engine → fan/air propeller → thrust against air | exposed rotor/guard, air thrust, wheel rolling losses; driven-wheel assumptions invalid |
| airboat | displacement/planing hull supports on water | engine → above-water air propeller → thrust against air | guard/noise/airflow, rudder/slip, hull/water state; propeller not submerged |
| conventional propeller boat | displacement/planing/hydrofoil hull supports on/in water | engine/motor → shaft/pod → propeller → thrust against water | cavitation/ventilation, shaft seal, fouling and advance ratio; airboat equations not substituted |
All three may be called propeller-driven, but propeller location, reaction medium, support medium, transmission, steering, hazards, maintenance and performance model differ. These facts are orthogonal axes; the preferred community label is a recipe result.
#J5. Underwater glider without propulsive propeller
Variable buoyancy plus hydrodynamic lift is a complete propulsion mechanism
Cycle mode DIVE:
reduce displaced volume / adjust ballast -> negative buoyancy
pitch mechanism establishes descent attitude
wings convert vertical motion into forward hydrodynamic lift
Cycle mode CLIMB:
increase displaced volume / adjust ballast -> positive buoyancy
shift mass/trim -> ascent attitude
wings again create forward component
State and evidence bind:
pressure/depth-positive frame, water density/current, hull volume,
pump/ballast energy, pitch/roll, leak/pressure-envelope state,
acoustic/satellite communication windows and surfacing fixes.
Locomotion capability is realized even when propeller count == 0.
Unknown density/current or pressure-envelope health may make mission feasibility
UNKNOWN although the generic motion recipe still matches.#J6. Transforming road eVTOL
| Mode | Active physical graph | Required transition evidence |
|---|---|---|
| road | wheel support/traction, road steering/braking, folded flight surfaces, road software/calibration | flight propulsion inhibited; road configuration and regulatory/operation assertions |
| deploying | actuators move wings/rotors; both road and flight clearance/energy constraints may apply | interlocks, exclusion zone, latch/position sensors, wind and fault checks |
| vertical flight | rotor lift/thrust, attitude control, airborne navigation and energy/thermal model | flight control lease, mass/CG, weather/airspace, rotor and battery health |
| wing-borne | aerodynamic wing lift plus propulsive thrust; transition controller | airspeed/attitude/altitude envelope and validated transition model |
| landing + stowing | flight then ground support; rotor stop and mechanical stow/latch | touchdown/load evidence, safe rotor state, clearance and configuration verification |
One permanent asset identity spans modes, while every observation, capability, control lease, operation, incident, service task, performance result and registry assertion binds the exact configuration/mode interval. Social popularity, auction price or agent confidence cannot authorize a transition or flight.
#J7. Minimum proof package for a new niche domain
- Define domain terms as versioned TermRefs with definitions, provenance, owners, synonyms and mapping—not one new universal enum.
- Show at least one complete support graph, resource/energy graph, propulsion/force path, steering/stopping path and useful-action graph.
- Define ports, mediums, units, frames, clocks, effectivity, configuration and failure behavior needed for the distinguishing mechanism.
- Register quantitative model families with equations, constraints, valid domains, solvers, initialization and validation evidence; do not force one physics model across all machines.
- Define operational modes, transition guards/reset maps, control functions, local fallbacks, hazards and release evidence.
- Define lifecycle activities, consumables, wear/fault families, inspection/maintenance and identity-continuity decisions relevant to the community.
- Define privacy, rights, registry, competition, marketplace and cultural mappings as adapters; none rewrites kernel identity or physics.
- Ship positive, negative, unknown, conflict, malicious-input, numerical-edge and cross-domain conformance fixtures plus one full ledger replay.