Care Feed

Part of the Anaya Care Handbook — the source of truth for how the product must behave. When the product needs to change, change this document first, then make the system match it.

What this covers

This page governs each agency's private Care Feed: posts with photos and videos, comments and replies, likes, bookmarks, and the automatic birthday celebrations the system creates each morning. The feed keeps an agency's community engaged; it is never visible outside the agency.

Key terms

• Post — a message on an agency's private Care Feed, optionally with photos, videos, hashtags, and mentions.
• Comment / reply — a response to a post; a reply is a response to a comment (one level deep only).
• Bookmark — a personal "save for later" mark on a post, visible only to the person who saved it.
• Birthday celebration post — an automatic feed post the system creates on a member's birthday.
• In-app camera — the only allowed source for Care Feed photos; pictures must be taken inside the Anaya app, and camera-roll uploads are not permitted.
• Face-photo opt-in — a per-client permission, granted by the client's representative, without which a photo showing a client's face cannot be posted.

How it works

Every agency has its own private feed. Members post updates with text, photos, or videos; others like, comment, reply, and bookmark. Posts go live immediately — there is no draft or approval step. Mentioning a member notifies them; liking or commenting notifies the relevant author (see Communication). Each morning the system also celebrates birthdays: it creates one celebration post per birthday member, shown under that member's own name with a friendly greeting, and notifies everyone in the agency.

Rules

1. FEED-1 — Each agency's feed is private to that agency. Posts, comments, likes, and bookmarks must never be visible to another agency.
2. FEED-2 — Any signed-in member of an agency can post to its feed. Posts appear immediately; there is no draft, approval, or scheduling step.
3. FEED-3 — A post can include text, image and video attachments, hashtags, and mentions. Every mentioned member must be notified.
4. FEED-4 — Only the author of a post or comment can edit or delete it.
5. FEED-5 — Deleting a post or comment hides it from everyone; it is never destroyed outright and can be recovered by the platform team.
6. FEED-6 — Comments allow exactly one level of replies: a reply can never have replies of its own. A single comment can hold at most 500 replies.
7. FEED-7 — A person can like a given post or comment only once (liking is an on/off toggle), and can bookmark a given post only once. Bookmarks are personal and apply to posts only.
8. FEED-8 — Liking a post notifies the post's author; commenting on a post notifies the post's author; replying to a comment notifies that comment's author.
9. FEED-9 — Every day the system creates exactly one birthday celebration post per member whose birthday falls on that day — never more than one per person per day.
10. FEED-10 — A birthday post appears under the celebrant's own name with a friendly pre-written greeting, and every active member of the same agency receives a birthday notification linking to it.
11. FEED-11 — A member born on February 29 is celebrated on February 28 in non-leap years.
12. FEED-12 — Members not attached to an agency never receive birthday posts or birthday notifications.
13. FEED-13 — A member who turns off "show my birthday in the feed" must not get a birthday post, and no one must be notified of their birthday.
14. FEED-14 — A member's birthday must be detected using their own local date, so everyone is celebrated on the right day wherever they live.
15. FEED-15 — Care Feed photos can only be captured with the in-app camera; camera-roll uploads are blocked and the user is directed to the in-app camera. (✅ In code — mobile is camera-only for every role and stamps a capture source; web uploads are stamped web_upload, exempt as it has no native camera)
16. FEED-16 — No user can download a Care Feed photo. (✅ In code — best-effort: web disables right-click/drag/save + controlsList="nodownload"; mobile viewers expose no save/share)
17. FEED-17 — A photo showing a client's face is blocked by default and can be posted only when that client's representative has opted in to face photos for that client; a face photo posted without the opt-in is blocked and the care provider is notified. (✅ In code — server-side AWS Rekognition gate on client-linked posts; per-client facePhotoOptIn granted by the representative or a care manager; blocked posts return FACE_PHOTO_CONSENT_REQUIRED and notify the author)
18. FEED-18 — A client-linked post is visible only to that client's assigned care team and the client's authorized representatives — a narrower audience than the agency-wide default in FEED-1 and FEED-2. (✅ In code — feed/detail/comments/bookmarks scoped by the requester's active care-team + representative links; managers with posts:view:all see all)
19. FEED-19 — A client's authorized representatives can react to that client's linked posts from within the app. (✅ In code — representatives have feed access, audience-scoped; like/comment/bookmark gated to posts they can see)
20. FEED-20 — A representative-flagged client-linked post is hidden pending review and the care manager is notified immediately; a Care Feed photo that fails to upload notifies the care provider and retries automatically. (✅ In code — flag → hidden-pending-review + manager notification; care-manager review queue restores/removes; mobile uploads retry with backoff then notify)

Note: This page's rules were retired from the Content & Community page: CONTENT-1 – CONTENT-14 → FEED-1 – FEED-14. IDs are never reused.

Who can do what

Decisions needed

• Feed access control — should posting and interacting on the feed stay open to everyone in the agency, or be governed by permission settings? Options: keep it open for all members; enforce per-role feed permissions.
• Feed moderation — beyond the representative-flag review flow that Developer Reference v4.2 reports as built, should admins also be able to flag, review, and remove other members' (non-client-linked) posts? Options: extend flagging and moderator removal to all posts; keep general posts author-managed.
• Client-linked post visibility (FEED-18 vs FEED-1/FEED-2) — Resolved: only posts explicitly linked to a client narrow to that client's care team + representatives; general staff posts stay agency-wide (FEED-1/FEED-2 preserved). Now in code.