Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/registry-cloud-tunnel.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"ftw-webapp": patch
---

Name the box session through FTW Cloud in the shared registry: the carrier `tunnel` and the capability `cloud.tun`. The web app does not use either yet.
8 changes: 7 additions & 1 deletion contract/registry.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,10 @@ capabilities:
# only and offers no FTW Cloud. It says nothing about whether the owner
# turned FTW Cloud on; the box's grant decides that.
- cloud.link
# The box takes its app session through FTW Cloud, end to end, as `tun`
# (docs/protocol-cloud.md, Tunnel, in srcfl/ftw). Absent means a phone
# reaches the box through the relay, even when it knows the home id.
- cloud.tun
# The box can take a watch: it opens the relay's exchange socket and mints
# watch codes. Absent means the phone offers no Add watch. The wire is
# docs/watch-exchange.md in srcfl/ftw-webapp.
Expand Down Expand Up @@ -274,7 +278,9 @@ client_errors:
# the two into one enum cannot express "connected, but the inverter is quiet".
# ---------------------------------------------------------------------------
source_states: [live, lagging, stale, down, never]
carrier_states: [webrtc, relay, cloud, cache, none]
# tunnel is the box's own session carried by FTW Cloud, which cannot read it.
# cloud is the box-signed copy FTW Cloud holds and can read.
carrier_states: [webrtc, relay, tunnel, cloud, cache, none]

# ---------------------------------------------------------------------------
# History resolutions backed by what the box actually stores.
Expand Down
Loading