edictIn development

Journaling and wellness

An example app for private journals, mood tracking, guided prompts, reminders, and retention controls.

Example app Built from planned modules. Not a customer. Not a supported app today.

Illustrative rule: delete entries after a retention period

AgentEdit edict.yaml+11illustrative
1modules:
2+ data:
3+ entries:
4+ owner: user
5+ visibility: private
6+ retention:
7+ keep_for: user_setting
8+ then: delete
9+ notifications:
10+ triggers:
11+ - on: schedule.evening
12+ send: reflection_prompt

Placeholder values and unfinished syntax. Not a released feature.

What is the Journaling and wellness example app?

A user writes a short entry each day, rates their mood, and answers a guided prompt. Entries are private by default. The user picks how long the app keeps them. An optional AI feature offers a gentle reflection on recent entries.

This category is a design target. It is not a claim that Edict already supports a complete wellness app, and it is not a medical product.

What backend does the Journaling and wellness example need?

  • Authentication.
  • Private data.
  • Scheduled reminders.
  • Retention controls.
  • AI integrations.

How do the planned modules compose in the Journaling and wellness example?

Authentication and the database are designed to make privacy the default: entries are owned by one user and are not visible to others. Retention is designed as a rule on the entity, with deletion after the period the user chooses. Background jobs are planned to enforce time-based expiration and to run the evening reminder at the right local time. Push notifications would deliver the prompt.

For the reflection feature, Authentication and the AI gateway are designed to work together. The gateway would keep the provider credentials on the backend and apply a per-user rate limit. If the feature is premium, Subscriptions can be added to the mix.

What would an illustrative rule look like in the Journaling and wellness example?

The configuration above marks entries private and sets a retention behavior, then ties a reminder to a schedule. The key names and the syntax are placeholders and are not final.

What is example and what is planned in the Journaling and wellness example?

All modules named here are planned and in development. Journals hold sensitive thoughts, so your app is responsible for its privacy policy, its handling of data sent to an AI provider, and any rules that apply in your market. Edict makes no security guarantee at this stage.

See the Database and Background jobs module pages for the planned design. Join the beta waitlist to follow progress.

These share the most modules with this one.

See all example apps

Get an invitation when the beta opens.

Joining gets you email updates while Edict is built, and an invitation to the hosted beta when it opens.

Building now. No launch date yet.