Gifting & Invitations

How DoCurious users share challenges with each other -- gifting, inviting, recommending, and assigning.

STATUS: BUILT

Store (useGiftStore), types (gift.types.ts), mock API (gift.api.ts), real API stubs (gift.real.api.ts), Gifts page, GiftCard, GiftModal, GiftPermissionSettings, and GiftRedemption page are all implemented. Some spec fields (claiming info, attached materials, fulfillment confirmation prompts) are not yet surfaced in the UI.

Philosophy

DoCurious is a messenger, not a guarantor. When someone gifts a challenge or invites another person to do one, the platform delivers information and facilitates the connection. It does not process payments, hold inventory, verify purchases, or guarantee fulfillment.

Trust flows through personal relationships. A parent buying a challenge kit for their child, a teacher distributing materials to a class, or a friend inviting others to try something together -- all of them rely on their own coordination and their own vendor relationships. DoCurious provides the envelope. The users provide what goes inside.

Core Principles

• Platform as facilitator. DoCurious connects gifters to vendor purchase pages, provides gifting and invitation screens to attach information, and delivers that information to recipients. It does not touch money unless DoCurious itself is the vendor selling the challenge.
• External purchase model. All paid challenges (except those sold by DoCurious) are purchased through the vendor's own website or storefront. DoCurious provides the link but does not process the transaction.
• Gifter/inviter responsibility. The gifter is responsible for purchasing materials, providing accurate claiming information, and ensuring the recipient gets what they need. The inviter is responsible for coordinating details with invitees outside the platform.
• Recipient confirmation. For gifts, recipients confirm whether they have received materials. If not, the platform nudges the gifter -- but does not resolve disputes. For invitations, recipients coordinate directly with the inviter.
• Only paid challenges can be gifted. Free challenges are available to anyone and do not need the gifting flow. Gifting is exclusively for vendor challenges that involve a purchase. Free challenges can be shared/recommended or used in invitations, but they cannot be gifted.

Four Distinct Actions

DoCurious distinguishes between four ways a user can share a challenge with someone else. Each action serves a different purpose and has different rules.

Action	What It Does	Available For	Permissions Required
Gift	Gifter purchases challenge externally, then attaches claiming info, materials, and a message. Recipient receives it in their Invitations tab.	Paid challenges only	Yes
Invite	Inviter proposes doing a challenge together. Includes coordination details (payment approach, timing, who else is invited, contact info). No purchase is involved.	Any challenge (free or paid)	Yes
Share / Recommend	Sends a link to the challenge detail page with an optional personal message. One-time email, no tracking.	Any challenge (free or paid)	No
Assign	A School Admin (or authorized teacher) assigns a challenge to students using the Gift or Invite flow. Not a separate software feature -- it uses the same mechanism with a note in the message text.	School context only, SA-initiated	SA role

Key Differences at a Glance

Feature	Share / Recommend	Invite	Gift
Appears in Invitations tab	No	Yes	Yes
Purchase involved	No	No	Yes
Confirmation / tracking	None	Start notifications	Fulfillment confirmation
Reminder emails	None	Day 7, 21, 30	Day 7, 21, 30
Works for free challenges	Yes	Yes	No
Works for paid challenges	Yes	Yes	Yes
Works for non-users	Yes (signup funnel)	Yes (signup funnel)	Yes (signup funnel)

Individual Gifting Flow

This is the core gifting experience: one user gifting a paid challenge to one or more other users.

Step-by-Step: Gifter Experience

1. Gifter views a paid challenge detail page. They click "Gift This Challenge."

2. Redirected to vendor site. DoCurious opens the vendor's external purchase URL in a new tab or window. The gifter completes the purchase on the vendor's site. DoCurious has zero visibility into this transaction.

3. Gifter returns to DoCurious. After purchasing, the gifter returns to the DoCurious gifting screen. The original tab remains open, or they navigate back via a "Return to complete your gift" prompt.

4. Gifter fills in the gifting screen:

   • Recipient email(s): One or more email addresses. Can be existing DoCurious users or new emails (see Gifting to Non-Users below). Whether a challenge can reasonably be gifted to multiple people depends on context -- the platform does not judge appropriateness. If someone wants to gift a single challenge seat to sixteen people, the remedy is for recipients to block that person from future gifting.
   • Personal message: Optional free-text message, max 500 characters.
   • Claiming information: Freeform text field for codes, reservation numbers, or instructions. Example: "Your kit order number is #XK-4829. Expected delivery: Feb 15."
   • Attached materials: Optional file uploads -- receipts, QR codes, confirmation PDFs, booking screenshots. Up to 5 files, max 10 MB each. The platform stores one copy of submitted info (not per-recipient duplicates). Admins can review and manage gifting messages and materials.

