Reference Trusted Runtime Host Loop

[flyingrobots]

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/v0.1.0/PLATFORM_reference-trusted-runtime-host-loop.md
Original lane: v0.1.0
Original legend: PLATFORM

Original backlog card

Reference Trusted Runtime Host Loop

Status: local reference boundary implemented; product adapter polish remains.

Depends on:

• Product-facing intent outcome API

Why now

The release model is clear:

application submits intents
trusted runtime owner ticks
application observes outcomes

Echo needs a documented local host loop that demonstrates the trusted runtime
owner role without requiring a daemon or distributed runtime.

Responsibilities

The reference host loop owns:

• contract package installation;
• trusted runtime control;
• fixed logical tick or until-idle policy;
• fault recovery authority;
• receipt publication;
• query service.

Acceptance criteria

• A clean example hosts one installed contract package locally.
• Application code submits through the app-safe API only.
• The host loop owns scheduler control and tick cadence.
• The host can run until idle without exposing that capability to
  application code.
• Runtime-local fault recovery is host-owned.
• The example can observe intent outcomes and query readings after ticks.

Implemented local slice

warp-core now provides TrustedRuntimeHost and TrustedRuntimeApp for the
local contract-host path. The host installs generated packages, stages ticketed
runtime ingress, runs super_tick until idle, and serves observations. The app
handle can submit intents and observe outcomes/readings, but it cannot tick,
install packages, stage ingress, or recover scheduler faults.

Non-goals

• Do not build a production daemon.
• Do not make wall-clock cadence semantic history.
• Do not let application code access trusted runtime control.

[coderabbitai]

🔗 Related PRs

#353 - Fix WASM application intent authority boundary [merged]
#360 - feat(core): stage ticketed ingress and outcome observation [merged]
#365 - feat(wesley): emit query observer host helpers [merged]
#368 - feat(core): connect installed contract intent pipeline [merged]
#369 - docs: add Echo v0.1.0 release plan [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!