# GHOST Asset Bridge v1

## Events

- Request: `ghost.asset.request.v1`
- Response: `ghost.asset.response.v1`
- Service ready: `ghost.asset.ready.v1`
- Protocol value: `ghost.asset.bridge.v1`

## Actions

- `asset.health`
- `asset.search`
- `asset.get`
- `asset.resolve`
- `asset.sources`

## Request example

```json
{
  "protocol": "ghost.asset.bridge.v1",
  "requestId": "req_123",
  "source": "ghost.command.panel",
  "action": "asset.search",
  "payload": { "query": "share icon", "limit": 24 }
}
```

## Host execution

After resolving a stable asset record, GHOST COMMAND calls `GhostHost.addLayerToComp(path, optionsJSON)` through the serialized command UI flow. A production AI planner should retain request IDs, confidence thresholds, validation, and a single undo transaction for each user command.
