Repository documentation
Native UI schema
The platform-neutral grammar that maps discovered resources, fields and actions to native components.
2 minute read · sourced from NATIVE_SCHEMA.mdNextcloud Native Schema 0.1
The schema is the trust boundary between discovery and presentation. Discovery may use deterministic inspection, verified adapters or local AI, but a renderer only accepts this typed document.
Top-level document
schemaVersionidentifies the contract version.appbinds the result to an installed app and exact version.confidencecommunicates how completely the app was understood.resourcesdescribe data entities and fields.actionsbind intent to real server operations.viewsselect reusable native components for resources and actions.warningsexplain missing or ambiguous semantics.
Confidence
| Level | Meaning |
|---|---|
verified |
A signed or reviewed adapter confirmed the semantics |
high |
Typed API metadata provides strong evidence |
medium |
Deterministic inference selected a likely interpretation |
low |
The runtime has insufficient evidence for normal interaction |
AI inference cannot raise confidence to verified by itself.
Actions and safety
Every action contains an immutable HTTP method, path and operation identifier discovered from the connected server. The inference engine cannot invent these values.
| Risk | Default behaviour |
|---|---|
readOnly |
May execute during discovery or normal browsing |
mutating |
Requires confirmation while inferred |
destructive |
Always requires confirmation and explicit UI treatment |
An adapter may improve labels, component selection and field semantics. It may not introduce an operation that was absent from the discovery snapshot.
Component families
The initial grammar includes dashboards, files, collections, media grids, details, forms, timelines, calendars, boards, mailboxes, contacts, tasks, data tables, media libraries, recipes, documents, conversations and chat threads.
New components must represent interaction patterns shared by more than one app whenever possible. App-specific behaviour belongs in a verified adapter, not in the generic component library.
Version invalidation
A compiled schema is cached against all of the following:
- Server URL and Nextcloud version.
- App ID and app version.
- OpenAPI and capability fingerprints.
- Adapter ID and adapter version, when present.
Any change causes revalidation before write actions are available.