Appendix F. Full KUN implementation trace and cross-domain proof

This trace shows how one physical truck becomes a durable vehicle identity, evidence dossier, social character, service history, telemetry source, governed commercial actor and transferable asset without collapsing those roles. Record names are illustrative; every step uses the canonical admission path and receives its own proof/admission/projection receipts where applicable.

#F1. KUN ‘Prague Workhorse’ — end-to-end lifecycle

#F2. One transaction expanded: KUN buys a race ticket

1. KUN's agent retrieves the public event, seat/price quote and the owner's current preferences through a purpose-bound projection.
2. It creates an inert ActionProposal containing the exact event, seat class, beneficiary, total currency/amount, provider and proposal digest.
3. The policy engine checks current principal authority, R3 risk, ticketing grant, period/action limits, jurisdiction, provider and conflict rules.
4. The owner confirms the exact canonical proposal. The confirmation artifact binds amount, terms, proposal digest, expiry and confirmation method.
5. Immediately before dispatch, policy reevaluates the unchanged proposal against the current grant epoch, mandate balance, quote validity and provider state.
6. The connector sends one operation with stable RTracer action ID and provider idempotency key. The local action becomes EXECUTING.
7. A provider success produces reservation/order/payment/entitlement records plus balanced journal entries and a final ActionReceipt.
8. A possible-effect timeout produces UNKNOWN_EFFECT. Reconciliation queries the provider before any retry and ends in SETTLED, COMPENSATED or OPERATOR_REQUIRED.
9. The social post ‘I’m going to the race’ can publish only after entitlement evidence exists; the post cites the safe projection, not payment secrets.

#F3. Cross-domain proof of the same substrate

#F4. Proof obligations before claiming ‘the vehicle lives’

• Every factual statement made by the vehicle resolves to evidence/assessment IDs and an as-of checkpoint; fiction and affect are explicitly persona expression.
• Every external action resolves to principal, beneficiary, current grant, policy decision, confirmation when required, provider receipt and reconciliation state.
• Every physical capability resolves to an exact configuration, support/propulsion/action paths, operating domain and function-scoped controller—not a marketing label.
• Every price/value surface identifies whether it is an appraisal, asking price, standing offer, eligible bid, close price or settled transaction.
• Every ownership, custody, profile, persona, media, telemetry and economic right has its own time-bounded authority record.
• Every public location/media view is a disclosure projection; raw precise data remains separately authorized and retention-controlled.
• Every derived profile/feed/search/market state can be destroyed and rebuilt from the ledger, artifacts, registry locks and deterministic projection versions.