Models and context
Give information a useful place.
Data is the information an app stores and uses. Context is the relevant information supplied for a particular task. A model uses context; it does not replace persistent storage.
How it works.
A database can keep structured records such as requests, progress and account relationships. File storage holds documents, images, audio and video. Context is a selected view of that information, together with instructions and a current request. An agent should only receive what its task and permissions allow.
In a customer portal, a project record identifies the customer and its documents. An agent drafting an update needs the permitted project information, not every customer’s files. The app should show where an answer came from and let a person check or correct the underlying record.
- Records and files have different storage needs.
- Context is selected for a task.
- Permissions apply to model inputs as well as screens.
What this looks like.
- A dashboard reads structured records to show current totals.
- A knowledge app selects relevant document sections for a question.
- A research agent saves a brief and its source references for later review.
The pieces that matter.
Structured records
Define fields, relationships and validation around the work the app needs to track.
Files
Keep original documents and media with useful names, ownership and lifecycle rules.
Relevant context
Select current, permitted information. A larger input does not automatically produce a better answer.
Review and correction
Let people trace results to their sources and correct information that has become outdated.
Before you begin.
An import is a snapshot
Uploading a file once does not keep it synchronized with its original. Decide how later changes will reach the app.
Access must hold behind the interface
Test record and file permissions for direct requests and for any agent using those services.
In your App Cloud.
Your App Cloud brings data models, a database and file storage together with the models and agents that use them. Exepad lets you shape the information around a useful app experience.
Explore the capabilities or find an app or agent to create. Plan allowances and usage are explained on Pricing.
A few useful distinctions.
Is agent memory just chat history?
It can include prior messages, saved records, files or task state. Decide what should persist, for how long and who can access it.
Does deleting a file remove every use of it?
Copies, derived records and earlier outputs can have separate lifecycles. Understand the app’s storage and deletion behavior rather than assuming one action removes everything.
Keep learning.
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building