Streaming and effects
Transit has durable streams, application materialization and recorded connector effects. SQL executes finite reads and explicitly routed Table DDL/DML. The transport of a result in several batches does not make that query continuous.
Operations and SQL coverage
| Task | Current interface | SQL coverage |
|---|---|---|
| Read an explicit state projection | Fuze over declared KV, Table or accepted Document state | Finite SELECT |
| Configure an external connector | HTTP/gRPC connector configuration and credential references | CREATE CONNECTION is grammar only |
| Read captured observations | Connector capture and application decoding | CREATE SOURCE is grammar only; no executable connector source binding |
| Maintain application state from messages | Application freezes input identity and publishes complete Table changes with durable progress | No CREATE MATERIALIZED VIEW |
| Maintain a supported relational result | Typed Zig owner publishes complete revisions and deltas from Table history, with explicit host activation and wakeups | No SQL view, materialized-view or subscription adapter |
| Refresh a displayed query | Int64 Table watch invalidation and finite snapshot refresh | No SUBSCRIBE or continuous SELECT |
| Dispatch external work | Recorded intent, authorized attempt and captured outcome | CREATE SINK is grammar only; no query-to-sink binding |
CREATE VIEW, CREATE MATERIALIZED VIEW, SUBSCRIBE, streaming windows and
event-time watermark declarations are absent from the grammar and runtime.
The existing historical-read fragment does not enable time travel or
stream resumption.
Connections, sources and sinks
CREATE CONNECTION names reusable configuration and secret references. CREATE SOURCE describes an adapter over captured connector observations. CREATE SINK describes a connector effect target. These grammar rules do not resolve dependencies, validate connector options, provision resources or authorize attempts.
An executable query source is instead an
explicit state declaration with names, types and source identity. It is not
created by the connector CREATE SOURCE statement. Queries require current
read rights even when a source or connection name is known.
Materialization and observation
An application can materialize mailbox input by binding durable input identity to its staged operation and publishing the complete Table successor with its recorded outcome. The application owns decoding and transformation. Fuze does not install a maintained query graph or automatically recompute Tables after upstream changes.
The separate maintained relational owner uses Fuze to recompute each recorded Table-history basis and publish a complete result and delta. Named definitions, authorization, activation and wakeups have explicit typed Zig interfaces. An application host schedules advancement; SQL declarations do not install a background service. This differs from refreshing a displayed finite query after an invalidation notice.
Reactive APIs notify a viewer that its source may have changed. The viewer acquires a new finite result and replaces the displayed result after complete verification. Notifications can be coalesced; they do not promise every intermediate row change, insert/delete deltas or an event-time frontier. Missing retained watch coverage requires reset rather than invented continuity.
A source revision identifies a captured state basis. A Table data watermark tracks data progress separately from bookkeeping. Neither is a SQL event-time watermark. Source cuts from different resources do not establish a global snapshot.
External effects
A sink declaration alone cannot send a request. The supported effect lifecycle records intent, authorizes an attempt and captures its outcome. Replay consumes those records; it does not dispatch. A changed or deleted input row cannot undo a remote effect.
An unknown remote outcome stays unknown until connector policy and evidence resolve it. Local cancellation, grant revocation and successful socket writes cannot establish remote rollback or safe retry. Secrets remain references in definitions and transcripts. SQL supplies no automatic retries, scheduling, external exactly-once guarantee or unbounded live connector stream.
See application declarations for the separate offline compiler and explicit interface publication. Publishing a UI definition does not activate a continuous query or connector effect.