5. Gifter submits. DoCurious sends emails to both the gifter and the recipient(s).

Email to Both Parties

Both the gifter and every recipient receive an email containing:

• Challenge name and description
• Personal message from the gifter
• Claiming information (codes, reservation numbers, etc.)
• Attached materials (as email attachments or secure download links)
• Link to the challenge on DoCurious
• Disclaimer (included in every gift email):

"Unless purchased directly from DoCurious, we will not have access to order details, tracking information, or purchase materials. The information above was provided by the gifter. If you have questions about your order, please contact the gifter or the vendor directly."

Why email to both parties?

• The gifter gets a receipt of what they sent.
• The recipient gets the information even if they have never logged into DoCurious.
• The claiming info is deliberately sent outside the platform so it persists in the recipient's email regardless of their DoCurious account status.

Gifting to Non-Users

If the gifter enters an email address that is not associated with any DoCurious account:

1. The gift email is sent to that address with all claiming information and materials.
2. The email includes a signup invitation: "[Gifter Name] has gifted you a challenge on DoCurious! Create your free account to track your experience and share your progress."
3. A pending gift record is created on the platform, linked to the email address.
4. When the recipient signs up with that email address, the pending gift automatically appears in their Invitations tab.
5. If the recipient never signs up, the gift information still lives in their email. The pending gift record persists on the platform for 1 year.

Fulfillment Confirmation

Before a gifted challenge can move to "In Progress," the recipient must confirm they have what they need. The confirmation prompt varies by fulfillment type:

Fulfillment Type	Confirmation Prompt	If Recipient Answers "No"
Kit	"Have you received your kit?"	Challenge stays in Invitations. Optional nudge sent to gifter.
Hosted	"Have you confirmed your appointment or reservation?"	Same: stays in Invitations, optional gifter nudge.
Digitally Guided	"Do you have access to the materials?"	Same: stays in Invitations, optional gifter nudge.

When the recipient answers "Yes": the challenge moves from Invitations to In Progress, a Track Record is created in draft state, and the gifting flow is complete.

Gift Persistence and Reminders

Gifts persist for 1 year from the date of gifting. If a recipient never confirms receipt, the gift remains in their Invitations tab for the full year. The platform sends periodic reminders:

When	What	Who Receives It
Day 7	"You have a gifted challenge waiting! Have you received your materials?"	Recipient
Day 21	Second reminder email	Recipient
Day 30	"[Recipient] hasn't confirmed receipt of your gift. You may want to check in with them."	Gifter
30 days before expiration	Expiration warning	Recipient
21 days before expiration	Second expiration warning	Recipient
7 days before expiration	Final expiration warning	Recipient
After 1 year	Gift expires and is permanently deleted from Invitations tab	--

Declining a Gift

A recipient can decline a gift. The gifter is not notified. The declined gift is moved to the "Declined" section of the recipient's Invitations page, where it persists for 1 year from the date of gifting. During that window:

• The recipient can un-decline (reverse the decline) at any time.
• The recipient can manually delete the declined gift at any time.
• Expiration warnings are sent 30, 21, and 7 days before automatic deletion.

There is no refund from DoCurious for gifted challenges. If the gifter wants a refund, that is between the gifter and the vendor. If a gifter arranges with the vendor to re-assign the product or service, they can re-gift by starting a new gifting flow on DoCurious.

Claiming info retention: The gifter's sent gifts history retains claiming information until the gifted challenge is either started or declined.

Invitation Flow

Inviting is a coordination tool -- not a commitment mechanism. It lets users propose doing a challenge together with one or more people.

Key Principles

• Coordination, not commitment. Invitations help people coordinate whether, when, and how to do a challenge together. They do not create shared Track Records or binding commitments.
• Individual Track Records. Each person completes their own Track Record. Many entries may be identical since they represent the same shared experience.
• One-way communication. Invitations are sent with coordination details. Further discussion happens outside the platform using the contact information the inviter provides.
• No purchase required. Invitations work for both free and paid challenges. Payment arrangements are coordinated between participants.

