Libertas App contract
This card is the entry to the App authoring contract. The contract's rules are generated into the task cards below; load each one the task needs, and read the linked owner before implementing its feature. Never infer schema behavior from a summary.
| The task | Card |
|---|---|
| Any App design or change: the design principle, asking once, the data-first model, types and Nullable choices, discovery and dependencies, permissions, the task lifecycle, documentation, wire compatibility and the compile loop | Designing an App |
| A page whose values come from a document, or a new field on an importing page | AI Import |
StringResources templates, notifications, FormattedText values and data names |
Messages (LMF1) |
A function whose task process uses TCP or UDP (AccessHost) |
Network access |
| Deployment to a Hub or Plaza publication | Deploying and publishing |
An Endpoint, its protocol Union, roles, access (AccessPrivilege, Write) or a client Endpoint's Default or Fixed selector |
Endpoint protocol, with Endpoint callback code for the App code that serves or calls it |
| A page searchable by AI Search | AI Search |
| A storage schema or persistent records | Persistent data |
Types, fields, attributes, Unions, keys, defaults, Schema Paths and CopyFrom/CopyTo |
Data model |
Related owners outside these cards:
- Data-type evolution before changing a published protocol or stored representation.
- The source documentation card for every schema-visible node and public function.
- The task pre-creation dependency check
for a client Endpoint with
DefaultorFixed.
Completion checklist
- Every required behavior has one owner and each fact is asked once
(
app.design.*,app.ask.*). - Every document-sourced page declares import, each added field is classified,
and replacement preserves person-supplied records (
app.import.*). - Every AI Search destination is bound and documented with its actual meaning, identifiers and common names (AI Search card).
- Exports, schema-visible documentation, permission and host reasons and wire
changes are intentional and complete (
app.discovery.*,app.docs.*,app.function.*,net.*,app.wire.*,app.checklist.*).
Then validate and report the result. Keep generated schema, documents, dependency lists, manifests and release versions generated.