Invoke executable Stories over Legra's authenticated QUIC network.
A Story is an executable action with declared inputs and outputs. Native Legra peers can invoke it through Legra's own application protocol over QUIC. A workspace does not need a separately deployed HTTP service for each action.
For a mortgage quotation, the lender's operation can call a collateral Story executed on the customer's authorized Host. The response carries the agreed result while the private records remain inside their workspace's processing boundary.
Asynchronous calls and incremental results let work proceed without first assembling an entire response. Reusable connections and concurrent streams carry multiple operations between peers.
QUIC provides encrypted transport, flow control and reliable stream delivery. These mechanisms support efficient communication under load; actual latency and throughput depend on workload, path and serving capacity.
HTTP clients and browsers can enter through a gateway; native peers use the Legra protocol directly. Solid/LWS resource access remains a standards-based interface alongside Story execution.
Workspace-aware routing locates a serving Host. Distributed task trees connects the remote work to its initiating user, transactions and costs.
Developer reference
Legra carries typed operation messages and result streams over UDP-based QUIC, using TLS 1.3 for transport security. Peer identity authenticates the connection; workspace authority governs the operation. QUIC acknowledgements establish transport delivery, not a committed business outcome.
Story resolution identifies the definition and execution workspace. Input bindings and declared output concepts retain their meaning across the native call and HTTP gateway representation. Connection pooling reuses peer connections while independent streams support concurrent operations and flow control.
HTTP/3 also uses QUIC. The distinction here is Legra's application protocol and execution context, not a claim that HTTP inherently requires TCP or is always slower.
A lost response can leave execution outcome uncertain. Reconnecting is separate from deciding whether a mutating Story may safely run again. Consult authoritative task/transaction evidence and the operation's retry contract before replaying side effects.