Docs · LLMs and developers
Version3.13.0How to build a memory app with the builder or from a description, and what you define and confirm.
Building an app
Any member can build an app. Open /apps/new in your workspace and choose one of two ways to start.
Two ways to start
- Describe your app. Write what the app should show and how its numbers are worked out, in up to 4,000 characters. Chiro, your team's assistant, drafts the specification and opens it in the builder.
- Use the structured builder. Set up sources, entities, signals, formulas, stages, and pages with form controls.
Both produce the same kind of specification, and you can switch to the builder at any point.
What you define
| Definition | What it is |
|---|---|
| Sources | Which of your connected sources the app reads. Only sources connected to the app's environment can be chosen. |
| Entity types | What the app is about, such as customers, people, or projects. |
| Signals | Named measures. Each has a source, an aggregation, and a time window. |
| Source authority | For a field that several sources carry, the order in which sources are trusted. |
| Formulas | Scores worked out from signals, with weights, thresholds, and bands. |
| Stages | Ordered stages and the rule that places an entity in each. |
Signal aggregations are count, sum, avg, min, max, latest, days_since, and exists.
Achiral does not supply default definitions of health, risk, or readiness. Your team defines them.
Formulas
A formula is an expression with a fixed set of operations: arithmetic, comparisons, and, or, not, and min, max, and avg over the signals and formulas you declared. A formula cannot depend on itself, call other functions, loop, or read anything outside those definitions.
A formula is limited to 1,000 characters. Division by zero gives no value.
Describing an app in words
When you describe an app, Chiro drafts only what you stated.
- Anything you did not state is left out and listed as an open question.
- Every drafted signal, authority rule, formula, and stage is marked unconfirmed.
- The model receives your description. The content of your sources is not sent.
- If no valid specification can be produced after three attempts, nothing is created.
On the edit page you can describe a change. That creates a new revision and shows what was added, changed, and removed. Definitions that did not change keep their confirmed state.
Confirming definitions
An app cannot be published while any signal, authority rule, formula, or stage is unconfirmed. Review each one in the builder and accept or edit it.
Preview
A draft runs against your team's real memory in the selected environment. Use the preview to check signal values, which source supplied each field, formula results, evidence, and empty states before you publish.
Names and addresses
An app has a title and a short address name, such as renewal-risk. The address name uses lowercase letters, digits, and single hyphens between them, up to 64 characters, and must be unique in the environment. new, drafts, approvals, settings, sources, and by-id are reserved. You can change it until the app is first published.
Limits on each run
| Limit | Value |
|---|---|
| Queries | 16 |
| Events or memories read per query | 2,000 |
| Records returned | 1,000 |
| Run time | 15 seconds |
| Narratives generated | 2 |
A specification cannot raise these limits.