Companion + CLI
Connect an assistant, propose and save a typed flow, grant access, review Activity, and revoke it.
Companion is available, several local demos run, and the Market is operated manually. Public Beacon presence and paid verification outcomes are still being developed. Technical Engine claims below point to code that can be inspected.
Product status
Connect an assistant, propose and save a typed flow, grant access, review Activity, and revoke it.
Calendar components and local actions run. Four personal-budget modules run separately; full user apps remain in progress.
The public board accepts real requests and specialist offers through a manual intake path. Seed budgets are not committed.
The local scheduling mock exists. Public addressing and offline delivery still need a pilot.
WebAssembly Components execute with a deny-all WASI context. Host functions are linked only when a policy explicitly permits them.
Read sandbox testThe pipeline contract has shared admission, metering, and backpressure semantics across HTTP and bidirectional gRPC.
Read streaming testCached components are checked and recompiled for compatibility before the host reports that it is ready to receive work.
Read warmup testFuel, CPU-time, and I/O facts are written to an encrypted local ledger and sealed into host-signed Merkle checkpoints.
Read integrity testOutbound wasi:http resolves an allowlisted host, rejects private ranges, and pins the TCP connection to the verified address.
Inspect policy sourceThe local tamper-evident record is implemented. Sending checkpoint roots to an independent party remains a separate trust boundary and is not claimed as complete.
The backend has discovery and automatic analysis paths. Companion still needs a connected remote discovery and artifact-install experience.
The local scheduling prototype runs; a public agent meeting point, offline delivery, and sealed inbox are in development.