Endpoint protocols and runtime
This page routes Endpoint and persistence work to its task cards. The Endpoint protocols and runtime contract owns every rule; each card quotes the rules of one task, generated from that contract. Path syntax and context belong to the Libertas Schema Path specification; exact callback and function signatures belong to the installed public SDK.
Choose the task cards
Load every card the task touches:
| The task changes | Card |
|---|---|
An Endpoint, its protocol Union, roles, errors, access, OutputOnly fields, the hidden context requests are built from, AI tool exposure or protocol conformance |
Endpoint protocol |
Endpoint entry, the Actions surface, input presentation, RequestConfirmation, ConstrainedBy, named action controls or native Back |
Actions, entry and choices |
Link, link returns, stacked links or LinkOnly |
Links |
EditRequest, WorkflowRequest, PrevRequest, workflow completion or a changed earlier page |
Workflows |
SubscriptionRequest or SubscriptionData, compatible or reduced reports, append or live charts |
Subscriptions |
| Field calculations or a calculated allowed set | Calculations |
AI Search: GoTo, AINavigationPrompt and searchable destinations |
AI Search |
| The App code that serves or calls an Endpoint | Endpoint callback code |
| A storage schema, keys, the key-value API or data-failure handling | Persistent data |
Payload types, attributes, defaults, Schema Paths and ordinary CopyFrom/CopyTo |
Data model |
A client implementation (Studio, Android or iOS) loads the client runtime card instead.
The four relations
Every runtime rule follows from four relations. Use them to find the card that owns a behavior.
1. Reachability: a Request is reached only through a declaration that names it
| Declaration | Reached by | Card |
|---|---|---|
NextRequest on the displayed Response or SubscriptionData |
the Actions surface | Actions |
ActionControl array on that page |
a named control | Actions |
Link on a displayed value's field or type |
a tap on that value's row | Links |
Link on a request-editor field |
the row's link button | Links |
CalculationRequest on an editor field |
a change of that input | Calculations |
DefaultRequest |
endpoint entry | Actions |
EditRequest / WorkflowRequest reply |
the server opening that editor | Workflows |
PrevRequest on the edited Request |
the workflow Back button | Workflows |
| none of the above | the request-list landing, only without a default entry | Actions |
Nothing else reaches a Request: the actions and
links cards hold the rules that infer nothing from CopyFrom, an
input-free payload or a missing NextRequest.
2. Replies: replace the working screen or are consumed in place
| Reply | Card |
|---|---|
Response with NextRequest, plain acknowledgement, Error and its field locator |
Endpoint protocol |
EditRequest, WorkflowRequest, and the end of a workflow |
Workflows |
| plain Response to a link from an editor (a link return) or a stacked page | Links |
| calculation reply | Calculations |
| SubscriptionData report | Subscriptions |
3. Copies: a target is built from the reference context
CopyFrom follows the
shared copy rules
and the context table, quoted on
the data model card; the
reference context
and its hidden continuation data are on the
Endpoint protocol card, a link's construction on the
links card, and a previous action's on the
workflow card.
4. Screens: landing entry, one working page, one composer
Landing kinds, endpoint entry and native Back are on the actions card; leaving an endpoint and waiting for a reply are on the Endpoint protocol card; the screen stack is owned by endpoint presentation, and draft recovery by CacheIdentity.
Persistent data schemas
Storage schemas, keys, the key-value API and data-failure handling are on the persistent data card; record names follow data and database names.