Step-by-Step: Inviter Experience

1. Inviter views any challenge detail page (free or paid). Clicks "Invite Others."

2. Invitation screen -- inviter fills in:

   • Invitee email(s): One or more email addresses. Can be existing DoCurious users or new emails.
   • Payment approach (if the challenge costs money), with four options:
     • "This challenge is free!"
     • "I'll pay for everything."
     • "We'll share the cost of everything."
     • "Will you pay for me?"
   • Proposed timing: Free-form text field (e.g., "Next Saturday afternoon," "Sometime in March," "After school gets out").
   • Contact information for coordination: Auto-populated with the inviter's email address (editable). Optional phone number field.
   • Personal message: Optional, max 500 characters.
   • "Who else is invited" is automatically shown: a list of all invitee names/emails based on the recipients entered.

3. Inviter submits. DoCurious sends invitation emails to all invitees and creates invitation records.

Invitation Email

Each invitee receives an email containing:

• Challenge name, description, and cover image
• Inviter's real name (display name)
• Full list of who else is invited (real names / display names)
• Payment approach selected by inviter
• Proposed timing
• Personal message (if included)
• Contact information for coordination (email and phone if provided)
• Link to the challenge on DoCurious
• Call-to-action button: "View Challenge Details"
• Disclaimer (included in every invitation email):

"This is an invitation to coordinate doing a challenge together. DoCurious does not manage scheduling, payments, or commitments between users."

Invitee Experience

Invitations appear in the invitee's Invitations tab under My Challenges. Each invitation card shows:

• Challenge title and cover image
• Inviter's display name
• Payment approach
• Proposed timing
• Who else is invited
• Personal message
• Contact information (email / phone)
• Date received
• Action buttons: "Start Challenge" | "Decline"

Starting the challenge: clicking "Start Challenge" moves the challenge from Invitations to In Progress and creates a Track Record in draft state. The inviter is notified via daily digest.

Declining an invitation: clicking "Decline" moves the invitation to the "Declined" section of the Invitations tab. The inviter is NOT notified. Declined invitations persist for 90 days, after which they auto-delete. The invitee can un-decline at any time during that window, or manually delete at any time.

Inviting Non-Users

If the inviter enters an email not associated with a DoCurious account:

1. The invitation email is sent with all coordination details.
2. The email includes a signup invitation: "[Inviter Name] has invited you to do a challenge together on DoCurious! Create your free account to see the full details and track your experience."
3. A pending invitation record is created, linked to the email.
4. When the recipient signs up with that email, the invitation automatically appears in their Invitations tab.
5. The pending record persists on the platform for 1 year.

Invitation Reminders and Expiration

Reminder schedule (from date sent):

• Day 7: "You have a challenge invitation waiting! [Inviter] invited you to [Challenge Name]."
• Day 21: Second reminder.
• Day 30: Third reminder.

Expiration warnings (before the 1-year mark):

• 30 days before expiration
• 21 days before expiration
• 7 days before expiration

After 1 year: unclaimed invitations are automatically deleted. No notification is sent to the inviter.

Sent Invitations View

The inviter can see their sent invitations in a "Sent Invitations" section within the Invitations tab.

• Grouped by invitation batch. Each card shows a summary: "You invited 5 people to Build a Wooden Boat on Jan 15, 2026."
• Expandable details: Click to see the full list of invitee names, payment approach, timing, personal message, and contact info.
• No status tracking. The inviter cannot see whether invitees have started or declined. Coordination happens through contact methods provided, or by checking public Track Records.
• Start notifications. When invitees start the challenge, the inviter receives a daily digest: "3 people started the [Challenge Name] challenge you invited them to: [Name 1], [Name 2], [Name 3]."

Duplicate Prevention

Users cannot send duplicate invitations to the same person for the same challenge while a previous invitation is still active (pending, not declined, not started).

If attempted, the system blocks it and shows: "You already invited [Name] to this challenge on [Date]. They can still accept that invitation."

A new invitation can be sent once the invitee starts, declines, or the invitation expires.

Sharing / Recommending

Sharing is the lightweight alternative -- no purchase, no coordination, no material transfer. Just a link.

How It Works

1. User views any challenge (free or paid) and clicks "Share/Recommend."
2. Enters the recipient's email address and an optional personal message (max 500 characters).
3. Recipient receives an email with a challenge preview (title, image, description) and the personal message.
4. Email includes a link to the challenge detail page.

