FieldSpace Protocol
An open, language-agnostic protocol for exposing content and interactivity across screen environments.
What is FieldSpace?
FieldSpace enables channels (external services) to expose capabilities, data, state, and actions to clients (such as ScreenSpace) that render and mediate interaction across diverse surfaces—from televisions and tablets to phones, desktops, and digital signage.
Design Philosophy
FieldSpace is a surface-first protocol, not a tool protocol.
| FieldSpace Is | FieldSpace Is Not |
|---|---|
| Stateful | Stateless RPC |
| Surface- and media-oriented | Tool- or function-oriented |
| Supports persistent views | Request-response only |
| Agent-readable and controllable | Human-only interfaces |
| Consumer-safe (TV, home, public) | Developer-only tooling |
| Interaction-adaptive | Single interaction model |
Channels expose capabilities, data, state, and actions — not apps.
Quick Example
A minimal FieldSpace channel manifest:
{
"fieldspace": "0.1",
"channel": {
"id": "com.example.weather",
"name": "Weather",
"description": "Current weather conditions"
},
"capabilities": [
{
"id": "current_conditions",
"type": "data",
"endpoint": "/api/conditions"
}
]
}
Goals
- Interaction-adaptive — Works with minimal interaction (remote, voice) but supports rich interaction (touch, keyboard) when available
- Agent-native — AI agents can discover, reason about, and act on channel capabilities
- Platform-agnostic — Works on tvOS, Android TV, web, mobile, desktop, signage
- Channel-agnostic — Any backend technology can implement the protocol
- Consumer-safe — Designed for home, family, and public environments
Specification
| Document | Description |
|---|---|
| Concepts | Core terminology and conceptual model |
| Capabilities | Capability declaration and discovery |
| Data & State | Data access and state inspection |
| Actions | Action model and invocation |
| Views | Optional view layer (advisory) |
| Permissions | Permission and trust model |
| Versioning | Versioning and compatibility |
License
This specification is released under CC BY 4.0.
FieldSpace Protocol v0.1.0 — Draft