Docs · LLMs and developers
Version3.13.0What a memory app is, who can build one, what it costs, and how it reads your team's memory.
Memory apps
A memory app is a published page over your team's memory: a table, a pipeline, a scorecard, a timeline. The layout and rules are fixed when you publish. The data keeps updating as your team works.
The settings page and the legal terms call the feature Memory-Native Apps.
Where apps live
Apps live in your team's workspace, at /apps on your workspace address. Each app has its own address under /apps. Each app belongs to one environment, such as production or a sandbox, and reads only that environment's memory.
Apps are available only inside the workspace. There is no public link.
What an app is made of
An app is stored as a specification. Achiral does not generate or run code for it. The specification holds:
- the connected sources the app reads, called its bound sources;
- the entity types it is about;
- your signals, source authority rules, formulas, and stages;
- pages built from eight components: table, scorecard, timeline, pipeline, narrative, evidence drawer, filters, and review queue; and
- the actions it offers.
Achiral validates the specification before it is saved. Unknown components, properties, and actions are rejected.
Who can do what
| Task | Owner or Admin | Developer or Member |
|---|---|---|
| Build an app and preview it | Yes | Yes |
| Edit an app someone else built | Yes | No |
| Submit an app for its first publication | Yes | Yes |
| Publish an app for the first time, or approve a submission | Yes | No |
| Publish a later release of an app they steward | Yes | Yes |
| Change who can open an app they steward | Yes | Yes |
| Correct a fact or record a decision through an app | Yes | No |
| Turn the add-on on or off | Yes | No |
The member who builds an app is its steward. The team owns the app. An Owner or Admin can reassign the steward.
The add-on
Memory apps are a paid add-on at $19 per month for each published app. Building apps, previewing them, and keeping drafts is free. An Owner or Admin turns the add-on on in the App store settings and accepts the Memory-Native Apps Additional Terms.
Until the add-on is on, members can see the App store, but creating, publishing, and running apps are locked.
What is billed:
- Every published app counts, in any environment. Drafts and archived apps do not.
- Nothing is prorated. An app published partway through a billing month is first charged at the next renewal. An archived app stops being charged at the next renewal.
- The price for an app does not depend on how many members open it or how often it runs.
Canceling stops the next renewal. Apps keep running until the end of the period already paid for, unless billing is past due or your add-on is on an order form, in which case they stop when you cancel. The apps, their versions, and their history stay with your team.
Generation that falls back to Achiral-hosted models is not part of the add-on. See Model providers.
Pages in this section
- Building an app: the builder, describing an app in words, signals, formulas, and what must be confirmed.
- Publishing and versions: who can publish, audiences and invitations, versions, and rollback.
- Evidence and inferred conclusions: how each value is marked, what counts toward a score, and what happens when a source is unavailable.