edictIn development

Social and community apps

An example app with profiles, relationships, reactions, feeds, permissions, and moderation workflows.

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

Illustrative rule: hold a post for review after repeated reports

AgentEdit edict.yaml+11illustrative
1modules:
2+ data:
3+ posts:
4+ owner: user
5+ visibility: followers
6+ rules:
7+ report_threshold:
8+ count: reports
9+ per: post
10+ at: 3
11+ then: set_status(held_for_review)
12+ emits: post.held

Placeholder values and unfinished syntax. Not a released feature.

What is the Social and community apps example app?

Members create profiles, follow or befriend each other, post, and react to posts. Each person sees a feed built from the people they follow. Members can report content, and the app can hold a post for review.

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

What backend does the Social and community apps example need?

  • Profiles.
  • Relationships.
  • Likes and reactions.
  • Permissions.
  • Feeds.
  • Notifications.
  • Moderation workflows.

How do the planned modules compose in the Social and community apps example?

Authentication is designed to give each member an identity and a profile. The database would store relationships, posts, and reactions, and enforce who may see what through visibility rules. Files would hold profile pictures and post images with the right access.

Business logic is where moderation is designed to live. A rule could count reports and change a post’s state when a threshold is reached, then emit an event. Push notifications could tell a member about a new follower or a reaction, with limits so that notifications stay useful. Background jobs are planned to handle clean-up work and to batch notifications.

What would an illustrative rule look like in the Social and community apps example?

The configuration above sets a post’s visibility and holds it for review after a number of reports. The key names, the threshold, and the syntax are placeholders and are not final.

What is example and what is planned in the Social and community apps example?

All modules named here are planned and in development. Feed ranking, search quality, and large-scale performance are not claimed. Your app owns its community rules, its moderation policy and decisions, and its duty to protect members, including the requirements of app stores and the law where you operate. Edict is designed to provide configurable building blocks. It does not moderate your community for you.

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