Recipient Experience

• Existing DoCurious user: Clicking the link goes to the challenge detail page. They can start it (free), purchase it (paid), or save it to Interesting or Bucket List.
• Non-user: Clicking the link shows a public preview of the challenge: cover image, title, description, category badges, difficulty, duration, age range, and cost. All interactive actions prompt the signup flow. The recommendation serves as a signup funnel.

Recommendations are NOT tracked in the recipient's Invitations tab. They are a one-time email only. The recipient has no obligation to act.

Gift & Invitation Permissions

Not everyone can gift or invite everyone. Permissions prevent unwanted gifts and invitations from strangers while preserving these features for family and trusted relationships.

Gifting and invitation permissions use the same system. If a user can gift to someone, they can also invite them.

Community-Based Defaults

Each community type has a default gifting/invitation permission:

Community Type	Default	Rationale
Family	Yes	Families naturally gift and coordinate together. Low risk.
Trusted Friends	Yes	Close friends selected deliberately. Similar trust level.
Casual Friends	No	Broader circle. Could feel presumptuous or create social pressure.
Interest / Hobby	No	Members may not know each other personally.
Other / General	No	Mixed context. Err on the side of privacy.
Institutional (School)	Yes	SA gifts/invites to students as part of curriculum. Teachers cannot purchase unless explicitly granted purchasing privileges.

Individual Overrides

Any user can override the community default:

• If default is Yes: User can turn gifting/inviting OFF for specific members ("I don't want [Person] to gift or invite me").
• If default is No: User can turn gifting/inviting ON for specific members ("I want [Person] to be able to gift and invite me even though our community default is No").

Where to configure: Account Settings > Gifting & Invitation Permissions. Shows all communities with toggles and per-member overrides.

Permission Requests

If a user wants to gift or invite someone who has not granted them permission:

1. User clicks "Gift This Challenge" or "Invite Others" and enters the recipient's email.
2. System checks permissions. If not permitted, user sees: "[Recipient] hasn't enabled gifting and invitations from you. Would you like to send a request?"
3. User sends a permission request (includes their name and the challenge).
4. Recipient receives an in-app notification: "[User] would like to gift and invite you to challenges. Allow gifting and invitations from this person?"
5. Recipient approves or denies. Approval is permanent -- not per-gift or per-invitation.
6. If approved, the user is notified and can proceed.

Under-13 Rules (Tier 1 Exclusion)

• Tier 1 (school-only under-13): Can only receive gifts and invitations from school (SA-initiated). Cannot receive personal gifts or invitations. This is a hard restriction.
• Tier 2 (parent-linked under-13): Can receive personal gifts and invitations subject to community permissions. Parents can view all gifts and invitations in the child's Invitations tab.
• Parent override: Parents of under-13 users can decline any gift or invitation on the child's behalf from the parent account, even if the child has already confirmed receipt (reverting the challenge back to the invitation state).

See Accounts for details on the two-tier under-13 account model.

School Bulk Gifting & Invitations

School gifting and invitations are specialized flows where a School Admin (SA) purchases challenge materials in bulk or coordinates group challenges. The flows are the same as individual gifting/inviting, but the interface makes it easy to select entire communities and groups.

SA Gifting Workflow

1. SA selects a paid challenge from the catalog or Explore page.
2. Clicks "Gift This Challenge" -- opens the school gifting screen (distinct from individual gifting).
3. Selects recipients from:
   • Entire school
   • Specific grades
   • Specific classes
   • Individual students and teachers
4. Enters quantity -- number of kits/spots/licenses purchased. System validates against recipient count.
5. Uploads receipt -- required. Proof of purchase (PDF, image) for school recordkeeping and DoCurious revenue-sharing tracking. DoCurious admins can access this.
6. Enters claiming information -- bulk info (e.g., "Kits will be distributed in homeroom on Monday") or per-student codes.
7. Attaches materials -- optional, same limits as individual gifting (5 files, 10 MB each).
8. Previews and confirms -- summary shows challenge name, recipient count, total cost, receipt attached.
9. Gifts distributed -- each selected student receives the challenge in their Invitations tab with the appropriate fulfillment confirmation prompt.

SA Invitation Workflow

