Data and Resources

RMT can describe host data sources and runtime resources next to the surfaces that use them. The runtime still owns execution; the RMT document declares the contract.

Data Contracts

Use datasource for host calls and resource for things that must be released, such as timers, subscriptions or object URLs.

template learn.rmt.dataflow {
  state app.items type object preserve {
    initial {
      id "inbox"
      count 3
    }
  }

  selector app.itemsView from state app.items {
    output ItemsView
  }

  datasource app.items from endpoint "/api/items" {
    method GET
    contract ItemList
    result records
    fallback fixture app.items.fixture
  }

  resource app.refreshTimer kind timer owner surface.inbox.card {
    dispose on surface.destroy
  }

  surface inbox.card kind card component x-status {
    source selector app.itemsView
    key items.id
    bounds x 16 y 16 width 320 height 100
    destroy releases resource app.refreshTimer

    lane visible weight 75 {
      hydrate inbox-card from selector app.itemsView
    }
  }
}

Maraca Resource Ownership

Resources are more than runtime notes for Maraca. owner surface.inbox.card and destroy releases resource app.refreshTimer are used in the orchestration plan so the kernel runtime and surface lifecycle share the same ownership rule. If the build cannot resolve a resource owner, treat that as a real app problem, not as missing prose in the docs.

Collection And Search Resources

The owned RMT surface uses the same data and resource model for data display and command/search:

• resource.orders feeds selector.visibleOrders, which feeds collection.orders.
• resource.commands feeds selector.visibleCommands, which feeds search.commands.
• Dashboard resources stay owner-scoped to their surface.
• Popover resources can use release: "on-surface-close" so query data is cleaned up when the overlay closes.

Use Native-First RMT Recipes for the full collection and command/search records, and RMT Surface Resource Graph Runtime for cleanup rules.

Next Step

Control render priority with Scheduling and Lanes.