edictIn development

Productivity and task management

An example app for to-dos, goals, and recurring tasks with dependencies, reminders, and shared lists.

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

Illustrative rule: a task unlocks when its dependency is done

AgentEdit edict.yaml+12illustrative
1modules:
2+ data:
3+ tasks:
4+ owner: user
5+ fields:
6+ title: text
7+ due_at: timestamp
8+ depends_on: tasks
9+ shared_with: [list_members]
10+ rules:
11+ unlock_dependents:
12+ on: task.completed
13+ sets: dependents.status = open

Placeholder values and unfinished syntax. Not a released feature.

What is the Productivity and task management example app?

A user keeps lists of tasks with due dates. Some tasks depend on others. Some repeat each week. A list can be shared with a partner or a team, where each member may view or edit. Reminders arrive before a task is due.

This category is a design target. It is not a claim that Edict already supports a complete task app.

What backend does the Productivity and task management example need?

  • Data storage.
  • Scheduling.
  • Relationships and dependencies.
  • Reminders.
  • Sharing.
  • Authorization.

How do the planned modules compose in the Productivity and task management example?

The database is designed to hold tasks, lists, and the relations between them, including dependencies. Authentication would supply identity. Together they are designed to enforce sharing rules: the owner decides who may view or edit a list, and the backend checks that on each request.

Business logic is designed to hold the rules that react to changes, such as unlocking a task when its dependency is completed. Background jobs are planned to create the next copy of a recurring task. Push notifications would send reminders before a due time, using the schedule.

For example, a household chore list could combine Authentication, Database, Background jobs, and Push notifications: each person sees only the lists they belong to, weekly chores reappear on schedule, and a reminder arrives before the due time.

What would an illustrative rule look like in the Productivity and task management example?

The configuration above defines tasks with a dependency and a sharing rule, and a rule that reacts when a task is completed. The key names and the syntax are placeholders and are not final.

What is example and what is planned in the Productivity and task management example?

All modules named here are planned and in development. Your app owns the interface, the meaning of priority and status, and the decisions about what is shared by default. Real-time collaboration behavior is not part of the stated plan, so this page does not promise it.

See the Database and Business logic 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.