1. SA selects any challenge (free or paid).
2. Clicks "Invite Others" -- opens the school invitation screen.
3. Selects recipients (same options as gifting: school, grades, classes, individuals).
4. Fills in invitation details: payment approach, proposed timing, contact info, personal message (can include assignment instructions, deadlines, grading criteria).
5. Previews and confirms.
6. Invitations distributed to each selected student.

Teacher Role

Teachers cannot purchase challenges or initiate school gifts unless specifically given purchasing privileges by the SA. If a teacher wants challenges for their class:

1. Teacher identifies the desired challenge.
2. Teacher submits a "Request Challenge for Class" through the platform.
3. SA reviews the request (challenge details, estimated cost).
4. SA approves and purchases, then uses the school gifting workflow.
5. Teacher is notified when the gift is distributed.

If the teacher has been assigned a role with purchasing privileges, they act as an SA for gifting purposes.

For invitations: Teachers with appropriate privileges can invite students to challenges directly without SA approval, since no purchase is involved.

Rationale: Centralizing purchasing authority with the SA ensures budget control and prevents fragmented spending. In small schools, teachers may also fulfill admin functions, so the system supports multiple admin-privilege levels.

School Gift & Invitation Tracking

The SA dashboard includes a Gift & Invitation History section:

• Challenge name and date gifted/invited
• Recipient group (school / grade / class / individuals)
• For gifts: quantity, total cost, uploaded receipt
• Confirmation status: how many students have confirmed receipt (gifts) or started (invitations)

This is purely recordkeeping. DoCurious does not provide budget management, purchase orders, or financial reporting.

Roles & Permissions Summary

Role	Can Gift	Can Invite	Can Receive Gifts	Can Receive Invitations	Special Rules
General User	Yes (paid challenges)	Yes (any challenge)	Yes (per permissions)	Yes (per permissions)	--
Student (Tier 1)	No	No	School-only (SA-initiated)	School-only (SA-initiated)	Cannot receive personal gifts/invitations
Student (Tier 2)	Yes	Yes	Yes (parent can view/override)	Yes (parent can view/override)	Parent can decline on child's behalf
Parent	Yes	Yes	Yes	Yes	Can manage child's gifts/invitations
Teacher	Only if granted SA purchasing privilege	Yes (to own students, if privileged)	Yes	Yes	Must request SA for class purchases
School Admin (SA)	Yes (bulk school gifting)	Yes (bulk school invitations)	Yes	Yes	Full school recipient selection UI
Vendor	No	No	No	No	Vendors do not participate in gifting
Platform Admin	Yes	Yes	Yes	Yes	Can review gifting messages/materials

Notification Schedule

Gift Notifications

Event	Who	Channel	When
Gift sent (confirmation)	Gifter	Email	Immediate
Gift received	Recipient	Email + In-app	Immediate
Gift reminder (Day 7)	Recipient	Email	7 days
Gift reminder (Day 21)	Recipient	Email	21 days
Gifter nudge (Day 30)	Gifter	Email	30 days
Gift expiration warnings	Recipient	Email	30, 21, 7 days before
Recipient confirms receipt	Gifter	In-app	Immediate
Recipient declines	Nobody	--	Gifter is not informed

Invitation Notifications

Event	Who	Channel	When
Invitation sent (confirmation)	Inviter	Email	Immediate
Invitation received	Invitee	Email + In-app	Immediate
Invitation reminder (Day 7)	Invitee	Email	7 days
Invitation reminder (Day 21)	Invitee	Email	21 days
Invitation reminder (Day 30)	Invitee	Email	30 days
Invitation expiration warnings	Invitee	Email	30, 21, 7 days before
Invitee starts challenge	Inviter	Email + In-app (daily digest)	End of day (batched)

Permission & School Notifications

Event	Who	Channel	When
Permission request	Target user	In-app	Immediate
Permission approved	Requester	In-app	Immediate
Recommendation sent	Recipient	Email only	Immediate
Teacher challenge request	SA	In-app + Email	Immediate
Challenge request fulfilled	Teacher	In-app	On distribution
School gift distributed	Each student	In-app	Immediate
School invitation distributed	Each student	In-app	Immediate

Design Decisions

Why the external purchase model?

DoCurious is a discovery and documentation platform, not a retailer. Handling payments would require PCI compliance, payment processing infrastructure, refund management, and vendor payout systems. By directing users to the vendor's own purchase page, DoCurious avoids all of that complexity. The platform only touches money for challenges that DoCurious itself sells in its capacity as a vendor.

