An IoT alarm names its iOS notification category (SP10)
Without aps.category iOS shows the alarm with no Acknowledge or Open buttons: the categoryId data key is only a custom property.
SP09 Alexa — master §10 rows for the plan's and the execution's deviations [skip ci]
Share device access from tickets and Exec2Exec, the card in both, and the recipient pages (IoT SP04)
The ticket header's action row and all three Exec2Exec header strips offer the share action (Exec2ExecHeaderActions keeps the meeting button beside it). An IOT_...
The sharing client and the Share device access dialog, button and card (IoT SP04)
The member-side of sharing (spec 4.16): app/lib/iot/sharesApi.ts is @kamo/iot-core's createSharesApi over a same-origin @kamo/net ApiClient on this app's authen...
Devices panel for Accounts and Contacts - data layer, live updates, tag and untag (SP13)
IoT Sharing Access report, registry guards, fifteen seed reports
Report option providers and Account merge keeps tagged devices (SP13)
IoT reports — no god mode, the owner rule, and ReportDefinition.exportRight enforced at download, schedule and every run (SP13)
SecurityService opens Service Work jobs for IoT — endpoints, one-transaction opener, crossapp scan (SP13)
The Advanced tab's Kamo OAuth client panel — status, one-time secret, Amazon vendor id, activate (IoT SP09)
SecurityService P1-P3 **************** had no screen, so operator step B5 (generate the Alexa client secret, register the vendor id's redirect addresses, activa...
IotReportSupport (SI clamp, vendor retention, lookups) and IotAlarmReportMapping
ReportDefinition.exportRight — a per-report export right on top of EXPORT_REPORTS
MediaService internal chat-post and chat-target endpoints for IoT (SP13)
SP13 service-job link entity, repository and six activity kinds
IOT_ALARM phone push body and withdraw-with-update (SP10)
An IOT_ALARM event card (source **************** as iot-service's AlarmNotifier writes it, or <alarmUuid>:<seq>) is mirrored as an IOT_ALARM push: channel/colou...
Holder-only relay topic /topic/iot/relay/{connectionId} (SP10)
Core NATS iot.relay.{uuid} is relayed verbatim to /topic/iot/relay/{uuid}. The frame is a wake only **************** SUBSCRIBE needs iot-service I-OD1 (GET ****...
IOT_ALARM — exempt from the presence gate and the rate limit (IoT SP10)
An alarm is not seen because a browser tab is open, and every lifecycle step (raised, escalated, acknowledged) shares one collapse key, so the 15 s limit would ...
Iot.relay.> — svc_iot publishes, svc_media subscribes (IoT SP10)
The Google Home relay wakes the phone that holds a connection's lease: IoTService publishes a content-free frame on iot.relay.{connectionId} and MediaService fo...
On-device vocabulary and iot_on_device_links entity (SP10)
The link entity keeps only the SHA-256 of the phone's link secret, and that hash is @JsonIgnore so it never reaches a response or an event.
Charter editor lists OPERATE_DEVICE and OPERATE_SECURITY_DEVICE; KamoAI master §11 and IoT master §10 rows (SP11)
ACTION_CLASSES ends with the two IoT SP11 classes and APPROVAL holds 24 items (one per shared-lib AiActionClass). The KamoAI master gains its §11 row for the io...
Classify the ten iot tools; the catalogue guards move 101 to 111 (SP11 P12)
The three iot writes are NOT_DISCLOSING and the seven reads NOT_CONTENT with the spec's reasons (pinned in ContentReadToolsCoverageTest too). RegistryCompletene...
IotCallerView and the pure view rules V1-V11 (SP11 §4.4)
A key a device lists twice is a manifest defect and is never used (fail closed).
IotManifestClient, a per-session ETag-validated manifest cache with single flight (SP11 §4.4)
Per-caller schemas and availability for the ten iot tools (SP11 §4.5)
IoT error map, value checks, class check, whitelisted results and the command watch (SP11 §4.7, §4.9)
Downstream approval headers, conditional GET with ETag, opt-in error fields (SP11 P11)
CallerSchema per caller after visibility; PHYSICAL after outside content always asks a person; the approval travels on the plan (SP11 P4-P7)
A static tool's schema and availability may depend on the caller (CallerSchema): viewed after visibility for tools/list (one 3 s budget shared by the list) and ...
ToolRisk.PHYSICAL, the iot_ prefix, two charter classes, the IOT door and ApprovalRef (SP11 P1-P3, P8-P10)
Brief words for the two physical charter classes; copilot ceiling pinned (SP11)
CharterCompiler words OPERATE_DEVICE and OPERATE_SECURITY_DEVICE and keeps both silent while unnamed (as the two team classes of CP05 R1-3), so no existing SI's...
SecurityService resolves the two IoT charter classes (SP11)
The charter catalogue lists 24 action classes (the owner's JOIN_MEETING made 22; IoT SP11 appends OPERATE_DEVICE and OPERATE_SECURITY_DEVICE, both APPROVE_BEFOR...
Purge sweep, OAuth configuration and the repository scan (IoT SP09)
Internal grant revocation for IoTService and platform client administration (IoT SP09)
OAuth mode — the standard page untouched, tenant chrome off (IoT SP09)
/?oauth_request=<64 hex> is the OAuth sign-in page by a beforeFiles rewrite in next.config.mjs to /oauth/sign-in (the browser keeps the URL), not by a switch in...
Token endpoint with PKCE, rotation with a 24-hour grace, reuse detection and RFC 7009 revocation (IoT SP09)
OPERATE_DEVICE and OPERATE_SECURITY_DEVICE charter classes (SP11-D2)
IoT SP11 (master §6.14, §10 SP11-D2): physical actions through the Tool Plane's iot_ pack are charter-approved per class. AiActionClass appends OPERATE_DEVICE (...
Consent view and single-use decision bound to the sign-in session, pending grants and codes (IoT SP09)
Keep hook-token and share-token hashes out of JSON; the OAuth secret prefix is a label
**************** was red on main: **************** and previousHookTokenHash, **************** and previousHookTokenHash, and IotShare.tokenHash had no @JsonIgn...
O3 binds a fresh sign-in to the authorization request with an atomically spent one-time key (IoT SP09)
Like what you see shipping?
All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.