surface: How do you embed a resource or interface?

Embedding a resource view requires a source, connection and capability constraints. The registry describes AFS paths and remote AUP connections. Embedding does not merge permissions or guarantee all child interfaces share state.

Start with these properties

renderConstraints limits the child view’s rendering types or size. Here capabilities is a compatibility alias for that property; prefer renderConstraints in new configurations. It is not a resource read/write permission. showStatus controls the connection-status indicator.

connect, disconnect and error describe connection and error states, rather than the outcome of a business operation.

Read a structural example

From the source registry. This is structural reading material, not a live demo; referenced resources and actions require an application.

{
  "id": "afs-surface",
  "type": "surface",
  "src": "/modules/smart-home",
  "props": {
    "showStatus": true,
    "renderConstraints": {
      "primitives": [
        "view",
        "text",
        "action",
        "chart"
      ]
    }
  }
}

The example names /modules/smart-home as its source and limits rendering to four types. That declares a rendering scope; it neither proves that the path is accessible nor merges the child’s authority into its parent. Connection status, resource loading and operation results still answer different questions.

Read the surface reference.