Why email to both parties?

The gifter needs a receipt for their records. The recipient needs the claiming information even if they have never used DoCurious. Sending the information via email ensures it persists outside the platform -- if the recipient never creates an account, they still have the order numbers, codes, and materials they need.

Why not verify purchases?

DoCurious has no integration with vendor payment systems. It cannot confirm whether a purchase was completed, whether a kit was shipped, or whether a reservation was made. Attempting to verify would create false confidence. Instead, the platform is transparent: the disclaimer in every gift email makes it clear that claiming information was provided by the gifter, not by DoCurious.

Why 1-year persistence for pending gifts?

Challenge kits might take time to arrive. Hosted experiences might be scheduled months in advance. A short expiration window could cause gifts to disappear before the recipient has a chance to use them. One year gives enough breathing room for any reasonable fulfillment timeline.

Why community-based permission defaults?

Blanket "anyone can gift anyone" creates spam and social-pressure risks. Blanket "nobody can gift" kills the feature. Community-based defaults strike the right balance: close relationships (family, trusted friends) default to open, while broader circles (interest groups, casual friends) default to closed. Individual overrides let users fine-tune from there.

Constraints & Edge Cases

• Cannot gift to yourself. The system blocks self-gifting.
• Cannot gift free challenges. Free challenges are available to everyone; there is nothing to gift.
• Duplicate invitation prevention. Cannot send the same invitation to the same person while a previous one is active.
• Declined gifts can be un-declined for up to 1 year. Declined invitations can be un-declined for up to 90 days.
• No refunds from DoCurious. Refund disputes are between the gifter and the vendor.
• Attached materials: Max 5 files, max 10 MB each. One copy stored (not per-recipient). Admin-reviewable.
• Personal messages: Max 500 characters for gifts, invitations, and recommendations.
• Gift expiration in code vs. spec: The spec says 1 year. The mock API currently calculates 1 year correctly (365 * 24 * 60 * 60 * 1000). The features audit flagged a previous 30-day value that has been corrected.

Implementation Details

Frontend Files

Layer	File	Description
Types	src/types/gift.types.ts	Gift, GiftStatus, GiftPermission, GiftPermissionType, GiftRequest, GiftRecipientSearchResult
Store	src/store/useGiftStore.ts	Zustand store with sent/received/pending gifts, permissions, recipient search
Mock API	src/api/gift.api.ts	Full mock implementation with permission checking, expiration, CRUD
Real API	src/api/gift.real.api.ts	Backend-connected for core CRUD; stubs for cancel, permissions, search
Page	src/pages/gifts/Gifts.tsx	Tabbed view: Pending, Sent, Received, Settings
Page	src/pages/challenges/GiftRedemption.tsx	Code-based gift redemption flow with confetti celebration
Component	src/components/gift/GiftCard.tsx	Gift display card with status badge, actions, expiry warning
Component	src/components/gift/GiftModal.tsx	3-step modal: select recipient > add message > confirm and send
Component	src/components/gift/GiftPermissionSettings.tsx	Permission type selector with allow/block user lists

Gift Status Lifecycle

pending --> accepted    (recipient confirms fulfillment)
pending --> declined    (recipient declines)
pending --> expired     (1 year passes without action)
pending --> cancelled   (gifter cancels before recipient acts)

What the Real API Covers vs. Stubs

Endpoint	Real API	Stubbed
Get sent gifts	GET /gifts?type=sent	--
Get received gifts	GET /gifts?type=received	--
Get pending gifts	GET /gifts?status=pending	--
Send gift	POST /gifts	--
Accept gift	POST /gifts/:id/accept	--
Decline gift	POST /gifts/:id/decline	--
Cancel gift	--	Stubbed (no backend route)
Get permissions	--	Stubbed (no backend route)
Update permissions	--	Stubbed (no backend route)
Search recipients	--	Stubbed (no backend route)

Cross-References

• Challenge System -- Challenges are what get gifted, invited, and shared. Gifting creates a Track Record in draft state.
• School Administration -- SA bulk gifting workflow, teacher challenge requests, school gift tracking.
• Communities -- Community types define default gifting/invitation permissions. Six types with different trust levels.
• Accounts -- Under-13 two-tier model (Tier 1 school-only vs. Tier 2 parent-linked) governs who can receive personal gifts.