jkunz
c8f7b62f23
- Dockerfile builds @git.zone/tsrepo v1.1.0 at the pinned TSREPO_REF (peeled commit 6d55d50) with a frozen install from the Verdaccio registry and serves `tsrepo docs website`. - The site settings move to "@git.zone/tsrepo".docs.website in .smartconfig.json; the validators, pins and AGENTS.md follow.
title, description, section, sectionOrder, order
| title | description | section | sectionOrder | order |
|---|---|---|---|---|
| smarthome.exchange | Source-verified documentation distinguishing published smarthome.exchange packages, integrated main changes, and production boundaries. | Overview | 10 | 1 |
smarthome.exchange
smarthome.exchange provides TypeScript contracts, automation plan builders, reference agents, an authenticated API client, integration runtimes, a secured durable hub host, and a component catalog. Hub and integrations 4.0.0, interfaces 2.1.0, SDK 1.1.0, API/CLI/catalog 1.0.1, and agents 1.0.0 are published. Hub 4.0.0 enforces authenticated home/tool grants and durable dispatch claims and consumes the released native home/lifetime contract; the embedding operator supplies its identity provider, database and credentials.
Issue Reporting and Security
For reporting bugs, issues, or security vulnerabilities, please visit community.foss.global/. This is the central community hub for all issue reporting. Developers who sign and comply with our contribution agreement and go through identification can also get a code.foss.global/ account to submit Pull Requests directly.
Read the status labels literally
| Label | Meaning in these docs |
|---|---|
| Released runtime | Behavior exists in the tagged package identified on the status page, with its limitations stated beside it. |
| Released contract/client | The named new package is published; its contracts and client capabilities require a compatible runtime. |
| Unreleased main | A verified change has been integrated into canonical main; it is not yet available in the published smarthome package version. |
| Worktree progress | Implementation and recorded verification are preserved in a worktree; current-main qualification, integration and publication remain pending. |
| Demo | Seeded or static data exercises a UI or runtime path without representing physical hardware. |
| Planned | Architecture direction only; not available from the audited packages. |
Package metadata such as control-runtime, MCP-shaped descriptors, a JSON schema, or an agent scope is not by itself evidence of live hardware control, authorization enforcement, or production readiness.
The October 13 checkpoint records integrations 4 and the hub 4 owner contract. Native onboarding requires the independently selected home and each adapter's exact identity/credential policy; the hub owns fresh adapter instances and denies controls until explicitly enabled. See Upgrading to 3.0 for provider/store references, permissions, pairing and plaintext choices. Hue 4 requires reference-only credentials and home-qualified targets; see Upgrading to 4.0 before restoring raw-key configurations. Physical acceptance and the independent Hue readback lane remain open. Historical checkpoints and hub 0.1.0 examples retain their dated limitations.
Current package boundaries
| Package | Current released behavior | Important boundary |
|---|---|---|
@smarthome.exchange/interfaces 2.1.0 |
Home-context requests, verified identity/grant vocabulary, revisioned tools, immutable ID/kind-bound approval actions, execution states and explicit TCP transport. | Types do not validate input or enforce policy; hub/integrations 4.0.0 pin 2.1.0, API/CLI/catalog 1.0.1 also consume 2.1.0; SDK/agents and the hub-pinned API 1.0.0 retain 2.0.0. |
@smarthome.exchange/sdk 1.1.0 |
Plan builders, legacy broad/exact dispatch, opt-in isolated stable invocation identities, removable registrations and owned close/drain. | No scheduler, durable invocation ledger or automatic effect retry; cancellation requires cooperative foreign work. |
@smarthome.exchange/api 1.0.1 |
Home-bound authenticated HTTP and Node sockets, digest-bound decisions and cancellable snapshot polling. | The application supplies credentials; a compatible secured hub and deployment policy are required. |
@smarthome.exchange/hub 4.0.0 |
Authenticated HTTP/Node WebSocket/modern MCP, enforced grants, immutable approvals, fenced durable claims/receipts, encrypted config, authenticated console bootstrap, owned adapters and explicit default-deny integration controls. | Operator identity/database provisioning is required; no physical exactly-once effect is promised. Its internal SDK remains 1.0.0. |
@smarthome.exchange/cli 1.0.1 |
Authenticated home inspection, one-shot tool plans, exact reviewed approval decisions, explicit console URL/browser handling and .shx source scaffolding. |
The host supplies credentials; generated files are not loaded by the hub. |
@smarthome.exchange/agents 1.0.0 |
Six frozen reference definitions and independent editable copies. | Definitions and configured scopes provide no runtime authority or LLM execution. |
@smarthome.exchange/catalog 1.0.1 |
Operational Dees/Lit views, authenticated API controller, cancellable home binding and immutable original-action approval review. | TCP inventory validation is included; hub 4 still pins catalog 1.0.0. The host supplies home/credentials; the server owns authorization and dispatch. |
@smarthome.exchange/integrations 4.0.0 |
Native home/owner migrations, reference-only credentials in migrated domains, explicit control permissions, encrypted scoped configuration and root operation admission. | Hue requires independent home/bridge/HTTPS selection, references and exact grants. Home Assistant retains its token API; real-device acceptance remains deferred. |
Start here
- Migrate native Hue before upgrading to 4.0
- Review the 3.0 native-domain migrations
- Configure a local host and understand the published graph
- Understand architecture and trust boundaries
- Learn the runtime model
- Embed the hub
- Author and test automations
- Onboard supported local integrations
- Use the API client with the hub host
- Diagnose and operate the hub
- Review published versions, evidence, and remaining work
License and Legal Information
This repository contains open-source code licensed under the MIT License. A copy of the license can be found in the repository license file.
Please note: The MIT License does not grant permission to use the trade names, trademarks, service marks, or product names of the project, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.
Trademarks
This project is owned and maintained by Task Venture Capital GmbH. The names and logos associated with Task Venture Capital GmbH and any related products or services are trademarks of Task Venture Capital GmbH or third parties, and are not included within the scope of the MIT license granted herein.
Use of these trademarks must comply with Task Venture Capital GmbH's Trademark Guidelines or the guidelines of the respective third-party owners, and any usage must be approved in writing. Third-party trademarks used herein are the property of their respective owners and used only in a descriptive manner, e.g. for an implementation of an API or similar.
Company Information
Task Venture Capital GmbH
Registered at District Court Bremen HRB 35230 HB, Germany
For any legal inquiries or further information, please contact us via email at hello@task.vc.
By using this repository, you acknowledge that you have read this section, agree to comply with its terms, and understand that the licensing of the code does not imply endorsement by Task Venture Capital GmbH of any derivative works.
© 2014 Task Venture Capital GmbH · Legal information