What does my app need to remember, and how do I tell my AI which information to keep?
Short answer
Tell Kai-Zen what your app must keep, such as orders or bookings, and who may see it; your app keeps it in vaults.
Before you start
Words used here (1)
- Kai-Zen
- Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
Deeper
What your app needs to remember is what it must still know the next time someone opens it: for example the people who use it, their orders or bookings, the products in a shop, or a setting someone chose. What it only shows for a moment, such as a word someone types to search, need not be kept.
You do not need technical words. Tell Kai-Zen, the planning agent (an agent is your AI following one written procedure for one kind of work), what your app must do and for whom; it asks what only you know in one round of questions. Say in your own words what must be kept, who may see it and who may change it, for example: keep each booking with the customer's name, the time and the service; only I and that customer may see it. Say also what must not be kept. You can tell Kai-Zen later too: it changes the plan, and Agent.Coder, the agent that writes your app's code, builds the change.
Where it is kept. An app on GilbPlatform has no database of its own (an organised store of data), no store of files of its own and no data that exists only in the app. When your app is published, GilbPlatform also makes a vault for it, named after your app and owned by you; who can reach it is set by that vault's access, as for any vault. Your users' own data stays in their own vaults. Everything it must remember is kept as records in vaults, the places where a person or a group keeps their records, and the app reads and writes there only with the access it is given. A record is one piece of data with its own address, such as a person, a place, a thing or a note. When people sign in to your app, your app reads and writes in their own vault; what your app shows everyone, such as a shared list, is kept in a vault of yours. Even a setting someone chose is kept in a vault, not only on one device. The answer Can my app have its own users who sign in? says more.
Each kind of data gets its proper name. Before Agent.Coder writes code that stores a new kind of data, it hands the names to Agent.Concept, the agent that finds and makes GilbVeda's terms, and goes on with the terms it returns, without asking you. GilbVeda is the shared list of terms every type (a kind of record) and field (one piece of information in a record) name on GilbPlatform comes from, so each app reads a record the same way. That is why your AI may say it is finding or making a term before it builds. The answer What is GilbVeda, and why do apps use it? says more.
Seeing what it keeps. Records your app writes in a vault you may read can be opened in GilbApp: press Main menu, the button at the top left, next to your profile picture, that shows the name of the section you are in, and choose Records; the answer How do I find a record? shows how. Your users' records are in their own vaults: you see them only if they share them with you. Your app keeps no passwords: people sign in with GilbPlatform.
If your app keeps details about people, rules such as GDPR, the European Union's law on personal data, may apply; the answer Do I have to follow rules such as GDPR or app store rules from the start? says more.
This answer is written for a computer screen.
Source: Standards: Rule_Code_gilb-app-stack-and-data (RuleBaseappNoData, RuleBaseappTypeAnchored, RuleBaseappNoTypeShortcut: settings kept in the vault, not only on the device); Agent.Coder (GilbStack item 4: terms to Agent.Concept before code, without asking the person); Kai-Zen.New and Kai-Zen.AskRules (one round of questions, as on the live answers). Live answers, sentences shared: Can my app have its own users who sign in? (reads and writes in that person's vault; no passwords), Why does my data stay mine?, What is GilbVeda, and why do apps use it?, What is a record?, How do I find a record?, How do I see a record as it was before (its history)? (Main menu, Records), When do I actually start making the app? (one round of questions).
Checked against GilbApp d529620.